Friends in testing: Difference between revisions

From OLPC
Jump to navigation Jump to search
(Add link to m_stones smoke test announcement)
No edit summary
 
(63 intermediate revisions by 21 users not shown)
Line 1: Line 1:
{{dated}}
{{Translations}}
{{Translations}}
{{Latest Releases | firmware = inline | devel = inline | rc = inline | livecd = inline |server = inline }}
{{TOCright}}
{{TOCright}}
{{:Friends_in_testing/banner}}

== Current status ==

* Thanks for testing [[Release notes/8.2.0|8.2.0]], our latest release.
* No testing is going on right now. Joyride builds are too unstable for testers, but there are [[Future releases|new releases]] coming, check back soon. And you're welcome to try out [[activities]] on 8.2.0 and [[reporting bugs|report bugs]].
* The Friends in Testing project is in transition, so the remainder of this wiki page may be under construction as you see it (feel free to jump in and help edit if you would like).


== 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.
The purpose of the Friends in Testing project is to perform and report short rounds of focused systematic and exploratory testing on the OLPC build candidate during the second half in each [[release cycle]].


<br>
== Current cycle ==


== Preparation ==
Cycles typically last one week for major releases; cycles for minor releases may be shorter. The current cycle expires on '''expiration-date.''' Results are due on that date, and these instructions are good until that date as well.


<!--[[Image:Power-button.jpg|thumb|right|Power & Game buttons for B2 and older XOs. B3 and newer have "O" at the top and "✓" (check) at the right.]]-->
=== Build under test ===


# Read the [[Friends in testing#Potential risks|potential risks]] below to decide if testing is right for you.
The Friends in Testing conductor for the 8.2.1 release is [[User:Bpepple| Brian Pepple]].
# Get a [[Developer key#Getting a Developer Key for your Running XO Laptop|developer key]] for your XO laptop
# [[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]].''
The release manager for the 8.2.1 release is Ed Mcnierney (contact info needed).


{{:Exploratory testing}}
[http://lists.laptop.org/pipermail/testing/2008-December/000685.html Announcing the 8.2.1 Smoke Test] (use the [[clean-install procedure]] to prepare your XO.)


{{:Systematic testing}}
''special note:''


<br>
The 8.2.1 build is currently identical to 8.2.0, so testing it won't be particularly interesting right now, but we can install that build and upgrade to the new [[firmware]] (OLPC Firmware q2e24 Candidate 2 for 8.2.1) which has [[Multicast_NAND_FLASH_Update|NANDblaster]], which ''is'' interesting to test, now.


=== Instructions ===
== 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.'''
General process:


In more detail:
<pre>
release manager: "Hey, this build has a sufficient number of new and interesting things
that would be worth doing another round of testing on."
FiT conductor : "Excellent. Can somebody smoke-test these?"
Somebody : *smoke tests*
Smoke test : *passes* (if not, return to release manager until you get a passing build)
FiT conductor : (to lots of volunteers) "hey everyone, TEST BUILD!"
Volunteers : *test build*
Volunteers : *report bugs in Trac, discuss on testing mailing list*
Bugs : *get fixed*
Developers : *love FiT*
</pre>


⚫
* '''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)'''.
=== Submit ===
⚫
* '''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>
''' how to report results, and in what format '''


== Participate ==
== Recovery ==

We'd love your help - please join us!

Participation in the Friends in Testing project is done one week at a time. You can start any time, and there's no obligation to continue after the week is over. This makes helping with Friends in Testing particularly suited to newcomers who are curious about testing but don't have a lot of time to spare for a first mini-project to attempt.

=== Who can participate ===

In order to participate, you must have an XO with a [[developer key]] that you are okay with ''completely'' wiping out and using as a test machine during your testing sprint (you will be able to restore your XO to its original state afterwards).

=== Potential risks ===

⚫
* '''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 back up '''(need link for backup)''' and restore '''(need link for restore)''' your Journal afterwards.
⚫
* '''Your Activities will be erased.''' However, as with your Journal, you can make a [[customization key]] with the Activities you want to keep, and restore your Activity set afterwards.
⚫
* '''You may brick your machine.''' 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.


* 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]].
=== How to participate ===
* If your machine becomes unbootable after an upgrade, you can recover by [[Cheat codes|holding the 'O' gamepad key]] during your next boot.


== Conclusion ==
Here's how to participate in a particular week's sprint.


Thanks very much for your help!
# Make sure you read and are okay with the [[#Potential risks]].
# Get a [[Developer key]] for your XO, if your XO does not already have one.
# [[Clean-install]] the [[#Build under test]].
# Follow the [[#Instructions]] for that week.
# [[#Submit]] your results.


If you have questions about how to participate, please leave them in [[Talk:Friends in testing]].
Finally, if you have questions about how to participate, please leave them in [[Talk:Friends in testing]].


[[Category:Participate]]
[[Category:Participate]]
[[Category:Testing]]
[[Category:Community testing]]

Latest revision as of 23:09, 13 November 2011

Emblem-warning.png The currency of this article or section may be limited by out-of-date information.
There may be relevant discussion on its talk page
  english | español HowTo [ID# 262709]  +/-  


 + Software 
XO
13.2.11 2020-01-29
XS
xs-0.7 2012-02-20


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

  1. Read the potential risks below to decide if testing is right for you.
  2. Get a developer key for your XO laptop
  3. Backup your XO (optional -- you decide).
  4. 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>
  5. Install activities with your favorite activity installation method.
  6. Help explore the OS and activities as described below or run some formal test cases.
  7. 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

Conclusion

Thanks very much for your help!

Finally, if you have questions about how to participate, please leave them in Talk:Friends in testing.

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Friends_in_testing&oldid=262709"