[
https://issues.apache.org/jira/browse/OAK-884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13833813#comment-13833813
]
angela commented on OAK-884:
----------------------------
ok... i applied it again, moved it to a separate package 'random' and wanted to
extract the setup into an abstract base
test such that we can use this as a starting point of a more comprehensive test
library of that kind of randomized tests.
while doing so i found that the complete setup is done in the static
beforeClass method: i don't think this is a good idea.
all sessions should be logged in in the non-static before test-setup and should
be released in the after teardown call.
similarly all modifications made by the test including creating nodes, users
and so forth should be done for every single test.
[~asanso], may i ask you to refactor the test accordingly. thanks.
> Add simple acl randomized test
> ------------------------------
>
> Key: OAK-884
> URL: https://issues.apache.org/jira/browse/OAK-884
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: run
> Reporter: Antonio Sanso
> Assignee: angela
> Fix For: 0.13
>
> Attachments: OAK-884-patch.txt, OAK-884-patch.txt
>
>
> Taking as example org.apache.jackrabbit.oak.plugins.mongomk.RandomizedTest it
> would be nice to have some randomized test also for the ACL evaluation.
> The logic for the upcoming test patch is to add/remove randomly read
> permission entry and traverse the tree evaluation the read permission.
> The result is compared with a Jackrabbit (that is considered as a functional
> gold implementation) outcome and it is expected to match.
> Should not match then we have a problem...
> Patch to follow
--
This message was sent by Atlassian JIRA
(v6.1#6144)
