On 03:34 pm, _...@lvh.cc wrote: >Hi, > > >I have no issue writing AMP responders TTD-edly, they work pretty much >the >way any other code would. However, I did notice that the only way I'd >notice if my Command definitions themselves were broken were if my >functional tests start failing.
Chris and I wrote all the AMP-using code for game TDD. See game/test/test_network.py in lp:game. Jean-Paul >It would be nice if I could write unit test driven Command >specifications, >as well. > >The quickest I could come up with was to call >makeArguments/makeResponse >with a few known-good/known-bad dictionaries, and see if it blows up. >Is >there a smarter way to do it? > >-- >cheers >lvh _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
