- 4 Writing Test Cases
- 4.1 Writing a Test Case: Quick Start
- 4.2 Test Case Coding Guidelines
- 4.3 Sample Test Case
- 4.4 Cleaning Up from a Previous Test Run
- 4.5 Generating a Test Case Result File
- 4.6 Checking for Expected Errors
- 4.7 Controlling the Information Produced by a Test Case
- 4.8 Dealing with Output That Varies Per Test Run
- 4.9 Passing Options from mysql-test-run.pl to mysqld or mysqltest
- 4.10 Specifying Test Case-Specific Server Options
- 4.11 Using Include Files to Simplify Test Cases
- 4.12 Controlling the Binary Log Format Used for Tests
- 4.13 Writing Replication Tests
- 4.14 Thread Synchronization in Test Cases
- 4.15 Other Tips for Writing Test Cases
Within a test case, many system variables can be set by using statements such as these:
SET sql_warnings=1; SET sql_mode='NO_AUTO_VALUE_ON_ZERO';
But sometimes you need to restart the server to use command-line
options that are specific to a given test case. You can specify
these options in a file named
mysql-test/t/.
When a file named
test_name-master.optt/
exists, mysql-test-run.pl examines it for extra
options that the server needs to be run with when executing the
test_name-master.opttest_name test case. If no server has
yet been started or the current server is running with different
options, mysql-test-run.pl restarts the server
with the new options.
Files in the mysql-test/t directory with
names ending in -slave.opt and
-im.opt are similar, but they are used for
slave servers and the Instance Manager, respectively.
