2006-03-27 19:54:58 +00:00
|
|
|
mysql's idea of a suitable place to install the regression tests is
|
|
|
|
/usr/mysql-test. To relocate this to a reasonably FHS-compliant place
|
2009-03-05 02:50:07 +00:00
|
|
|
like /usr/share/mysql-test, we have to hack up the paths in mtr_cases.pm.
|
2007-02-09 20:32:52 +00:00
|
|
|
This patch also improves the documentation a tad.
|
2006-03-27 19:54:58 +00:00
|
|
|
|
|
|
|
|
2009-01-14 17:10:05 +00:00
|
|
|
diff -Naur mysql-5.1.30.orig/mysql-test/README mysql-5.1.30/mysql-test/README
|
|
|
|
--- mysql-5.1.30.orig/mysql-test/README 2008-11-14 11:34:38.000000000 -0500
|
|
|
|
+++ mysql-5.1.30/mysql-test/README 2009-01-13 11:30:00.000000000 -0500
|
2008-08-23 20:31:19 +00:00
|
|
|
@@ -6,6 +6,19 @@
|
2006-05-02 03:37:40 +00:00
|
|
|
actually have a co-existing MySQL installation. The tests will not
|
|
|
|
conflict with it.
|
2006-03-27 19:54:58 +00:00
|
|
|
|
|
|
|
+For use in Red Hat distributions, you should run the script as user mysql,
|
|
|
|
+so the best bet is something like
|
|
|
|
+ cd /usr/share/mysql-test
|
|
|
|
+ sudo -u mysql ./mysql-test-run
|
|
|
|
+This will use the installed mysql executables, but will run a private copy
|
|
|
|
+of the server process (using data files within /usr/share/mysql-test),
|
2008-07-27 17:54:30 +00:00
|
|
|
+so you need not start the mysqld service beforehand. If you have not
|
|
|
|
+installed mysql-cluster, use
|
|
|
|
+ sudo -u mysql ./mysql-test-run --skip-ndbcluster
|
2008-08-23 20:31:19 +00:00
|
|
|
+to skip the cluster-related tests. To clean up afterwards, remove the
|
|
|
|
+created "var" subdirectory, eg
|
|
|
|
+ sudo -u mysql rm -rf /usr/share/mysql-test/var
|
2006-03-27 19:54:58 +00:00
|
|
|
+
|
2006-05-02 03:37:40 +00:00
|
|
|
All tests must pass. If one or more of them fail on your system, please
|
|
|
|
read the following manual section for instructions on how to report the
|
|
|
|
problem:
|
2008-08-23 20:31:19 +00:00
|
|
|
@@ -25,7 +38,8 @@
|
2006-03-27 19:54:58 +00:00
|
|
|
|
2006-05-02 03:37:40 +00:00
|
|
|
With no test cases named on the command line, mysql-test-run falls back
|
|
|
|
to the normal "non-extern" behavior. The reason for this is that some
|
|
|
|
-tests cannot run with an external server.
|
|
|
|
+tests cannot run with an external server (because they need to control the
|
|
|
|
+options with which the server is started).
|
|
|
|
|
|
|
|
|
|
|
|
You can create your own test cases. To create a test case, create a new
|
2009-03-05 02:50:07 +00:00
|
|
|
diff -Naur mysql-5.1.32.orig/mysql-test/lib/mtr_cases.pm mysql-5.1.32/mysql-test/lib/mtr_cases.pm
|
|
|
|
--- mysql-5.1.32.orig/mysql-test/lib/mtr_cases.pm 2009-02-13 19:52:34.000000000 -0500
|
|
|
|
+++ mysql-5.1.32/mysql-test/lib/mtr_cases.pm 2009-03-04 20:34:23.000000000 -0500
|
|
|
|
@@ -228,7 +228,9 @@
|
|
|
|
else
|
|
|
|
{
|
|
|
|
$suitedir= my_find_dir($::basedir,
|
|
|
|
- ["mysql-test/suite",
|
|
|
|
+ ["share/mysql-test/suite",
|
|
|
|
+ "share/mysql-test",
|
|
|
|
+ "mysql-test/suite",
|
|
|
|
"mysql-test",
|
|
|
|
# Look in storage engine specific suite dirs
|
|
|
|
"storage/*/mysql-test-suites"
|