[merge] doc how to use new test features

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
> silently return - this test just doesn't make sense in this case

I don't like silent returns at all.  The test should not report that it
passed unless it ran to completion.

> This raises the question of when it's acceptable to have tests in any
> of these cases.  Will we merge code with known failures?

I think that has to be case-by-case.  We would certainly merge a test
case that failed for already-present code.  Otherwise, it's a tradeoff
based on the utility of the code vs the importance of the failure vs the
difficulty in fixing the code.

> Are we going
> to try to drive the skip count to 0?

Perhaps skips are for things that aren't worth fixing?  In that case, it
would be foolish to spend effort fixing them.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGOI210F+nu1YWqI0RAqbfAJ9QvAIcAytJNNPxfc81nMBMMWEpaQCffZUk
JvIVdn4XbmVSb/PRbR5XDiE=
=4b0R
-----END PGP SIGNATURE-----