Hi,
A while back, I wrote collective.xmltestreport [1,2]. In short, it's a
wrapper around zope.testing's test runner that can produce output in
an XML format compatible with the xUnit family of testing tools. This
is useful for integrating with things like Hudson, which can parse
these kinds of files.
The problem is that changes in zope.testing/zope.testrunner keep
breaking collective.xmltestreport. At first, I was using "-x" as the
option to turn on XML output, before zope.testing took that option as
its own. Now, with version 3.10, it's broken again, because it's
trying to import zope.testing.testrunner, which is no longer there.
I wonder if it'd be a good idea to just merge this functionality into
zope.testrunner itself?
The problem is that in the short term, I probably won't have time to
look into it. I may, but there are a few other things that have to
take precedence. I was going to just leave it, but given that people
are working on zope.testing/zope.testrunner right now, I thought I'd
bring it up and see if there was any interest. I'd be happy to support
anyone who wants to attempt this, and in reality it's only a couple of
relatively small modules that need to be transposed into the codebase.
It'd need better (read: some) test coverage if it were to go into
zope.testrunner, though.
Is there interest in this kind of thing?
Martin
[1] http://pypi.python.org/pypi/collective.xmltestreport
[2] http://svn.plone.org/svn/collective/collective.xmltestreport/trunk
I've released zope.sqlalchemy 0.6 with the following changes:
* Implement should_retry for sqlalchemy.orm.exc.ConcurrentModificationError
and serialization errors from PostgreSQL and Oracle.
(Specify transaction>=1.1 to use this functionality.)
* Include license files.
* Add ``transaction_manager`` attribute to data managers for compliance with
IDataManager interface.
Release available from http://pypi.python.org/pypi/zope.sqlalchemy
Laurence
Considering recent discussions on Python 2.7 support, should we disable the
failure reports for Python 2.7? (6 failures out of 17 in the last report)
Christophe
Hi again,
another week another developer meeting in IRC.
We had a bugday last week and we should review that and plan ahead.
We've also had the languishing bug check run for a while without too
much improvements, so I'd also like to spend some time triaging them.
Additional topic suggestions are, as always, welcome.
See http://docs.zope.org/zopetoolkit/zope-dev/zope-dev-20100720.html
(should be available in a few minutes).
Christian
--
Christian Theune · ct(a)gocept.com
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1
Zope and Plone consulting and development
Hi everyone,
here's the Doodle for our next bug day:
http://www.doodle.com/6gydequztpac3xud
I'd like to see many people there, so if you have any questions that
need answering before you can join us on the bug day: ask them!
Christian
--
Christian Theune · ct(a)gocept.com
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1
Zope and Plone consulting and development
Am I doing something wrong? I have a dedicated python 2.6, and run
python2.6 dev.py and then bin/test.
--
Lennart Regebro, Colliberty: http://www.colliberty.com/
Python, Zope, Plone blog: http://regebro.wordpress.com/
Telephone: +33 661 58 14 64