db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4638) Expose names of top-level test suites for easier scripting
Date Thu, 06 May 2010 13:58:48 GMT

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

Knut Anders Hatlen commented on DERBY-4638:
-------------------------------------------

Hi Bryan,

That sounds like a good idea. I haven't used Ant a lot for running JUnit tests, but I don't
see any reason why it shouldn't be possible to do something similar 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.


Mime
View raw message