[
https://issues.apache.org/jira/browse/DERBY-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876218#action_12876218
]
Kristian Waagan commented on DERBY-4638:
----------------------------------------
I tried back-porting this to 10.5, but there are some issues with that, besides
the merges not being clean;
1) Configurable port functionality missing (fixed by back-porting DERBY-4217)
2) SysinfoTest fails (fixed by DERBY-858?)
It may be possible to do this, but I guess the safest approach is to have more
patience when testing changes on the 10.5 branch :)
In any case, thanks a lot to Tiago and Knut Anders for making this improvement
happen!
> 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.
