Test suites for engine testing, moved from test-extra so will be available

for general use.


mysql-test/Makefile.am:
  Adding directories of additional test suites
mysql-test/mysql-stress-test.pl:
  Adding check for additional errors checking during test run

mysql-test/Makefile.am

@@ -99,7 +99,11 @@ TEST_DIRS = t r include std_data std_data/parts collections \
 	suite/ndb suite/ndb/t suite/ndb/r \
 	suite/rpl_ndb suite/rpl_ndb/t suite/rpl_ndb/r \
 	suite/parts suite/parts/t suite/parts/r suite/parts/inc \
-	suite/innodb suite/innodb/t suite/innodb/r suite/innodb/include
+	suite/innodb suite/innodb/t suite/innodb/r suite/innodb/include \
+	suite/engines suite/engines/funcs suite/engines/iuds suite/engines/rr_trx \
+	suite/engines/funcs/r suite/engines/funcs/t suite/engines/iuds/r \
+	suite/engines/iuds/t suite/engines/rr_trx/include suite/engines/rr_trx/r \
+	suite/engines/rr_trx/t
 
 # Used by dist-hook and install-data-local to copy all
 # test files into either dist or install directory

mysql-test/mysql-stress-test.pl

@@ -122,8 +122,8 @@ $opt_threads=1;
 $pid_file="mysql_stress_test.pid";
 $opt_mysqltest= ($^O =~ /mswin32/i) ? "mysqltest.exe" : "mysqltest";
 $opt_check_tests_file="";
-# OBM adding a setting for 'max-connect-retries=7' the default of 500 is to high  
-@mysqltest_args=("--silent", "-v", "--skip-safemalloc", "--max-connect-retries=7");
+# OBM adding a setting for 'max-connect-retries=20' the default of 500 is to high  
+@mysqltest_args=("--silent", "-v", "--skip-safemalloc", "--max-connect-retries=20");
 
 # Client ip address
 $client_ip=inet_ntoa((gethostbyname(hostname()))[4]);
@@ -150,7 +150,12 @@ $client_ip=~ s/\.//g;
                             
 %error_strings = ( 'Failed in mysql_real_connect()' => S1,
                    'Can\'t connect' => S1,       
-                   'not found (Errcode: 2)' => S1 );
+                   'not found (Errcode: 2)' => S1,
+                   'does not exist' => S1,
+                   'Could not open connection \'default\' after \d+ attempts' => S1,
+                   'wrong errno ' => S3,
+                   'Result length mismatch' => S4,
+                   'Result content mismatch' => S4);
   
 %error_codes = ( 1012 => S2, 1015 => S2, 1021 => S2,
                  1027 => S2, 1037 => S2, 1038 => S2,

mysql-test/suite/engines/README

+
+
+
+This directory includes a set of three test suites aimed as testing functionality
+in an engine independent way, that is - the tests should work identically against
+different engines.
+
+
+The following suites are included:
+
+1) 'funcs' suite
+   -------------
+   A collection of functional tests covering basic engine and server functionality that can be run
+   against iany engine.
+
+   To run the test suite:
+      cd INSTALL_DIR/mysql-test
+      run: perl ./mysql-test-run.pl --suite=engines/funcs --mysqld=--default-storage-engine=<engine>
+
+2) 'iuds' suite
+   ------------
+   Similar to the above focused on insert/update/delete operations of different different data types.
+
+   To run the test suite:
+      cd INSTALL_DIR/mysql-test
+      run: perl ./mysql-test-run.pl --suite=engines/iuds --mysqld=--default-storage-engine=<engine>
+
+3) 'rr_trx' suite (transactional engines only)
+   --------------
+   A scenario of multiple client connections verifying transactions with repeatable read isolation level
+
+   To run the test suite with innodb:
+      cd INSTALL_DIR/mysql-test
+      run: perl ./suite/engines/rr_trx/run_stress_tx_rr.pl --engine=<engine> [--duration=<nn>]
+                                                          [--threads=<nn>] [--try] [--help] 
+
+   This test is can be run against any transactional engine. However scripts need to be modified in order
+   to support such engines (current scripts support only InnoDB).
+   In order to add support for a new engine, you will need to modify scripts as follows:
+   1) cd to INSTALL_DIR/mysql-test/suite/engines/rr_trx
+   2) Modify the 'run_stress_rr.pl' file by adding an 'elsif' section for your engine and have it
+      include specific values required to be passed as startup parameters to the MySQL server by
+      specifying them using "--mysqld" options (see InnoDB example).
+   3) Copy the 'init_innodb.txt' file to 'init_<engine>.txt file and change its content to be "init_<engine>".
+   4) In the 't' directory copy the "init_innodb.test" file to "init_<engine>.test" and change the value of
+      the '$engine' variable to <engine>.
+   5) In the 'r' directory copy "the init_innodb.result" file to "init_<engine>.result" and change refrences
+      to 'InnoDB' to <engine>.
+
+
+Known Issues
+------------
+1) The 'funcs' and 'iuds' suites currently runs only against MySQL 5.1 server.
+   Running them against MySQL 5.5 will generate errors.
+
+2) The folowing tests in the 'iuds' suite:
+     - delete_decimal
+     - insert_decimal 
+     - update_decimal
+   will return a 'Warning 1264 - Out of range value...' warning if run in a 32-bit environment.
+   Add the '--force' option to prevent the test run from aborting.
+
+3) The following tests in the 'funcs' suite will fail when run against the innodb_plugin:
+   - crash_manycolumns_string (bug 50495) 
+   - ix_unique_lob (bug 52056, masked by an 'Out of memory error' on some 32-bit platforms)
+   - ix_unique_string_length (bug 52056, masked by an 'Out of memory error' on some 32-bit platforms)
+   Add the '--force' option to prevent the test run from aborting.
+
+4) Some of the rpl_xxx tests in the 'funcs' suite require a secific binlog_forat setting and will be
+   skipped otherwise.
+ 

mysql-test/suite/engines/funcs/r/an_calendar.result

+DROP TABLE IF EXISTS t1;
+CREATE TABLE t1(c1 DATE NULL, c2 DATE NULL);
+SET TIMESTAMP=1171346973;
+INSERT INTO t1 VALUES(NOW(),NOW());
+Warnings:
+Note	1265	Data truncated for column 'c1' at row 1
+Note	1265	Data truncated for column 'c2' at row 1
+INSERT INTO t1 VALUES(NOW(),NOW());
+Warnings:
+Note	1265	Data truncated for column 'c1' at row 1
+Note	1265	Data truncated for column 'c2' at row 1
+ANALYZE TABLE t1;
+Table	Op	Msg_type	Msg_text
+test.t1	analyze	status	OK
+DROP TABLE t1;
+CREATE TABLE t1(c1 TIME NULL, c2 TIME NULL);
+SET TIMESTAMP=1171346973;
+INSERT INTO t1 VALUES(NOW(),NOW());
+INSERT INTO t1 VALUES(NOW(),NOW());
+ANALYZE TABLE t1;
+Table	Op	Msg_type	Msg_text
+test.t1	analyze	status	OK
+DROP TABLE t1;
+CREATE TABLE t1(c1 DATETIME NULL, c2 DATETIME NULL);
+SET TIMESTAMP=1171346973;
+INSERT INTO t1 VALUES(NOW(),NOW());
+INSERT INTO t1 VALUES(NOW(),NOW());
+ANALYZE TABLE t1;
+Table	Op	Msg_type	Msg_text
+test.t1	analyze	status	OK
+DROP TABLE t1;
+CREATE TABLE t1(c1 TIMESTAMP NULL, c2 TIMESTAMP NULL);
+SET TIMESTAMP=1171346973;
+INSERT INTO t1 VALUES(NOW(),NOW());
+INSERT INTO t1 VALUES(NOW(),NOW());
+ANALYZE TABLE t1;
+Table	Op	Msg_type	Msg_text
+test.t1	analyze	status	OK
+DROP TABLE t1;