Release 2.7.5 introduced a change wherein if a method filter is supplied via the prefix.method system property a NoTestsRemainException even if there are other test suites for which the method filter does match. This seems to be because we apply method filters before class filters, so even if a later class will match our filter we fail all other test suites even if they are also filtered out vi a prefix.class filter.

This current behavior effectively makes it impossible to use method filters for any test execution which includes more than a single test suite. The expected behavior should be that class filters by applied first and we only throw the NoTestsRemainException if none of the remaining classes match the supplied method filter.