db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Van Couvering (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-892) add mechanism for specifying policy file for individual function tests
Date Mon, 30 Jan 2006 23:44:33 GMT
    [ http://issues.apache.org/jira/browse/DERBY-892?page=comments#action_12364513 ] 

David Van Couvering commented on DERBY-892:

I vote for this too, I think this makes a lot of sense.

> add mechanism for specifying policy file for individual function tests
> ----------------------------------------------------------------------
>          Key: DERBY-892
>          URL: http://issues.apache.org/jira/browse/DERBY-892
>      Project: Derby
>         Type: Bug
>     Versions:
>     Reporter: Myrna van Lunteren
>     Priority: Minor

> It would be nice to be able to specify a test-specific policy file.
> This should get handled similar to existing properties, i.e. get specified in a test_app.properties
file (or, for a suite, in the suite.properties file).  The file should then be copied into
the correct place.
> Note, that the 'old' functionTests harness (as opposed to junit tests) includes a check
for a property called 'serverPolicyFile' (in harness/jvm.java). The name is a left over from
when the policy file was only used for/by network server, and should be renamed - derbyTestPolicyFile,
for instance. It is not used anywhere at present, and not specific to network server. It would
be nice if this could be expanded, or, if not used, removed.
> The default policy file used is the derby_tests.policy file under functionTests/util.
> Also, currently, the property can only be used with RunTest - for further traction, it
should probably get passed on through RunSuite/RunList.
> Once confirmed to be working, the property should get documented in <trunk>/java/testing/README.htm.

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