diff options
author | sasha@mysql.sashanet.com <> | 2000-12-13 18:23:55 -0700 |
---|---|---|
committer | sasha@mysql.sashanet.com <> | 2000-12-13 18:23:55 -0700 |
commit | 7c8773d9a33d8fdfec9046641713c4d68d9699a6 (patch) | |
tree | 5ab0647c2a5502b00ddbacef80efb01f9985737b /mysql-test/README | |
parent | 57c65749dc5920e3726eb791255e79089a1eeda3 (diff) | |
download | mariadb-git-7c8773d9a33d8fdfec9046641713c4d68d9699a6.tar.gz |
fixes for parallel make, re-added the lost README files in mysql-test
Diffstat (limited to 'mysql-test/README')
-rw-r--r-- | mysql-test/README | 29 |
1 files changed, 29 insertions, 0 deletions
diff --git a/mysql-test/README b/mysql-test/README new file mode 100644 index 00000000000..35ab424190e --- /dev/null +++ b/mysql-test/README @@ -0,0 +1,29 @@ +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 + + + |