[
https://issues.apache.org/jira/browse/SUREFIRE-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17134920#comment-17134920
]
Vincent Massol commented on SUREFIRE-1633:
------------------------------------------
bq. Strange to use nested classes.
There are use cases. I our case, it's to run scenarios for functional selenium
tests. We use also `@Order`. This allows sharing the fixture between all tests
and to organize them cleanly by topics instead of mixing everything at the same
level.
bq Vincent Massol, according to your last execution, it seems that now it's
running correctly. So try to run the "testXXX" with
[~silramos] I've tried {{mvn -Dit.test=*NestedWikiTemplateIT* clean verify}}
and it doesn't work:
{noformat}
[INFO] --- maven-failsafe-plugin:2.22.2:integration-test (functional-tests) @
xwiki-platform-wiki-test-docker ---
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
{noformat}
Same results with {{mvn -Dit.test=*AllIT* clean verify}}.
Thanks
> [JUnit5 follow-up #1343] JUnit Jupiter @Nested tests do not run when
> selecting enclosing class with Surefire
> ------------------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-1633
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1633
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support
> Reporter: Christian Stein
> Priority: Major
> Fix For: Backlog
>
>
> https://github.com/junit-team/junit5/issues/1343
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
