documentation lacks a TDD example.

[Robert Collins]

The documentation (specifically the finger-server evolution) gives a nice intro
to the code, but without demonstrating how to unit test the code being written.
Given twisteds event driven nature this makes it hard to learn to write good
unit-tested twisted code. It would really help to have a TDD version of the
finger-server evolution.

http://twistedmatrix.com/bugs/issue1148: http://twistedmatrix.com/bugs/issue1148

[Matthias Klose (doko)]

which twisted version?

[Robert Collins (lifeless)]

all of them ;0. There is now an upstream bug for this
..http://twistedmatrix.com/bugs/issue1148

[rusivi2 (rusivi2-deactivatedaccount)]

Thank you for posting this bug.

Does this occur in Lucid?

[Robert Collins (lifeless)]

Thats very easy for you to check you know, and given the upstream bug watch you don't even need to look at the code!

[rusivi2 (rusivi2-deactivatedaccount)]

Robert Collins, thank you for responding so quickly and contributing to this bug. For me it is not that easy as I am learning about this. However, I will refrain from posting further unless I have something more constructive to add.

[Duncan McGreggor (oubiwann)]

I believe that this has been addressed with therve's addition to the last release:
  http://twistedmatrix.com/documents/current/core/howto/trial.html

[Glyph Lefkowitz (glyph)]

The "remote watch" thingy appears to be targeting the wrong ticket. It's pointed at #1148 but based on its description it should arguably be pointed at http://twistedmatrix.com/trac/ticket/2443. I can't figure out how to re-target it, but someone else should feel free to. Perhaps a Launchpad usability bug, too?