You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Bryan Pendleton (JIRA)" <ji...@apache.org> on 2010/05/06 15:32:48 UTC

[jira] Commented: (DERBY-4638) Expose names of top-level test suites for easier scripting

    [ https://issues.apache.org/jira/browse/DERBY-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864764#action_12864764 ] 

Bryan Pendleton commented on DERBY-4638:
----------------------------------------

Can we make an Ant script which does this, by using the parallel task support in Ant? 


> Expose names of top-level test suites for easier scripting
> ----------------------------------------------------------
>
>                 Key: DERBY-4638
>                 URL: https://issues.apache.org/jira/browse/DERBY-4638
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.7.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.7.0.0
>
>         Attachments: DerbyTestRunner.tar.gz, list-tests.diff
>
>
> I sometimes run each of the top-level JUnit test suites individually so that they can be run in parallel and complete faster. It would be useful if AllPackages could expose the list of suites to allow scripting of such tasks without needing to change the script when a new suite is added.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.