If I have these classes:

abstract class FooTest { @Test public void foo() {} }
class BarTest extends Foo { @Test public void bar() {} }

In JUnit 4 I can run the "foo" test as a standalone method from the test window, as the concrete class BarTest is passed to Surefire ("-Dtest=Bar#foo").

In JUnit 5 the abstract superclass Foo is passed to surefire("-Dtest=Foo#foo") which cannot be instantiated and so cannot run. This occurs regardless of whether FooTest is abstract, concrete or an interface.

Is it possible to tighten the logic that determines which class to pass to Surefire without having to wait for fully fledged JUnit 5 support? (Which actually seems to work perfectly fine, apart from Netbeans occasionally trying to re-add JUnit 4 to my dependencies.)