Hi Benji

> Betreff: Re: [Zope3-dev] Why do we restrict our egg testing?
> Roger Ineichen wrote:
> > Can anybody tell me why we restrict our test setup in zope eggs and 
> > only use a subset of package for our test setup?
> I don't know what you're asking, so I can't tell you why it is <wink>.

I mean, we don't use all zope packages in our test dependency
if we develop eggs. What was the reason to use a subset of
of zope packages for egg testing? 

extras_require = dict(
        test = [
            'some more zope.* packages but why not all zope.*'

> > Why do we not use a Zope3 meta egg which contains all our zope 
> > packages as a test base. This whould allow us to test the 
> same we have 
> > in the zope3 trunk and let us run *buildout/test -s zope* 
> from within 
> > each egg.
> Perhaps because there isn't a Zope 3 meta egg.

I see

> > btw,
> > what is the builbot doing right now? Does the builbot still 
> runs test 
> > on the trunk? Or does the buildbot test the eggs?
> It doesn't do much of value at all right now.  The transition 
> to individual projects per package has left it behind.  There 
> are good ideas to make the buildbot work with the new setup, 
> now we need someone to implement them.

Is there a benefit to not depend on all zope.* packages
in each egg test setup if we do a transition to indvidual

I understand the benefit to have smaller dependencies
in eggs, but I still think a egg should run all tests
we have in the zope namespace. Like we did in our old
trunk setup.

python test.py -s zope -pv

could be now in a egg:
bin\test -s zope -pv

This whould allow us to run all zope.* tests
during egg development. 

Roger Ineichen

> --
> Benji York
> Senior Software Engineer
> Zope Corporation
> _______________________________________________
> Zope3-dev mailing list
> Zope3-dev@zope.org
> Unsub: 
> http://mail.zope.org/mailman/options/zope3-dev/dev%40projekt01.ch

Zope3-dev mailing list
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to