mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-17 20:42:30 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
mariadb/mysql-test
History
unknown 8c02fad253 Fix wrong memory allocation in SHOW OPEN TABLES 
BUILD/compile-alpha-cxx:
  Fix for Alpha ccc
configure.in:
  Remove not used libraries
mysql-test/r/innodb.result:
  Fix test case
sql/sql_base.cc:
  Fix wrong memory allocation in SHOW OPEN TABLES.
2001-11-08 00:43:27 +02:00
..
include Fix error messages 2001-11-04 15:43:41 +02:00
misc Fixed that LOAD DATA INFILE works with transactions. 2001-08-28 06:43:55 +03:00
r Fix wrong memory allocation in SHOW OPEN TABLES 2001-11-08 00:43:27 +02:00
std_data Remved Gemini code. 2001-10-10 02:50:28 +03:00
t Add timeout for shutdown to mysql-test-run 2001-11-07 23:38:33 +02:00
xml sel000029.xml Escaped &,< chars. 2000-10-18 08:03:55 -05:00
create-test-result Fixed temp tables to work with replication. It will not work if you stop the slave 2000-11-25 23:29:01 -07:00
fix-result post-merge fixes 2001-10-03 15:19:58 -06:00
install_test_db.sh Remved Gemini code. 2001-10-10 02:50:28 +03:00
Makefile.am support for eval_result and let $var = query syntax in mysql-test 2001-06-30 13:08:35 -06:00
mysql-test-run.sh Add timeout for shutdown to mysql-test-run 2001-11-07 23:38:33 +02:00
README Fixed bug in MAX() optimizing for BDB tables 2001-03-10 17:05:10 +02:00
README.gcov fixes for parallel make, re-added the lost README files in mysql-test 2000-12-13 18:23:55 -07:00

README 

This directory contains a test suite for mysql daemon. To run
the currently existing test cases, simply execute ./mysql-test-run in
this directory. It will fire up the newly built mysqld and test it.
Note that you do not have to have to do make install, and you could
actually have a co-existing MySQL installation - the tests will not
conflict with it.

All tests must pass. If one or more of them fail on your system, please
read the following manual section of how to report the problem:

http://www.mysql.com/doc/M/y/MySQL_test_suite.html


You can create your own test cases. To create a test case:

 cd t
 vi test_case_name.test

 in the file, put a set of SQL commands that will create some tables,
 load test data, run some queries to manipulate it.

 We would appreciate if the test tables were called t1, t2, t3 ... (to not
 conflict too much with existing tables).

 Your test should begin by dropping the tables you are going to create and
 end by dropping them again.  This will ensure that one can run the test
 over and over again.
 
 If you are using mysqltest commands (like result file names) in your
 test case you should do create the result file as follows:

 mysql-test-run --record test_case_name

 or

 mysqltest --record < t/test_case_name.test

 If you only have a simple test cases consistent of SQL commands and comments
 you can create the test case one of the following ways:

 mysql-test-run --record test_case_name

 mysql test < t/test_case_name.test > r/test_case_name.result

 mysqltest --record --record-file=r/test_case_name.result < t/test_case_name.test

 When this is done, take a look at r/test_case_name.result
 - If the result is wrong, you have found a bug;  In this case you should
   edit the test result to the correct results so that we can verify
   that the bug is corrected in future releases.

To submit your test case, put your .test file and .result file(s) into
a tar.gz archive, add a README that explains the problem, ftp the 
archive to ftp://support.mysql.com/pub/mysql/secret/ and send  a mail
to bugs@lists.mysql.com