A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2004-September/048649.html below:

[Python-checkins] python/dist/src/Lib/test test_compiler.py, 1.5, 1.6 test_decimal.py, 1.13, 1.14

[Python-Dev] Re: [Python-checkins] python/dist/src/Lib/test test_compiler.py, 1.5, 1.6 test_decimal.py, 1.13, 1.14Jeremy Hylton jhylton at gmail.com
Tue Sep 7 16:26:34 CEST 2004
On Sat, 04 Sep 2004 13:09:15 -0700, rhettinger at users.sourceforge.net
<rhettinger at users.sourceforge.net> wrote:
> Update of /cvsroot/python/python/dist/src/Lib/test
> In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv11509
> 
> Modified Files:
>         test_compiler.py test_decimal.py
> Log Message:
> Change the strategy for coping with time intensive tests from
> "all or none" to "all or some".
> 
> This provides much greater test coverage without eating much time.
> It also makes it more likely that routine regression testing will
> unearth bugs.

If the time is really a problem, I'd rather select a certain set of
files to test all the times.  I'm interested in making sure the
compiler is run against the widest possible range of language
constructs, which plain old random testing isn't likely to do.

I'd prefer, even, an option to enable random sampling for these tests.
 When I'm testing the compiler package, I really want to run the
entire test, not a small part of it.

Jeremy
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4