deprecate trial, focus on a more widely-used unit test runner

New submission from zooko <[email protected]>:

I've been setting up continuous integration using Hudson. These instructions make it very easy to set up junit-xml integration, coverage.py integration, and other things: http://redsolo.blogspot.com/2007/11/hudson-embraces-python.html . I got that running -- it took about 10 minutes -- and then I decided to do the same thing with trial. This has taken one whole day since then and I'm still not done.

I propose that the Twisted project deprecate trial and start supporting nosetests (or py.test, or anything that a lot of other non-Twisted-hackers are also supporting).

A requirement for this would be that the Twisted test suite itself can run under this alternative runner.

I hasten to add that I like trial. It is IMO well-engineered and well-maintained. The only advantage that nosetests has is that it is more widely used and comes with a lot more howtos like http://redsolo.blogspot.com/2007/11/hudson-embraces-python.html , integrations into other tools like hudson, etc.

The advantage of declaring nosetests (or some such tool) to be the primary testing tool for Twisted would be that more people would use it and report bugs in its Twisted integration (http://code.google.com/p/python-nose/source/browse/nose/twistedtools.py ) and contribute improvements to its twisted integration. Another advantage would be that people who are considering using twisted and who already use nosetests would feel reassured that their familiar testing tools will work well with this unfamiliar library.

Thomas Herve said on IRC that there were some problems with the nose/twistedtools.py code, but he didn't give details. If I end up switching my current project from "integrate trial with all these other tools" to "integrate nose with twisted" then I'll report on this ticket how it went.

----------
Type     : task
Component: trial
Keywords : 
Priority : normal
Nosy     : 
----------
http://twistedmatrix.com/trac/ticket/4306