Tests/Activity/Generic/Sanity Check

From OLPC

< Tests
Revision as of 23:44, 8 February 2011 by Skierpage (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Test case: Sanity Check
How to report results

Stream 11.2, Any
Category Activity Sub-category Generic
Component Generic
Feature Smoke test
Objective basic activity sanity check
Tools n/a
Setup n/a
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
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 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
Facts about Tests/Activity/Generic/Sanity CheckRDF feed
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:
  1. All activit The following should happen:
  2. All activities installed on the XO platform(s) chosen should open, do basic actions, and close correctly.
  3. 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  +
    Personal tools
    • Log in
    • Login with OpenID
    About OLPC
    About the laptop
    About the tablet
    Projects
    OLPC wiki
    Toolbox