lp:~therve/mocker/299930-assert-raises

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #299930: Mocker should define its own assertRaises that return the exception caught

Undecided

Fix Released

Link a bug report

Related blueprints

53. By Thomas Herve on 2008-11-19

Return exception in failUnlessRaises, test it.

52. By Gustavo Niemeyer on 2008-07-01

Moved the __mocker_mock__ cleaning up test from Patcher into its
own method around the Mocker.patch() tests.

51. By Gustavo Niemeyer on 2008-07-01

Merging branch from Thomas which changes Mocker.patch() to use the
patcher when setting __mocker_mock__, rather than setting it in a
persistent way.

50. By Gustavo Niemeyer on 2008-07-01

Prevent the MockerTestCase base from leaving the mocker in replay mode
while the base class run() method runs, since this might have additional
logic which touches mocked content (time.time() was one case). Thanks
to Thomas for the initial debugging.

49. By Gustavo Niemeyer on 2008-03-28

A couple of changes to better accomodate py3k changes.

48. By Gustavo Niemeyer on 2008-03-28

When cleaning up on MockerTestCase, use reset() rather than restore(),
so that the same test case instance may be run more than once (like
Trial does).

47. By Gustavo Niemeyer on 2007-12-11

Fixed patching of objects which define __getattr__.

46. By Gustavo Niemeyer on 2007-12-09

Preparing to release 0.10.

45. By Gustavo Niemeyer on 2007-12-09

Orderer() is now implemented based on may_run() instead of matches().
If the event is run with may_run() False, a nice assertion error is
raised with a nice debugging message. :-)

44. By Gustavo Niemeyer on 2007-12-09

Introduced {Task,Event}.may_run() to improve replaying ordering
logic. Now events which have may_run() true will be run before
events which don't.