Testing

  This page is monitored by the OLPC team.

Links of Interest:

• Test Group Release Notes - Quick info/smoke test on the latest builds. Read this before you bother to load a build
• Test Config Notes - Links to configuration info that are useful in testing
• Test meeting Minutes - Weekly meetings of interested test people, Mondays 1pm EDT
• QA engineer needed - want to work at our office in Boston to coordinate testing? Apply now.
• Test process sprint- Wed, Oct 17th, 2007
• Upgrade for OLPC shipping
• Upgrade for G1G1 at Brightstar

Check out these new links to test plans and result matrices -- Get involved and help test some activities:

• Activity Testing Project
• Activity Testing Matrix
• Activity Testing Template

Test Strategy

Purpose:
The purpose of testing is to measure and document the quality of a product.

This information, along with the requirements from our customers, will allow us to make an informed decision as to when the product is ready to ship.

Plans:
The XO software can be emulated on a number of environments, which means many people are helping out with the testing at the unit and module level for software. Our partners who are closest to the hardware and firmware have provided test resources to test in areas that not accessible in the open source community.

There are also many people now from early trials or the developers program who have a laptop and can help out with testing on the hardware. We are working on the idea of a 'Test Activity' that loads test cases directly onto the XO; and sends test results back to olpc. More on that as it materializes.

User-focused test plans are being developed for all the basic features of the laptop, for many of the activities, and for the interaction with the school server, collaboration, connectivity, etc. Please follow this link to read, review, and help create test plans:

• User-Focused Test Plans

Or check out the new pages:

• Activity Testing Project

If you want to help:

1. Sign up on the bugtracking system: Trac
2. Load the latest developer's build: Install/upgrade
3. Choose a test plan User-Focused Test Plans
4. Follow the steps.

If you find a bug you would like to log in trac, please follow these steps:

1. Log into Trac: Trac
2. Use the search to try and determine if your bug has already been reported
3. If a bug like yours is there, you can add notes about your instance of this bug.
4. If you need to start a new bug, please try to include the following information:
   • A short, but descriptive title (think about what you just tried to search for)
   • What build you were running; both the OS and the firmware if you can
   • Description of what happened (if the title is not enough)
   • Steps to reproduce the bug -- this is really important and will save a lot of time if it is easy to reproduce
   • Add files or logs to help for debugging. See the Test Config Notes for info on how to turn on logging
   • Choose the component that you think is involved in this bug.
   • Choose the priority -- how important you think it is.
   • Leave the milestone as 'untriaged'. A triage team will review the bugs for priority and add them to the appropriate milestone.

THANKS for your help!

Other Test plans can be found here:

• 802.11s Connectivity Test Plan - Connectivity, wifi protocol
• File:B3-B4 OLPC Test Plan.xls - Low Level Test Plan
• Tinderbox Testing - automated testing for each build

Schedule:

Please see the official roadmap (from the trac main page) for schedule dates and features for each release.

Roadmap

Release Criteria

Trial-2

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. It is expected to be alpha level quality with no serious crash bugs. It is important to be able to demo some of the new features that make our product unique: collaboration both locally and with access to internet, good power consumption, great mechanics/hardware to meet environmental conditions, "open" product -- hardware, firmware, software, activities.

With that in mind, we need to focus on a few good features to demonstrate 'explore', 'express', 'communicate', and 'collaborate' with good quality. This translates into the prioritized feature set for the Trial-2 milestone, which is found here:

< http://dev.laptop.org/milestone/Trial-2 >

Trial-3

Trial-3 needs to meet our beta level expectations. Many more features and activities are demonstrable with collaboration and a solid journal/sugar UI. It is also key that we have activation and upgrades working well. This is the first step in our BitFrost security plan.

We will not be adding many new features (perhaps none) between trial-3 and first deployment, so we really need to focus on blocking and high priority bugs associated with basic features and functionality including mesh, connectivity, power management, and activities.

The prioritized feature list for Trial-3 can be found here:

< http://dev.laptop.org/milestone/Trial-3 >

First Deployment

Release criteria:

See Release Criteria