Re: [Zope-dev] How to test changes to ZTK packages?
On Jun 30, 2009, at 10:14 AM, Stephan Richter wrote:
On Tuesday 30 June 2009, Jim Fulton wrote:
I should know this, but I don't. What is the recommended way to test changes to core ZTK packages to mitigate the risk that changes affect other packages? Is there a page somewhere with instructions?
I tried using using zope.release. Building the trunk of zope.release with Python 2.4 and running the tests gives lots of test import errors and test failures. (Lots of tests want to import z3c.pt.) The tests hang when I try to build and run with Python 2.6.
Yes, I think testing with zope.release is a good way of doing this right now.
What is the difference between zope.release and zope.kgs? Is the latter a fossil? Does it need to go away? Why does zope.release have a 2-step build process? Perhaps naively, it seems that one could define a simple project that defined a test script over a "known good set" of projects. Is the 2-step process a consequence of maintaining the index or tar ball? (I'm not criticizing, I'm just trying to understand.) Jim -- Jim Fulton Zope Corporation
On Wednesday 01 July 2009, Jim Fulton wrote:
What is the difference between zope.release and zope.kgs? Is the latter a fossil? Does it need to go away?
zope.kgs is the software and zope.release is the management of the Zope 3 KGS. So a Grok KGS would use zope.kgs but not zope.release.
Why does zope.release have a 2-step build process? Perhaps naively, it seems that one could define a simple project that defined a test script over a "known good set" of projects. Is the 2-step process a consequence of maintaining the index or tar ball? (I'm not criticizing, I'm just trying to understand.)
I have been bothered by this before, but not enough to fix it. Basically, It could easily be one step. The two steps stem from the fact that you have a KGS file from which you produce all sorts of interesting artifacts. The test setup is one such artifact. you then use the artifact. Of course, for convenience one step would be fine. Maybe it is even a PITA in zope.release. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"
On Jul 1, 2009, at 1:42 PM, Stephan Richter wrote:
On Wednesday 01 July 2009, Jim Fulton wrote:
What is the difference between zope.release and zope.kgs? Is the latter a fossil? Does it need to go away?
zope.kgs is the software and zope.release is the management of the Zope 3 KGS. So a Grok KGS would use zope.kgs but not zope.release.
Why does zope.release have a 2-step build process? Perhaps naively, it seems that one could define a simple project that defined a test script over a "known good set" of projects. Is the 2-step process a consequence of maintaining the index or tar ball? (I'm not criticizing, I'm just trying to understand.)
I have been bothered by this before, but not enough to fix it. Basically, It could easily be one step.
The two steps stem from the fact that you have a KGS file from which you produce all sorts of interesting artifacts. The test setup is one such artifact. you then use the artifact. Of course, for convenience one step would be fine. Maybe it is even a PITA in zope.release.
OK, well, I'll try to sort this out using zope.release. Wish me luck. :) Jim -- Jim Fulton Zope Corporation
participants (2)
-
Jim Fulton -
Stephan Richter