![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
redsolo
|
|
Attachments:
|
ASI.SOP.AmazonBTI.Tests.xml, junitResult.xml, TestResultLevel1.jpg, TestResultLevel2.jpg, TestResultLevel3.jpg |
|
Components:
|
junit, nunit |
|
Created:
|
26/Feb/13 7:56 PM
|
|
Description:
|
In the conversion of the NUnit XML results to JUnit, some tests are named incorrectly. When an NUnit output file contains a test-suite of type "TestFixture" containing a results element containing both test-suites of type "ParameterizedTest" and test-cases (not parameterized), the test-cases are reported with incorrect namespace and class names. It is as if some code were determining the namespace/class names to report by walking a certain number of tokens back in a fully qualified class name, and too many steps back are being taken for simple tests when parameterized tests are present.
In TestResultLevel1.jpg all tests should appear under pacakge ASI.SOP.AmazonBTI.Tests. TestResultLevel3.jpg shows the badly parsed name AmazonUpcParseStrategyTests.ShouldRequireProductProgramFinder.
|
|
Environment:
|
Windows Server 2003, Jenkins 1.497, Jenkins NUnit plugin 0.14, NUnit 2.6.2
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
David Odren
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
