Add support for TestNG

[dodie]

Scott supports JUnit4 and 5, but It would be nice to support TestNG as well.

To achieve this, the system has to be extended in at least the following places:

• This class is responsible to determine what methods should be instrumented to track behavior. This should be modified to mark TestNG methods as well.
• The same class is responsible to determine what classes should be instrumented with integration to the test framework. For example in the case of JUnit4, it marks a class to be injected with a ReportingRule it the class contains a @Test method. Similarly to the first point, this should be augmented to handle TestNG code.
• Finally, the instrumentation part of the code has to be extended to inject TestNG specific code to the tests (marked by the previous point) to handle failing test cases and print the report. See visitMethod and visitEnd in this class to see how it's handled for the JUnit4 Reporting Rule.

For more info about the architecture, please see the development guide.

[dodie]

Moved to the idea list in wiki.

[geofflangenderfer]

I believe TestDiscoveryMethodVisitor was renamed to DiscoveryMethodVisitor

[dodie]

Hi @geofflangenderfer,

Yes, TestDiscoveryMethodVisitor was renamed to DiscoveryMethodVisitor as part of an API stabilization when new configuration options were introduced. May I ask where did you bump into the old name? I'd be happy to clean up obsolete documentation.

Cheers,
Dávid

[geofflangenderfer]

I was thinking about using scott with testng. This is one of the first roadblocks I ran into. I thought I would share my findings for the next person. Hopefully I have time at some point to look at this.