I found that when tests that were annotated with @RunWith(SpringJUnit4ClassRunner.class) did not get properly executed when using junit-interface (sbt 0.13). After some digging, it appeared that it was because these test definitions were being assigned the JunitFingerprint, when they should have been assigned the RunWithFingerprint. My guess was that the first matching fingerprint for each test definition was used, so it made sense that making RunWithFingerprint the first item returned from the framework would cause RunWithFingerprint to be assigned to test definitions having the @RunWith annotation - after switching to the forked version with the new ordering, my tests now execute using the Junit Runner as expected.
Changing order of fingerprints to allow tests with @RunWith to execute
Open issue for this bug with reproduction steps: #14 (comment)
See also the comment by @retronym on another open bug #21 (comment)
Looks to me like this is the same problem as #21
Nice analysis and fix! Thanks much.