Tests/Neighborhood view: Difference between revisions
< Tests
Jump to navigation
Jump to search
m (Neighborhood View Test Plan moved to Tests/Neighborhood view: unifying names) |
(fix cat) |
||
Line 54: | Line 54: | ||
* That after each XO closes the activity, it no longer appears clustered around it. |
* That after each XO closes the activity, it no longer appears clustered around it. |
||
[[Category:Test |
[[Category:Test Plans]] |
Revision as of 05:33, 22 March 2008
Notes
We are going to want to test the following scenario on at least three different network topologies:
- All XOs using a WiFi AP
- All XOs using a school server as an MPP
- No AP or MPP present.
So I'm thinking we may want to have three separate versions of this plan, but I'm hoping that's not necessary...
Also, you'll notice that I am very vague here about which activity to start, or what if anything to do once inside it. This is intentional, as this test plan only intends to test the mesh view itself. Filtering, searching, etc. will be going into this plan also.
Setup:
- No AP previously set up on any XO
- No school server
- Need anywhere from 2 to N XOs (Is N 100?)
Boot the XOs
Justification: HIG
Actions:
- Boot up each XO.
- On each XO, switch to neighborhood view.
Verify:
- That all XOs can see each other.
Start an activity
Justification: HIG
Actions:
- On the first XO, start any activity.
Verify:
- That all XOs can see the shared activity.
- That the activity icon took on the colors of the XO sharing it.
Join the activity
Justification: HIG
Actions:
- One by one, join the activity on all XOs.
- On each, switch to the neighborhood view.
Verify:
- That all XOs are seeing the same activity state.
- That all XOs appear to be clustered around the shared activity.
Close the activity
Justification: HIG
Actions:
- One by one, close the activity on all XOs.
Verify:
- That after each XO closes the activity, it no longer appears clustered around it.