You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Marc Philipp <mp...@gmail.com> on 2017/05/17 14:19:26 UTC
JUnit 5 Support
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
Re: JUnit 5 Support
Posted by Gonzalo Ortiz Jaureguizar <go...@gmail.com>.
Hi Marc,
I'm using JUnit 5 on Netbeans, but with Maven and the JUnit 4 backport. It
works, but there are some issues with that. It would be great to have
propper support for JUnit 5.
2017-05-17 16:19 GMT+02:00 Marc Philipp <mp...@gmail.com>:
> 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
>
>
>
Re: JUnit 5 Support
Posted by John McDonnell <mc...@gmail.com>.
After a conversation with Geertjan at NetBeans Day UK earlier today, I have
migrated these requirements into a more formal document:
https://cwiki.apache.org/confluence/display/NETBEANS/Feature+Request+-+JUnit+5+Outline
Please feel free to add requirements to this and we can start working on
introducing this to NetBeans 9, maybe with some features even making a
NetBeans 9.0 release :)
Regards
John
On 25 April 2018 at 08:35, John McDonnell <jo...@apache.org> wrote:
>
>
> On 2017/05/17 17:50:30, Marc Philipp <mp...@gmail.com> wrote:
> > Hi Emi,
> >
> > JUnit 5 introduces a new architecture: It supports running multiple
> engines (i.e. testing frameworks) on a common platform. JUnit Vintage is an
> engine implementation that makes it possible to run JUnit 3 and 4 tests on
> the new platform. JUnit Jupiter is comprised of an API to write tests and
> an engine implementation to execute them on the platform.
> >
> > The platform provides an API (the Launcher API) for IDEs and build tools
> to execute tests using any engine that’s available at runtime. For example,
> an IDE would tell the the Launcher to execute a Java class. It does not
> necessarily have to know anything about the testing framework this test
> class was written for. The platform is open for any testing framework that
> runs on the JVM, not just for JUnit projects. Thus, we’d like to see
> Netbeans support the new platform instead of providing custom support for
> JUnit 4. Please refer to the documentation for an example of how to use the
> Launcher API: http://junit.org/junit5/docs/current/user-guide/#
> launcher-api
> >
> > We can’t spare any resources at the moment but would be happy to provide
> guidance, feedback on the implementation etc.
> >
> > Thanks,
> > Marc
> >
> >
> > On 17. May 2017, 16:43 +0200, Emilian Bold <em...@gmail.com>,
> wrote:
> > > Hello Marc,
> > >
> > > I've read that with "JUnit Vintage" one can still run Junit 3 and 4
> tests.
> > > Presumably IDE support will work for those out of the box?
> > >
> > > So the problem is only for tests specifically written for JUnit 5? Do
> you
> > > have any statistics of the JUnit 5 adoption within the dev community?
> > >
> > > I remember there was a license conflict with NetBeans under the
> previous
> > > license and we couldn't ship JUnit.
> > >
> > > Now I see that the Junit Eclipse Public License (EPL 1.0) is compatible
> > > with Apache ( https://www.apache.org/legal/resolved.html#category-b )
> so
> > > it's nice that we will ship it again after switching to the ASF.
> > >
> > > Just having you here on the mailing list and available is a good step.
> > > Various other ways JUnit could help, but it depends on the kind of
> > > resources you can spare and who will take up the Junit5 task.
> > >
> > >
> > >
> > > --emi
> > >
> > > On Wed, May 17, 2017 at 5:19 PM, Marc Philipp <mp...@gmail.com>
> wrote:
> > >
> > > > 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
> > > >
> > > >
> > > >
> >
> Hi,
>
> Resurrecting an ancient thread here, but I recently went to a DubJug event
> and we walked through migrating code from JUnit 4 to 5, and last week when
> I had some downtime I migrated some work related stuff as well. So I find
> myself starting to use JUnit 5 more and more and want to see what support
> we need to get into Netbeans.
>
> I've started to compile a sort of requirements list and would like some
> input into area's I'm missing. Note I only work with Maven based projects,
> so knowledge of ant based projects I would need help with (will need to
> also read up on how JUnit 5 handles ant as well)
>
> Maven Based Projects:
> Create/Update Tests dialog to automatically pick JUint 5.x when Java
> version is 8+
> + Auto generate correct code for JUnit 5
> Test File & Debug Test File Actions work
> Run/Debug Focused actions to handle new annotations/custom (tagged)
> annotations
>
> Test Results window to support JUnit 5 features like:
> + Parameterized Tests
> + Display Names
>
> Unit Test Template for JUnit 5.x
> Don't change JUint 4 Support, i.e. Don't use Vintage Engine
> Include Library for JUnit 5 (Tools -> Library -> JUnit 5.x) to include
> the following dependencies :
> + org.junit.platform:junit-platform-launcher:1.1.1:jar
> + org.junit.jupiter:junit-jupiter-engine:5.1.1:jar
> + org.junit.jupiter:junit-jupiter-api:5.1.1:jar
> + org.junit.jupiter:junit-jupiter-params:5.1.1:jar
>
> Any areas of the IDE that I'm missing?
>
>
> John
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: JUnit 5 Support
Posted by John McDonnell <jo...@apache.org>.
On 2017/05/17 17:50:30, Marc Philipp <mp...@gmail.com> wrote:
> Hi Emi,
>
> JUnit 5 introduces a new architecture: It supports running multiple engines (i.e. testing frameworks) on a common platform. JUnit Vintage is an engine implementation that makes it possible to run JUnit 3 and 4 tests on the new platform. JUnit Jupiter is comprised of an API to write tests and an engine implementation to execute them on the platform.
>
> The platform provides an API (the Launcher API) for IDEs and build tools to execute tests using any engine that’s available at runtime. For example, an IDE would tell the the Launcher to execute a Java class. It does not necessarily have to know anything about the testing framework this test class was written for. The platform is open for any testing framework that runs on the JVM, not just for JUnit projects. Thus, we’d like to see Netbeans support the new platform instead of providing custom support for JUnit 4. Please refer to the documentation for an example of how to use the Launcher API: http://junit.org/junit5/docs/current/user-guide/#launcher-api
>
> We can’t spare any resources at the moment but would be happy to provide guidance, feedback on the implementation etc.
>
> Thanks,
> Marc
>
>
> On 17. May 2017, 16:43 +0200, Emilian Bold <em...@gmail.com>, wrote:
> > Hello Marc,
> >
> > I've read that with "JUnit Vintage" one can still run Junit 3 and 4 tests.
> > Presumably IDE support will work for those out of the box?
> >
> > So the problem is only for tests specifically written for JUnit 5? Do you
> > have any statistics of the JUnit 5 adoption within the dev community?
> >
> > I remember there was a license conflict with NetBeans under the previous
> > license and we couldn't ship JUnit.
> >
> > Now I see that the Junit Eclipse Public License (EPL 1.0) is compatible
> > with Apache ( https://www.apache.org/legal/resolved.html#category-b ) so
> > it's nice that we will ship it again after switching to the ASF.
> >
> > Just having you here on the mailing list and available is a good step.
> > Various other ways JUnit could help, but it depends on the kind of
> > resources you can spare and who will take up the Junit5 task.
> >
> >
> >
> > --emi
> >
> > On Wed, May 17, 2017 at 5:19 PM, Marc Philipp <mp...@gmail.com> wrote:
> >
> > > 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
> > >
> > >
> > >
>
Hi,
Resurrecting an ancient thread here, but I recently went to a DubJug event and we walked through migrating code from JUnit 4 to 5, and last week when I had some downtime I migrated some work related stuff as well. So I find myself starting to use JUnit 5 more and more and want to see what support we need to get into Netbeans.
I've started to compile a sort of requirements list and would like some input into area's I'm missing. Note I only work with Maven based projects, so knowledge of ant based projects I would need help with (will need to also read up on how JUnit 5 handles ant as well)
Maven Based Projects:
Create/Update Tests dialog to automatically pick JUint 5.x when Java version is 8+
+ Auto generate correct code for JUnit 5
Test File & Debug Test File Actions work
Run/Debug Focused actions to handle new annotations/custom (tagged) annotations
Test Results window to support JUnit 5 features like:
+ Parameterized Tests
+ Display Names
Unit Test Template for JUnit 5.x
Don't change JUint 4 Support, i.e. Don't use Vintage Engine
Include Library for JUnit 5 (Tools -> Library -> JUnit 5.x) to include the following dependencies :
+ org.junit.platform:junit-platform-launcher:1.1.1:jar
+ org.junit.jupiter:junit-jupiter-engine:5.1.1:jar
+ org.junit.jupiter:junit-jupiter-api:5.1.1:jar
+ org.junit.jupiter:junit-jupiter-params:5.1.1:jar
Any areas of the IDE that I'm missing?
John
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: JUnit 5 Support
Posted by Marc Philipp <mp...@gmail.com>.
Hi Emi,
JUnit 5 introduces a new architecture: It supports running multiple engines (i.e. testing frameworks) on a common platform. JUnit Vintage is an engine implementation that makes it possible to run JUnit 3 and 4 tests on the new platform. JUnit Jupiter is comprised of an API to write tests and an engine implementation to execute them on the platform.
The platform provides an API (the Launcher API) for IDEs and build tools to execute tests using any engine that’s available at runtime. For example, an IDE would tell the the Launcher to execute a Java class. It does not necessarily have to know anything about the testing framework this test class was written for. The platform is open for any testing framework that runs on the JVM, not just for JUnit projects. Thus, we’d like to see Netbeans support the new platform instead of providing custom support for JUnit 4. Please refer to the documentation for an example of how to use the Launcher API: http://junit.org/junit5/docs/current/user-guide/#launcher-api
We can’t spare any resources at the moment but would be happy to provide guidance, feedback on the implementation etc.
Thanks,
Marc
On 17. May 2017, 16:43 +0200, Emilian Bold <em...@gmail.com>, wrote:
> Hello Marc,
>
> I've read that with "JUnit Vintage" one can still run Junit 3 and 4 tests.
> Presumably IDE support will work for those out of the box?
>
> So the problem is only for tests specifically written for JUnit 5? Do you
> have any statistics of the JUnit 5 adoption within the dev community?
>
> I remember there was a license conflict with NetBeans under the previous
> license and we couldn't ship JUnit.
>
> Now I see that the Junit Eclipse Public License (EPL 1.0) is compatible
> with Apache ( https://www.apache.org/legal/resolved.html#category-b ) so
> it's nice that we will ship it again after switching to the ASF.
>
> Just having you here on the mailing list and available is a good step.
> Various other ways JUnit could help, but it depends on the kind of
> resources you can spare and who will take up the Junit5 task.
>
>
>
> --emi
>
> On Wed, May 17, 2017 at 5:19 PM, Marc Philipp <mp...@gmail.com> wrote:
>
> > 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
> >
> >
> >
Re: JUnit 5 Support
Posted by Emilian Bold <em...@gmail.com>.
Hello Marc,
I've read that with "JUnit Vintage" one can still run Junit 3 and 4 tests.
Presumably IDE support will work for those out of the box?
So the problem is only for tests specifically written for JUnit 5? Do you
have any statistics of the JUnit 5 adoption within the dev community?
I remember there was a license conflict with NetBeans under the previous
license and we couldn't ship JUnit.
Now I see that the Junit Eclipse Public License (EPL 1.0) is compatible
with Apache ( https://www.apache.org/legal/resolved.html#category-b ) so
it's nice that we will ship it again after switching to the ASF.
Just having you here on the mailing list and available is a good step.
Various other ways JUnit could help, but it depends on the kind of
resources you can spare and who will take up the Junit5 task.
--emi
On Wed, May 17, 2017 at 5:19 PM, Marc Philipp <mp...@gmail.com> wrote:
> 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
>
>
>
Re: JUnit 5 Support
Posted by Marc Philipp <mp...@gmail.com>.
I’ve created https://issues.apache.org/jira/browse/NETBEANS-6
Please comment there if you’re interested in JUnit 5 support for Netbeans. I am going to unsubscribe from this mailing list for now. Feel free to reach out to the JUnit team by creating an issue on GitHub: https://github.com/junit-team/junit5/
Thanks,
Marc
On 10. Jun 2017, 21:50 +0200, Geertjan Wielenga <ge...@googlemail.com>, wrote:
> https://issues.apache.org/jira/browse/NETBEANS
>
> File it under component "java - JUnit".
>
> Gj
>
> On Sat, Jun 10, 2017 at 9:42 PM, Marc Philipp <mp...@gmail.com> wrote:
>
> > Hi again,
> >
> > this mailing list has way too much traffic for me to stay on it. Can I
> > create a ticket in Bugzilla or JIRA to continue the discussion instead?
> >
> > Thanks,
> > Marc
> >
> > On 18. May 2017, 13:22 +0200, Geertjan Wielenga <
> > geertjan.wielenga@googlemail.com>, wrote:
> > > Great discussion! Maybe this is one of the most promising threads on this
> > > mailing list -- i.e., a representative from a technology pops up on the
> > > Apache NetBeans mailing list to interact on a new integration of that
> > > technology with NetBeans.
> > >
> > > Maybe we need to have a place on the Wiki where specs can be put
> > together?
> > > I.e., a long list of specs for higher-level features (as opposed to bug
> > > fixes and so on)? There'd be an enhancement request in the bug tracker,
> > > with a reference to a location on the Apache NetBeans Wiki where the
> > > related spec for that enhancement would be found, e.g., a "support JUnit
> > 5"
> > > enhancement request, pointing to a Apache NetBeans Wiki page where the
> > > JUnit team briefly lists the key features that they'd suggest the JUnit 5
> > > support in NetBeans should consist of, as a starting point for others in
> > > Apache NetBeans to work out together further, prior to anyone
> > implementing
> > > anything?
> > >
> > > There'll be more of these kinds of mail threads starting up,
> > increasingly,
> > > especially by representatives of other Apache projects, and it would be
> > > great to have a standard process, beyond simply saying 'file an
> > enhancement
> > > request please'. I.e., some kind of form on the Wiki would be filled in
> > so
> > > that right from the start we'd have formalized input for the requested
> > > feature from the group requesting that feature.
> > >
> > > Gj
> > >
> > > On Wed, May 17, 2017 at 8:42 PM, Marc Philipp <mphilipp82@gmail.com
> > wrote:
> > >
> > > > 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 <
> > attila.kelemen85@gmail.com>,
> > > > 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 <mp...@gmail.com>:
> > > > >
> > > > > > 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
> > > > > >
> > > > > >
> > > > > >
> > > >
> >
Re: JUnit 5 Support
Posted by Geertjan Wielenga <ge...@googlemail.com>.
https://issues.apache.org/jira/browse/NETBEANS
File it under component "java - JUnit".
Gj
On Sat, Jun 10, 2017 at 9:42 PM, Marc Philipp <mp...@gmail.com> wrote:
> Hi again,
>
> this mailing list has way too much traffic for me to stay on it. Can I
> create a ticket in Bugzilla or JIRA to continue the discussion instead?
>
> Thanks,
> Marc
>
> On 18. May 2017, 13:22 +0200, Geertjan Wielenga <
> geertjan.wielenga@googlemail.com>, wrote:
> > Great discussion! Maybe this is one of the most promising threads on this
> > mailing list -- i.e., a representative from a technology pops up on the
> > Apache NetBeans mailing list to interact on a new integration of that
> > technology with NetBeans.
> >
> > Maybe we need to have a place on the Wiki where specs can be put
> together?
> > I.e., a long list of specs for higher-level features (as opposed to bug
> > fixes and so on)? There'd be an enhancement request in the bug tracker,
> > with a reference to a location on the Apache NetBeans Wiki where the
> > related spec for that enhancement would be found, e.g., a "support JUnit
> 5"
> > enhancement request, pointing to a Apache NetBeans Wiki page where the
> > JUnit team briefly lists the key features that they'd suggest the JUnit 5
> > support in NetBeans should consist of, as a starting point for others in
> > Apache NetBeans to work out together further, prior to anyone
> implementing
> > anything?
> >
> > There'll be more of these kinds of mail threads starting up,
> increasingly,
> > especially by representatives of other Apache projects, and it would be
> > great to have a standard process, beyond simply saying 'file an
> enhancement
> > request please'. I.e., some kind of form on the Wiki would be filled in
> so
> > that right from the start we'd have formalized input for the requested
> > feature from the group requesting that feature.
> >
> > Gj
> >
> > On Wed, May 17, 2017 at 8:42 PM, Marc Philipp <mp...@gmail.com>
> wrote:
> >
> > > 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 <
> attila.kelemen85@gmail.com>,
> > > 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 <mp...@gmail.com>:
> > > >
> > > > > 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
> > > > >
> > > > >
> > > > >
> > >
>
Re: JUnit 5 Support
Posted by Marc Philipp <mp...@gmail.com>.
Hi again,
this mailing list has way too much traffic for me to stay on it. Can I create a ticket in Bugzilla or JIRA to continue the discussion instead?
Thanks,
Marc
On 18. May 2017, 13:22 +0200, Geertjan Wielenga <ge...@googlemail.com>, wrote:
> Great discussion! Maybe this is one of the most promising threads on this
> mailing list -- i.e., a representative from a technology pops up on the
> Apache NetBeans mailing list to interact on a new integration of that
> technology with NetBeans.
>
> Maybe we need to have a place on the Wiki where specs can be put together?
> I.e., a long list of specs for higher-level features (as opposed to bug
> fixes and so on)? There'd be an enhancement request in the bug tracker,
> with a reference to a location on the Apache NetBeans Wiki where the
> related spec for that enhancement would be found, e.g., a "support JUnit 5"
> enhancement request, pointing to a Apache NetBeans Wiki page where the
> JUnit team briefly lists the key features that they'd suggest the JUnit 5
> support in NetBeans should consist of, as a starting point for others in
> Apache NetBeans to work out together further, prior to anyone implementing
> anything?
>
> There'll be more of these kinds of mail threads starting up, increasingly,
> especially by representatives of other Apache projects, and it would be
> great to have a standard process, beyond simply saying 'file an enhancement
> request please'. I.e., some kind of form on the Wiki would be filled in so
> that right from the start we'd have formalized input for the requested
> feature from the group requesting that feature.
>
> Gj
>
> On Wed, May 17, 2017 at 8:42 PM, Marc Philipp <mp...@gmail.com> wrote:
>
> > 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 <at...@gmail.com>,
> > 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 <mp...@gmail.com>:
> > >
> > > > 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
> > > >
> > > >
> > > >
> >
Re: JUnit 5 Support
Posted by Geertjan Wielenga <ge...@googlemail.com>.
Great discussion! Maybe this is one of the most promising threads on this
mailing list -- i.e., a representative from a technology pops up on the
Apache NetBeans mailing list to interact on a new integration of that
technology with NetBeans.
Maybe we need to have a place on the Wiki where specs can be put together?
I.e., a long list of specs for higher-level features (as opposed to bug
fixes and so on)? There'd be an enhancement request in the bug tracker,
with a reference to a location on the Apache NetBeans Wiki where the
related spec for that enhancement would be found, e.g., a "support JUnit 5"
enhancement request, pointing to a Apache NetBeans Wiki page where the
JUnit team briefly lists the key features that they'd suggest the JUnit 5
support in NetBeans should consist of, as a starting point for others in
Apache NetBeans to work out together further, prior to anyone implementing
anything?
There'll be more of these kinds of mail threads starting up, increasingly,
especially by representatives of other Apache projects, and it would be
great to have a standard process, beyond simply saying 'file an enhancement
request please'. I.e., some kind of form on the Wiki would be filled in so
that right from the start we'd have formalized input for the requested
feature from the group requesting that feature.
Gj
On Wed, May 17, 2017 at 8:42 PM, Marc Philipp <mp...@gmail.com> wrote:
> 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 <at...@gmail.com>,
> 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 <mp...@gmail.com>:
> >
> > > 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
> > >
> > >
> > >
>
Re: JUnit 5 Support
Posted by Marc Philipp <mp...@gmail.com>.
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 <at...@gmail.com>, 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 <mp...@gmail.com>:
>
> > 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
> >
> >
> >
Re: JUnit 5 Support
Posted by Attila Kelemen <at...@gmail.com>.
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 <mp...@gmail.com>:
> 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
>
>
>