Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jackrabbit-dev@incubator.apache.org
Message-ID: <1337040981.1121095930286.JavaMail.jira@ajax.apache.org>
Date: Mon, 11 Jul 2005 17:32:10 +0200 (CEST)
From: "Marcel Reutegger (JIRA)" <jira@apache.org>
To: jackrabbit-dev@incubator.apache.org
Subject: [jira] Resolved: (JCR-117) Test cases not fully initialized at first
 run
In-Reply-To: <2032405801.1114590998551.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/JCR-117?page=all ]
     
Marcel Reutegger resolved JCR-117:
----------------------------------

    Resolution: Fixed

Moved init test cases to a preGoal.

Fixed in svn revision: 210145

> 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