Skip to content

Files

Latest commit

author
knielsen@mysql.com
Jan 1, 2006
6b2771f · Jan 1, 2006

History

History

mysql-test

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Dec 22, 2005
Dec 22, 2005
Dec 18, 2005
Jun 23, 2004
Nov 24, 2005
Dec 31, 2005
Dec 22, 2005
Jan 7, 2005
Dec 31, 2005
Jan 1, 2006
Jun 22, 2005
Dec 14, 2000
Oct 18, 2005
Aug 16, 2004
Nov 19, 2001
Nov 10, 2004
Sep 28, 2004
Feb 9, 2005
Oct 27, 2005
Dec 14, 2004
Oct 18, 2005
Dec 22, 2005
Dec 29, 2005
Nov 10, 2005
Jan 20, 2002
May 15, 2005
Nov 23, 2005
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.

If you want to run a test with a running MySQL server use the --extern
option to mysql-test-run. Please note that in this mode the test suite
expects user to specify test names to run. Otherwise it falls back to the
normal "non-extern" behaviour. The reason is that some tests
could not run with external server. Here is the sample command
to test "alias" and "analyze" tests on external server:

mysql-test-run --extern alias analyze

To match your setup you might also need to provide --socket, --user and
other relevant options.

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://dev.mysql.com/doc/mysql/en/MySQL_test_suite.html


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

 xemacs t/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