homberghp opened a new issue, #8160: URL: https://github.com/apache/netbeans/issues/8160
### Description # The first test in each test class takes 18.000 milliseconds on average. With 31 test classes in the `org.netbeans.modules.refactoring.java.test` package alone, that is a huge waiting bill, or stated otherwise it takes my caffeine level over healthy values. Since some of these tests involve the GUI, working on other things on the same machine is unproductive, because your work will lose focus. ### Use case/motivation Run the tests in package `refactoring/netbeans/org.netbeans.modules.refactoring.java.test` and measure. NetBeans will do that for you. The last run on my machine (AMD64, 24 virtual cores, that do not help,32 Gigs of memory for me and netbeans alone).  I would replace the method `writeFilesAndWaitForScan` with one that skips the *wait for scan* part. The wait for scan part is documented as use with care, it takes a long time. From experience some, maybe a lot more can do without the full scan. I will be waiting for approval before starting this effort. ### Related issues developing/adding features/resolve bugs. #7043, #7044 ### Are you willing to submit a pull request? Yes -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@netbeans.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@netbeans.apache.org For additional commands, e-mail: notifications-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
