Sri Lanka Testers
OLPC Sri Lanka QA Page
Testing teams have been organized by Sri Lanka to do a more comprehensive functional and regression testing. Functional testing is about ensuring that the OLPC XO functions as it was intended by the designers. This is different to usability testing that is typically carried out. However functional testing needs clear requirements and standards specifications, which the Sugar activities are often missing. Thus the initial part of functional testing was to gather the requirement specifications from the community in order to be able to write the test cases. You can find out more about this at the following references. [Ref: Requirements based Functional Testing, Types of Testing ]
Introduction
The OLPC (One Laptop Per Child) Foundation affiliated with MIT(Massachusetts Institute of Technology) Media Labs in Boston creates educational opportunities for the world's poorest children by providing each child with a rugged, low-cost, low-power, connected laptop with content and software designed for collaborative, joyful, self-empowered learning.
Testing Engagement
The focus of testing for the Sri Lankan team has been functional testing. 800+ test cases have been captured after seeking input from the community on the expected functionality and from the various standards and documentation in the WIKI. You can find the detailed test cases and results of testing below.
Picture of Virtusa testing team working running test cases.
Testing Process
Below is a depiction of the high level process we followed when testing the OLPCs.
Quick Start for new Testers
The following documents provide a packaged quick guide and reference for new testers who wish to quickly come upto speed with testing process for the OLPC. It contains much, specific to testing that has been extracted from the OLPC WIKI, community discussions, trial and error and some of the Virtusa best practices as well.
Test Cases
800+ test cases have been captured for functional and regression testing so far of the various hardware and software test areas listed below. You can find out more about what a test case should contain here
Sample Test Case (template)
The table below gives a custom test case template that we have used to perform testing.
| Test Case ID | Category | Feature Description | Prerequisite | Test Description | Input Data | Expected Result | No Of TC combination | Status (Pass/Fail) |
|---|---|---|---|---|---|---|---|---|
| 1. Verify the navigation to the Paint Activity | ||||||||
| 1 | ||||||||
| 1.1. Verify the navigation to the Main Menu | ||||||||
| 1.1 | ||||||||
1.Hardware
Hardware Abbreviations
| Hardware Abbreviations | |
|---|---|
| Audio (Mic, Micro phone, Speakers) | AUD |
| Booting | BOT |
| Charging & Discharging | CHR |
| Direct Suspend & Idle Suspend | SUP |
| Game buttons | GMB |
| Initial Installation | IIT |
| Key board | KBD |
| Lid | LID |
| OLPC indicators | OID |
| Resume | RES |
| Screen | SCR |
| Touch pad | TPD |
| Wireless | WIR |
Hardware Testing
| Component \ Area | Component \ Area Description | Component \ Area Decision Tree Diagram | Component \ Area Test Cases | QA Contact | Developer Contact |
|---|---|---|---|---|---|
| Audio,Screen and Charging | Description | Tree Diagram | Test Case | Sandun Sandun.mohottige@gmail.com | Developer Contact |
| Boot | Description | Tree Diagram | Test Case | Dhanushka dhanushkaprjct@gmail.com | Developer Contact |
| Direct & Idle Suspend | Description | Tree Diagram | Test Case | QA Contact | Developer Contact |
| Indicators | Description | Tree Diagram | Test Case | Ruwan rtf.fdo@gmail.com |
Developer Contact |
| Installation | Description | Tree Diagram | Test Case | Dhanushka dhanushkaprjct@gmail.com | Developer Contact |
| Keyboard | Description | Tree Diagram | Test Case | Ruwan rtf.fdo@gmail.com |
Developer Contact |
| Lid | Description | Tree Diagram | Test Case | Ruwan rtf.fdo@gmail.com |
Developer Contact |
| Touch Pad | Description | Tree Diagram | Test Case | QA Contact | Developer Contact |
| Wireless | Description | Tree Diagram | Test Case | QA Contact | Developer Contact |
2.Activity
Activity Abbreviations
| Acitivity Abbreviations | |
|---|---|
| Browse | BRW |
| Calculate | CAL |
| Chat | CHT |
| Colors | COL |
| Distance | DIS |
| Etoys | ETY |
| Finance | FIN |
| Measure | MEA |
| Memorize | MEM |
| Physics | PHY |
| Paint | PNT |
| Record | REC |
| Read | RED |
| Scratch | SCT |
| Social cal | SOL |
| Speak | SPE |
| Stop Watch | STW |
| Tam Tam jam | TAM |
| Typing Turtle | TYP |
| Words | WOR |
| Write | WRI |
Activity Testing
The team has been captured over 800 test cases on the OLPC activities so far. The table provides the Activity Description, Decision tree diagram & Test cases:
| Activity Name | Activity Description | Activity Decision Tree Diagram | Activity Test Cases | QA Contact | Developer Contact |
|---|---|---|---|---|---|
| Browse | Description | Tree Diagram | Test Case | Nuwan (nuwannilupul@gmail.com) | Developer Contact |
| Calculator | Description | Tree Diagram | Test Case | Niranjala (ggnfer@yahoo.com) | Developer Contact |
| Color | Description | Tree Diagram | Test Case | QA Contact | Developer Contact |
| Paint | Description | Tree Diagram | Test Case | Kirja (nkirja80@gmail.com) | Developer Contact |
| Physics | Description | Tree Diagram | Test Case | Kirja (nkirja80@gmail.com) | Developer Contact |
| Read | Description | Tree Diagram | Test Case | Anuruddhika (anuruddthika@gmail.com) | Developer Contact |
| Record | Description | Tree Diagram | Test Case | Anuruddhika (anuruddthika@gmail.com) | Developer Contact |
| Scratch | Description | Tree Diagram | Test Case | Niranjala (ggnfer@yahoo.com) | Developer Contact |
| Speak | Description | Tree Diagram | Test Case | Kirja (nkirja80@gmail.com) | Developer Contact |
| StopWatch | Description | Tree Diagram | Test Case | Niranjala (ggnfer@yahoo.com) | Developer Contact |
Test Results
Overall Test results till now
This is the overall status of the testing till present. And we are installing new releases as well.
| Coverage | Total Pass | Total Fail | No of On Hold | Total Test case | %Completed | % Pass | % Comments |
|---|---|---|---|---|---|---|---|
| 1. Hardware Test Result | |||||||
| Audio | 11 | 0 | 0 | 11 | 100 | 100 | |
| Boot | 2 | 0 | 0 | 2 | 100 | 100 | |
| Direct/Idle Suspend | 3 | 0 | 0 | 3 | 100 | 100 | |
| Installation | 9 | 0 | 0 | 9 | 100 | 100 | |
| Resume | 5 | 0 | 0 | 5 | 100 | 100 | |
| Screen | 5 | 0 | 0 | 5 | 100 | 100 | |
| Touch pad | 6 | 0 | 0 | 6 | 100 | 100 | |
| 2. Activity Test Result | |||||||
| Browse | 40 | 0 | 1 | 41 | 97.56 | 97.56 | On hold due to pending clarifications |
| Calculator | |||||||
| Color | |||||||
| Etoys | 65 | 0 | 1 | 66 | 98.48 | 98.48 | On hold due to pending clarifications |
| Finance | |||||||
| Measure | 19 | 0 | 0 | 19 | 100 | 100 | |
| Memorize | |||||||
| Paint | 70 | 4 | 0 | 74 | 100 | 94.59 | Fails due to following existing bugs. Ticket #1863, #6231, #9025, #6320 and newly entered bug ticket #1902 |
| Physics | |||||||
| Read | 26 | 0 | 0 | 26 | 100 | 100 | |
| Record | 22 | 1 | 0 | 23 | 100 | 95.65 | Fail due to ticket #1945 |
| Scratch | 34 | 0 | 1 | 35 | 97.14 | 97.14 | On hold due to pending clarifications |
| SocialCalc | 28 | 0 | 0 | 28 | 100 | 100 | |
| Speak | 21 | 0 | 0 | 21 | 100 | 100 | |
| Stop watch | |||||||
| Tam Tamjam | 21 | 1 | 0 | 22 | 100 | 95.45 | Fail due to ticket #1923 |
| Typing Turtle | |||||||
| Words | |||||||
| Write | 0 | 1 | 53 | 54 | 1.85 | 0 | |
| Total | 397 | 7 | 56 | 460 | 87.83 | 86.3 | |
Initial SL Testing Team
Coordinators
- Chamindra De Silva
- Dhanushka Ranganath
- Kapila Karunaratne
- Samanthi Kumarasinghe
Team Leaders
- Karthika Karunanithy
- Yasoda De Silva
- Shanthi Karunaratna
- Prasanna Gunawardana
Team Members
- Dhanushka Nainanayake (Leader - Hardware testing)
- Kirja Nanthagopal (Leader - Activity testing)
- Anuruddhika Chandrakeerthi
- Johan Sahabandu
- Madhushani Bogahawattage
- Nipuni Malwenna
- Niranjala Fernando
- Nuwan Weerasinghe
- Ruwan Fernando
- Sandun Mohottige
- Mohammadu Asran (Developer)
- Mihirani Gunawardana (Developer)