Tests/Activity/Generic/Sanity Check

From OLPC
< Tests
Revision as of 15:10, 3 February 2011 by Greenfeld (talk | contribs) (Test case creation)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Test case: Short name::Sanity Check
How to report results

Stream ,|x|Build stream::x}}
Category Test category::Activity Sub-category Test subcategory::Generic
Component System component::Generic
Feature System feature::Smoke Test
Objective Test objective::basic activity sanity check
Tools Test tools::n/a
Setup Test setup::n/a
Procedure [[Test procedure::On all platforms (XO-1, XO-1.5, etc.) to be tested:
  1. Select an activity in Sugar, and start it for testing.
  2. Do a basic action to verify that the activity is working.
  3. Verify that all menus in the activity are visible and make sense.
  4. Close the tested activity.
  5. 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.)
  6. Verify that no exceptions are recorded in any Sugar or activity logs.]]
Expected Results
and Pass Criteria
[[Pass criteria::The following should happen:
  1. All activities installed on the XO platform(s) chosen should open, do basic actions, and close correctly.
  2. No exceptions should occur. (This testcase should not fail however for known documented cases unless they block the ability to run an activity properly.)]]
Comments More notes::Should be run on all XO platforms supported for a build, unless otherwise instructed.
Release Stream Build Pass/Fail Trac Ticket(s) Comment(s) Date of Test