-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tests annotated using @RunWith not picked up by sbt #66
Comments
+1 In my case just using the plain Junit Parametrized.class runner @RunWith(Parameterized.class) My parametrized test ran (6 of them) but in the SBT console I see contradictory results: [info] Test run finished: 6 failed, 0 ignored, 6 total, 70.937s My dependencies: |
I think I've encountered this bug in my play project which seems to use this project (if I interpret https://github.com/playframework/playframework/blob/3c530e93603d4005211d466923fff486338faf00/framework/project/Dependencies.scala correctly). As you can see in the linked issue from the play bugtracker the tests are run (and output to the console) yet they are not counted as either passed, failed or errors. |
I have the same problem, when use @RunWith, I get zero value test report. |
@RunWith(SpringJUnit4ClassRunner.class) works for me (in "IntegrationTest"). Have you tried the latest sbt version 0.13.8? |
I've also seen the same problem (using |
Having the same issue. Having a class annotated with @RunWith(MockitoJUnitRunner.class), and |
managed to have it run by adding |
This test is not picked up:
@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(locations = {"classpath:test-context.xml"})
public class MyTest {
but if @RunWith is commented out the test is picked up (but obviously does not work correctly)
//@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(locations = {"classpath:test-context.xml"})
public class MyTest {
This is using 0.11 of junit-interface library
libraryDependencies += "com.novocode" % "junit-interface" % "0.+" % "test"
...
Resolving com.novocode#junit-interface;0.11-RC1
The text was updated successfully, but these errors were encountered: