|Build stream ||11.2 +info.pngLink to builds in stream, Packages in stream, ChangeLog, Differences vs joyride , and Any +info.pngLink to builds in stream, Packages in stream, ChangeLog, Differences vs joyride |
|More notes ||Should be run on all XO platforms supported for a build, unless otherwise instructed.|
|Pass criteria ||The following should happen:
- All activit … The following should happen:
- All activities installed on the XO platform(s) chosen should open, do basic actions, and close correctly.
- No exceptions should occur. (This testcase should not fail however for known documented cases unless they block the ability to run an activity properly.) the ability to run an activity properly.)
|Short name ||Sanity Check +|
|System component ||Generic +|
|System feature ||Smoke test +|
|Test category ||Activity +|
|Test objective ||basic activity sanity check +|
|Test procedure ||On all platforms (XO-1, XO-1.5, etc.) to b … On all platforms (XO-1, XO-1.5, etc.) to be tested:
Select an activity in Sugar, and start it for testing.
Do a basic action to verify that the activity is working.
Verify that all menus in the activity are visible and make sense.
Close the tested activity.
Move on to the next activity to test, and repeat the above procedure. Be sure to eventually test all activities visible in Sugar. (There likely are not enough system resources available to open all activities at once.)
Verify that no exceptions are recorded in any Sugar or activity logs. re recorded in any Sugar or activity logs.|
|Test setup ||n/a|
|Test subcategory ||Generic +|
|Test tools ||n/a +|