Tests/Activity/Generic/Sanity Check: Difference between revisions

From OLPC
Jump to navigation Jump to search
(Test case creation)
 
m (use [ [ ] ] so Wiki link to feature works)
 
Line 5: Line 5:
|testcase_stream=11.2, Any
|testcase_stream=11.2, Any
|testcase_component=Generic
|testcase_component=Generic
|testcase_feature=Smoke Test
|testcase_feature=[[Smoke test]]
|testcase_objective=basic activity sanity check
|testcase_objective=basic activity sanity check
|testcase_tools=n/a
|testcase_tools=n/a
Line 16: Line 16:
# 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.)
# 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.
# Verify that no exceptions are recorded in any Sugar or activity logs.
|testcase_expectedresults= The following should happen:
|testcase_expectedresults=The following should happen:
# All activities installed on the XO platform(s) chosen should open, do basic actions, and close correctly.
# 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.)
# No exceptions should occur. (This testcase should not fail however for known documented cases unless they block the ability to run an activity properly.)

Latest revision as of 23:44, 8 February 2011

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