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] Updated: (DERBY-4638) Expose names of top-level test suites for easier scripting
Date Thu, 06 May 2010 11:28:49 GMT

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

Knut Anders Hatlen updated DERBY-4638:
--------------------------------------

    Attachment: DerbyTestRunner.tar.gz

I threw together an application that extracts the list of suites from the new public method
in AllPackages and runs them in parallel. On my machine, suites.All takes about 38 minutes
when I run the suites in four sub-processes this way. Attaching it here in case someone is
interested in using it as a starting point. There's a README.txt file in the tarball explaining
how to use 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.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