Tests/Network/100XO/Collaboration

From OLPC

< Tests
Revision as of 16:18, 20 December 2009 by Cjl (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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

Stream Any
Category Network Sub-category 100XO
Component warning.pngEmpty strings are not accepted.
Feature warning.pngEmpty strings are not accepted.
Objective To verify collaboration working with a 100 XO, 2 AP testbed.
Tools 50 XOs connected to 2 APs/ Note the AP hardware you are using!
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 # 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
Collaboration for all 4 activities should persist for longer than 2 hours.
Comments warning.pngEmpty strings are not accepted.
Release Stream Build Pass/Fail Trac Ticket(s) Comment(s) Date of Test
Facts about Tests/Network/100XO/CollaborationRDF feed
Build stream Any  +info.pngLink to builds in stream, Packages in stream, ChangeLog, Differences vs joyride
More notes warning.pngEmpty strings are not accepted.
Pass criteria Collaboration for all 4 activities should persist for longer than 2 hours.
Short name 100 XO, 2 AP collaboration  +
System component warning.pngEmpty strings are not accepted.
System feature warning.pngEmpty strings are not accepted.
Test category Network  +
Test objective To verify collaboration working with a 100 XO, 2 AP testbed.  +
Test procedure # Verify (by taking a picture, sending a C # 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. te connectivity for each 3 XO group again.
Test setup # Connect all 100 XOs to the APs (50 on on # Connect all 100 XOs to the APs (50 on one, 50 on the other).
  • Designate 1 XO as the host.
  • Start Chat, Browse, and Record on the host XO. Share all three Activities with Neighborhood.
  • On the other 99 XOs, join the Chat, Browse, and Record sessions.
  • 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. 99 laptops, with 1 laptop not using Write.
  • Test subcategory 100XO  +
    Test tools 50 XOs connected to 2 APs/ Note the AP hardware you are using!  +
    Personal tools
    • Log in
    • Login with OpenID
    About OLPC
    About the laptop
    About the tablet
    Projects
    OLPC wiki
    Toolbox