mariadb/mysql-test
Jon Olav Hauglid 8e154c93ab Followup for Bug #54360 Deadlock DROP/ALTER/CREATE DATABASE
with open HANDLER

Fixes a problem with schema.test visible using embedded server.
The HANDLER was not closed which caused the test to hang.

The problem was not visible if the test was run on a normal server
as the the handler there was implicitly closed by DATABASE DDL
statements doing Events::drop_schema_events().
2010-07-02 11:54:14 +02:00
..
collections Mark parts.partition_alter4_innodb experimental due to Bug 45299. 2010-06-28 09:57:06 +04:00
extra Merge trunk-bugfixing -> trunk-runtime 2010-06-17 17:31:51 +04:00
include Merge trunk-bugfixing -> trunk-runtime 2010-06-17 17:31:51 +04:00
lib Temporary fix for bug#54835 2010-06-30 13:37:03 +02:00
r Followup for Bug #54360 Deadlock DROP/ALTER/CREATE DATABASE 2010-07-02 11:54:14 +02:00
std_data Manual merge of mysql-5.1-bugteam into mysql-trunk-merge. 2010-04-03 21:35:51 +04:00
suite A 5.5 version of the fix for Bug #54360 "Deadlock DROP/ALTER/CREATE 2010-07-01 15:53:46 +02:00
t Followup for Bug #54360 Deadlock DROP/ALTER/CREATE DATABASE 2010-07-02 11:54:14 +02:00
CMakeLists.txt merge 2010-06-18 17:04:15 +02:00
Makefile.am Another incarnation of the patch for Bug#30708 2010-05-19 17:00:23 +04:00
mtr.out-of-source
mysql-stress-test.pl Test suites for engine testing, moved from test-extra so will be available 2010-03-17 23:42:07 -07:00
mysql-test-run.pl WL 5408: automerged bzr bundle from original commit. 2010-06-23 11:17:59 +01:00
purify.supp
README
README.gcov
README.stress
valgrind.supp Merge from mysql-5.1-innodb: 2010-06-01 14:56:22 +03:00

This directory contains a test suite for the 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 for instructions on how to report the
problem:

http://dev.mysql.com/doc/mysql/en/mysql-test-suite.html

If you want to use an already running MySQL server for specific tests,
use the --extern option to mysql-test-run. Please note that in this mode,
the test suite expects you to provide the names of the tests to run.
For example, here is the command to run the "alias" and "analyze" tests
with an external server:

mysql-test-run --extern alias analyze

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

With no test cases named on the command line, mysql-test-run falls back
to the normal "non-extern" behavior. The reason for this is that some
tests cannot run with an external server.


You can create your own test cases. To create a test case, create a new
file in the t subdirectory using a text editor. The file should have a .test
extension. For example:

 xemacs t/test_case_name.test

 In the file, put a set of SQL statements that create some tables,
 load test data, and run some queries to manipulate it.

 We would appreciate it if you name your test tables 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 ensures that you can run the test over
 and over again.
 
 If you are using mysqltest commands (like result file names) in your
 test case, you should 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 consisting of SQL statements and
 comments, you can create the test case in 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 incorrect, 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