Closed Codym48 closed 2 years ago
Only NUnit now.
The legacy JUnit export was out of convenience.
The NUnit format is much better supported in Azure Pipelines, so you'll get tracebacks, you can add attachments, all sorts.
Understood. So pytest-azurepipelines 1.0.x is NUnit only, Python 3 only, and pytest >= 5 only, while 0.8.0 still supported JUnit, Python 2.7, and pytest 4 (but not 7.1)
Yes, Pytest dropped support for Python 2.7 in 5.x so Pytest 5> means Python 3.6+ too.
You can pin an old version of this package if you need to test Python 2.7 and an old Pytest version.
Understood. Thank you for creating and maintaining this plugin!
After upgrading to pytest-azurepipelines 1.0.3, when I call
pytests --junit-xml=test-output.xml
as part of the pipeline, I get a JUnit format output file overwriting an NUnit format output file, and the pytest-azuredevops plugin fails when trying to publish the JUnit XML file because it treats it as an NUnit file (#vso[results.publish type=NUnit;]
)I notice this in the 1.0.0a1 release notes,
Is the intent to only support NUnit, not JUnit? If so, feel free to close the issue.