[Twisted-Python] Running twisted.trial unittests using nose

[Jonathan Lange]

On 8/6/07, Chris Miles <miles.chris at gmail.com> wrote:
> I'm simply curious as to whether it is safe for me to rely on a test
> runner other than "trial" to run the tests?  I assume any magic
> (knowledge of deferreds) is within the
> twisted.trial.unittest.TestCase class and the "trial" command is
> simply another tool to discover and pretty print the results.  From
> what I've seen, both "nosetests" and "trial" will produce the same
> report (although "trial" looks nicer :-).  Or perhaps this wouldn't
> be the case if I needed to interact with the reactor?
>

So, what Glyph says modulo what Andrew says is right and good and true.

One known issue is that tests that descend from
twisted.trial.unittest.TestCase assume that they are being run inside
a twisted.trial.runner.TrialSuite. This suite does post-run cleanup of
thread pools, IIRC.

jml