RetroSearch Browse

Sun Feb 27 15:27:02 CET 2011 · https://mail.python.org/pipermail/python-dev/2011-February/108435.html

On Sun, Feb 27, 2011 at 06:31, brett.cannon <python-checkins at python.org> wrote:
> +When writing new tests to increase coverage, do take note of the style of tests
> +already provided for a module (e.g., whitebox, blackbox, etc.). As
> +some modules are primarily maintained by a single core developer they may have
> +a specific preference as to what kind of test is used (e.g., whitebox) and
> +prefer that other types of tests not be used (e.g., blackbox). When in doubt,
> +stick with whitebox testing in order to properly exercise the code.

Do you think it could be nice to have a reference to what
whitebox/blackbox testing is, ie

http://en.wikipedia.org/wiki/White-box_testing
http://en.wikipedia.org/wiki/Black-box_testing

?

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

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

Showing content from https://mail.python.org/pipermail/python-dev/2011-February/108435.html below:

[Python-Dev] [Python-checkins] devguide: List common gotchas people might come across when doing coverage work.