testtools

inconsistency between manual and testtools.TestResult.startTestRun behaviour

Bug #685680 reported by Jelmer Vernooij on 2010-12-06

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	testtools	Fix Released	Medium	Jonathan Lange	testtools 0.9.9

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.

It would be nice if documentation and code are consistent :-)

Also, 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.

See original description

Jelmer Vernooij (jelmer) on 2010-12-06

description:

updated

Jonathan Lange (jml) on 2010-12-07

Changed in testtools:
status:	New → Triaged
importance:	Undecided → High

Robert Collins (lifeless) on 2010-12-10

Changed in testtools:
importance:	High → Medium

Jonathan Lange (jml) on 2010-12-29

Changed in testtools:
status:	Triaged → Fix Committed
assignee:	nobody → Jonathan Lange (jml)
milestone:	none → next

Jonathan Lange (jml) on 2011-04-08

Changed in testtools:
status:	Fix Committed → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.