diff options
| author | unknown <sasha@mysql.sashanet.com> | 2000-12-13 18:23:55 -0700 |
|---|---|---|
| committer | unknown <sasha@mysql.sashanet.com> | 2000-12-13 18:23:55 -0700 |
| commit | e842d46efa151e00e0998a3ad65f9c99b2e18519 (patch) | |
| tree | 5ab0647c2a5502b00ddbacef80efb01f9985737b /mysql-test | |
| parent | 123946665cd437eb9249b500d710b4a5fcab39bc (diff) | |
| download | mariadb-git-e842d46efa151e00e0998a3ad65f9c99b2e18519.tar.gz | |
fixes for parallel make, re-added the lost README files in mysql-test
BUILD/compile-pentium-debug:
fox for parallel make
BUILD/compile-pentium-gcov:
fix for parallel make
BUILD/compile-pentium:
fix to enable parallel make when recursing to subdirectories
Build-tools/Do-all-build-steps:
fix for parallel make, remove the stale comment to make Tim happy
Build-tools/Do-rpm:
fix for parallel make
Diffstat (limited to 'mysql-test')
| -rw-r--r-- | mysql-test/README | 29 | ||||
| -rw-r--r-- | mysql-test/README.gcov | 11 |
2 files changed, 40 insertions, 0 deletions
diff --git a/mysql-test/README b/mysql-test/README new file mode 100644 index 00000000000..35ab424190e --- /dev/null +++ b/mysql-test/README @@ -0,0 +1,29 @@ +This directory contains a test suite for mysql daemon. To run +the currently existing test cases, simply execute ./mysql-test-run in +this directory. It will fire up the newly built mysqld and test it. +Note that you do not have to have to do make install, and you could +actually have a co-existing MySQL installation - the tests will not +conflict with it. + +All tests must pass. If one or more of them fail on your system, please +report the details to bugs@lists.mysql.com + +You can create your own test cases. To create a test case: + + cd t + vi test_case_name.test + + in the file, put a set of SQL commands that will create some tables, + load test data, run some queries to manipulate it. + + then do ./mysql-test-run -record test_case_name + and look at r/test_case_name.result - edit the result if necessary. If you + have to edit it, you have found a bug. + +To submit your test case, put your .test file and .result file(s) into +a tar.gz archive, add a README that explains the problem, ftp the +archive to ftp://support.mysql.com/pub/mysql/secret/ and send a mail +to bugs@lists.mysql.com + + + diff --git a/mysql-test/README.gcov b/mysql-test/README.gcov new file mode 100644 index 00000000000..83ddd6df2e1 --- /dev/null +++ b/mysql-test/README.gcov @@ -0,0 +1,11 @@ +To be able to see the level of coverage with the current test suite, +do the following: + + - make sure gcov is installed + - compile with BUILD/compile-pentium-gcov ( if your machine is not pentium, hack +this script, or just live with the pentium-specific stuff) + - ./mysql-test-run -gcov + - to see the level of coverage for a given source file: + grep source_file_name /tmp/gcov.out + - to see which lines are not yet covered, look at source_file_name.gcov in the source tree. Then think hard about a test case that will cover those +lines, and write one! |