Am Dienstag, 7. Februar 2006 23:48 schrieb Roger Ineichen:
Hi Stephan
[...]
No, this is usually painful tracking down. You could check
for test setup code
that assigns AttributeAnnotatable to File. Also note that
there is no good
way for tearing down classImplements() statements. So
Hi Florian
[...]
[...]
No, this is usually painful tracking down. You could check
for test setup code
that assigns AttributeAnnotatable to File. Also note that
there is no good
way for tearing down classImplements() statements. So this
issue potentially
exists in many
On Monday 06 February 2006 19:18, Roger Ineichen wrote:
Does somebody know if there is a method for check if
a teardown get called after a test? Some hints?
No, this is usually painful tracking down. You could check for test setup code
that assigns AttributeAnnotatable to File. Also note that
Am Dienstag, 7. Februar 2006 10:31 schrieb Stephan Richter:
On Monday 06 February 2006 19:18, Roger Ineichen wrote:
Does somebody know if there is a method for check if
a teardown get called after a test? Some hints?
No, this is usually painful tracking down. You could check for test setup
Hi Florian
[...]
No, this is usually painful tracking down. You could check
for test setup
code that assigns AttributeAnnotatable to File. Also note
that there is no
good way for tearing down classImplements() statements. So
this issue
potentially exists in many places. I think
Hi Stephan
[...]
No, this is usually painful tracking down. You could check
for test setup code
that assigns AttributeAnnotatable to File. Also note that
there is no good
way for tearing down classImplements() statements. So this
issue potentially
exists in many places. I think for
Hi Florian, and other unittest gurus?
The README.txt test in zope.app.homefolder is failing (trunk).
This happens because the zope.app.file.file.File doesn't
implement IAttributeAnnotatable in the test setup.
The bad thing about this is, that the tests are running if you
run all tests at once.
