OLE Nepal:Testing

From OLPC
Revision as of 08:07, 23 October 2008 by Tony37 (talk | contribs) (New page: == Introduction == This page is a stub for testing of OLE Nepal's version of XO, XS, and their interaction. It is based on the OLPC test procedures and forms. === Test XO Release 8.2.0-...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Introduction

This page is a stub for testing of OLE Nepal's version of XO, XS, and their interaction. It is based on the OLPC test procedures and forms.

Test XO Release 8.2.0-767 and activities

On 2008-10-14, Release 8.2.0 (build 767) became available as the latest stable release. This release needs to be tested with all OLPC and OLENepal acivities which are to be included in the next OLE Nepal Release: NEXO-767-2.0.

Preparation

Clean install the XO-767 release. Install the activities. Pradosh has a USB key with the correct image to install. You may need to disable security with a developer key. See Pradosh for details.


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.