You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
unknown 4958eec7ec Added sql_mode PAD_CHAR_TO_FULL_LENGTH (WL#921) 19 years ago
..
extra Fixed federated and some replication tests to not stop slave until it's up and running. 19 years ago
include Merge romeo.(none):/home/bkroot/mysql-5.1-rpl 19 years ago
lib Small fixes for merge. 19 years ago
misc WL#1717 "binlog/innodb consistency". 22 years ago
ndb minor fix of ndb cluster startup script 19 years ago
r Added sql_mode PAD_CHAR_TO_FULL_LENGTH (WL#921) 19 years ago
std_data Merge bk-internal.mysql.com:/home/bk/mysql-5.1-new-rpl 19 years ago
suite Merge mysql.com:/tmp/mysql-5.0-build 19 years ago
t Added sql_mode PAD_CHAR_TO_FULL_LENGTH (WL#921) 19 years ago
Makefile.am Merge pilot.blaudden:/home/msvensson/mysql/bug20166/my50-bug20166 19 years ago
README README: 20 years ago
README.gcov README.gcov: 20 years ago
README.stress mysql-stress-test.pl, README.stress: 20 years ago
create-test-result fixed problem spoted by Vladimir V. Kolpakov 21 years ago
fix-result fixed problem in rpl_log test 24 years ago
install_test_db.sh Merge mysql.com:/home/kent/bk/tmp/mysql-5.0-build 19 years ago
mysql-stress-test.pl mysql-stress-test.pl, README.stress: 20 years ago
mysql-test-run-shell.sh Merge shakedown.(none):/home/jpipes/dev/bug21970/my50-bug21970 19 years ago
mysql-test-run.pl Clear field_alloc when it's moved to result set (allows us to always call free_root on field_alloc) 19 years ago
purify.supp Fixed compiler warnings 19 years ago
resolve-stack Here comes a nasty patch, although I am not ready to push it yet. I will 24 years ago
valgrind.supp Added back sql-bench directory, so that one can more easily run benchmarks on a server and add new benchmarks for new optimizations 19 years ago

README

This directory contains a test suite for the 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
read the following manual section for instructions on how to report the
problem:

http://dev.mysql.com/doc/mysql/en/mysql-test-suite.html

If you want to use an already running MySQL server for specific tests,
use the --extern option to mysql-test-run. Please note that in this mode,
the test suite expects you to provide the names of the tests to run.
For example, here is the command to run the "alias" and "analyze" tests
with an external server:

mysql-test-run --extern alias analyze

To match your setup, you might also need to provide --socket, --user, and
other relevant options.

With no test cases named on the command line, mysql-test-run falls back
to the normal "non-extern" behavior. The reason for this is that some
tests cannot run with an external server.


You can create your own test cases. To create a test case, create a new
file in the t subdirectory using a text editor. The file should have a .test
extension. For example:

xemacs t/test_case_name.test

In the file, put a set of SQL statements that create some tables,
load test data, and run some queries to manipulate it.

We would appreciate it if you name your test tables 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 ensures that you can run the test over
and over again.

If you are using mysqltest commands (like result file names) in your
test case, you should 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 consisting of SQL statements and
comments, you can create the test case in 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 incorrect, 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