[
https://issues.apache.org/jira/browse/DERBY-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren resolved DERBY-1952.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.0.0
Looks fixed to me.
> Remove the running of JUnit tests from the old derby test harness to allow
> faster conversion to a pure-Junit world.
> -------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1952
> URL: https://issues.apache.org/jira/browse/DERBY-1952
> Project: Derby
> Issue Type: Test
> Components: Test
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
> Fix For: 10.3.0.0
>
>
> Assuming we had a top-level JUnit suite that ran all the Junit tests
> successfully (with the same configuration coverage as they are run today
> in derbyall) switch to a dual testing environment until
> all the tests were converted to JUnit. This would include removing all
> the JUnit tests from the old harness suite files.
> That is if one wanted to run all the tests one would have to run:
> derbyall with the old harness
> suites.All using JUnit test runners directly.
> Discussion thread is:
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200610.mbox/[EMAIL
> PROTECTED]
> Since no objections have been raised I will make progress on this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
