db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samuel Andrew McIntyre (JIRA)" <derby-...@db.apache.org>
Subject [jira] Closed: (DERBY-313) testing/README.htm property descriptions: testSpecialProps wrongly named; useprocess omitted
Date Wed, 01 Jun 2005 19:26:58 GMT
     [ http://issues.apache.org/jira/browse/DERBY-313?page=all ]
Samuel Andrew McIntyre closed DERBY-313:

     Resolution: Fixed
    Fix Version:

Committed, revision 179402.

> testing/README.htm property descriptions: testSpecialProps wrongly named; useprocess
> --------------------------------------------------------------------------------------------
>          Key: DERBY-313
>          URL: http://issues.apache.org/jira/browse/DERBY-313
>      Project: Derby
>         Type: Bug
>   Components: Documentation
>     Versions:
>  Environment: n/a
>     Reporter: Dag H. Wanvik
>     Assignee: Dag H. Wanvik
>     Priority: Minor
>      Fix For:
>  Attachments: 313.diff
> In section 4.12 in ../testing/README.htm, the property 
>     TestSpecialFlags 
> is described for specifying additional properties to RunTest. I could not
> find any evidence of this in RunTest or elsewhere. However, the property
>     testSpecialProps
> is supported by RunTest.java. I found this to work. This property
> also has a syntax for specifying more than one property using a "^"
> delimiter between properties, i.e.
>     testSpecialProps=<prop-1>=<value-1>^ ... ^<prop-n>=<value-n>
> Also,I noticed the property "useprocess" (default=true) for controlling
> whether RunTest runs the test in a separate vm or a thread in current
> vm isn't documented in README.htm.  I suggest it be included, since
> it's potentially useful for debugging tests. I could include it in the
> patch for derby-313 (I don't think anybody committed it yet) or file a
> new JIRA issue.
> Looking at RunTest reveals that unit tests are not (yet) runnable with
> "useprocess=false", though.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message