Testing

From OLPC
Revision as of 19:03, 3 January 2008 by 200.51.208.38 (talk) (delgetnogets)
Jump to: navigation, search

latroc

  This page is monitored by the OLPC team.

Links of Interest:


Check out these new links to test plans and result matrices -- Get involved and help test some activities:


Community Testing

Purpose:
The Activities on the XO have been developed by community members. Many of them are not well documented and there may not be much information on how to use them; so this testing can be described as 'Descriptive Testing', where you are helping to provide and/or correct the wiki pages that describe how an activity works.


Plans:
The XO software can be emulated on a number of environments, which means many people are helping out with the testing at the unit and module level for software. Our partners who are closest to the hardware and firmware have provided test resources to test in areas that not accessible in the open source community.

There are also many people now from early trials or the developers program who have a laptop and can help out with testing on the hardware. We are working on the idea of a 'Test Activity' that loads test cases directly onto the XO; and sends test results back to olpc. More on that as it materializes.


If you want to help:

  1. Sign up on the bugtracking system: Trac
  2. Load the latest developer's build: Install/upgrade
  3. Choose a test plan User-Focused Test Plans
  4. Follow the steps.

If you find a bug you would like to log in trac, please follow these steps. Here is an example bug to look at: [1]:

  1. Log into Trac: Trac
  2. Use the search to try and determine if your bug has already been reported
  3. If a bug like yours is there, you can add notes about your instance of this bug in the add/change section.
  4. If you need to start a new bug, please try to include the following information:
    • A short, but descriptive title (think about what you just tried to search for)
    • What build you were running; both the OS and the firmware if you can
    • Description of what happened (if the title is not enough)
    • Steps to reproduce the bug -- this is really important and will save a lot of time if it is easy to reproduce
    • Add files or logs to help for debugging. See the Test Config Notes for info on how to turn on logging
    • Choose the component that you think is involved in this bug.
    • Choose the priority -- how important you think it is.
    • Leave the milestone as 'Never Assigned'. A triage team will review the bugs for priority and add them to the appropriate milestone.


Now go to the Activity Testing Project to pick an activity to get started.

THANKS for your help!


Testing at OLPC/Partners

User-focused test plans are being developed for all the basic features of the laptop, for many of the activities, and for the interaction with the school server, collaboration, connectivity, etc. Please follow this link to read, review, and help create test plans:


Areas that we need to test in house (due to the use of special equipment and quantities of laptops) include:

  • All keyboards. - Bernardo/Kim/Walter
    • Keyboard settings preserved across updates.
  • All languages we can
    • Mandantory: English, Spanish, Portuguese (Brazil), Arabic for sure; others as possible for update1.
  • Firmware
    • WPA - Richardo/Michailis
    • WEP - Richardo/Michailis
    • Mesh - upgrade under loaded network - Scott
    • Suspend/resume - Wad
  • Scaling/performance
    • Jabber server scaling - OLPC/Collabora
    • Link local presence (Salut) - OLPC/Collabora
    • Journal/datastore
  • Upgrades /backward compatibility


Other Test plans can be found here:


Schedule:

Please see the official roadmap (from the trac main page) for schedule dates and features for each release.

Roadmap

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