I converted a dynamically generated JUnit test suite to TestNG using a @Factory
annotation. The tests are generated by scanning a directory that contains severa
As carlin.scott suggested, extending XmlTest
works for this problem. However, I overrode toString()
to return the test name (instead of calling setName
). This has the advantage that the test name in the TestNG view is easier to read. By default, it contains additional information such as parameters and metagroups.
Try extending XmlTest in your test class and call setName(). I extended XmlSuite and used setName to name my "test suite" which is a class with multiple tests defined in it and that worked for me. In fact I just tried what I suggested on the same class and now it's called a test with the correct name. I'm not sure why the ITest interface is being ignored as I also tried that approach without success.