XMPP collaboration and scalability testing: Difference between revisions

From OLPC
Jump to navigation Jump to search
(New page: There are three cases we want to test for * XO's failing to connect to the xmpp server: ([http://dev.laptop.org/ticket/5908 #5908]) * The xmpp server falling over (runs out of memory) ([ht...)
 
No edit summary
Line 2: Line 2:
* XO's failing to connect to the xmpp server: ([http://dev.laptop.org/ticket/5908 #5908])
* XO's failing to connect to the xmpp server: ([http://dev.laptop.org/ticket/5908 #5908])
* The xmpp server falling over (runs out of memory) ([http://dev.laptop.org/ticket/5313 #5313])
* The xmpp server falling over (runs out of memory) ([http://dev.laptop.org/ticket/5313 #5313])
* XO's and activities not showing up in all neighbourhood views ([http://dev.laptop.org/ticket/6884, #6884],[http://dev.laptop.org/ticket/6884 #6884],[http://dev.laptop.org/ticket/6888 #6888],[http://dev.laptop.org/ticket/6940 #6940],[http://dev.laptop.org/ticket/7457 #7457])
* XO's and activities not showing up in all neighbourhood views ([http://dev.laptop.org/ticket/6884 #6884],[http://dev.laptop.org/ticket/6888 #6888],[http://dev.laptop.org/ticket/6940 #6940],[http://dev.laptop.org/ticket/7457 #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
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

Revision as of 14:13, 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..