Regarding the Gradle plugin: What we currently have works for basic use cases but we’d rather get official support into Gradle core. Please see https://github.com/gradle/gradle/issues/1037 for details.
Thanks, Marc On 17. May 2017, 19:51 +0200, Attila Kelemen <[email protected]>, wrote: > Hi, > > I'm the developer of the Gradle integration of NB, so I can speak for that > part. > > For running tests, I just execute the appropriate Gradle task. If Gradle's > test task (`org.gradle.api.tasks.testing.Test`) were to support it (though > as far as I know it does not), it would work without change. If the task's > type is different, then I need some adjustments to configure it properly > when only running a particular test class (or method). The only possible > issue (which I don't know if it is an issue) is if NB recognizes the @Test > annotation or not (that is not within the scope of the build tool > integration). > > Anyway, if JUnit 5 uses a different task type, I would need the following > for proper support: > > - A property to configure the test class to be executed. > - A property to configure the method to be executed. > > It would be a nice bonus if it would work the same way (using the --tests > argument) as it does now but I could make it work even if the configuration > was different (it would be considerably more work for me but I would do it). > > bye, > Attila Kelemen > > > 2017-05-17 16:19 GMT+02:00 Marc Philipp <[email protected]>: > > > Hi all, > > > > I’m a member of the JUnit team. We’re currently working on a major new > > version: JUnit 5. It will require work by IDEs to support test execution > > and reporting within the IDE. IntelliJ IDEA and Eclipse (on a branch) > > already support the new JUnit Platform and the new Jupiter API to write > > tests. > > > > Are there any plans to add JUnit 5 support to Netbeans? If so, how can we > > help? > > > > Thanks, > > Marc > > > > > >
