This series of commits attempts to make test output coloring
more intuitive, so that:
- red is _only_ used for things which have gone unexpectedly wrong:
test failures, unexpected test passes, and failures with the
framework,
- yellow is _only_ used for known breakages and skipped tests, and
- green is _only_ used for things which have gone to plan and
require no further work to be done.
Adam Spiers (6):
Change the color of individual known breakages
Make 'not ok $count - $message' consistent with 'ok $count -
$message'
Color skipped tests the same as informational messages
Refactor mechanics of testing in a sub test-lib
Test the test framework more thoroughly
Treat unexpectedly fixed known breakages more seriously
t/t0000-basic.sh | 179 ++++++++++++++++++++++++++++++++++++++++++++++++-------
t/test-lib.sh | 25 +++++---
2 files changed, 174 insertions(+), 30 deletions(-)
mode change 100644 => 100755 t/test-lib.sh
--
1.7.12.147.g6d168f4
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html