chewie.py is not really tested here.

[Bairdo]

#39 adds some tests, but more would be good.

look into mocking the socket operations.

[samrussell]

it would be better to refactor out the network-level stuff into its own classes - potentially a couple for the IO handling,, deserialising from the wire, and parsing the messages

that way we can test the following parts of the journey individually:

• socket IO lifecycle (port up/down, connection closed, device disappearing, probably easier tested offline as these classes shouldn't change once they're working)
• deserialising data into something meaningful (address/serialised message data)
• deserialising messages
• routing messages to the correct state machine
• serialising messages
• serialising serialised message + metadata into something to go in a packet
• socket IO lifecycle (as above)

im working on a raw packet IO lifecycle class at samrussell/rawserver and we probably want a similar one for the UDP packets, and once it's ready we should have a slightly higher level option that just calls the handler and plays nicely with eventlet