mirror of
https://github.com/MariaDB/server.git
synced 2025-01-17 12:32:27 +01:00
5bf17d04f5
client/mysqltest.c: Auto merged include/mysql.h: Auto merged innobase/dict/dict0dict.c: Auto merged innobase/include/row0mysql.h: Auto merged innobase/lock/lock0lock.c: Auto merged innobase/row/row0mysql.c: Auto merged libmysql/libmysql.c: Auto merged mysql-test/README: Auto merged mysql-test/r/select_found.result: Auto merged mysql-test/t/select_found.test: Auto merged mysys/mf_wcomp.c: Auto merged mysys/mf_wfile.c: Auto merged sql/ha_innodb.cc: Auto merged sql/set_var.cc: Auto merged sql/sql_base.cc: Auto merged configure.in: Get changes for netware include/my_sys.h: Use local file innobase/include/os0file.h: auto merge innobase/os/os0file.c: auto merge sql/mysqld.cc: auto merge sql/sql_acl.cc: indentation change sql/sql_acl.h: use local file sql/sql_class.h: auto merge sql/sql_db.cc: use local file sql/sql_parse.cc: use local file sql/sql_select.cc: Merge sql/sql_show.cc: use local file
58 lines
2.1 KiB
Text
58 lines
2.1 KiB
Text
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://dev.mysql.com/doc/mysql/en/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
|