Why is test.py silent by default
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The "default" usecase for running tests should be a developer making changes and running tests. In this case, "silent" mode is unhelpful; it gives no feedback until the very end of the run, which takes a **long** time for the whole Zope2 tree. The "dots" provided at verbosity level one are good feedback for the developer: they provide a clue about how many tests have run, and give some chance of deducing that the tests have hung. Unless somebody has a compelling counter-argument, I will check in a patch which makes verbosity level 1 ("dots") the default value. People who want quiet mode can always pass '-q'. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDWSAW+gerLs4ltQ4RAs3NAKCodcPqXIDlTJ3QGa4z8gFNc92LcACeJNLc 7ms5+UFjYgv+i/M6/I4eIOc= =wEwp -----END PGP SIGNATURE-----
Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The "default" usecase for running tests should be a developer making changes and running tests. In this case, "silent" mode is unhelpful; it gives no feedback until the very end of the run, which takes a **long** time for the whole Zope2 tree. The "dots" provided at verbosity level one are good feedback for the developer: they provide a clue about how many tests have run, and give some chance of deducing that the tests have hung.
Unless somebody has a compelling counter-argument, I will check in a patch which makes verbosity level 1 ("dots") the default value. People who want quiet mode can always pass '-q'.
-1 I prefer not to get output unless there is a problem. I'm happy to defer to others, but I personally prefer less output. BTW, within the next week, I will be integrating the new test runner into z2 and z3. So if people agree with you and we decide that the default verbosity level should be 1, then I'll do that when I integrate the new runner. (I guess I'll have to add a quiet option to cancel a default verbosity level.) Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jim Fulton wrote:
Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The "default" usecase for running tests should be a developer making changes and running tests. In this case, "silent" mode is unhelpful; it gives no feedback until the very end of the run, which takes a **long** time for the whole Zope2 tree. The "dots" provided at verbosity level one are good feedback for the developer: they provide a clue about how many tests have run, and give some chance of deducing that the tests have hung.
Unless somebody has a compelling counter-argument, I will check in a patch which makes verbosity level 1 ("dots") the default value. People who want quiet mode can always pass '-q'.
-1
I prefer not to get output unless there is a problem. I'm happy to defer to others, but I personally prefer less output.
Hmm, maybe we need a 'testrunner.rc' file with personal-preference options, then. Assuming that the script looked for it in sensible places (homedir, instance_home/etc, maybe?), I could live without changing the default in the script.
BTW, within the next week, I will be integrating the new test runner into z2 and z3. So if people agree with you and we decide that the default verbosity level should be 1, then I'll do that when I integrate the new runner. (I guess I'll have to add a quiet option to cancel a default verbosity level.)
Having such an option is usual, for the cases when some other script is driving your testrunner; if '-q' cancels any previous '-v' (explicit or default), then you can shut off unneeded output driven by the upstream script. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDWTmN+gerLs4ltQ4RAjPZAJ9NRehkIN9iMAZqfRvGjwjTeUJwAACfcWEi rgpXVBO4k/sxsWccUmLA62E= =BZX8 -----END PGP SIGNATURE-----
Tres Seaver wrote:
The "default" usecase for running tests should be a developer making changes and running tests. In this case, "silent" mode is unhelpful; it gives no feedback until the very end of the run, which takes a **long** time for the whole Zope2 tree. The "dots" provided at verbosity level one are good feedback for the developer: they provide a clue about how many tests have run, and give some chance of deducing that the tests have hung.
Unless somebody has a compelling counter-argument, I will check in a patch which makes verbosity level 1 ("dots") the default value. People who want quiet mode can always pass '-q'.
+1 Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg@nuxeo.com
Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The "default" usecase for running tests should be a developer making changes and running tests. In this case, "silent" mode is unhelpful; it gives no feedback until the very end of the run, which takes a **long** time for the whole Zope2 tree. The "dots" provided at verbosity level one are good feedback for the developer: they provide a clue about how many tests have run, and give some chance of deducing that the tests have hung.
Unless somebody has a compelling counter-argument, I will check in a patch which makes verbosity level 1 ("dots") the default value. People who want quiet mode can always pass '-q'.
+1 Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
participants (4)
-
Chris Withers -
Florent Guillaume -
Jim Fulton -
Tres Seaver