[ https://issues.apache.org/jira/browse/OAK-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved OAK-287.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.5
Assignee: Jukka Zitting
Fixed in revision 1378510 by making each test case to use a separate fresh repository.
> 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
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 0.5
>
>
> 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
|