Adam Spiers <g...@adamspiers.org> writes:
> This series of commits attempts to make test output coloring
> more intuitive,...
Thanks; I understand that this is to replace the previous one
b465316 (tests: paint unexpectedly fixed known breakages in bold
red, 2012-09-19)---am I correct?
> - red is only used for things which have gone unexpectedly wrong:
> test failures, unexpected test passes, and failures with the
> - yellow is only used for known breakages,
> - green is only used for things which have gone to plan and
> require no further work to be done,
> - blue is only used for skipped tests, and
> - cyan is used for other informational messages.
> Since unexpected test passes are no longer treated as passes, the
> summary lines displayed at the end of a test run have enough different
> possible outputs to warrant them being covered in the test framework's
> self-tests. Therefore this series also refactors and extends the
> Adam Spiers (7):
> tests: test number comes first in 'not ok $count - $message'
> tests: paint known breakages in bold yellow
> tests: paint skipped tests in bold blue
> tests: change info messages from yellow/brown to bold cyan
> tests: refactor mechanics of testing in a sub test-lib
> tests: test the test framework more thoroughly
> tests: paint unexpectedly fixed known breakages in bold red
> t/t0000-basic.sh | 211
> t/test-lib.sh | 25 ++++---
> 2 files changed, 180 insertions(+), 56 deletions(-)
Will take a look; thanks.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html