Fixie v2.2.0 Release NotesRelease Date: 2019-10-05 // 10 days ago
📚 When running under Azure DevOps, if you have configured your Pipeline to allow access to the Azure DevOps test reporting API, Fixie will report each test result so that they will appear on the build's "Tests" screen. If you forget that configuration, the console output will provide guidance based on the Azure DevOps documentation (https://docs.microsoft.com/en-us/azure/devops/pipelines/build/variables#systemaccesstoken)
Previous changes from v2.1.1
✅ When running tests in Visual Studio under Test Explorer:
- 👌 Improved error reporting, both in the Output pane and in the tree of test results, to help with troubleshooting.
- 👌 Improved performance when selecting a large number of individual tests to run in Test Explorer. Previously, we performed an excessive amount of reflection and redundant evaluation of which test classes and test methods need to be executed.
- ↔ Integrate with Test Explorer's test progress icons, so that the user can identify long-running tests.
- ✅ Graceful handling of catastrophic failures such as tests which perform Environment.Exit(...) or which throw StackOverflowException. Naturally such catastrophic errors force the test run to end early, and that is out of our control, but now we accurately report what happened in both the Test Explorer tree and in the 'Tests' Output pane.