[TIP] Declarative style acceptance tests
tseaver at palladion.com
Mon Jan 6 13:28:41 PST 2014
-----BEGIN PGP SIGNED MESSAGE-----
On 01/06/2014 03:53 PM, Paul Moore wrote:
> Can you clarify why? It may be that the reason is that what you're
> referring to as acceptance tests is not what I'm trying to create
> (see below).
"Straight" doctests don't model user stories very well, except (some
argue) if your users are other software developers (i.e., you are writing
a library). They also have significant maintainability defects (e.g.,
subtle changes in "irrelevant" details like object reprs and traceback
formatting between Python versions). Working around those defects tends
to reduce their value as documentation.
Benji York's 'manuel' allows extending doctests with custom
syntax, such that the tescases can be expressed in more "user
comprehensible" form than exercising the API at the Python prompt.
Tres Seaver +1 540-429-0999 tseaver at palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
More information about the testing-in-python