Open quinkennedy opened 10 years ago
The way I am envisioning this now, is simply a "parrot" client for each library, and then one testing client that will send a message of each type (each supported type plus a few examples of custom types) and expect the same in response.
The following post is one example of what we want to avoid: https://groups.google.com/forum/#!topic/spacebrew-cc/978nPJEjzKQ
This should probably be split into a separate issue for each test script. I don't have experience in test-driven dev, but perhaps some "black-box" testing of each app as a whole would be good. I'm envisioning test scripts for: