We are using testng with a large source base. With testng 6.3.2 and 6.4 there is a long pause before tests start running. It seems that this is the time that testng is scanning classes for testng annotations. For our source base, this requires 15+ minutes to complete. Unfortunately, our test classes are in the same package structure as the product classes themselves and it is not possible to change this organization. I have looked for a way to limit that classes (and jars) that testng is scanning, but it seems to pick up the test classes, everything in the classpath that matches the package definition specified in testng.xml are scanned.Is it possible to further limit this scanning or otherwise speed up the startup time for testng.
--
You received this message because you are subscribed to the Google Groups "testng-dev" group.
To view this discussion on the web visit https://groups.google.com/d/msg/testng-dev/-/iVXlAbeoN3MJ.
To post to this group, send email to testn...@googlegroups.com.
To unsubscribe from this group, send email to testng-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/testng-dev?hl=en.
There are thousands of test classes, so specifying each individual test class is not feasible. Previously, with testng 6.0.1m the project team used an include sub-element in the package specification too filter specific tests. For example,
Is there a way in testng.xml to specify a pattern for the classes to scan for annotations within a package structure?
--
You received this message because you are subscribed to the Google Groups "testng-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to testng-dev+...@googlegroups.com.
To post to this group, send email to testn...@googlegroups.com.
Visit this group at https://groups.google.com/group/testng-dev.
For more options, visit https://groups.google.com/d/optout.