From 587387f5d0af6a4381c99bc3da4f87bae63f5cef Mon Sep 17 00:00:00 2001 From: unknown Date: Sat, 16 Dec 2000 01:17:13 +0200 Subject: Configure updates Fixed my_print_defaults --no-defaults Docs/manual.texi: Updated changelog acinclude.m4: Patches for large file support configure.in: New TCP libwrap extra/my_print_defaults.c: Fixed that --no-defaults include/my_pthread.h: Fixes for Tru64 ltconfig: Fixes for Tru64 ltmain.sh: Fixes for Tru64 mysql-test/README: Fixed types mysql-test/mysql-test-run.sh: Changed to long options --- mysql-test/README | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) (limited to 'mysql-test/README') diff --git a/mysql-test/README b/mysql-test/README index f33218b617c..ca7284d173a 100644 --- a/mysql-test/README +++ b/mysql-test/README @@ -22,14 +22,20 @@ You can create your own test cases. To create a test case: 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 < t/test_case_name.test + 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 < t/test_case_name.test > r/test_case_name.result + mysql-test-run --record test_case_name + + mysql test < t/test_case_name.test > r/test_case_name.result - mysql-test-run --record --record-file=r/test_case_name.result < t/test_case_name.test + 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 -- cgit v1.2.1