From 92a3aedc05dd07e1d00986f237a2097af595e584 Mon Sep 17 00:00:00 2001 From: unknown Date: Thu, 4 Jan 2001 02:56:38 +0200 Subject: Fixes to get mysql-test-run more portable Docs/manual.texi: More examples based on user comments client/mysqltest.c: Added --sleep and --tmpdir mysql-test/README: Update mysql-test/include/master-slave.inc: Fixed to not be dependent on path to sockets mysql-test/install_test_db.sh: Added privilege for hostname% mysql-test/mysql-test-run.sh: Portability fixes + a lot of new options mysql-test/r/bigint.result: Made test portable mysql-test/t/bigint.test: Made test portable mysql-test/t/rpl000008.test: Changed sleeptime mysql-test/t/rpl000012.test: Fixed to not be dependent on path to sockets mysql-test/t/rpl000013.test: Fixed to not be dependent on path to sockets mysql-test/t/rpl000014.test: Fixed to not be dependent on path to sockets mysql-test/t/rpl000015.test: Fixed to not be dependent on path to sockets mysql-test/t/rpl000016.test: Fixed to not be dependent on path to sockets --- mysql-test/README | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'mysql-test/README') diff --git a/mysql-test/README b/mysql-test/README index ca7284d173a..6ad59ea6a8b 100644 --- a/mysql-test/README +++ b/mysql-test/README @@ -18,6 +18,10 @@ You can create your own test cases. To create a test case: 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: -- cgit v1.2.1