You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running pytest --looponfail --junitxml=report.xml tests/ results in the following:
Runs the tests
Generates the test report file
File watcher says # MODIFIED path/to/report.xml
Runs the tests
Generates a new test report file...
I can invoke it without the report, that's fine, but it's annoying because I have the report argument in my tox.ini, so using tox -- --looponfail shows this behavior.
Given that the junitxml argument knows the file path, it seems like a potential solution here is to explicitly skip changes to that file.
It's likely there's a similar issue for html reports and coverage.
The text was updated successfully, but these errors were encountered:
RonnyPfannschmidt
changed the title
--looponfail runs tests forever when using --junitxml
--looponfail consider junitxml output a change
Sep 15, 2016
The same issue occurs when pytest-cov or coverage is used to generate an HTML coverage report.
I think the best fix would indeed be a command line parameter to ignore a glob of files.
Running
pytest --looponfail --junitxml=report.xml tests/
results in the following:# MODIFIED path/to/report.xml
I can invoke it without the report, that's fine, but it's annoying because I have the report argument in my tox.ini, so using
tox -- --looponfail
shows this behavior.Given that the
junitxml
argument knows the file path, it seems like a potential solution here is to explicitly skip changes to that file.It's likely there's a similar issue for html reports and coverage.
The text was updated successfully, but these errors were encountered: