[Product-Developers] Running all Plone tests?

Chris Rossi chris at christophermrossi.com
Fri Jan 2 21:50:11 UTC 2009

Hello all,

I think this is probably mostly just a question about standard practice and
expected outcomes as regards testing in Plone.  I thought it would be cute
to try running all of the tests in Plone.  To do this I'm using the most
basic, undoctored buildout from ZopeSkel and then:

 $ bin/instance test

What I find is this results in a decent number of errors and doesn't
actually finish--the last output is a stack trace from one of the tests and
not a report of any kind.

Which, makes me wonder, does anybody do this?  Is it advisable to even think
about doing this?  Is the standard practice to just isolate and test the
modules that are relevant to what you're doing?

While it would be nice to have a nice, known to work, global baseline, I
understand that maybe some of these tests assume external dependencies in
your server environment are configured in a particular way.  What is the
standard practice, here, with regard to running these tests and what is the
expected outcome?

Running the above generated about 4MB of console output that I'm happy to
forward to anyone who cares take a gander.

Chris Rossi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.plone.org/pipermail/plone-product-developers/attachments/20090102/9a9ae9a6/attachment.html>

More information about the Product-Developers mailing list