On Mon, 1 Aug 2022 at 11:31, Luff, Chris <[email protected]> wrote: > Following up on a tweet[1] conversation about the interactions of the > NetBeans UI and JUnit Jupiter. I created an example project[2]. The takeaway > is that, if the junit-jupiter-engine is not on the class path the UI controls > for running focused test methods do nothing and report a misconfigured > Surefire or Junit4.
Thanks. The error message and POM change could definitely be more helpful there, but I still think the project is probably misconfigured. The check is at https://github.com/apache/netbeans/blob/master/java/maven/src/org/netbeans/modules/maven/ActionProviderImpl.java#L224 and the error message is in that file too. Try with mvn --debug. While the test runs on the CLI, it seems to pick up JUnit 3? More to the point, without adding the junit-jupiter-engine dependency, single test method selection on the CLI doesn't work either as far as I can see - try adding a second test method that throws an assertion error and using -Dtest=... to select the method. Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
