[
https://issues.apache.org/jira/browse/DERBY-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-4638:
--------------------------------------
Issue & fix info: [Patch Available]
I have run suites.All on Java 6 and on Java 1.4.2 and verified that all the
tests still run, and that the suites that need to be added using reflection on
1.4.2 (because they are compiled with target level 1.5 or higher) don't cause
any problems with these changes.
I've also run the replication test on phoneME to verify that moving the check
of the JDBC level didn't cause problems. Before the change, the suite() method
failed with a NoClassDefFoundError. After the change, suite() returned
successfully (but didn't add any tests, as expected).
> 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
> Attachments: 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.
