- 12.3 Manual Pages
- 12.3.1 MySQL Utilities Overview — Brief overview of command-line utilities
- 12.3.2 mut — MySQL Utilities Testing
- 12.3.3 mysqldbcompare — Compare Two Databases and Identify Differences
- 12.3.4 mysqldbcopy — Copy Database Objects Between Servers
- 12.3.5 mysqldbexport — Export Object Definitions or Data from a Database
- 12.3.6 mysqldbimport — Import Object Definitions or Data into a Database
- 12.3.7 mysqldiff — Identify Differences Among Database Objects
- 12.3.8 mysqldiskusage — Show Database Disk Usage
- 12.3.9 mysqlfailover — Automatic replication health monitoring and failover
- 12.3.10 mysqlindexcheck — Identify Potentially Redundant Table Indexes
- 12.3.11 mysqlmetagrep — Search Database Object Definitions
- 12.3.12 mysqlprocgrep — Search Server Process Lists
- 12.3.13 mysqlreplicate — Set Up and Start Replication Between Two Servers
- 12.3.14 mysqlrpladmin — Administration utility for MySQL replication
- 12.3.15 mysqlrplcheck — Check Replication Prerequisites
- 12.3.16 mysqlrplshow — Show Slaves for Master Server
- 12.3.17 mysqlserverclone — Clone Existing Server to Create New Server
- 12.3.18 mysqlserverinfo — Display Common Diagnostic Information from a Server
- 12.3.19 mysqluserclone — Clone Existing User to Create New User
This utility executes predefined tests to test the MySQL
Utilities. The tests are located under the
/mysql-test directory and divided into suites
(stored as folders). By default, all tests located in the
/t folder are considered the ‘main’ suite.
You can select any number of tests to run, select one or more suites to restrict the tests, exclude suites and tests, and specify the location of the utilities and tests.
The utility requires the existence of at least one server to clone for testing purposes. You must specify at least one server, but you may specify multiple servers for tests designed to use additional servers.
The utility has a special test suite named ‘performance’ where
performance-related tests are placed. This suite is not included
by default and must be specified with the
--suite option to execute the
performance tests.
OPTIONS
mut accepts the following command-line options:
-
Specify how much information to display. Use this option multiple times to increase the amount of information. For example,
-v= verbose,-vv= more verbose,-vvv= debug. To diagnose test execution problems, use-vvvto display the actual results of test cases and ignore result processing.
NOTES
The connection specifier must name a valid account for the server.
Any test named ???_template.py is skipped. This enables the developer to create a base class to import for a collection of tests based on a common code base.
EXAMPLES
The following example demonstrates how to invoke mut to execute a subset of the tests using an existing server which is cloned. The example displays the test name, status, and relative time:
$ python mut --server=root@localhost --do-tests=clone_user --width=70 MySQL Utilities Testing - MUT Parameters used: Display Width = 70 Sorted = True Force = False Test directory = './t' Utilities directory = '../scripts' Starting port = 3310 Test wildcard = 'clone_user%' Servers: Connecting to localhost as user root on port 3306: CONNECTED ---------------------------------------------------------------------- TEST NAME STATUS TIME ====================================================================== main.clone_user [pass] 54 main.clone_user_errors [pass] 27 main.clone_user_parameters [pass] 17 ---------------------------------------------------------------------- Testing completed: Friday 03 December 2010 09:50:06 All 3 tests passed.
