On Feb 5, 2007, at 11:41 PM, Fred Drake wrote:
On 2/5/07, Baiju M <[EMAIL PROTECTED]> wrote:
I have created zope.app egg two weeks back
(http://svn.zope.org/zope.app/trunk/)
I have used setuptools.find_packages function, so setuptools is a
dependency.
Should we need compatibility with distutil
On Feb 5, 2007, at 11:34 PM, Baiju M wrote:
Jim Fulton wrote:
On Feb 5, 2007, at 4:40 AM, Baiju M wrote:
> We have to add test layer for each packages in zope.app namespace.
I think we should. I'm not sure we *need* to. I certainly don't
want to do this if it will delay full eggification.
On 2/5/07, Baiju M <[EMAIL PROTECTED]> wrote:
I have created zope.app egg two weeks back
(http://svn.zope.org/zope.app/trunk/)
I have used setuptools.find_packages function, so setuptools is a
dependency.
Should we need compatibility with distutils.core ?
I suspect it's fine ok for an egg-suppo
Jim Fulton wrote:
On Feb 5, 2007, at 4:40 AM, Baiju M wrote:
> We have to add test layer for each packages in zope.app namespace.
I think we should. I'm not sure we *need* to. I certainly don't
want to do this if it will delay full eggification. As I've
mentioned before, I'd be perfectly ha
On Feb 5, 2007, at 4:40 AM, Baiju M wrote:
We have to add test layer for each packages in zope.app namespace.
I think we should. I'm not sure we *need* to. I certainly don't
want to do this if it will delay full eggification. As I've
mentioned before, I'd be perfectly happy to see
Hi,
We have to add test layer for each packages in zope.app namespace.
I have added few of them. This is easy but massive task, boring too :)
Here is the remaining list of packages:
apidoc
applicationcontrol
authentication
boston
component
dav
debugskin
exception
file
generations
http
i18nfi
Hi,
Few weeks back we discussed using test layers for zope.* packages.
I tried to do it in my checkout. Here is the patch for trunk:
http://zissue.berlios.de/z3/zope-testbrowser-diff.txt
When running the tests the output will be like this :
http://zope3.pastebin.com/851855
Jim wants to do it
Jim Fulton wrote:
I may be missing some then... which narratives are you thinking of?
You cited 3 in your note.
I'd like there to be a good narrative that actually ships in
zope.testing, I'm willing to do the work to make that happen provided I
can get some help on writing the doctest of zo
Chris Withers wrote:
Jim Fulton wrote:
Am I right in assuming that there aren't any good narrative docs for
test layers?
This is obviously in the eye of the beholder. I'm sure the people
who created narratives tried to do a good job. Perhaps you can do better.
I may be missing some then...
Jim Fulton wrote:
Am I right in assuming that there aren't any good narrative docs for
test layers?
This is obviously in the eye of the beholder. I'm sure the people
who created narratives tried to do a good job. Perhaps you can do better.
I may be missing some then... which narratives are y
Martin Aspeli wrote:
Layers are ... layered. If your test base class has layer X and a test case
subclass of that has layer Y, then it will set up X, run all the X tests,
then setup Y and run all the Y and X&Y tests, then tear down Y and then X.
I didn't mention subclassing tests. Personally,
Chris Withers wrote:
Hi All,
Am I right in assuming that there aren't any good narrative docs for
test layers?
This is obviously in the eye of the beholder. I'm sure the people
who created narratives tried to do a good job. Perhaps you can do better.
...
Now, related to this, say I have co
Chris Withers wrote:
>
> Now, related to this, say I have content objects X and Y, which are
> expensive to set up. I have LayerX which sets up a sample content object
> X, and LayerY which does the same for content object Y. This is fine for
> tests which need one or other content type, but
Hi All,
Am I right in assuming that there aren't any good narrative docs for
test layers?
I've read the relevant text files in zope.testing but am none the wiser...
I found an article of Philipp's here which helped a bit:
http://www.z3lab.org/sections/blogs/philipp-weitershausen/2006_03_10_d
14 matches
Mail list logo