-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
xUnit Plugin 2.2.5
-
-
2.3.2
When NUnit Tests are run with a [SetupFixture] class, the results XML file is structured a bit differently.
Normally it looks like:
<test-suite type="TestSuite" ...> <test-suite type="TestFixture ...>...</test-suite> </test-suite>
but with [SetupFixture] in the mix, it looks like:
<test-suite type="TestSuite" ...> <test-suite type="SetUpFixture ...> <test-suite type="TestFixture ...>...</test-suite> </test-suite> </test-suite>
Since the xsl file looks for (as far as I can tell) @type=TestFixture directly under @Type=TestSuite, it misses anything with @type=SetUpFixture in between. Taken from nunit-3.0-to-junit.xsl, line 60,61:
<xsl:for-each select="//test-suite[@type='TestSuite']"> <xsl:for-each select="test-suite[@type='TestFixture']">
To reproduce it, create a TestAssembly with a SetupFixtureAttribute
- is related to
-
JENKINS-56271 xUnit produce an empty report for NUnit3 type
-
- Resolved
-
[JENKINS-55907] NUnit3 fails when SetUpFixture feature is used
Attachment | New: AGT-CHC-BLD191-Results.xml [ 45898 ] |
Summary | Original: NUnit3 Tests missing after XSL Transformation | New: NUnit3 fails when SetupFixture feature is used |
Summary | Original: NUnit3 fails when SetupFixture feature is used | New: NUnit3 fails when SetUpFixture feature is used |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Fixed but Unreleased [ 10203 ] |
Link |
New:
This issue is related to |
Released As | New: 2.3.2 | |
Status | Original: Fixed but Unreleased [ 10203 ] | New: Resolved [ 5 ] |