testtools-dev team mailing list archive
-
testtools-dev team
-
Mailing list archive
-
Message #00359
[Bug 685680] [NEW] inconsistency between manual and testtools.TestResult.startTestRun behaviour
Public bug reported:
MANUAL claims:
testtools.TestResult provides empty startTestRun and stopTestRun methods, and
the default testtools runner will call these methods appropriately.
Yet testtools.startTestRun is not empty.
If it's correct that startTestRun is not empty then it would be nice if
its docstring could mention that this was different from the behaviour
of Python2.7's TestResult.startTestRun.
** Affects: testtools
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of testtools
developers, which is subscribed to testtools.
https://bugs.launchpad.net/bugs/685680
Title:
inconsistency between manual and testtools.TestResult.startTestRun behaviour
Status in testtools:
New
Bug description:
MANUAL claims:
testtools.TestResult provides empty startTestRun and stopTestRun methods, and
the default testtools runner will call these methods appropriately.
Yet testtools.startTestRun is not empty.
If it's correct that startTestRun is not empty then it would be nice if its docstring could mention that this was different from the behaviour of Python2.7's TestResult.startTestRun.
Follow ups
References