Testing
User Stories
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.
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
Start up scenario 1: Server support
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.
Thoughts: Typical start up with a server in a large school...imprinting, download content
Start up scenario 2: No server support
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
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
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
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
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
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
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