On Sun, Aug 3, 2008 at 1:56 PM, Jorgen Grahn <[EMAIL PROTECTED]> wrote:
> On Tue, 29 Jul 2008 20:12:14 +0200, Nikolaus Rath <[EMAIL PROTECTED]> wrote:
>> Jean-Paul Calderone <[EMAIL PROTECTED]> writes:
>>> On Tue, 29 Jul 2008 19:26:09 +0200, Nikolaus Rath <[EMAIL PROTECTED]> wrote:
Jean-Paul Ca
On Tue, 29 Jul 2008 20:12:14 +0200, Nikolaus Rath <[EMAIL PROTECTED]> wrote:
> Jean-Paul Calderone <[EMAIL PROTECTED]> writes:
>> On Tue, 29 Jul 2008 19:26:09 +0200, Nikolaus Rath <[EMAIL PROTECTED]> wrote:
>>>Jean-Paul Calderone <[EMAIL PROTECTED]> writes:
On Tue, 29 Jul 2008 16:35:55 +0200,
In article <[EMAIL PROTECTED]>,
Nikolaus Rath <[EMAIL PROTECTED]> wrote:
> But at least this variation doesn't work, because unittest apparently
> also creates two separate TwoTests instances for the two tests. Isn't
> there some way to convince unittest to reuse the same instance instead
> of tr
On Tue, 29 Jul 2008 20:12:14 +0200, Nikolaus Rath <[EMAIL PROTECTED]> wrote:
Jean-Paul Calderone <[EMAIL PROTECTED]> writes:
On Tue, 29 Jul 2008 19:26:09 +0200, Nikolaus Rath <[EMAIL PROTECTED]> wrote:
Jean-Paul Calderone <[EMAIL PROTECTED]> writes:
On Tue, 29 Jul 2008 16:35:55 +0200, Nikolaus
Jean-Paul Calderone <[EMAIL PROTECTED]> writes:
> On Tue, 29 Jul 2008 19:26:09 +0200, Nikolaus Rath <[EMAIL PROTECTED]> wrote:
>>Jean-Paul Calderone <[EMAIL PROTECTED]> writes:
>>> On Tue, 29 Jul 2008 16:35:55 +0200, Nikolaus Rath <[EMAIL PROTECTED]> wrote:
Hello,
I have a number of co
On Tue, 29 Jul 2008 19:26:09 +0200, Nikolaus Rath <[EMAIL PROTECTED]> wrote:
Jean-Paul Calderone <[EMAIL PROTECTED]> writes:
On Tue, 29 Jul 2008 16:35:55 +0200, Nikolaus Rath <[EMAIL PROTECTED]> wrote:
Hello,
I have a number of conceptually separate tests that nevertheless need
a common, compl
Jean-Paul Calderone <[EMAIL PROTECTED]> writes:
> On Tue, 29 Jul 2008 16:35:55 +0200, Nikolaus Rath <[EMAIL PROTECTED]> wrote:
>>Hello,
>>
>>I have a number of conceptually separate tests that nevertheless need
>>a common, complicated and expensive setup.
>>
>>Unfortunately, unittest runs the setUp
On Tue, 29 Jul 2008 16:35:55 +0200, Nikolaus Rath <[EMAIL PROTECTED]> wrote:
Hello,
I have a number of conceptually separate tests that nevertheless need
a common, complicated and expensive setup.
Unfortunately, unittest runs the setUp method once for each defined
test, even if they're part of
Hello,
I have a number of conceptually separate tests that nevertheless need
a common, complicated and expensive setup.
Unfortunately, unittest runs the setUp method once for each defined
test, even if they're part of the same class as in
class TwoTests(unittest.TestCase):
def setUp(self):
