Hanno Schlichting wrote:
> On Thu, Jul 29, 2010 at 2:23 PM, Martin Aspeli<optilude+li...@gmail.com>
>> On 29 July 2010 20:14, yuppie<y.2...@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:
> 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.
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -