[Zope3-dev] Re: Why do we restrict our egg testing?
Hi, I thought Christian Theune already did some work on buildbots for Zope 3 buildouts. Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: Why do we restrict our egg testing?
On Thu, Sep 27, 2007 at 10:33:09AM -0400, Tres Seaver wrote: > Why would we want to pull in all of Zope3 as a dependency (worse, a > hidden one) before testing an egg? If the egg's dependencies are > broken, I *want* the tests to fail. I don't think testing against a > "fat" meta-egg satisfies that goal. Fix the egg so that its > 'install_requires' or 'tests_requires' are sufficient to make the tests > pass instead. There are two conflicting goals here: (1) testing that an egg's tests fail when its dependency list is incomplete (2) testing whether any of the other eggs that depend on this one break due to recent changes > I thought Roger was one of the folks looking to *reduce* the set of > dependencies his application had on zope3 coee -- testing against the > meta-egg actually makes that problem worse. I think Roger wants (2). Marius Gedminas -- "...the only place for 63,000 bugs is a rain forest" signature.asc Description: Digital signature ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
AW: [Zope3-dev] Re: Why do we restrict our egg testing?
Hi Tres > Betreff: [Zope3-dev] Re: Why do we restrict our egg testing? [...] > I thought Roger was one of the folks looking to *reduce* the set of > dependencies his application had on zope3 coee -- testing against the > meta-egg actually makes that problem worse. Yes, I was one of the folks proposing to take more care on separating things. And I'm also proposing running all tests for a single package in a namesapce which the package is using before deployment. I think testing is overall a quality management aspect. Let me explain quality management in a abstract context. If you have a house and the target is that arround your house the tings must be clean and arrangend. You will define soemthing like: All things arround my house have to be clean and not dirty. This quality management rule will work. If you define many different things like; My carpet in front of my hous door must be clean. This whould not work. Because why, if somebody takes the carpet and brings it to a cleaning company, probably the floor under the missing carpet is dirty then. And this does not fit with your overall quality target. This is similar to our testing concept. Using small test setups for single eggs without to focus on zope as a monolitic thing will fail. Regards Roger Ineichen > Tres. > - -- > === > Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] > Palladion Software "Excellence by Design"http://palladion.com ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Why do we restrict our egg testing?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephan Richter wrote: > On Thursday 27 September 2007 08:43, Benji York wrote: >> 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 . >> >>> 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. > > Roger is suggesting that we should have one, so that problems are detected > early. Any comments on that? Why would we want to pull in all of Zope3 as a dependency (worse, a hidden one) before testing an egg? If the egg's dependencies are broken, I *want* the tests to fail. I don't think testing against a "fat" meta-egg satisfies that goal. Fix the egg so that its 'install_requires' or 'tests_requires' are sufficient to make the tests pass instead. I thought Roger was one of the folks looking to *reduce* the set of dependencies his application had on zope3 coee -- testing against the meta-egg actually makes that problem worse. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG+78l+gerLs4ltQ4RApFIAJ9byQ03OzbOeYK8HAt+QFJMHQkxcwCdF1XJ 02Wi+nxNV3UnkNk2qaGIN6I= =r6Bz -END PGP SIGNATURE- ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
