diff options
| author | Marko Mäkelä <marko.makela@mariadb.com> | 2019-08-12 18:23:42 +0300 |
|---|---|---|
| committer | Marko Mäkelä <marko.makela@mariadb.com> | 2019-08-12 18:25:35 +0300 |
| commit | be33124c9dc284c4409d02e5405de568b467a167 (patch) | |
| tree | 7188f6effdace66ce24af17fd1bd0d89f5b76999 /mysql-test/README | |
| parent | fe8181aca13cf7ba1835fa6c89f297a1d0e79856 (diff) | |
| parent | 15c1ab52a9f2827724c5d007ce7b8c607dc8f0a9 (diff) | |
| download | mariadb-git-be33124c9dc284c4409d02e5405de568b467a167.tar.gz | |
Merge 10.1 into 10.2
Diffstat (limited to 'mysql-test/README')
| -rw-r--r-- | mysql-test/README | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/mysql-test/README b/mysql-test/README index d925964fed5..cc028050d1a 100644 --- a/mysql-test/README +++ b/mysql-test/README @@ -60,7 +60,7 @@ In the file, put a set of SQL statements that create some tables, load test data, and run some queries to manipulate it. Your test should begin by dropping the tables you are going to create and -end by dropping them again. This ensures that you can run the test over +end by dropping them again. This ensures that you can run the test over and over again. If you are using mysqltest commands in your test case, you should create @@ -81,7 +81,7 @@ comments, you can create the result file in one of the following ways: # mysqltest --record --database test --result-file=r/test_case_name.result < t/test_case_name.test -When this is done, take a look at r/test_case_name.result . +When this is done, take a look at r/test_case_name.result. If the result is incorrect, you have found a bug. In this case, you should edit the test result to the correct results so that we can verify that the bug is corrected in future releases. |