Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Date: Wed, 29 Aug 2012 21:49:07 +1100 (NCT)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: oak-dev@jackrabbit.apache.org
Message-ID: <2019727872.11176.1346237347637.JavaMail.jiratomcat@arcas>
Subject: [jira] [Created] (OAK-287) PrivilegeManagerImplTest.testJcrAll
 assumes that there are no custom privileges
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jukka Zitting created OAK-287:
---------------------------------

             Summary: PrivilegeManagerImplTest.testJcrAll assumes that there are no custom privileges
                 Key: OAK-287
                 URL: https://issues.apache.org/jira/browse/OAK-287
             Project: Jackrabbit Oak
          Issue Type: Bug
          Components: jcr
            Reporter: Jukka Zitting
            Priority: Minor


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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira