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] Closed: (DERBY-4638) Expose names of top-level test suites for easier scripting
Date Mon, 07 Jun 2010 12:12:52 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen closed DERBY-4638.
-------------------------------------


Thanks for checking out the possibility for a backport, Kristian. Since there's not more to
do on this issue, I'm closing it.

> 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.6.1.1, 10.7.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.6.1.1, 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