mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-23 15:24:16 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
mariadb/mysql-test
History
monty@mysql.com 3fb088a075 Add 0x before pointers (to help with debugging) 
Add support for VARCHAR with 1 or 2 length bytes
Enable VARCHAR packing in MyISAM files (previous patch didn't pack data properly)
Give error if we got problems in temporary tables during a SELECT
Don't use new table generated by ALTER TABLE if index generation fails
Fixed wrong call by range_end() (Could cause an ASSERT in debug mode)
2004-12-18 05:19:21 +02:00
..
include Add 0x before pointers (to help with debugging) 2004-12-18 05:19:21 +02:00
misc
ndb ndbcluster.sh: 2004-11-11 11:08:37 +00:00
r Add 0x before pointers (to help with debugging) 2004-12-18 05:19:21 +02:00
std_data Update results for new varchar handling 2004-12-07 15:47:00 +02:00
t Add 0x before pointers (to help with debugging) 2004-12-18 05:19:21 +02:00
create-test-result
fix-result
init_db.sql replaced init_db.sql 2004-11-10 15:03:59 +05:00
install_test_db.sh
Makefile.am merge with 4.0 2004-11-12 11:17:53 +02:00
my_manage.c mysql_test_run_new.c, my_manage.h, my_manage.c: 2004-11-09 20:21:37 +01:00
my_manage.h mysql_test_run_new.c, my_manage.h, my_manage.c: 2004-11-09 20:21:37 +01:00
mysql-test-run.sh Merge with 4.1 2004-12-06 11:38:56 +02:00
mysql_test_run_new.c mysql_test_run_new.c, my_manage.h, my_manage.c: 2004-11-09 20:21:37 +01:00
README
README.gcov
resolve-stack

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://dev.mysql.com/doc/mysql/en/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