[ http://issues.apache.org/jira/browse/JCR-117?page=comments#action_64753 ] Jukka Zitting commented on JCR-117: -----------------------------------
It seems that the Maven test:test goal is implemented using the Ant JUnit task with a FileSet containing all files that match the unitTest includes defined in project.xml. I'm not an expert on how Ant FileSets work under the hood, but I believe that the order of the unit tests is determined either by a HashSet somewhere along the line or the order in which the underlying filesystem returns the file names. Based on the fact that your test cases seem to be executed in alphabetical order, I'd suspect that the problem is in the underlying filesystem (on Linux you need to specifically sort file names if you want them ordered). I'll check if I could instruct Maven to process the tests in some specific order. > Test cases not fully initialized at first run > --------------------------------------------- > > Key: JCR-117 > URL: http://issues.apache.org/jira/browse/JCR-117 > Project: Jackrabbit > Type: Test > Components: TCK > Reporter: Jukka Zitting > Priority: Minor > > It seems that some test cases in o.a.j.test.api.query and o.a.j.test.api do > not properly initialized the test repository before running tests against it. > The repository gets initialized by other test cases, and later runs of the > troublesome tests report no errors. > Thus the problem appears right after a fresh checkout and a tree cleanup. The > command sequence below illustrates this problem. The error messages reported > by the initial test runs are "Workspace does not contain test data at: > /testdata/query" and "Workspace does not contain test data at: /testdata". > I tried tracing the cause of this problem, but couldn't find it easily as I'm > not yet too familiar with the test setup. > $ svn co > $ maven test > [junit] Running org.apache.jackrabbit.test.api.query.TestAll > [junit] Tests run: 77, Failures: 30, Errors: 0, Time elapsed: 5,333 sec > [junit] [ERROR] TEST org.apache.jackrabbit.test.api.query.TestAll FAILED > [junit] Running org.apache.jackrabbit.test.api.TestAll > [junit] Tests run: 534, Failures: 181, Errors: 0, Time elapsed: 16,105 sec > [junit] [ERROR] TEST org.apache.jackrabbit.test.api.TestAll FAILED > $ maven test > [junit] Running org.apache.jackrabbit.test.api.query.TestAll > [junit] Tests run: 77, Failures: 0, Errors: 0, Time elapsed: 5,887 sec > [junit] Running org.apache.jackrabbit.test.api.TestAll > [junit] Tests run: 534, Failures: 0, Errors: 0, Time elapsed: 18,427 sec > $ maven clean > $ maven test > [junit] Running org.apache.jackrabbit.test.api.query.TestAll > [junit] Tests run: 77, Failures: 30, Errors: 0, Time elapsed: 13,185 sec > [junit] [ERROR] TEST org.apache.jackrabbit.test.api.query.TestAll FAILED > [junit] Running org.apache.jackrabbit.test.api.TestAll > [junit] Tests run: 534, Failures: 181, Errors: 0, Time elapsed: 40,42 sec > [junit] [ERROR] TEST org.apache.jackrabbit.test.api.TestAll FAILED > $ maven test > [junit] Running org.apache.jackrabbit.test.api.query.TestAll > [junit] Tests run: 77, Failures: 0, Errors: 0, Time elapsed: 5,942 sec > [junit] Running org.apache.jackrabbit.test.api.TestAll > [junit] Tests run: 534, Failures: 0, Errors: 0, Time elapsed: 17,797 sec -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
