ie if you wish to certify your client you point it at the server. From that point you run through the usual set of things you would do from the begining to end.
Say:
Register new user (in this case an id for the client that is being tested eg JClientv2),
login,
presence use,
roster management (adding/removing specially prepared fake JIDs that will automaticaly respond to these requests),
MUC tests,
sending receiving various types of messages,
file transfers with the test users,
etc...
every time it does an action that ID will be scored on how perfect it's XML is and if it responds correctly to errors, etc.
The score given at the end of testing would tell you how compliant your client is, where the faults lay and what level of certification the client is at.
Natasha Live
Hal Rottenberg wrote:
On 5/14/05, Natasha Live <[EMAIL PROTECTED]> wrote:
Sorry for being slightly naive on this but, are you on about a Basic
cert. based on compliance to the Core XMPP documents and then assigning
extra points for additional JEPs covered?
You basically have the idea. We would also rely on "meta-jeps" such as the Basic IM and Intermediate IM Suites.
_______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
