You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand if the original intention of the fix for @Suite was to only fix JUnit 4 suites. I only wish to provide some feedback about other cases.
steps
// src/test/MathTest.scala// This is a definition of a JUnit 3 test case. Many of these test cases will be "dynamically" collected into a JUnit 3 `TestSuite` and run.classMathTest(op1: Int, op2: Int, res: Int) extendsTestCase(s"$op1 + $op2 = $res") {
finaloverridedefrunTest():Unit= {
assertEquals(res, op1 + op2)
}
}
// src/test/MathSuite.scalaclassMathSuiteextendsTestCaseobjectMathSuite {
// This is essentially a Scala 2.12+ hack, where methods on the companion object produce static forwarders on the class.// This is the Scala equivalent of the JUnit 3 convention public static Test suite() { ... }defsuite():Test= {
vals=newTestSuite("MathSuite")
s.addTest(newMathTest(1, 2, 3))
s.addTest(newMathTest(2, 3, 4))
s
}
}
problem
It still produces:
[error] java.lang.RuntimeException: Test class MathTest is not enclosed by MathSuite
notes
The JUnit 3 TestSuite is still not fixed by #87 (I did a publishLocal).
An additional detail to this ticket, "org.junit.vintage" % "junit-vintage-engine" % JupiterKeys.junitVintageVersion.value % Test is required as a dependency for reproducing the described problem.
I understand if the original intention of the fix for
@Suite
was to only fix JUnit 4 suites. I only wish to provide some feedback about other cases.steps
problem
It still produces:
notes
The JUnit 3
TestSuite
is still not fixed by #87 (I did apublishLocal
).Originally posted by @vasilmkd in #87 (comment)
The text was updated successfully, but these errors were encountered: