[SUREFIRE-2298] fix xml output with junit 5 nested classes (fix integration with Cucumber and Archunit) by olamy · Pull Request #828 · apache/maven-surefire (original) (raw)
added the bug
Something isn't working
label
olamy mentioned this pull request
8 tasks
olamy marked this pull request as draft
Signed-off-by: Olivier Lamy olamy@apache.org
Signed-off-by: Olivier Lamy olamy@apache.org
Signed-off-by: Olivier Lamy olamy@apache.org
…arallel is enabled
Signed-off-by: Olivier Lamy olamy@apache.org
Signed-off-by: Olivier Lamy olamy@apache.org
Signed-off-by: Olivier Lamy olamy@apache.org
Signed-off-by: Olivier Lamy olamy@apache.org
Signed-off-by: Olivier Lamy olamy@apache.org
Signed-off-by: Olivier Lamy olamy@apache.org
Signed-off-by: Olivier Lamy olamy@apache.org
Signed-off-by: Olivier Lamy olamy@apache.org
This was linked to issues
Sep 4, 2025
olamy mentioned this pull request
olamy linked an issue
that may beclosed by this pull request
Signed-off-by: Olivier Lamy olamy@apache.org
Signed-off-by: Olivier Lamy olamy@apache.org
olamy deleted the SUREFIRE-2298-nested-classes branch
olamy changed the title
[SUREFIRE-2298] fix xml output with junit 5 nested classes [SUREFIRE-2298] fix xml output with junit 5 nested classes (fix integration with Cucumber and Archunit)
mpkorstanje added a commit to cucumber/cucumber-jvm that referenced this pull request
With Surefire 3.5.4 the heuristic for naming tests changed[1]. As a
result the surefire strategy no longer works as expected. But the
long strategy now does provide reasonable results.
On Surefire <= 3.5.2 with the surefire strategy the test results would
be rendered as:
<testcase name="a few cukes" classname="Belly" time="0.062">On Surefire >= 3.5.4 with the long strategy the test results will
be rendered as:
<testcase name="Belly - a few cukes" classname="RunCucumberTest" time="0.06">
mpkorstanje added a commit to cucumber/cucumber-jvm that referenced this pull request
With Surefire 3.5.4 the heuristic for naming tests changed[1]. As a
result the surefire strategy no longer works as expected. But the
long strategy now does provide reasonable results.
On Surefire <= 3.5.2 with the surefire strategy the test results would
be rendered as:
<testcase name="a few cukes" classname="Belly" time="0.062">This includes both the scenario and feature name.
On Surefire >= 3.5.4 with the surefire strategy the test results will
be rendered as:
<testcase name="a few cukes" classname="RunCucumberTest" time="0.06">This does not include the feature name.
On Surefire >= 3.5.4 with the long strategy the test results will be
rendered as:
<testcase name="Belly - a few cukes" classname="RunCucumberTest" time="0.06">This does the scenario and feature name and also the name of the Suite that ran Cucumber. This is the optimal outcome.
Closes: #2984
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})