[ https://issues.apache.org/jira/browse/NETBEANS-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728264#comment-16728264 ]
Pieter van den Hombergh edited comment on NETBEANS-1817 at 12/24/18 9:11 AM: ----------------------------------------------------------------------------- Ant based project: Changing the library set back to Jnunt 4.12 and changing the imports and annotation accoridingly makes it into a project that can be tested, both on the project level and on the test-class level. This makes me infer that the old ant-based test infrastructure is still in place. {color:#14892c}OK{color} The{color:#333333} annoying part{color} lies in the fact that the test templates expanded from new-> unit-test->junit produce junit 5 code and imports, which are then not usable. This makes a very bad experience and is not acceptable when teaching novices to create unit tests. First steps should be easy, not hard. {color:#d04437}NOT OK{color} It would help if the test wizard would allow selection between junit 4 and junit 5, like it has been possible (in some previous version) to choose between junit 3.8 and junit 4. Then I would have an easy transition from NB 8.2 to NB10, keeping my old (junit 4) tests and allow a more gradual transition to the newer stuff (Java 11, modules, JUnit 5 etc). I do welcome the addition of Junit 5, which is an area in which nb has been lagging. Having it only in maven based projects is ok for the time being, as it also works as advertised and shown with NetCat. I ran those tests myself, and was pleased and surprised at the same time. I might be thinking to simple here, but I surmise that the build files (build.xml, build-impl.xml, build.properties) are also generated from templates. It might suffice to add the proper code (and conditions) to the ant files (which are big beasts) and add the odd jar file, needed for ant to have a working runner. From the junit 5 tutorial website [https://junit.org/junit5/docs/current/user-guide/#running-tests-build-ant] I infer that it might be as simple as adding a different runner. I might find some spare time between the holiday obligations to experiment with the build file to first make it work from the command line and the proper libraries/jars and then see how this can be integrated into NB10. was (Author: homberghp): Ant based project: Changing the library set back to Jnunt 4.12 and changing the imports and annotation accoridingly makes it into a project that can be tested, both on the project level and on the test-class level. This makes me infer that the old ant-based test infrastructure is still in place. {color:#14892c}OK{color} The{color:#333333} annoying part{color} lies in the fact that the test templates expanded from new-> unit-test->junit produce junit 5 code and imports, which are then not usable. This makes a very bad experience and is not acceptable when teaching novices to create unit tests. First steps should be easy, not hard. {color:#d04437}NOT OK{color} It would help if the test wizard would allow selection between junit 4 and junit 5, like it has been possible (in some previous version) to choose between junit 3.8 and junit 4. Then I would have an easy transition from NB 8.2 to NB10, keeping my old (junit 4) tests and allow a more gradual transition to the newer stuff (Java 11, modules, JUnit 5 etc). I do welcome the addition of Junit 5, which is an area in which nb has been lagging. Having it only in maven based projects is ok for the time being, as it also works as advertised and show with NetCat. I rand those tests myself, and was pleased and surprised at the same time. I might be thinking to simple here, but I surmise that the build files (build.xml, build-impl.xml, build.properties) are also generated form templates. It might suffice to add the proper code (and conditions) to the ant files (which are big beasts) and add the odd jar file, needed for ant to have a working runner. From the junit 5 tutorial website [https://junit.org/junit5/docs/current/user-guide/#running-tests-build-ant] I infer that it might be as simple as adding a different runner. I might find some spare time between the holiday obligations to experiment with the build file to first make it work from the command line and the proper libraries/jars and then see how this can be integrated into NB10. > exception thrown on startup > --------------------------- > > Key: NETBEANS-1817 > URL: https://issues.apache.org/jira/browse/NETBEANS-1817 > Project: NetBeans > Issue Type: Bug > Reporter: Pieter van den Hombergh > Priority: Major > > see report log below -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists