1
0
mirror of https://github.com/MariaDB/server.git synced 2025-09-02 09:41:40 +03:00
Files
mariadb/mysql-test
sasha@mysql.sashanet.com d9d49dfa44 client/mysqltest.c
fixed bug that created empty result files in no-record mode
mysql-test/t/rpl000007.test
    testing non-replication of load data infile when the table is excluded from replication
mysql-test/t/rpl000016.test
    test purge master logs
sql/slave.cc
    fix memory leaks found by  purge master logs test
sql/sql_repl.cc
    fixed race condition and delete before close bug in reset_slave()

Overall comments - coverage testing is a very good thing!
2000-12-14 20:17:18 -07:00
..
2000-12-07 08:02:11 -07:00
2000-12-14 17:43:13 -07:00
2000-12-14 20:17:18 -07:00
2000-10-18 08:03:55 -05:00
2000-12-13 17:17:19 -07:00
2000-12-14 10:05:04 -07:00

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
report the details to bugs@lists.mysql.com

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.

 then do ./mysql-test-run -record test_case_name
 and look at r/test_case_name.result - edit the result if necessary. If you
 have to edit it, you have found a bug.

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