Tests/Network/100XO/Collaboration: Difference between revisions

From OLPC
Jump to navigation Jump to search
(New page: {{Test case |testcase_name=100 XO, 2 AP collaboration |testcase_category=Network |testcase_subcategory=100XO |testcase_stream=Any |testcase_objective=To verify collaboration working with a...)
 
m (Walter's rectum 4 moved to Tests/Network/100XO/Collaboration over redirect: revert)
 
(One intermediate revision by one other user not shown)
(No difference)

Latest revision as of 16:18, 20 December 2009

Test case: Short name::100 XO, 2 AP collaboration
How to report results

Stream ,|x|Build stream::x}}
Category Test category::Network Sub-category Test subcategory::100XO
Component System component::
Feature System feature::
Objective Test objective::To verify collaboration working with a 100 XO, 2 AP testbed.
Tools Test tools::50 XOs connected to 2 APs/ Note the AP hardware you are using!
Setup [[Test setup::# Connect all 100 XOs to the APs (50 on one, 50 on the other).
  1. Designate 1 XO as the host.
  2. Start Chat, Browse, and Record on the host XO. Share all three Activities with Neighborhood.
  3. On the other 99 XOs, join the Chat, Browse, and Record sessions.
  4. Get XOs into groups of 3. Share a Write activity between each group of 3 XOs. (You will have 33 groups of 3 for a total of 99 laptops, with 1 laptop not using Write.]]
Procedure [[Test procedure::# Verify (by taking a picture, sending a Chat message, and sharing a bookmark in one of the XOs) that there is connectivity and collaboration between all XOs in those 3 Activities.
  1. Verify Write connectivity for each group of 3 XOs by typing in each XO in each 3 XO group, and seeing that the correct text shows up on the screens of the other 2 XOs each time.
  2. Wait at least 2 hours.
  3. Verify Chat, Browse, and Record collaboration for the 100-XO group again.
  4. Verify Write connectivity for each 3 XO group again.]]
Expected Results
and Pass Criteria
Pass criteria::Collaboration for all 4 activities should persist for longer than 2 hours.
Comments More notes::
Release Stream Build Pass/Fail Trac Ticket(s) Comment(s) Date of Test