Testing: Difference between revisions
| Line 3: | Line 3: | ||
=== Test Strategy === |
=== Test Strategy === |
||
There are many people and organizations who are helping out with the test effort for the XO, network communications, the server, performance and system testing. This page will summarize all the test efforts and link to more details where ever possible. |
There are many people and organizations who are helping out with the test effort for the XO, network communications, the server, performance and system testing. This page will summarize all the test efforts and link to more details where ever possible. |
||
The open source community is providing a good test effort for much of the open source code. In our local test plans we need to concentrate on areas that are not easy or possible for the community due to lack of physical XO, Server, or other OLPC specific equipment. |
|||
Trac is being used to track bugs found during test. We currently don't have a system for test case management, but we may want to implement something for that as well. |
Trac is being used to track bugs found during test. We currently don't have a system for test case management, but we may want to implement something for that as well. |
||
| Line 17: | Line 19: | ||
# Programming |
# Programming |
||
Collaboration and communication should work across these |
Collaboration and communication should work across these activities. |
||
[[Release Criteria Trial-2]] |
|||
Revision as of 15:13, 24 May 2007
Test Strategy
There are many people and organizations who are helping out with the test effort for the XO, network communications, the server, performance and system testing. This page will summarize all the test efforts and link to more details where ever possible.
The open source community is providing a good test effort for much of the open source code. In our local test plans we need to concentrate on areas that are not easy or possible for the community due to lack of physical XO, Server, or other OLPC specific equipment.
Trac is being used to track bugs found during test. We currently don't have a system for test case management, but we may want to implement something for that as well.
Release Criteria:
The release criteria for Trial-2 software is based on meeting the expectations of as many as 2000 children and teachers using OLPC products to evaluate whether this is the right product for their school/country.
With that in mind, we need to focus on a few good features to demonstrate 'explore', 'express', and 'communicate' with good quality. This translates to prioritizing the following features:
- Writing
- Drawing
- Video create
- Programming
Collaboration and communication should work across these activities.
Test plans/pages:
- Quanta HW test plan - One time test per build. This test is aimed at environmental conditions (thermal, humidity, altitude, shake)
- Quanta SW Test plan - One time test per SW release to Quanta. This test is aimed at basic functionality of XOs.
- OLPC Test Plan - One time test per build. Written for B2, to be modified for B3 so as not to overlap Tinderbox or Quanta testing. Detailed manual testing for camera, keyboard, USB, mouse pad, other devices, power management.
- Tinderbox Testing - Regression after all new SW builds. This test is aimed at boot up, X drivers, low level device testing, network, and performance at the CPU level, and power management.
- User Stories Testing - One time test per SW release. This testing is aimed at system level testing based on real user stories.