| << Back to previous view |
|
[QB-2279] "Publish NUnit Report" treats Inconclusive results as Failures
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 5.1.40 |
| Fix Version/s: | 6.0.4 |
| Type: | Bug | Priority: | Major |
| Reporter: | Daniel Yankowsky | Assigned To: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
NUnit tests, in addition to succeeding or failing, can result in an "inconclusive" result. The current NUnitTestProcessor doesn't correctly handle that case; it marks these tests as failures. Given that the only choices for Status are PASS, FAIL, and SKIP, inconclusive results should instead be counted as SKIP.
Here's an example of inconclusive output: <test-case name="NUnit.Tests.Assemblies.MockTestFixture.InconclusiveTest" executed="True" result="Inconclusive" success="False" time="0.001" asserts="0"> <reason> <message><![CDATA[No valid data]]></message> </reason> </test-case> The two important parts are that the test was "executed=True" and "success=False". Looking at NUnitTestProcessor, it looks like the particular code path that we're going down doesn't look at the "result" attribute. An executed but unsuccessful test is always marked as FAIL. These results are from NUnit 2.x-style output. |