Tests/Boot/Cleaninstall

From OLPC

< Tests
Revision as of 00:03, 9 February 2011 by Skierpage (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Test case: Use USB stick and cleaninstall the image; secure and not secured
How to report results

Stream joyride, 8.2, 11.2, Any
Category Boot Sub-category Cleaninstall
Component OFW
Feature (Trac #7394)
Objective Ensure that a cleaninstall of a build image works properly from a USB key. Both on secure laptop (with a signed build) and an unsecured laptop (unsigned build). (see http://wiki.laptop.org/go/Clean-install_procedure for reference)
Tools none
Setup
  1. One XO that is write protected (secure)
  2. One XO that is not write protected (not secure)
  3. For the non-secure XO: USB stick with the correct .fth file in the boot directory along with non signed .img and .crc files
  4. For the non-secure XO: USB stick with .zip and .img signed images in the root
Procedure
  1. Using a signed build, ensure that the secure laptop can install the image by holding the four game buttons while powering on.
  2. Using an unsigned build, ensure that a non secure laptop can install the image by holding the four game buttons while powering on.
Expected Results
and Pass Criteria
These laptops should install the new image writing directly to nand; blowing away any data that was there; and boot up properly.
Comments none
Release Stream Build Pass/Fail Trac Ticket(s) Comment(s) Date of Test
Candidate 8.2 762 Pass clean installed from 653 warning.pngThe date "" was not understood (support for dates is still experimental).


Candidate 8.2 762 Pass clean installed from 650 warning.pngThe date "" was not understood (support for dates is still experimental).


Candidate 8.2 763 Pass warning.pngEmpty strings are not accepted. warning.pngThe date "" was not understood (support for dates is still experimental).


Candidate 8.2 765 Pass warning.pngEmpty strings are not accepted. warning.pngThe date "" was not understood (support for dates is still experimental).


Candidate 8.2 766 Pass warning.pngEmpty strings are not accepted. warning.pngThe date "" was not understood (support for dates is still experimental).


Candidate 8.2 767 Pass clean installed with unsigned gg-767-4 warning.pngThe date "" was not understood (support for dates is still experimental).


Candidate 8.2 767 Pass copy-nand clean install for signed gg-767-4 warning.pngThe date "" was not understood (support for dates is still experimental).


Facts about Tests/Boot/CleaninstallRDF feed
Build number 762  +, 763  +, 765  +, 766  +, and 767  +
Build stream Joyride  +info.pngLink to builds in stream, Packages in stream, ChangeLog, Differences vs joyride , 8.2  +info.pngLink to builds in stream, Packages in stream, ChangeLog, Differences vs joyride , 11.2  +info.pngLink to builds in stream, Packages in stream, ChangeLog, Differences vs joyride , and Any  +info.pngLink to builds in stream, Packages in stream, ChangeLog, Differences vs joyride
Comments clean installed from 653, clean installed from 650, warning.pngEmpty strings are not accepted. , clean installed with unsigned gg-767-4, and copy-nand clean install for signed gg-767-4
Created warning.pngThe date "" was not understood (support for dates is still experimental).
More notes none
Pass criteria These laptops should install the new image writing directly to nand; blowing away any data that was there; and boot up properly.
PassFail Pass  +
Short name Use USB stick and cleaninstall the image; secure and not secured  +
Software release Candidate  +
System component OFW  +
System feature (Trac #7394)  +
Test category Boot  +
Test objective Ensure that a cleaninstall of a build image works properly from a USB key. Both on secure laptop (with a signed build) and an unsecured laptop (unsigned build). (see http://wiki.laptop.org/go/Clean-install_procedure for reference)  +
Test procedure <br />
  1. Using a signed build, ensur <br />
  2. Using a signed build, ensure that the secure laptop can install the image by holding the four game buttons while powering on.
  3. Using an unsigned build, ensure that a non secure laptop can install the image by holding the four game buttons while powering on. g the four game buttons while powering on.
Test setup <br />
  • One XO that is write protec <br />
  • One XO that is write protected (secure)
  • One XO that is not write protected (not secure)
  • For the non-secure XO: USB stick with the correct .fth file in the boot directory along with non signed .img and .crc files
  • For the non-secure XO: USB stick with .zip and .img signed images in the root th .zip and .img signed images in the root
  • Test subcategory Cleaninstall  +
    Test tools none  +
    Personal tools
    • Log in
    • Login with OpenID
    About OLPC
    About the laptop
    About the tablet
    Projects
    OLPC wiki
    Toolbox