mariadb/mysql-test
unknown e842d46efa fixes for parallel make, re-added the lost README files in mysql-test
BUILD/compile-pentium-debug:
  fox for parallel make
BUILD/compile-pentium-gcov:
  fix for parallel make
BUILD/compile-pentium:
  fix to enable parallel make when recursing to subdirectories
Build-tools/Do-all-build-steps:
  fix for parallel make, remove the stale comment to make Tim happy
Build-tools/Do-rpm:
  fix for parallel make
2000-12-13 18:23:55 -07:00
..
include fixed bug in load data infile replication 2000-12-08 07:11:22 -07:00
misc stop chewing! 2000-12-07 08:02:11 -07:00
r fixed 2000-12-13 09:58:26 -07:00
std_data test case for a coredump on merge tables. Sergei or Monty, can you fix this? 2000-12-12 08:24:50 -07:00
t fixed 2000-12-13 09:58:26 -07:00
xml sel000029.xml Escaped &,< chars. 2000-10-18 08:03:55 -05:00
create-test-result Fixed temp tables to work with replication. It will not work if you stop the slave 2000-11-25 23:29:01 -07:00
install_test_db.sh install_test_db.sh fixes for distribution 2000-12-13 10:32:54 -07:00
Makefile.am fixed typo 2000-12-13 17:17:19 -07:00
mysql-test-run.sh install_test_db.sh fixes for distribution 2000-12-13 10:32:54 -07:00
README fixes for parallel make, re-added the lost README files in mysql-test 2000-12-13 18:23:55 -07:00
README.gcov fixes for parallel make, re-added the lost README files in mysql-test 2000-12-13 18:23:55 -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