Client Test Cases

This is a list of different test cases that client developers should apply to their code base.

= Tool Suite =

TODO: create and document an automated tool suite.

An ideal tool suite would be one of (or all of):


 * A hosted component with well-defined JIDs exhibiting the test case behavior
 * An XMPP component that can be self-hosted
 * A set of bot scripts / tools that can connect to a given (set of) account(s)

= Message Errors =

A client should properly support the following cases:


 * 1) A message is rejected by the other side - display error on message, show text message describing the failure in the details
 * 2) A message is accepted by the other side (you receive a Receipt) - display normally or with an additional checkmark
 * 3) A message is accepted (Receipt), then bounced (you receive an error) - the error is probably from a stale session and should be ignored - display checkmark
 * 4) A message is bounced, then accepted - first display error, then checkmark

There is a hosted version of test 1. at xmpp:reject@yax.im

= Multi User Chats =

Joining

 * 1) A join is not responded to at all by the MUC
 * 2) A join is responded to with an error presence
 * 3) The join response does not contain a subject
 * 4) The join response does not contain a self-presence
 * 5) The join response neither contains a subject nor a self-presence

Staying inside

 * 1) The client gets kicked by the MUC, with or without a message
 * 2) The client gets banned by the MUC, with or without a message
 * 3) The MUC join completes, but the occupant is then silently removed, all subsequent messages get rejected (see XEP-0410)

Affiliation

 * 1) The client gets muted by the MUC, with or without a message

= HTTP File Upload =

A testing component could reject the file slot request IQ with different errors based on the requested file name / file size. A client developer would have a set of according files to trigger different conditions.