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 2006/10/27 22:09:00 UTC
svn commit: r468517 -
/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/nist/readme
Author: djd
Date: Fri Oct 27 13:09:00 2006
New Revision: 468517
URL: http://svn.apache.org/viewvc?view=rev&rev=468517
Log:
DERBY-2007 (partial) Update readme to reflect switch to JUnit for NIST suite.
Modified:
db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/nist/readme
Modified: db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/nist/readme
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/nist/readme?view=diff&rev=468517&r1=468516&r2=468517
==============================================================================
--- db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/nist/readme (original)
+++ db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/nist/readme Fri Oct 27 13:09:00 2006
@@ -12,10 +12,9 @@
The following changes were made:
- no use is made of the NIST testing harness. Instead, suiteable .sql files from
the original sql directory have been placed in a separate (this) directory of
- the Derby functionTests package. The sql scripts are executed by the Derby
- functionTests harness using the Derby interactive sql tool 'ij'.
- Expected output for Derby is placed in the location suitable for the Derby
- functionTests harness. (../../master/*).
+ the Derby functionTests package. The scripts are run using the NistScripts
+ JUnit test.
+ Expected output for Derby is placed in (../../master/*).
- sections of the tests - i.e. selected test cases - not applicable to Derby
have been commented out, for instance all tests using TRIM.
@@ -47,8 +46,8 @@
- exit commands removed from basetab.sql, schema1.sql and schema5.sql (possibly
were not in original scripts)
-- SQL routine creation and call to check if the suite is running with a Java
- SecurityManager added to dml160.sql
+- Constraint names have been added to various constraints to ensure consistent
+ output when running the tests.