Hi Uli,
Thanks for your reply to clarify the history of zope.pytest.
On 05/17/2012 07:22 AM, Uli Fouquet wrote:
>
> On Wed, 16 May 2012 03:40:17 -0500 Jeff Rush wrote:
>
>> 5) the unit tests for zope.pytest itself are failing with:
>>> from zope.interface.interfaces import ComponentLookupErr
On Thu, May 17, 2012 at 5:52 PM, Uli Fouquet wrote:
[...snip...]
> The main problem why we got stuck is test separation.
>
> Especially the setup and teardown of ZCA registrations, which should
> happen before and after each single test and might be different for
> certain groups of tests. So we l
Hi Jeff,
On Wed, 16 May 2012 03:40:17 -0500 Jeff Rush wrote:
> Are many folks using zope.pytest? We're looking into it but, for such a
> small amount of code, are finding it a bit odd and seemingly broken.
No, I don't think many folks are using it right now. zope.pytest was a
quick shot to chec
Are many folks using zope.pytest? We're looking into it but, for such a
small amount of code, are finding it a bit odd and seemingly broken.
Breaking down the basic creation of an application object, here is what
the code does, with indentation to show what a method call performs:
create_app()
