summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorStefano Lattarini <stefano.lattarini@gmail.com>2012-04-18 11:40:15 +0200
committerStefano Lattarini <stefano.lattarini@gmail.com>2012-04-18 11:40:15 +0200
commitf46359b42790945e42e78a620e651ce66c2b8833 (patch)
treee5d28d358e38fdcb54af3a2a00832abef4849d09 /NEWS
parent0c2cc2c9d171ef21ef54c87569837ff41cd09a9d (diff)
downloadautomake-f46359b42790945e42e78a620e651ce66c2b8833.tar.gz
parallel-tests: 'recheck' must depend on 'all'
Fixes automake bug#11252. When a developer experience one or more failures in the testsuite, a good workflow is for him to modify its program's sources to fix the bug thus revealed, run "make recheck" to verify that the change has indeed solved the testsuite failures previously experienced, and then run "make check" to verify that the change has not introduced any new failure or regression. Unfortunately, this apparently natural workflow couldn't have worked until now, since the Automake-provided 'recheck' target (which didn't depend on 'all') wouldn't have causes the program to be recompiled, and the failed tests would have thus been run with the older, buggy version of the program, failing the same way as before. * lib/am/check.am (recheck): Depend on 'all'. * t/parallel-tests-recheck-depends-on-all.sh: New test. * t/list-of-tests.mk: Add it. * NEWS: Update. Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS4
1 files changed, 4 insertions, 0 deletions
diff --git a/NEWS b/NEWS
index 142f805f6..bb2480fea 100644
--- a/NEWS
+++ b/NEWS
@@ -92,6 +92,10 @@ New in 1.11c:
testsuite harness. This is still the default at the moment, but it
might change in future versions.
+ - The 'recheck' target (provided by the parallel testsuite harness) now
+ depends on the 'all' target. This allows for a better user-experience
+ in test-driven development. See automake bug#11252.
+
- Test scripts that exit with status 99 to signal an "hard error" (e.g.,
and unexpected or internal error, or a failure to set up the test case
scenario) have their outcome reported as an 'ERROR' now. Previous