mirror of
https://github.com/MariaDB/server.git
synced 2025-10-31 15:50:51 +03:00
d69250a969
Warning handling and initial prepared statement handling (last not complete yet) Changed a lot of functions that returned 0/1 to my_bool type. GRANT handling now uses read/write locks instead of mutex Change basic net functions to use THD instead of NET (needed for 4.1 protocol) Use my_sprintf instead of sprintf() + strlen() Added alloc_query() to be able to chare query initialization code with prepared statements. Cleanup handling of SHOW COUNT(*) WARNINGS and SELECT LAST_INSERT_ID() Note that the following test fails (will be fixed ASAP): sub_select, union, rpl_rotate_logs and rpl_mystery22
59 lines
2.1 KiB
Plaintext
59 lines
2.1 KiB
Plaintext
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 the test with a running MySQL server use the --external
|
|
option to mysql-test-run.
|
|
|
|
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:
|
|
|
|
xeamacs 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
|