Nepal: XO Testing Plan
The OLE Nepal team will use this document as the basis for acceptance testing for new XO's. This plan will test for hardware and software problems.
We are using this document on a daily basis. If you have a tried-and-true solution you are welcome to post it here. Please keep suggestions or points for discussion onto the Talk Page that will make this document more easy to use.
The new XO's will be kept in the OLE Nepal storage room and not moved until testing is complete. Otherwise they will mingle w/ our other XO's and everything will be confused. We will test them in batches of 24 XO's at a time. (Why 24? because they are stacked 6 high.)
Stage 1 - Receipt of XO's
Stage 1 will be done by Upaya, Bryan, and Sulochan. Covers receipt and basic testing
- At airport, count # of XO's if individually packed
- Upon arrival at office, recount XO's
- Inventory the XO's in a spreadsheet. The spreadsheet should record the XO's serial #, whether it shows any physical damage, or won't boot. If there is physical damage, write "physical damage" on the box w/ a red marker. If it won't boot, write "won't boot" with red marker.
- Insert USB key, containing runos.zip and actos.zip, see Procedure for Collecting UUID's and Serial Numbers
- At the login screen enter the Serial Number as the Name. This will distinguish the XO while you are testing it.
- Attach a label to the XO that has the Serial Number as the identifier
- Send file to OLPC containing the information needed to get developer keys for each XO to help@laptop.org
Stage 2 will be done by Bryan, Upaya, Rajeev, Sulochan, Rabi, and Saurav
