XMPP collaboration and scalability testing: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
Line 7: Line 7:


Work in progress..
Work in progress..


== Test plan ==

* Setup a ejabberd server running the same version and with the same configuration (including shared roster patches) as on XS.
FIXME: What's this configuration exactly?

* Configure N XO's and/or sugar-jhbuild instances to use this server
* Connect them to the jabber server
* Check if N buddies are displayed on the mesh view (using the sugar-xos script) of each laptop
* For each buddy:
** Start and share a Connect instance
** Check if this activity is displayed on the mesh view of each laptop (FIXME: write a xo-activities script ?)

Then restart the procedure with N+M laptops

Revision as of 14:39, 7 August 2008

There are three cases we want to test for

  • XO's failing to connect to the xmpp server: (#5908)
  • The xmpp server falling over (runs out of memory) (#5313)
  • XO's and activities not showing up in all neighbourhood views (#6884,#6888,#6940,#7457)

Specifically, we want to know if these situations occur under all loads or only when the xmmp server has a certain amount of logged in users. And ofcourse, if the bug is on the server side or the client side

Work in progress..


Test plan

  • Setup a ejabberd server running the same version and with the same configuration (including shared roster patches) as on XS.

FIXME: What's this configuration exactly?

  • Configure N XO's and/or sugar-jhbuild instances to use this server
  • Connect them to the jabber server
  • Check if N buddies are displayed on the mesh view (using the sugar-xos script) of each laptop
  • For each buddy:
    • Start and share a Connect instance
    • Check if this activity is displayed on the mesh view of each laptop (FIXME: write a xo-activities script ?)

Then restart the procedure with N+M laptops