diff options
| author | darxus@chaosreigns.com <darxus@chaosreigns.com> | 2016-07-26 13:38:52 -0400 |
|---|---|---|
| committer | Bryce Harrington <bryce@bryceharrington.org> | 2016-08-31 20:29:57 -0700 |
| commit | cbbd02f9c5389522cddecd53ca109f2e3ef98f58 (patch) | |
| tree | cb4231a5769374d97b0014e5ddfb678435410567 | |
| parent | 66205ad48efaea3ebb87b344719b64c8745f177e (diff) | |
Add example to run specific tests by name to the test/README
Reviewed-by: Bryce Harrington <bryce@osg.samsung.com>
Reviewed-by: Uli Schlachter <psychon@znc.in>
| -rw-r--r-- | test/README | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/test/README b/test/README index 9ed9bc78b..84d7b4170 100644 --- a/test/README +++ b/test/README @@ -21,9 +21,10 @@ The test suite needs to be run before any code is committed and before any release. See below for hints and rules governing the use of the suite. The test suite is built as a single binary, which allows you to choose -individual or categories of tests to run. For example, if you want to -run all text related tests you can use: - ./cairo-test-suite text +individual or categories of tests to run. For example, to run specific tests: + ./cairo-test-suite record-neg-extents-unbounded record-neg-extents-bounded +Or if you want to run all paint.* related tests you can use: + ./cairo-test-suite paint Or if you want to check the current status of known failures: ./cairo-test-suite XFAIL Or to run a subset of tests, use the -k option to run only the tests |