mariadb

mirror of https://github.com/MariaDB/server.git synced 2025-01-18 21:12:26 +01:00

History

unknown 4637832fa1 Some SHOW VARIABLES have been renamed: collation_client -> character_set_client collation_results -> character_set_results character_set -> character_set_server SET NAMES now doesn't start client->server conversion SET CHARACTER SET now starts both client->server and server->client conversion		2003-05-21 17:44:12 +05:00
..
include	added compress/uncompress function	2003-04-09 20:50:30 -04:00
misc	Fixed that LOAD DATA INFILE works with transactions.	2001-08-28 06:43:55 +03:00
r	Some SHOW VARIABLES have been renamed:	2003-05-21 17:44:12 +05:00
std_data	Resolve merge colflict	2003-05-21 00:12:09 -07:00
t	Some SHOW VARIABLES have been renamed:	2003-05-21 17:44:12 +05:00
create-test-result	new EXPLAIN	2002-09-26 23:08:22 +03:00
fix-result	fixed problem in rpl_log test	2001-11-19 12:03:30 -07:00
install_test_db.sh	Fixed a lot of wrong memory references as reported by valgrind	2003-02-12 21:55:37 +02:00
Makefile.am	- typo fix (replaced blanks with a tab)	2003-03-05 08:13:37 +01:00
mysql-test-run.sh	Scrum task 845. Thi is a behaviour change :	2003-05-15 18:35:39 +02:00
README	Fixes and code cleanups after merge with 4.0.3	2002-10-02 13:33:08 +03:00
README.gcov	fixes for parallel make, re-added the lost README files in mysql-test	2000-12-13 18:23:55 -07:00
resolve-stack	Here comes a nasty patch, although I am not ready to push it yet. I will	2002-01-19 19:16:52 -07:00

README

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://www.mysql.com/doc/M/y/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