[PATCH v2 0/6] make test output coloring more intuitive
- From
Adam Spiers <git@adamspiers.org>
- Date
- Sep 19, 2012, 17:15 UTC
- Message-ID
- <1348074915-19985-1-git-send-email-git@adamspiers.org>
- In-Reply-To
- <20120918213617.GB2567@atlantic.linksys.moosehall>
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 seriouslyt/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