Comment 16 for bug 916545

As I said, I wasn't sure how easy it would be. It just seemed like a nice opportunity to add tests to one of the important components. Like SirVer mentioned, I imagined something like running a local server and seeing if that responds in the expected way would be the easist way. (Mocking [1] might also be appropriate.)

I have to admit I wasn't really sure to what extent there would be to create an identical replacement or rather a server performing the same tasks. (If that makes sense?) In the latter case, tests for the old server would obviously not work for the new one. So that part is probably not relevant.

All in all though, it is probably more important to get something which work than to be able to automatically check whether it works. ;) So while I ideally would appreciate to see a test suite added at the same time, I'm perfectly happy that someone is capable of adding a replacement. It can also be argued that as long as for instance the protocol is still discussed writing tests might be a waste of time as those parts end up being changed later anyways, so it might make more sense to add them later, when we have a working implementation. I also realize that developer time is limited.

[1] http://en.wikipedia.org/wiki/Mock_object