Hi Alll,

Apologies, I did start this nd during NetBeans Day UK I said I would push
my branch with what I had.

I didn't, as work and personal stuff got in the way and for the last few
months have consumed a lot of my time, and I'll admit I did sort of forgot
what I said I would do...

At the moment I have a local branch (on my Laptop at home) made a start to
this, focusing mainly on maven integration and including a library for none
maven projects.

A list of the features I had done (or close to it off the top of my head
was):

   - Adding JUnit 5 Library to Libraries in NetBeans,
   - Adding support for Maven projects to generate a JUnit 5 unit test if
   the project was using Java 8 (it would default to JUnit 4/3 in other cases
   as the current IDE does)
   - Added JUnit 5 Test Templates - Note I had an ugly warning popup if you
   added a Test Suite template into a JUnit 5 project as JUnit doesn't support
   Test Suites yet - they have an open defect on this.
   - Added Support for running individual tests annotated with the JUnit 5
   on methods that had an annotation that inherited @Testable (on a plan with
   limited internet, I believe this was the parent annotation) - Interesting
   issue here I came across here - The JUnit 5 guys in their glitter chat told
   me there's a better way to do this, using a method in their test engine
   project, but I couldn't get this to work, maybe this is a phase 2
   enhancement?
   - Made sure the Test Results window showed results for JUnit 5 (Again
   not near the code but I think that used the maven surefire reports - as a
   result, Maven Surefire didn't support the JUnit 5 displayName annotation,
   so I never had that granularity in my rest results)

I hadn't looked into project inspection or transformation at all.

I think that was mostly it off the top of my head.  I'm not sure back home
for another few days.  I will make sure I set aside time to merge/rebase in
the latest master changes into my local branch and push it for others to
view, and maybe use this as a starting or reference point for their own
implementation. - I'm setting an alarm on my phone for Saturday to ensure I
don't forget again.


Regards

John





On Wed, 8 Aug 2018 at 15:49, [email protected] <[email protected]> wrote:

> Happy to.  Also put together a quickie helloworld.
> https://github.com/hanasaki/helloworld-gradle
>
> On 8/8/18 4:06 AM, Geertjan Wielenga wrote:
> > Hi all,
> >
> > Now that the dust around the first Apache NetBeans release is settling
> and
> > we're converging around a tentative release cycle, maybe we could look at
> > one of the big missing features, i.e., JUnit 5:
> >
> > https://issues.apache.org/jira/browse/NETBEANS-6
> >
> > John McDonnell, as mentioned in the issue above, has put this together:
> >
> >
> https://cwiki.apache.org/confluence/display/NETBEANS/Feature+Request+-+JUnit+5+Outline
> >
> > Are there any takers for working on this?
> >
> > A significant starting point would be to see how support for earlier
> > versions of JUnit are implemented in
> > https://github.com/apache/incubator-netbeans and then to start doing
> > something as similar and as integrated into that way of doing things as
> > possible.
> >
> > Especially for those of us who have years of NetBeans plugin development
> > experience, this seems like a reasonable challenge for which you'll get
> > maximum gratitude from the community. :-)
> >
> > Gj
> >
>
> ---------------------------------------------------------------------
> 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
>
>
>
>

Reply via email to