db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3218) Around 200 (~ 4%) junit fixtures fail when running 10.3 branch (596744) against 10.3.1.4 derbyTesting.jar using junit-all-codeline-jars
Date Wed, 28 Nov 2007 22:08:43 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546431
] 

Daniel John Debrunner commented on DERBY-3218:
----------------------------------------------

Would be useful if the test changes made could be kept so that the tests could be run against
future 10.3 versions.

One way to do this would be to create a 10.3.1.4_test branch that is a snapshot of the 10.3
branch at the point 10.3.1.4 was made and then only allow test changes to accommodate changes
made in later 10.3 releases. Then anyone could build the tests from 10.3.1.4_test with required
changes and run the junit tests against 10.3.x.

Since branches are cheap in subversion this should be easy.

> Around 200 (~ 4%) junit fixtures fail when running 10.3 branch (596744) against 10.3.1.4
derbyTesting.jar using junit-all-codeline-jars
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3218
>                 URL: https://issues.apache.org/jira/browse/DERBY-3218
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.3.1.5
>            Reporter: Daniel John Debrunner
>            Priority: Minor
>         Attachments: TEST-org.apache.derbyTesting.functionTests.tests.derbynet._Suite.xml,
TEST-org.apache.derbyTesting.functionTests.tests.jdbcapi._Suite.xml, TEST-org.apache.derbyTesting.functionTests.tests.lang._Suite.xml,
TEST-org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite.xml
>
>
> Investigate reason for failures.
> derbyTesting.jar from 10.3.1.4 can be seen as an existing application that ideally should
work when run against a newer version.
> Some failures might be due to valid reasons such as change in SQL States.
> Significant number of the failures seem to be due to the inability of the junit clean
database code to drop a schema due to it not being empty.
> AutoLoadTest failing can be ignored, it failed against 10.3.1.4 and has now been fixed
(as a test bug) in 10.3.

-- 
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