Description
The testJcrAll test checks the contents of the jcr:all privilege by first verifying that all standard JCR privileges are included and then asserting that no other privileges are included.
That last assertion doesn't work properly since the jcr:all privilege is defined to also "include all implementation-defined privileges" and in some orderings of the test suite the other test cases like testRegisterCustomPrivileges have already added such custom privileges before the testJcrAll test gets executed.
Ideally we'd run each test case in a completely isolated state so the ordering of tests won't matter. If that can't be done, the assertion at the end of testJcrAll should be disabled.