Hi! On Sun, Jun 21, 2009 at 22:48, Niklas Gustavsson<[email protected]> wrote: > On Sun, Jun 21, 2009 at 10:21 PM, Bernd Fondermann<[email protected]> > wrote: >> But we're kind of talking very theoretical here (otherwise my answer >> could have been shorter and there'd be somebody still listening down >> here). Let's talk about a concrete example. > > Agreed, I'll see what I can come up with :-)
What about defining a high-level test suite which is abstract enough to be carried out by more than one XMPP library? I'm thinking of an abstracted API which can run on Smack and other libs for - openeing a connection, - registering useres, - sending messages and the like. Since the clients run under the same hood, checking whether a message arrives within a certain amount of time should be easy. With more than one client-implementation the chances are high that we catch interoperability bugs earlier. For example if I want to test my pubsub implementation I'd add 3 users, one publisher and two subscribers. When publishing a message, the two subscribers should receive a notification within a certain amount of time (some seconds), if not we've got a problem. This, of course, is complementary to the unit (whitebox) tests. Just a few early thoughts on this. Michael
