Skip to content

Commit

Permalink
README : Update README file related to usage of FORMAT make variable
Browse files Browse the repository at this point in the history
Reformatted the README file to simplify the sentences.

Signed-off-by: Ravi Nanjundappa <nravi.n@samsung.com>
Reviewed-by: Bryce Harrington <bryce@osg.samsung.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
  • Loading branch information
Ravi Nanjundappa authored and Bryce Harrington committed Aug 14, 2014
1 parent c61aedd commit 7736d08
Showing 1 changed file with 12 additions and 5 deletions.
17 changes: 12 additions & 5 deletions test/README
Original file line number Diff line number Diff line change
Expand Up @@ -41,14 +41,21 @@ There are some mechanisms to limit the tests run during "make test".
These come very handy when doing development, but should not be used
to circumvent the "pass" requirements listed below.

To limit the backends that the tests are run against, use the
TARGETS make variable, that can also be passed to make.
It should contain a (space-, comma-, etc-separated) list of backends to test.
To limit the tests run, use the CAIRO_TESTS environment variable, which
should be a space-separated list of tests to run. For example:
make's TARGETS environment variable can be used to limit the backends when
running the tests. It should contain a (space-, comma-separated) list of
backends. CAIRO_TESTS environment variable, which is a comma-, space-seperated
lists, can be used to limit the tests run.
For example:

CAIRO_TESTS="zero-alpha" make test TARGETS=image,ps

make's FORMAT variable can also be used to limit the content formats when
running the tests. It should contain a (space-, comma-separated) list of
content formats to test.
For example:

CAIRO_TESTS="zero-alpha" make test TARGETS=image,ps FORMAT="rgb,rgba"

Another very handy mechanism when trying to fix bugs is:

make retest
Expand Down

0 comments on commit 7736d08

Please sign in to comment.