|
 |
2aefdf |
Improve the documentation that will be installed in the mysql-test RPM.
|
|
|
2aefdf |
|
|
|
2aefdf |
|
|
|
2aefdf |
diff -Naur mysql-5.5.20.orig/mysql-test/README mysql-5.5.20/mysql-test/README
|
|
|
2aefdf |
--- mysql-5.5.20.orig/mysql-test/README 2011-12-16 14:52:05.000000000 -0500
|
|
|
2aefdf |
+++ mysql-5.5.20/mysql-test/README 2012-02-10 17:06:19.531082253 -0500
|
|
|
2aefdf |
@@ -1,14 +1,26 @@
|
|
|
2aefdf |
This directory contains a test suite for the MySQL daemon. To run
|
|
|
2aefdf |
-the currently existing test cases, simply execute ./mysql-test-run in
|
|
|
2aefdf |
-this directory. It will fire up the newly built mysqld and test it.
|
|
|
2aefdf |
+the currently existing test cases, execute ./mysql-test-run in
|
|
|
2aefdf |
+this directory.
|
|
|
2aefdf |
|
|
|
2aefdf |
-Note that you do not have to have to do "make install", and you could
|
|
|
2aefdf |
-actually have a co-existing MySQL installation. The tests will not
|
|
|
2aefdf |
-conflict with it.
|
|
|
2aefdf |
-
|
|
|
2aefdf |
-All tests must pass. If one or more of them fail on your system, please
|
|
|
2aefdf |
-read the following manual section for instructions on how to report the
|
|
|
2aefdf |
-problem:
|
|
|
2aefdf |
+For use in Red Hat distributions, you should run the script as user mysql,
|
|
|
2aefdf |
+so the best bet is something like
|
|
|
2aefdf |
+ cd /usr/share/mysql-test
|
|
|
2aefdf |
+ sudo -u mysql ./mysql-test-run --skip-test-list=platform-specific-tests.list
|
|
|
2aefdf |
+This will use the installed mysql executables, but will run a private copy
|
|
|
2aefdf |
+of the server process (using data files within /usr/share/mysql-test),
|
|
|
2aefdf |
+so you need not start the mysqld service beforehand.
|
|
|
2aefdf |
+
|
|
|
2aefdf |
+The "--skip-test-list=platform-specific-tests.list" option excludes tests that are
|
|
|
2aefdf |
+known to fail on one or more Red-Hat-supported platforms. You can omit it
|
|
|
2aefdf |
+if you want to check whether such failures occur for you. Documentation
|
|
|
2aefdf |
+about the reasons for omitting such tests can be found in the file
|
|
|
2aefdf |
+platform-specific-tests.list.
|
|
|
2aefdf |
+
|
|
|
2aefdf |
+To clean up afterwards, remove the created "var" subdirectory, eg
|
|
|
2aefdf |
+ sudo -u mysql rm -rf /usr/share/mysql-test/var
|
|
|
2aefdf |
+
|
|
|
2aefdf |
+If one or more tests fail on your system, please read the following manual
|
|
|
2aefdf |
+section for instructions on how to report the problem:
|
|
|
2aefdf |
|
|
|
2aefdf |
http://dev.mysql.com/doc/mysql/en/mysql-test-suite.html
|
|
|
2aefdf |
|
|
|
2aefdf |
@@ -25,7 +37,8 @@
|
|
|
2aefdf |
|
|
|
2aefdf |
With no test cases named on the command line, mysql-test-run falls back
|
|
|
2aefdf |
to the normal "non-extern" behavior. The reason for this is that some
|
|
|
2aefdf |
-tests cannot run with an external server.
|
|
|
2aefdf |
+tests cannot run with an external server (because they need to control the
|
|
|
2aefdf |
+options with which the server is started).
|
|
|
2aefdf |
|
|
|
2aefdf |
|
|
|
2aefdf |
You can create your own test cases. To create a test case, create a new
|