Re: NetCAT test specs for 12.0
I can do some NB 12 testing for Java EE/Payara. I'm also happy to create some new Java EE/Payara test specification(s) if anyone can suggest some specific gaps that we should plug. Should we be creating some EE 8 test specifications? All feedback welcome. Rick On Sun, Feb 2, 2020 at 1:01 PM Pieter van den Hombergh < pieter.van.den.hombe...@gmail.com> wrote: > I would definitely say maven, in particular testing experience. > * the test report window should get preference over the output window, > which is way more usefull, although sometimes to much truncated. > * when a test is selected in the left panel, the right panel of the test > report should show the output. no i type this i wonder if it already does > that. > * running one test file is not very stable, in that something runs but no > results are shown. > * high on my wishlist: run a single test method from either the navigator > or the editor (there are annotations) or both, or at least re_run from test > report window. > i try to promote tdd, and to make that really work, running tests should be > blazingly fast. might need some cooperation from either apache-maven and > the junit 5 team or even both. > > keep making netbeans the preferred java ide. > > On Sat, 1 Feb 2020 at 17:20, Geertjan Wielenga > wrote: > > > Hi all, > > > > Thinking ahead a bit, as soon as 11.3 is out, we should be evaluating the > > test specs so we can start NetCAT so we can start that a month later when > > the first beta is available when the merge window closes. > > > > Now -- the question of the moment is: which areas of NetBeans do we want > to > > prioritize for NetCAT, especially which have not been tested before that > we > > now find important (e.g., Gradle) and are essentially new kids on the > > block. > > > > Here is my (and Neil's) proposal for what we should be focusing on (and > > what we should not be focusing on for NetCAT 12.0). > > > > Focus areas (in alphabetical order): > > > > 1. Gradle > > 2. Jakarta EE (including Payara) > > 3. Java Editor -- new language features for JDK 11+ in particular > > 4. PHP Editor -- focus on the newest PHP language features > > 5. Maven > > 6. Ergonomics/enablement of features (issues with being behind proxy, > etc) > > > > Things to deprioritize (this time around and remember we can't do > > everything and if you disagree please speak up and pick up the specs), > > i.e., things that haven't changed: > > > > 1. Form Editor (i.e., GUI Builder, Matisse) > > 2. Ant-based anything > > 3. Subversion, CVS, i.e., anything not Git > > > > Anyway, that's a starting point for discussion, also see this updated > > schedule: > > > > https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule > > > > Thanks, > > > > Gj and Neil > > > -- > Pieter Van den Hombergh. > No software documentation is complete with out it's source code. > > > -- > Pieter Van den Hombergh. > No software documentation is complete with out it's source code. >
Fwd: NetCAT test specs for 12.0
I would definitely say maven, in particular testing experience. * the test report window should get preference over the output window, which is way more usefull, although sometimes to much truncated. * when a test is selected in the left panel, the right panel of the test report should show the output. no i type this i wonder if it already does that. * running one test file is not very stable, in that something runs but no results are shown. * high on my wishlist: run a single test method from either the navigator or the editor (there are annotations) or both, or at least re_run from test report window. i try to promote tdd, and to make that really work, running tests should be blazingly fast. might need some cooperation from either apache-maven and the junit 5 team or even both. keep making netbeans the preferred java ide. On Sat, 1 Feb 2020 at 17:20, Geertjan Wielenga wrote: > Hi all, > > Thinking ahead a bit, as soon as 11.3 is out, we should be evaluating the > test specs so we can start NetCAT so we can start that a month later when > the first beta is available when the merge window closes. > > Now -- the question of the moment is: which areas of NetBeans do we want to > prioritize for NetCAT, especially which have not been tested before that we > now find important (e.g., Gradle) and are essentially new kids on the > block. > > Here is my (and Neil's) proposal for what we should be focusing on (and > what we should not be focusing on for NetCAT 12.0). > > Focus areas (in alphabetical order): > > 1. Gradle > 2. Jakarta EE (including Payara) > 3. Java Editor -- new language features for JDK 11+ in particular > 4. PHP Editor -- focus on the newest PHP language features > 5. Maven > 6. Ergonomics/enablement of features (issues with being behind proxy, etc) > > Things to deprioritize (this time around and remember we can't do > everything and if you disagree please speak up and pick up the specs), > i.e., things that haven't changed: > > 1. Form Editor (i.e., GUI Builder, Matisse) > 2. Ant-based anything > 3. Subversion, CVS, i.e., anything not Git > > Anyway, that's a starting point for discussion, also see this updated > schedule: > > https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule > > Thanks, > > Gj and Neil > -- Pieter Van den Hombergh. No software documentation is complete with out it's source code. -- Pieter Van den Hombergh. No software documentation is complete with out it's source code.
Re: NetCAT test specs for 12.0
+1 to Geertjan and Neils list and including JavaFX too. El 1/2/20 a las 20:48, Glenn Holmer escribió: On 2/1/20 10:19 AM, Geertjan Wielenga wrote: Thinking ahead a bit, as soon as 11.3 is out, we should be evaluating the test specs so we can start NetCAT so we can start that a month later when the first beta is available when the merge window closes. Now -- the question of the moment is: which areas of NetBeans do we want to prioritize for NetCAT, especially which have not been tested before that we now find important (e.g., Gradle) and are essentially new kids on the block. JavaFX - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: NetCAT test specs for 12.0
I agree with the list and also including JavaFX. Thanks Josh Juneau juneau...@gmail.com http://jj-blogger.blogspot.com https://www.apress.com/us/search?query=Juneau > On Feb 1, 2020, at 5:47 PM, Geertjan Wielenga wrote: > > Yes, makes sense to include JavaFX. > > Gj > >> On Sat, Feb 1, 2020 at 8:48 PM Glenn Holmer >> wrote: >> >>> On 2/1/20 10:19 AM, Geertjan Wielenga wrote: >>> Thinking ahead a bit, as soon as 11.3 is out, we should be evaluating the >>> test specs so we can start NetCAT so we can start that a month later when >>> the first beta is available when the merge window closes. >>> >>> Now -- the question of the moment is: which areas of NetBeans do we want >> to >>> prioritize for NetCAT, especially which have not been tested before that >> we >>> now find important (e.g., Gradle) and are essentially new kids on the >> block. >> >> JavaFX >> >> -- >> Glenn Holmer (Linux registered user #16682) >> "After the vintage season came the aftermath -- and Cenbe." >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org >> For additional commands, e-mail: dev-h...@netbeans.apache.org >> >> For further information about the NetBeans mailing lists, visit: >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists >> >>
Re: NetCAT test specs for 12.0
Yes, I believe that source code has not been donated yet -- something on my list to investigate. Gj On Sun, Feb 2, 2020 at 11:46 AM Luca Mambretti wrote: > Hi, > > It might be a little selfish for me to say, but are there any news/plans > regarding the JIRA integration, I'd be willing to setup and run a test > specification for that since it's one of the most useful features for me > and it's currently broken with no documented workaround in all versions. > > Cheers, > Luca > > - Messaggio originale - > Da: "Geertjan Wielenga" > A: "netcat" , "dev" > Inviato: Sabato, 1 febbraio 2020 17:19:59 > Oggetto: NetCAT test specs for 12.0 > > Hi all, > > Thinking ahead a bit, as soon as 11.3 is out, we should be evaluating the > test specs so we can start NetCAT so we can start that a month later when > the first beta is available when the merge window closes. > > Now -- the question of the moment is: which areas of NetBeans do we want to > prioritize for NetCAT, especially which have not been tested before that we > now find important (e.g., Gradle) and are essentially new kids on the > block. > > Here is my (and Neil's) proposal for what we should be focusing on (and > what we should not be focusing on for NetCAT 12.0). > > Focus areas (in alphabetical order): > > 1. Gradle > 2. Jakarta EE (including Payara) > 3. Java Editor -- new language features for JDK 11+ in particular > 4. PHP Editor -- focus on the newest PHP language features > 5. Maven > 6. Ergonomics/enablement of features (issues with being behind proxy, etc) > > Things to deprioritize (this time around and remember we can't do > everything and if you disagree please speak up and pick up the specs), > i.e., things that haven't changed: > > 1. Form Editor (i.e., GUI Builder, Matisse) > 2. Ant-based anything > 3. Subversion, CVS, i.e., anything not Git > > Anyway, that's a starting point for discussion, also see this updated > schedule: > > https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule > > Thanks, > > Gj and Neil > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: NetCAT test specs for 12.0
Hi, It might be a little selfish for me to say, but are there any news/plans regarding the JIRA integration, I'd be willing to setup and run a test specification for that since it's one of the most useful features for me and it's currently broken with no documented workaround in all versions. Cheers, Luca - Messaggio originale - Da: "Geertjan Wielenga" A: "netcat" , "dev" Inviato: Sabato, 1 febbraio 2020 17:19:59 Oggetto: NetCAT test specs for 12.0 Hi all, Thinking ahead a bit, as soon as 11.3 is out, we should be evaluating the test specs so we can start NetCAT so we can start that a month later when the first beta is available when the merge window closes. Now -- the question of the moment is: which areas of NetBeans do we want to prioritize for NetCAT, especially which have not been tested before that we now find important (e.g., Gradle) and are essentially new kids on the block. Here is my (and Neil's) proposal for what we should be focusing on (and what we should not be focusing on for NetCAT 12.0). Focus areas (in alphabetical order): 1. Gradle 2. Jakarta EE (including Payara) 3. Java Editor -- new language features for JDK 11+ in particular 4. PHP Editor -- focus on the newest PHP language features 5. Maven 6. Ergonomics/enablement of features (issues with being behind proxy, etc) Things to deprioritize (this time around and remember we can't do everything and if you disagree please speak up and pick up the specs), i.e., things that haven't changed: 1. Form Editor (i.e., GUI Builder, Matisse) 2. Ant-based anything 3. Subversion, CVS, i.e., anything not Git Anyway, that's a starting point for discussion, also see this updated schedule: https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule Thanks, Gj and Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: NetCAT test specs for 12.0
Yes, makes sense to include JavaFX. Gj On Sat, Feb 1, 2020 at 8:48 PM Glenn Holmer wrote: > On 2/1/20 10:19 AM, Geertjan Wielenga wrote: > > Thinking ahead a bit, as soon as 11.3 is out, we should be evaluating the > > test specs so we can start NetCAT so we can start that a month later when > > the first beta is available when the merge window closes. > > > > Now -- the question of the moment is: which areas of NetBeans do we want > to > > prioritize for NetCAT, especially which have not been tested before that > we > > now find important (e.g., Gradle) and are essentially new kids on the > block. > > JavaFX > > -- > Glenn Holmer (Linux registered user #16682) > "After the vintage season came the aftermath -- and Cenbe." > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > >
Re: NetCAT test specs for 12.0
On 2/1/20 10:19 AM, Geertjan Wielenga wrote: > Thinking ahead a bit, as soon as 11.3 is out, we should be evaluating the > test specs so we can start NetCAT so we can start that a month later when > the first beta is available when the merge window closes. > > Now -- the question of the moment is: which areas of NetBeans do we want to > prioritize for NetCAT, especially which have not been tested before that we > now find important (e.g., Gradle) and are essentially new kids on the block. JavaFX -- Glenn Holmer (Linux registered user #16682) "After the vintage season came the aftermath -- and Cenbe." - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
NetCAT test specs for 12.0
Hi all, Thinking ahead a bit, as soon as 11.3 is out, we should be evaluating the test specs so we can start NetCAT so we can start that a month later when the first beta is available when the merge window closes. Now -- the question of the moment is: which areas of NetBeans do we want to prioritize for NetCAT, especially which have not been tested before that we now find important (e.g., Gradle) and are essentially new kids on the block. Here is my (and Neil's) proposal for what we should be focusing on (and what we should not be focusing on for NetCAT 12.0). Focus areas (in alphabetical order): 1. Gradle 2. Jakarta EE (including Payara) 3. Java Editor -- new language features for JDK 11+ in particular 4. PHP Editor -- focus on the newest PHP language features 5. Maven 6. Ergonomics/enablement of features (issues with being behind proxy, etc) Things to deprioritize (this time around and remember we can't do everything and if you disagree please speak up and pick up the specs), i.e., things that haven't changed: 1. Form Editor (i.e., GUI Builder, Matisse) 2. Ant-based anything 3. Subversion, CVS, i.e., anything not Git Anyway, that's a starting point for discussion, also see this updated schedule: https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule Thanks, Gj and Neil
