Open vlsi opened 3 years ago
That's strange we've never seen the issue before. I don't know yet what is the TestNG expected behavior.
Could you provide a sample that will allow us to reproduce the issue easily?
It comes from the already existing test:
<suite name="TestNG Running Junit Tests">
<test name="Junit via TestNG XML" junit="true">
<classes>
<class name="test.junit.SetNameTest" />
</classes>
</test>
</suite>
However, for some reason, Gradle does not recognize the failure and it treats the outcome as "zero tests found", so you do not see the build failure:
WARNING 0.1sec, 0 completed, 0 failed, 0 skipped, Junit via TestNG XML
Ok, thanks! Did you open an issue for Gradle? I think its behavior is not the expected one because it provides some false-positive and we can miss some test issues :(
There's an
AssertionFailure
coming from Gradle.Gradle code: https://github.com/gradle/gradle/blob/06140ac5fbdce282f868197064156b9b1753012f/subprojects/testing-jvm/src/main/java/org/gradle/api/internal/tasks/testing/testng/TestNGTestResultProcessorAdapter.java#L184
// Gradle code:
I guess that they expect that each method should have a parent (suite?)
I do not completely follow the logic here, however, my understanding is: a) It could be TestNG defect, and TestNG should call
onStart(ITestContext iTestContext)
oronBeforeClass(ITestClass testClass)
before running JUnit methods b) It might be a false assumption by Gradle. In that case, they need to adjust the code.