TeamCity reporter shows skipped tests as passed instead of ignored
See original GitHub issuePlease change the TeamCity reporter to report skipped tests as being ignored and not passed.
Here is the scenario I use: I begin with a test that installs a full web site and if it fails I set:
canopy.configuration.skipAllTestsOnFailure <- true
so that all subsequent tests are ignored and bypassed. But TeamCity shows something like this:
Tests failed: 1, passed: 99
which is misleading. The right thing to show is something like this:
Tests failed: 1, ignored: 99
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
How to show messages with reason for skipped tests in ...
1 Answer. If you would really like to ignore some tests then you should go for @Ignore Junit annotation. Reason could also be...
Read more >Reason of skipped/Ignored tests on overview tab
On the overview tab, on expanding an ignored/skipped test, I want to show the reason of skipping a test. here is how my...
Read more >JUnit test result showing as ignored in TeamCity
I've created XML report build feature with the Ant JUnit report in TC 9.0.1 and your example .xml. The result is: "Tests passed:...
Read more >mocha-teamcity-reporter - npm package
Learn more about mocha-teamcity-reporter: package health score, ... Display skip tests as ignored ... Show diff between expected and actual values.
Read more >Allure Framework
Allure Framework is a flexible lightweight multi-language test report tool that not only shows a very concise representation of what have ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It is working properly now. Thank you.
This is fixed in the latest version of canopy that you can download here: https://www.nuget.org/packages/canopy/1.2.0