Hi!
Marius Gedminas wrote:
>> And if I use the -t option (-ttest_tool), most tests fail :(
>
> That is an indication that the tests aren't independent. I would
> consider such a test suite to be broken.
Well. In this case the tests are independent from each other, but not
from the way tests ar
On Thu, Jul 29, 2010 at 02:52:36PM +0200, yuppie wrote:
> Hi Martin!
>
>
> Martin Aspeli wrote:
> > On 29 July 2010 20:14, yuppie 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 automat
On Thu, Jul 29, 2010 at 4:35 PM, Tres Seaver 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 don't have to provide
On 7/29/10 16:35 , Tres Seaver wrote:
> yuppie wrote:
>> 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()'.
It seems to
On 29 July 2010 22:35, Tres Seaver 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
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yuppie wrote:
> Hi!
>
>
> Hanno Schlichting wrote:
>> On Thu, Jul 29, 2010 at 2:23 PM, Martin Aspeli
>> wrote:
>>> On 29 July 2010 20:14, yuppie wrote:
Sure. But do you always run all tests it picks up while working on a
specific test fi
On Thu, Jul 29, 2010 at 3:57 PM, yuppie wrote:
> 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
I'm using CMF.buildout and was always annoyed by it overriding the -m
option. But the CMF tests are
-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 Aspeli
>> wrote:
>>> On 29 July 2010 20:14, yuppie wrote:
Sure. But do you always run all tests it picks up while working on a
specific
Hi!
Hanno Schlichting wrote:
> On Thu, Jul 29, 2010 at 2:23 PM, Martin Aspeli
> wrote:
>> On 29 July 2010 20:14, yuppie 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 fil
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, yuppie wrote:
>>> 1.) Is it still policy to add these lines?
>>>
>>> 2.) Is there a better solution for using zope testrunner than t
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, yuppie wrote:
>>> 1.) Is it still policy to add these lines?
>>>
>>> 2.) Is there a better solution for using zope testrunner than t
Hi Martin!
Martin Aspeli wrote:
> On 29 July 2010 20:14, yuppie 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 wo
On Thu, Jul 29, 2010 at 2:23 PM, Martin Aspeli wrote:
> On 29 July 2010 20:14, yuppie 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. :)
D
On 29 July 2010 20:14, yuppie 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 test file? Or do yo
Am 29.07.2010, 14:14 Uhr, schrieb yuppie :
> 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?
I try and limit my tests to the package or module I'm working on. I've
been bitten by m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/29/10 14:00 , Martin Aspeli wrote:
> On 29 July 2010 19:26, yuppie wrote:
>> 1.) Is it still policy to add these lines?
>>
>> 2.) Is there a better solution for using zope testrunner than the one
>> shown above?
>
> I never do either. I install
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 19:26, yuppie 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 tests that requir
18 matches
Mail list logo
