More test suite infrastructure improvements:

- Remove cairo_test_expect_failure.  cairo-test.c now checks
  env var CAIRO_XFAIL_TESTS to see if the running test is
  expected to fail.  The reason for expected failure is
  appended to the test description.
- Test description is written out.
- Failed/crashed tests also write a line out to stderr (in red),
  so one can now redirect stdout to /dev/null to only see failures.
- cairo_test() has been changed to not take the draw function
  anymore, instead, draw function is now part of the test struct.
- "make check" doesn't allow limiting backends to test using env
  var anymore.  To limit backends to test, one should use the
  TARGETS variable on the make command line.
- "make check-valgrind" now writes its log to valgrind-log instead
  of valgrind.log, to not interfere with test log file processing.

1 files changed, 3 insertions, 3 deletions

diff --git a/test/README b/test/README
index 0fb7f7254..468ff4a0e 100644
--- a/test/README
+++ b/test/README
@@ -22,12 +22,12 @@ 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
-CAIRO_TEST_TARGET environment variable, that can also be passed to make.
+TARGETS make variable, that can also be passed to make.
 It should contain a (space-, comma-, etc-separate) list of backends to test.
-To limit the tests run, use the make TESTS variable, which should be a
+To limit the tests run, use the TESTS make variable, which should be a
 space-separated list of tests to run.  For example:
 
-  make check CAIRO_TEST_TARGET=image,ps TESTS="zero-alpha"
+  make check TARGETS=image,ps TESTS="zero-alpha"
 
 
 Before committing