mirror/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-01-19 05:22:25 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
mariadb/mysql-test
History
unknown 64cad16faa Post-fix of bug #302 fix. 
Fixed bug #320.
Some new tests and cosmetic changes.
Another strcasecmp() replaced.


mysql-test/r/sp.result:
  Moved SP tests from subselect and added some more.
mysql-test/r/subselect.result:
  Moved SP tests to sp.test.
mysql-test/t/sp.test:
  Moved SP tests from subselect and added some more.
mysql-test/t/subselect.test:
  Moved SP tests to sp.test.
sql/sp.cc:
  Don't close derived tables.
sql/sp_head.cc:
  Minor layout and comment fix.
sql/sp_head.h:
  Minor comment fix.
sql/sql_derived.cc:
  Don't set org_table_list->derived to 1 when debugging, as this breaks certain
  subselect args to SPs.
sql/sql_parse.cc:
  Post-fix of bugfix (free memory on error), and added comment.
sql/sql_yacc.yy:
  Another strcasecmp() replaced.
2003-04-27 17:35:54 +02:00
..
include added compress/uncompress function 2003-04-09 20:50:30 -04:00
misc
r Post-fix of bug #302 fix. 2003-04-27 17:35:54 +02:00
std_data Merge with 4.0 2003-04-03 21:19:12 +03:00
t Post-fix of bug #302 fix. 2003-04-27 17:35:54 +02:00
create-test-result new EXPLAIN 2002-09-26 23:08:22 +03:00
fix-result
install_test_db.sh Most of the groundwork for sprint task 729 (implement FUNCTIONs). 2003-02-21 17:37:05 +01:00
Makefile.am - typo fix (replaced blanks with a tab) 2003-03-05 08:13:37 +01:00
mysql-test-run.sh Merge with 4.0 2003-03-16 19:17:54 +02:00
README Fixes and code cleanups after merge with 4.0.3 2002-10-02 13:33:08 +03:00
README.gcov
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