Hi!
Traditionally the last two lines of unit test files look like this:
if __name__ == '__main__':
unittest.main(defaultTest='test_suite')
That makes it easy to run the tests of a specific file. But it doesn't
work with tests that require the zope testrunner. AFAICS something like
this
Summary of messages to the zope-tests list.
Period Wed Jul 28 12:00:00 2010 UTC to Thu Jul 29 12:00:00 2010 UTC.
There were 50 messages: 6 from Zope Tests, 1 from buildbot at
enfoldsystems.com, 4 from buildbot at pov.lt, 13 from buildbot at
winbot.zope.org, 11 from ccomb at free.fr, 15 from
On 29 July 2010 19:26, yuppie y.2...@wcm-solutions.de wrote:
Hi!
Traditionally the last two lines of unit test files look like this:
if __name__ == '__main__':
unittest.main(defaultTest='test_suite')
That makes it easy to run the tests of a specific file. But it doesn't
work with
Martin Aspeli wrote:
I never do either. I install zc.recipe.testrunner in a buildout and
use bin/test, which picks up tests in modules automatically.
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
On 29 July 2010 20:14, yuppie y.2...@wcm-solutions.de wrote:
Martin Aspeli wrote:
I never do either. I install zc.recipe.testrunner in a buildout and
use bin/test, which picks up tests in modules automatically.
Sure. But do you always run all tests it picks up while working on a
specific
Hi Martin!
Martin Aspeli wrote:
On 29 July 2010 20:14, yuppiey.2...@wcm-solutions.de wrote:
Martin Aspeli wrote:
I never do either. I install zc.recipe.testrunner in a buildout and
use bin/test, which picks up tests in modules automatically.
Sure. But do you always run all tests it picks
On 07/29/2010 02:17 PM, Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/29/10 14:00 , Martin Aspeli wrote:
On 29 July 2010 19:26, yuppiey.2...@wcm-solutions.de wrote:
1.) Is it still policy to add these lines?
2.) Is there a better solution for using zope
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/29/10 15:57 , yuppie wrote:
Hanno Schlichting wrote:
On Thu, Jul 29, 2010 at 2:23 PM, Martin Aspelioptilude+li...@gmail.com
wrote:
On 29 July 2010 20:14, yuppiey.2...@wcm-solutions.de wrote:
Sure. But do you always run all tests it picks
On Thu, Jul 29, 2010 at 3:57 PM, yuppie y.2...@wcm-solutions.de wrote:
If everybody is using this, nobody is using CMF.buildout for
development. Anyway. I fixed CMF.buildout:
http://svn.zope.org/?rev=115204view=rev
I'm using CMF.buildout and was always annoyed by it overriding the -m
option.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yuppie wrote:
Hi!
Hanno Schlichting wrote:
On Thu, Jul 29, 2010 at 2:23 PM, Martin Aspelioptilude+li...@gmail.com
wrote:
On 29 July 2010 20:14, yuppiey.2...@wcm-solutions.de wrote:
Sure. But do you always run all tests it picks up while
On 29 July 2010 22:35, Tres Seaver tsea...@palladion.com wrote:
I don't believe that zope.testing's testrunner works without 'def
test_suite()'.
Latter versions can detect unittest.TestCase-derived test suites
automatically. For doctests you still need test_suite().
Martin
On Thu, Jul 29, 2010 at 4:35 PM, Tres Seaver tsea...@palladion.com wrote:
I don't believe that zope.testing's testrunner works without 'def
test_suite()'.
Oh it does. Ever since 3.8.0 from mid 2009:
- Testrunner automatically picks up descendants of unittest.TestCase
in test modules, so you
On Thu, Jul 29, 2010 at 02:52:36PM +0200, yuppie wrote:
Hi Martin!
Martin Aspeli wrote:
On 29 July 2010 20:14, yuppiey.2...@wcm-solutions.de wrote:
Martin Aspeli wrote:
I never do either. I install zc.recipe.testrunner in a buildout and
use bin/test, which picks up tests in modules
13 matches
Mail list logo