On 3/30/06, Gabriel Wicke <lists(a)wikidev.net> wrote:
Having many failing tests to document obvious and
that won't be fixed without a rewrite tends to decrease the motivation
to run the test suite and distracts from important regressions. Who
cares if there are 50 or 52 failing tests? Having all tests pass and
then suddenly two fail generates far more attention.
I agree. I was a bit shocked when I started receiving "20 tests
failed" messages - normally a failed regression test is a cause for
On the other hand, you could definitely create tests for features that
have not been implemented, and run them separtely, perhaps replacing
"FAILED" with "Sorry, not yet".