[ https://issues.apache.org/jira/browse/SUREFIRE-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445805#comment-17445805 ]
Thierry Ygé commented on SUREFIRE-1373: --------------------------------------- +1 I was also reading the same as [~sebastiankirsch] , and thought that @NotThreadSafe annotated classes would at the end sequentially. Would be great to solve it indeed. > Tests annotated with @NotThreadSafe are not executed in isolation > ----------------------------------------------------------------- > > Key: SUREFIRE-1373 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1373 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin > Affects Versions: 2.20 > Reporter: Sebastian Kirsch > Assignee: Tibor Digana > Priority: Major > Fix For: Backlog > > Original Estimate: 48h > Remaining Estimate: 48h > > The [surefire > documentation|http://maven.apache.org/components/surefire/maven-failsafe-plugin/examples/fork-options-and-parallel-execution.html] > states that > bq. you can apply the JCIP annotation @net.jcip.annotations.NotThreadSafe on > the Java class of JUnit test (pure test class, Suite, Parameterized, etc.) in > order to execute it in single Thread instance. The Thread has name > maven-surefire-plugin@NotThreadSafe and it is executed at the end of the test > run. > However, the thread is run in parallel to the other tests being executed, > which contradicts the documentation and defeats the purpose of running tests > sequentially in a single thread. > See https://github.com/sebastiankirsch/surefire-nonthreadsafe for a test case. -- This message was sent by Atlassian Jira (v8.20.1#820001)