Closed VijayKrishna closed 4 years ago
@kajdreef i have not setup the tests yet. Will get the ball rolling on that shortly /within this very PR/. In the meanwhile, feel free to try this out locally and see if this works for your the projects that you were trying Tacoco with.
When running the changes on the TestNG project it fails, see output here output_spiderMath_TestNG.txt. maybe for now we should consider TestNG first (not using testng-junit5), and then let it check for JUnit4 and JUnit5 through the unified approach.
Interestingly, if I update the TestNG dependency for spiderMath_TestNG to 7.0.0 the errors go away and I can run the project without a problem.
I will continue testing some things out today.
containsExecutableTest
) and test execution (getExecutableTest
). b. Using a different discovery path is useful to answer questions questions like: "Does the testClass have executable tests?", and as such, "Can we use the UnifiedTestRunner?" c. If the discovery path fails, then the UnifiedTest runner is not viable for a given test class.Next Steps: integration tests that run on projects.