Testing: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{OLPC}} |
{{OLPC}} |
||
=== |
=== 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. |
|||
User Stories are meant to provide a narrative description of how the OLPC products will be used in schools and homes. These stories provide the basis for Use Case or System Tests that will help ensure we have prioritized and documented the most important uses of our products in the field. |
|||
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. |
|||
High level topics for User Stories can be divided into a few major categories: |
|||
# Start up (out-of-the-box experience) |
|||
# Connectivity and Collaboration |
|||
# Archive, Backup, Content |
|||
Test plans/pages that exist today: |
|||
# Quanta HW test plan - One time test per build. This test is aimed at environmental conditions (thermal, humidity, altitude, shake |
|||
'''Start up scenario 1: Server support'''<br> |
|||
# Quanta SW Test plan - One time test per SW release to Quanta. This test is aimed at basic functionality of XOs. |
|||
Jose is a 6 year-old student at a school in Brazil is being issued his XO laptop today. The school has spent weeks preparing for this day. The school server is set up and has internet connectivity. It contains books and software specific for Jose's grade level. The teacher has a specific activity she asks all the children to work on. |
|||
# 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 - 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. |
|||
Thoughts: Typical start up with a server in a large school...imprinting, download content |
|||
# [[User Stories Testing]] - One time test per SW release. This testing is aimed at system level testing based on real user stories. |
|||
'''Start up scenario 2: No server support'''<br> |
|||
Maria is a 10 year-old student in a school being issued XOs. This school just received their server and have not set it up yet and have no internet connectivity. The teacher is not prepared with activities or curriculum, but will allow the children time to explore the laptops on their own. |
|||
Thoughts: Typical start up with no server...imprinting, running some local apps, simple mesh connectivity to find a friend. |
|||
'''Start up scenario 3: Server start up'''<br> |
|||
The server hardware and cables have arrived early at a school in Uruguay. The local administrator takes the hardware out of the box and would like to set up the server and download the curriculum books and software that have been created ahead of time. |
|||
Thoughts: How to set up a server... |
|||
'''Connectivity scenario 1: Connectivity with or without a server'''<br> |
|||
Three students are working on a project together using the Journal to track/save their files. They start the project at their 'large' school with 3 mesh channels and internet connectivity. They save their work and get together later at home to continue working. They don't have internet connectivity or access to the server, but they can continue with Abiword and images they previously downloaded. |
|||
Thoughts: Ensure that collaboration projects can resume without a server... |
|||
'''Connectivity scenario 2: Mesh hoping connectivity'''<br> |
|||
The school server's wireless connection does not reach to all classrooms in and around the school. Andres is outside the range for a direct connection, but there is a laptop between his and the server that is currently i standby mode. He opens his XO to work on a project that includes downloading images from the internet. |
|||
Thoughts: Ensure connectivity through a standby XO to a server; also ensure it will work with 2 hops, one standby and one active XO... |
|||
'''Connectivity scenario 3: 200 XOs on one server'''<br> |
|||
On a particularly well-attended day of school, Uma is the 200th student to open her laptop to get started on a project. She opens the 'shared' document that she worked on at home yesterday. There is only one server in this school. |
|||
Thoughts: Ensure that 200 laptops can be seen by the server; ensure that the 200th laptop has no more trouble accessing the network than the first ones; is there any automatic updating of shared documents when a version change is detected? How does Uma find her friend if there are 200 other laptops in the mesh... |
|||
'''Connectivity scenario 4: Two server school'''<br> |
|||
School with two servers -- may not be needed for first release |
|||
Thoughts: We want to write down the scenerios for using a repeater and multiple hops, but testing and support for more sophisticated connectivity may have to be scheduled while shipping the first release. |
|||
'''Backup/Archive scenario 1: Basic backup'''<br> |
|||
Parvis goes to a school where he gets connected to the server every day. One day he inadvertently deleted a document that he had spent many days working on. |
|||
Thoughts: Automatic back up when connected to the server; Retrieval of a lost document |
|||
'''Other''' |
|||
Revision as of 14:39, 24 May 2007
This page is monitored by the OLPC team.
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.
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.
Test plans/pages that exist today:
- 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 - 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.