Nepal: XO Testing Plan: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
The [http://www.olenepal.org 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.
The [http://www.olenepal.org 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.
[[User:Berrybw|Berrybw]] 06:55, 14 March 2008 (EDT)


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:Nepal:_XO_Testing_Plan|Talk Page]] that will make this document more easy to use.
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:Nepal:_XO_Testing_Plan|Talk Page]] that will make this document more easy to use.
Line 13: Line 14:
# 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. Here is a inventory template spreadsheet you can use [[Image:XO-Inventory-template.xls]]
# 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. Here is a inventory template spreadsheet you can use [[Image:XO-Inventory-template.xls]]
# Insert USB key, containing runos.zip and actos.zip, see [http://wiki.laptop.org/index.php?title=Activation_and_Developer_Keys&section=5#Collecting_Serial_Numbers_and_UUID.27s_for_one_or_many_XOs Procedure for Collecting UUID's and Serial Numbers]
# Insert USB key, containing runos.zip and actos.zip, see [http://wiki.laptop.org/index.php?title=Activation_and_Developer_Keys&section=5#Collecting_Serial_Numbers_and_UUID.27s_for_one_or_many_XOs Procedure for Collecting UUID's and Serial Numbers]
#* You should see a message like "SHFxxxxxxxx nnnnnnnnnnnnnnn; Laptop data recorded successfully"
#* The XO will then reboot, remove the USB key
# At the login screen enter the Serial Number as the Name. This will distinguish the XO while you are testing it.
# 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
# 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
# Send file to OLPC containing the information needed to get developer keys for each XO to help@laptop.org



== Stage 2 - Serious Testing ==
== Stage 2 - Serious Testing ==


Stage 2 will be done by Bryan, Upaya, Rajeev, Sulochan, Rabi, and Saurav
Stage 2 will be done by Bryan, Upaya, Rajeev, Sulochan, Rabi, and Saurav

For Stage you need a USB key with the following contents:
* Develop.sig -- developer key for this specific laptop. Create the /security folder at the USB root and place the develop.sig in that folder.
* your customized XO build, we will most likely use [http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/build699/devel_jffs2/ os699]
* Any Bundles you will use according together with the [[Customization key]]
* [[Customization key]]





Line 25: Line 36:


Stage 3 will be Bryan, Sulochan, and Dev (if available)
Stage 3 will be Bryan, Sulochan, and Dev (if available)

Will test many XO's together w/ School Server, Moodle, activities we will pre-install. It will be a testing bonanza!


# Test 70 XO's together w/ access point
# Test 70 XO's together w/ access point

Revision as of 10:55, 14 March 2008

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. Berrybw 06:55, 14 March 2008 (EDT)

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

  1. At airport, count # of XO's if individually packed
  2. Upon arrival at office, recount XO's and note any discrepancies
  3. 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. Here is a inventory template spreadsheet you can use File:XO-Inventory-template.xls
  4. Insert USB key, containing runos.zip and actos.zip, see Procedure for Collecting UUID's and Serial Numbers
    • You should see a message like "SHFxxxxxxxx nnnnnnnnnnnnnnn; Laptop data recorded successfully"
    • The XO will then reboot, remove the USB key
  5. At the login screen enter the Serial Number as the Name. This will distinguish the XO while you are testing it.
  6. Attach a label to the XO that has the Serial Number as the identifier
  7. Send file to OLPC containing the information needed to get developer keys for each XO to help@laptop.org


Stage 2 - Serious Testing

Stage 2 will be done by Bryan, Upaya, Rajeev, Sulochan, Rabi, and Saurav

For Stage you need a USB key with the following contents:

  • Develop.sig -- developer key for this specific laptop. Create the /security folder at the USB root and place the develop.sig in that folder.
  • your customized XO build, we will most likely use os699
  • Any Bundles you will use according together with the Customization key
  • Customization key


Stage 3 - Load Testing

Stage 3 will be Bryan, Sulochan, and Dev (if available)

Will test many XO's together w/ School Server, Moodle, activities we will pre-install. It will be a testing bonanza!

  1. Test 70 XO's together w/ access point