Activity testing template

This page has a more up-to-date location: Test cases 8.2.0#Create new test cases

Activity testing project | Testing matrix | Activity testing guide | Activity testing template +/-

---

To merge: Testing | Testing ideas | Friends in testing

---

See also: Sugar Labs testing | the Testing mailing list

Instructions for Template Use

Developers, use this template to create your test cases.

1. Create a new page, entitled Tests/ActivityName, replacing ActivityName with the name of your activity.
2. Cut and paste the table below into the new page.
3. Edit to add new test activities as you see fit.
4. Create a new entry in the Activity Testing Matrix.

Template

Parts no longer applies to Release 8.2.0, for example in 8.2.0 the Frame replaces the "Activity donut".

Action	Result
This is what a successful test looks like.	pass
This is what a failed test looks like.	fail, bug report
Opening the activity: click on the activity icon.
The icon appears in the activity donut, and pulses during activity startup.	-
The activity opens properly.	-
Closing the activity: click the X in the upper-right-hand corner of the activity.
The activity closes properly.	-
The icon disappears from the activity donut.	-
Journal functionality: open the journal activity.
A journal entry for the previous activity session appears.	-
Clicking on the journal entry restores the activity to an appropriate state.	-
Activity functionality: functional tests.
Add additional tests here.	-

The NZ activity test

Here is a quick list of things to go through when you test an activity and if you complete this checklist as you go it helps you report any bugs you find.

• Tester name:
• Activity Tested:
• Activity Version:
• Sugar Version or Build number:
• XO hardware or Emulate O/S:

• Activity Wiki Page: (provide link)
• Description on Wiki Page: yes/no
• Behaviour matches description on wiki: yes/no

• Sound works: yes/no
• Webcam works: yes/no
• Rotate key works: yes/no
• Joystick pad works: yes/no
• Game keys work: yes/no
• Black and white mode works: yes/no
• Save/Keep works: yes/no
• Stop button works: yes/no
• Resume from Journal works: yes/no

• Neighbourhood environment: (when doing test are you on MESH, ad hoc, using school server)
• Collaboration apparent: yes/no
• Share to Neighbourhood works: yes/no
• Can join Activity: yes/no
• Friends appear in frame: yes/no

• Comments on the test you have done: (write comments)
• Trac bug number: (write number here if you reported a bug in trac for sugarlabs or olpc)

Post all of this into your testing summary and email it to testing mailing list