Hi Jay,
On 2012-03-02, at 10:17 AM, Jay Pipes wrote:
>
> ++ to unittest2. Frankly, it's a dependency of sqlalchemy, so it gets
> installed anyway during any installation. Might as well use it IMHO.
Good to know!
>> Separately, is the use of mox open to discussion? mock was recently added
>
On 03/01/2012 08:12 PM, Maru Newby wrote:
Is there any interest in adding unittest2 to the test dependencies for
openstack projects? I have found its enhanced assertions and 'with
self.assertRaises' very useful in writing tests. I see there have been past
bugs that mentioned unittest2, and a
Mark:
I think Maru is talking about the distinction between record/replay mocking and
action/assertion mocking.
In record/replay mocking (e.g., mox) you define the expected behavior *before*
executing the code under test (i.e., "I expect A, B, and C to happen, now go
execute the code under tes
Apologies to Maru for the double-email. Left out the list by mistake.
When you say "non-replay mocking," are you talking about ensuring that a
particular function is not called, or replacing a function/whatever with a
lambda that doesn't care if it gets called or how often it gets called but
stil
Is there any interest in adding unittest2 to the test dependencies for
openstack projects? I have found its enhanced assertions and 'with
self.assertRaises' very useful in writing tests. I see there have been past
bugs that mentioned unittest2, and am wondering if the reasons for not adopting
5 matches
Mail list logo
