Friends in testing: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (168 intermediate revisions by 37 users not shown) | |||
| Line 1: | Line 1: | ||
{{dated}} |
|||
'''You can now proceed with software installation and testing. Thank you!''' |
|||
{{Translations}} |
|||
-------------- |
|||
{{Latest Releases | firmware = inline | devel = inline | rc = inline | livecd = inline |server = inline }} |
|||
{{TOCright}} |
|||
{{:Friends_in_testing/banner}} |
|||
== Introduction == |
== Introduction == |
||
[[OLPC]]'s software releases are tested almost entirely by volunteers. This page explains, step by step, what you need to do to get involved. |
|||
Since the schedule for the next G1G1 is not firm, we have decided to make: |
|||
<br> |
|||
''a backup ship plan'' |
|||
| ⚫ | |||
: ship the 8.1.1 release (currently candidate-708) and minor changes to the G1G1 activity pack available today |
|||
: anticipates 4 weeks time before image delivery |
|||
| ⚫ | |||
''a goal ship plan'' |
|||
# Read the [[Friends in testing#Potential risks|potential risks]] below to decide if testing is right for you. |
|||
: ship the 8.2.0 release or defer the ship decision until better information is available |
|||
# Get a [[Developer key#Getting a Developer Key for your Running XO Laptop|developer key]] for your XO laptop |
|||
: anticipates more than 10 weeks time before image delivery. |
|||
# [[Backup]] your XO (optional -- you decide). |
|||
# [[Clean-install procedure#Development Builds|Clean-install]] or [[Olpc-update|upgrade]] your XO to the {{{{:Friends in testing/current image stream}}-jffs2-link}} test build. |
|||
#* If you clean-install, you will lose all your data. |
|||
#* The command you enter in [[Terminal Activity]] for upgrade is <br /><tt>sudo [[olpc-update]] <CURRENT/TEST IMAGE></tt> |
|||
# Install activities with your favorite [[Activity installation|activity installation method]]. |
|||
# Help [[Friends in testing#Exploratory Testing|explore]] the OS and activities as described below or run some [[Test cases 8.2.1|formal test cases]]. |
|||
# Should you need them, [[Friends in testing#Recovery|recovery]] instructions are available. |
|||
''Several other test preparation instructions are available, for example in [[OS images]] and in [[Emulating the XO]], and other pages in [[:Category:Preparing for testing]].'' |
|||
Your assistance would be invaluable in improving the results of the "goal" ship plan. Also '''if you have any friends with G1G1 or developer XOs''', please help '''spread the word'''. |
|||
{{:Exploratory testing}} |
|||
Send your friends with XOs to this Wiki page, which will be updated weekly. This is '''your opportunity''' to help give better software to hundreds of thousands of children next year as well as to future G1G1 donors. |
|||
{{:Systematic testing}} |
|||
| ⚫ | |||
<br> |
|||
| ⚫ | |||
''DO NOT'' attempt this procedure if you use an SD card with your XO. If you do, ''you may lose all your data.'' Please see the [[OLPC 8.1.1 Software Release Notes]] for details. |
|||
| ⚫ | |||
== Potential risks == |
|||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
In more detail: |
|||
# How to clean-install: |
|||
#* Download the [http://download.laptop.org/xo-1/custom/g1g1/en-708-1/en708-1.img OS image] and its [http://download.laptop.org/xo-1/custom/g1g1/en-708-1/fs.zip signatures file] to your local computer. DO NOT open them. P.S. If your computer runs on MS Windows, point your cursor on the link, click the right mouse button and choose "Save Link Target As". |
|||
#* Copy these files onto of a clean (Full (not Quick!) formatted) USB memory stick. Your USB memory stick should now contain two files named: '''en708-1.img''' and '''fs.zip'''. |
|||
#* Unmount the USB memory stick and disconnect it from your computer '''when it is safe to do so'''. |
|||
#* Insert the USB stick into the XO Laptop and power up '''while holding the four game keys'''. (this is VERY important!) |
|||
#* Release game keys when it asks you to. It will take a few minutes to rewrite the memory. |
|||
# Reboot. |
|||
# Check that you have the correct build: |
|||
#* Hover over the XO in the Home screen and click on 'About my XO' |
|||
#* It should say build Update.1 708, firmware Q2D16 |
|||
* '''Your XO's software may look and feel "weird."''' The new build you are testing may behave differently from what you're used to (that's the point - it's a new build). Before beginning to test, you can find out the build you're running '''(need link)''', and you can reinstall your original build afterwards '''(need link)'''. |
|||
NB. If the install "hangs", then you may have a corrupted USB memory stick. In this case, reformat the stick (FULL format!), then copy the '''en708-1.img''' and '''fs.zip''' files to the stick. '''Be sure to properly unmount/remove the stick''' before repeating the clean-install procedure. |
|||
* '''Your Journal will be erased.''' However, you can [[backup]] and restore your Journal afterwards. |
|||
* '''Your Activities will be erased.''' However, as with your Journal, you can make a [[customization stick]] with the Activities you want to keep, and restore your Activity set afterwards. |
|||
* '''You may brick your machine.''' (That is, leave it "useful only as a brick" - break it so badly you can't fix it.) We've made every effort possible to make sure that the builds that we release for Friends in Testing will not harm your XO, and to provide you with instructions on how to restore your XO to its pre-testing state, but there is a ''very slim'' chance that something might go awry and that you won't be able to restore your XO to its pre-testing state. It's never happened before to our knowledge, but we cannot guarantee it won't ever happen. We'll do our best to be honest with you each week about the risks you might be taking. We hope that, after reading this, you'll still want to participate; we do, however, want to make sure that if you're going to help us out, you know what you might be getting yourself into. |
|||
<br> |
|||
== Testing == |
|||
| ⚫ | |||
==='''Test 1: Wireless Internet access'''=== |
|||
* If your machine becomes unbootable after a clean-install, you can recover by [[Clean-install_procedure#Official releases and candidate builds |clean-installing an official build]]. |
|||
For this test you need a wireless access point set up and running. You should know the SSID of the access point and a password, if any. If your access point is password-protected, you should also know whether your access point is setup to operate in the 'Open System' or 'Shared Key" mode. |
|||
* If your machine becomes unbootable after an upgrade, you can recover by [[Cheat codes|holding the 'O' gamepad key]] during your next boot. |
|||
== Conclusion == |
|||
# After booting the laptop go to the Neighborhood view (Alt-ctl 'neighborhood', which is the 3rd key from the left on the top row) |
|||
# Click on the Circle that represents your wireless access point. If the wireless encription key is required, the prompt will appear, requiring you to enter the password. Please be very carefull to choose the correct Key Type and Authentication Type!!! After clicking on "OK", wait until the circle stops blinking. Hover over that circle and see that the laptop is connected to your access point. You can also check it in the Home view (5th key from the left on the top row) - hover over the circle near the battery indicator. |
|||
# Click on Browse |
|||
# Browse the internet to make sure you have a good connection |
|||
# Go to this wiki page: [[Wireless_Access_Point_Compatibility]] and enter your test results. Please specify your contact email (without using the @ sign), your XO's serial number (seen in "About your XO"), and the manufacturer and type of your access point. |
|||
Thanks very much for your help! |
|||
| ⚫ | |||
[[Category:Participate]] |
[[Category:Participate]] |
||
[[Category:Community testing]] |
|||
Latest revision as of 23:09, 13 November 2011
|
The currency of this article or section may be limited by out-of-date information. There may be relevant discussion on its talk page |
Current test image: 11.3.1
Introduction
OLPC's software releases are tested almost entirely by volunteers. This page explains, step by step, what you need to do to get involved.
Preparation
- Read the potential risks below to decide if testing is right for you.
- Get a developer key for your XO laptop
- Backup your XO (optional -- you decide).
- Clean-install or upgrade your XO to the Template:Official-jffs2-link test build.
- If you clean-install, you will lose all your data.
- The command you enter in Terminal Activity for upgrade is
sudo olpc-update <CURRENT/TEST IMAGE>
- Install activities with your favorite activity installation method.
- Help explore the OS and activities as described below or run some formal test cases.
- Should you need them, recovery instructions are available.
Several other test preparation instructions are available, for example in OS images and in Emulating the XO, and other pages in Category:Preparing for testing.
Exploratory Testing
- Known issues are recorded in the release notes for a release; check both the current stable release's notes and/or the in-progress release notes for the development release you're testing.
- Sometimes people enumerate problems in Test group release notes.
- People report problems on the testing mailing list
You should report new issues in our bug-tracking system. You can also send any issues or comments to the development list, devel at lists.laptop.org.
Test 1: Wifi Testing
Can Current test image: 11.3.1 associate with your (encrypted?) access point?
If not, let us know!
Test 2: Explore the Smoke Test
Try out parts of the release's smoke test that appeal to you.
(Older tests are available.)
Systematic Testing
In addition to our freeform exploratory testing effort, we also engage in systematic testing efforts designed to achieve the test coverage necessary to make release decisions around future releases, much like past releases.
Systematic testing consists of several basic tasks:
- Reviewing a test plan.
- Writing the test cases, if needed.
- Executing the test cases and recording test results.
- To record results on a particular test case page, click on the "Edit with form" button in the top of the page, and use the "Add Another" button just above the "Add New Results" section (i.e. at the bottom of the page).
- Contributing patches to the Tinderbox or Sugarbot automated testing platforms.
Test 1: Multiple Key Support
We are particularly interested, this week, in systematically testing OFW's new multiple key support.
Potential risks
This procedure asks you to install alpha software. You may lose all your data. Please back up personal files to another source if you would like to keep them.
In more detail:
- Your XO's software may look and feel "weird." The new build you are testing may behave differently from what you're used to (that's the point - it's a new build). Before beginning to test, you can find out the build you're running (need link), and you can reinstall your original build afterwards (need link).
- Your Journal will be erased. However, you can backup and restore your Journal afterwards.
- Your Activities will be erased. However, as with your Journal, you can make a customization stick with the Activities you want to keep, and restore your Activity set afterwards.
- You may brick your machine. (That is, leave it "useful only as a brick" - break it so badly you can't fix it.) We've made every effort possible to make sure that the builds that we release for Friends in Testing will not harm your XO, and to provide you with instructions on how to restore your XO to its pre-testing state, but there is a very slim chance that something might go awry and that you won't be able to restore your XO to its pre-testing state. It's never happened before to our knowledge, but we cannot guarantee it won't ever happen. We'll do our best to be honest with you each week about the risks you might be taking. We hope that, after reading this, you'll still want to participate; we do, however, want to make sure that if you're going to help us out, you know what you might be getting yourself into.
Recovery
- If your machine becomes unbootable after a clean-install, you can recover by clean-installing an official build.
- If your machine becomes unbootable after an upgrade, you can recover by holding the 'O' gamepad key during your next boot.
Conclusion
Thanks very much for your help!
Finally, if you have questions about how to participate, please leave them in Talk:Friends in testing.