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
When using the new @autoretry functionality in combination with the JSON formatter, the JSON output contains multiple tests, one for each run regardless of the final result. This is different from the JUnit output which only contains the final run (pass or fail). You can see a demonstration of this in the sample code here. Simply run tox:
Whereas the JSON output (reports/report_behave.json) contains 5 items under elements:
... "name": "I have a test that fails three times" ...
... "name": "I have a test that fails three times" ...
... "name": "I have a test that fails three times" ...
... "name": "I have a test that fails twice before passing" ...
... "name": "I have a test that fails twice before passing" ...
Is this the expected behavior? Is there some way to configure the JSON formatter? I suspect this is because the JSON output is a formatter (as opposed to the JUnit report).
The text was updated successfully, but these errors were encountered:
The @autoretry mechanism is a convenience hack. The JSON formatter shows you what gets really executed while the JUnit XML output only contains the compressed summary which scenarios are run and with which result.
When using the new @autoretry functionality in combination with the JSON formatter, the JSON output contains multiple tests, one for each run regardless of the final result. This is different from the JUnit output which only contains the final run (pass or fail). You can see a demonstration of this in the sample code here. Simply run
tox
:You can see the XML output (reports/TESTS-test.xml) starts with:
Whereas the JSON output (reports/report_behave.json) contains 5 items under
elements
:Is this the expected behavior? Is there some way to configure the JSON formatter? I suspect this is because the JSON output is a formatter (as opposed to the JUnit report).
The text was updated successfully, but these errors were encountered: