Home Original page

[Python-Dev] Trimming the fat from "make quicktest" (was Re: I am now lost

[Python-Dev] Trimming the fat from "make quicktest" (was Re: I am now lost - committed, pulled, merged, what is "collapse"?)

Barry Warsaw barry at python.org
Wed Mar 23 16:51:56 CET 2011 
On Mar 23, 2011, at 10:02 AM, skip at pobox.com wrote:

>Eliminating tests based on the time it takes to run them suggests that the
>resulting smaller test run may have considerably different overall coverage
>quality than you might desire.  Some tests (syntax, basic arithmetic, etc)
>probably run blazingly fast and will be fully covered by a "make nanotest",
>while some really important stuff (anything which forks or creates sockets)
>will have very poor nanotest coverage because many of its tests cases won't
>be run.  The odds that someone breaks syntax or basic arithmetic
>functionality (or even changes those parts of the system) are pretty low, so
>repeatedly running those tests simply because they run fast gives a false
>sense of security.

Not if you keep in mind the appropriate use case for each of the separate make
test targets.

-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-dev/attachments/20110323/5fc39bfa/attachment.pgp>
More information about the Python-Dev mailing list