Smoke test: Difference between revisions
Jump to navigation
Jump to search
(+section) |
|||
Line 4: | Line 4: | ||
# Connect to a local mesh and see other XOs (this needs to be in a location with no school server or infrastructure AP) |
# Connect to a local mesh and see other XOs (this needs to be in a location with no school server or infrastructure AP) |
||
# Run a collaborative activity (AbiWord, Connect4, or Chat) with another XO |
# Run a collaborative activity (AbiWord, Connect4, or Chat) with another XO |
||
# Run Browse and ensure that library navigation sidebar and index page loads |
# Run Browse and ensure that library navigation sidebar and index page loads; successfully browse the internet. |
||
# Ensure that the journal is able to resume an activity |
# Ensure that the journal is able to resume an activity |
||
# Connect to an AP (and/or school mesh) and browse the web |
# Connect to an AP (and/or school mesh) and browse the web |
Revision as of 19:37, 5 September 2007
Full-build smoke test
This set of test cases represents a quick smoke test that the build should pass:
- Boot into sugar
- Connect to a local mesh and see other XOs (this needs to be in a location with no school server or infrastructure AP)
- Run a collaborative activity (AbiWord, Connect4, or Chat) with another XO
- Run Browse and ensure that library navigation sidebar and index page loads; successfully browse the internet.
- Ensure that the journal is able to resume an activity
- Connect to an AP (and/or school mesh) and browse the web
- Connect one XO to an AP; then boot a second XO, which should connect to a local mesh and browse the web through the second XO.