From 1094589f799804a4a2f33f98212094e847e4566e Mon Sep 17 00:00:00 2001 From: Tim Abbott Date: Mon, 27 Apr 2020 16:34:17 -0700 Subject: [PATCH] test-all: Print a colorful notice on startup discouraging use. The test-all tool is useful if you want to be really sure everything passes, but it's almost always better to run a smaller subsuite when doing active development, and just run test-all (or CI) at the end. Our docs already covered this issue well, but this presents the idea in a place one is definitely looking at when running test-all. --- tools/test-all | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/tools/test-all b/tools/test-all index 9902f84f1a..dbb46e3098 100755 --- a/tools/test-all +++ b/tools/test-all @@ -34,6 +34,14 @@ function run { fi } +printf '\n\e[33;1m' +echo "Because test-all is very slow, we recommend running individual (sub)suites " +echo "and relying on CI to run the complete test suite for a fast edit-test cycle. See" +echo " https://zulip.readthedocs.io/en/latest/testing/testing.html#running-tests" +echo "for details on how to run just the relevant subsets of our tests." +printf '\e[0m' +echo + # prep run ./tools/check-provision $FORCEARG run ./tools/clean-repo