mnewby at internap
Apr 6, 2012, 1:44 PM
Views: 213
Permalink
|
So, there are mock adherents other than me. And apparently no strong voices advocating for removal. Should it co-exist alongside mox then? Should there be a preference as to how new tests are implemented? If replay is desired, mox may still be useful, although my own experience suggests that functionality requiring replay-oriented testing could likely benefit from testability improvements.
Thoughts?
On 2012-04-06, at 1:23 PM, Trey Morris wrote:
> +1 to mock
>
> On Thu, Apr 5, 2012 at 10:51 PM, Jason Kölker <jkoelker [at] rackspace> wrote:
> On Thu, 2012-04-05 at 20:04 -0700, Maru Newby wrote:
> > With that in mind, does anybody have any good arguments in favour of
> > keeping mock?
>
> PEP 417 - mock is in the stdlib as of Python 3.3.
>
> Happy Hacking!
>
> 7-11
>
>
> --
> Mailing list: https://launchpad.net/~netstack
> Post to : netstack [at] lists
> Unsubscribe : https://launchpad.net/~netstack
> More help : https://help.launchpad.net/ListHelp
>
> --
> Mailing list: https://launchpad.net/~netstack
> Post to : netstack [at] lists
> Unsubscribe : https://launchpad.net/~netstack
> More help : https://help.launchpad.net/ListHelp
|
