-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 yuppie wrote:
Hi!
Hanno Schlichting wrote:
On Thu, Jul 29, 2010 at 2:23 PM, Martin Aspeli<optilude+lists@gmail.com> wrote:
On 29 July 2010 20:14, yuppie<y.2010@wcm-solutions.de> wrote:
Sure. But do you always run all tests it picks up while working on a specific test file? Or do you use bin/test with options that allow to run specific files? See the -s and -t options. :) Don't forget -m which runs exactly one module (file).
I always use commands like:
bin/test -s zope.package bin/test -s zope.package -m test_module bin/test -s zope.package -m test_module -t test_some_method
If everybody is using this, nobody is using CMF.buildout for development. Anyway. I fixed CMF.buildout: http://svn.zope.org/?rev=115204&view=rev
+1 for removing the 'if __name__ == "__main__"' boilerplate opportunistically.
Especially since unittest and zope.testing can even discover TestSuites inside modules, it seems any kind of explicit configuration in the test files isn't needed anymore.
Do you think it should become policy to remove "def test_suite():" where possible? I'm not sure if I like that because it is less explicit.
I don't believe that zope.testing's testrunner works without 'def test_suite()'. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkxRkb0ACgkQ+gerLs4ltQ4KugCgtZa1XK2SRcMIeu4e0BlZZOQ4 t2gAnjPZjjPewRWr0OnxOeezDn0crgb5 =8VTG -----END PGP SIGNATURE-----