Q:

Fail test when to much assumes fails

In JUnit we can use Assume in stead of Assert.
This has the advantage that the test doesn't fail but it also mark as no full success.
Is there any possibility to configure all Assume testing that for xx% have to succeed or else the TestCase will fail?
It's not that we only write Assume testing but in some particular cases we need to do so because we don't have an LDAP testing environment and changes there could affect our testing.
If the tests fails => resolve testing before you can release.
With Assume we can still release if most of the assumes succeed and refactor the testing when we have time and not in stress of a release.
Of course the success percentage need's to be high like 90 - 95%. 
I'm now thinking in the direction of creating a static wrapper class where I log the calls and the failures.
Of course I don't want to reinvent the wheel when it already exist with an even better implementation then what I would write.

A:

Maybe you can implement a RunListener to count the quantity of failed assumes, using testAssumptionFailure().

