On Mar 23, 2011, at 07:31 AM, Nick Coghlan wrote: >On Wed, Mar 23, 2011 at 4:25 AM, Barry Warsaw <ba...@python.org> wrote: >> It probably wouldn't be a bad idea to add a very fast "smoke test" for the >> case where you get tripped up on the merge dance floor. When that happens, >> you could run your localized tests, and then a set of tests that run in just >> a >> minute or two. > >What would such a smoke test cover, though? It's hard to think of >anything particularly useful in the middle ground between "Can you run >regrtest *at all*?" and "make quicktest".
make quicktest runs 340 tests, and I'm certain many don't need to be run in a smoke test. E.g. test_aifc test_colorsys test_concurrent_futures (that's as far as it's gotten so far ;) Or you could time each individual test, choose a cut off for total test run and then run whatever you can within that time (on some reference machine). Or maybe just remove the longest running 50% of the quick tests. -Barry
signature.asc
Description: PGP signature
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
