You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by dj...@apache.org on 2007/11/29 00:10:03 UTC
svn commit: r599190 -
/db/derby/code/branches/10.3.1.4_test/README_10_3_1_4_test.txt
Author: djd
Date: Wed Nov 28 15:10:02 2007
New Revision: 599190
URL: http://svn.apache.org/viewvc?rev=599190&view=rev
Log:
Add top-level README for the test branch 10.3.1.4_test
Added:
db/derby/code/branches/10.3.1.4_test/README_10_3_1_4_test.txt (with props)
Added: db/derby/code/branches/10.3.1.4_test/README_10_3_1_4_test.txt
URL: http://svn.apache.org/viewvc/db/derby/code/branches/10.3.1.4_test/README_10_3_1_4_test.txt?rev=599190&view=auto
==============================================================================
--- db/derby/code/branches/10.3.1.4_test/README_10_3_1_4_test.txt (added)
+++ db/derby/code/branches/10.3.1.4_test/README_10_3_1_4_test.txt Wed Nov 28 15:10:02 2007
@@ -0,0 +1,27 @@
+10.3.1.4_test is a branch based upon the 10.3.1.4 code
+(10.3 branch, revision 561794).
+
+This is to allow modification of and building derbyTesting.jar in
+order to run the 10.3.1.4 junit tests against later 10.3 releases.
+This allows testing of the backwards compatability by having
+the 10.3.1.4 tests mimic an users application.
+Changes are only made in this branch to testing code.
+Such changes are to allow error free test runs when Derby's
+behaviour has changed in an acceptable manor.
+Examples might be:
+ - the expected SQL state thrown by a statement
+ - fixes for test failures for tests not passing at the original revision
+ - Removal of/changes to bug workarounds in the tests
+
+Ideally changes would be 'svn merge'd in from testing changes
+in the 10.3 branch. Changes should be resticted to java/testing
+or other testing related files.
+
+General idea is to build the jars with this codeline and then
+run the junit tests with derbyTesting.jar from this codeline
+and all the other jars from the later version or release candidate.
+
+The tests can be run by running suites.All or through the junit targets.
+
+Junit tests in theory should be easier to run against newer versions
+as they do not rely on diff'ing output.
Propchange: db/derby/code/branches/10.3.1.4_test/README_10_3_1_4_test.txt
------------------------------------------------------------------------------
svn:eol-style = native