mirror of https://github.com/zulip/zulip.git
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.
This commit is contained in:
parent
03fecba917
commit
1094589f79
|
@ -34,6 +34,14 @@ function run {
|
||||||
fi
|
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
|
# prep
|
||||||
run ./tools/check-provision $FORCEARG
|
run ./tools/check-provision $FORCEARG
|
||||||
run ./tools/clean-repo
|
run ./tools/clean-repo
|
||||||
|
|
Loading…
Reference in New Issue