Testing

From OLPC
Revision as of 06:25, 17 November 2008 by Skierpage (talk | contribs) (→‎General navigation: add a br clear="all" after {{Community testing}})
Jump to navigation Jump to search
  This page is monitored by the OLPC team.

The community and core team work through a slate of test issues for each major build and release. This page highlights the current tests being run, the testing process in general, and how to contribute your own results or bugs.


Release info

Testing for major release 8.2.0

Testing for minor releases 8.1.x

Testing for release 8.1.0

Release 8.1.0 was also known as "Update.1", see Update.1 tests for tests and test results.

Community Testing

Test beds:


Older community efforts (should be updated to the new test template):

Links of Interest to Testing

Equipment specs:

  • Infrastructure_AP: Zoom 4400 AP+2 Wireless-G Access Point (Approx. $50 USD)
  • Long range Wireless: Wavion’s WS410 Spatially Adaptive Wi-Fi Access Point (Approx. $1600 USD)
  • Server HW Specs

Builds of interest

See OS images for build streams, release candidates, joyride builds, etc.

For latest activities, run Software update in Sugar Control Panel, or download individual Activities.

Older builds and activities

Activities script/latest activities for 8.1:

Notes and minutes

General navigation

Test cases 8.2.0 lists the test cases created for the recent release 8.2.0.

Test results are in TestResults 8.2.0

The {{Community testing}} navigation template is shown below:

  This page is part of the OLPC Community testing Project. How to test an Activity | Reporting test results | Meetings
XO Checkbox


The navigation template {{Test-nav}} is shown below, it should be updated and many related pages need to be merged:

Activity testing project | Testing matrix | Activity testing guide | Activity testing template +/-

To merge: Testing | Testing ideas | Friends in testing

 See also: Sugar Labs testing | the Testing mailing list

Test cases and test results

Mid-2008 users including Femslade, Charlie, and Kimquirk created test cases for 8.2.0 that can be created and modified using a form. Testers can also use the same form to add testing results, see Reporting test results.

See, e.g. Tests/Activity/Write/Public_sharing as a sample.

All these test cases are in Category:Test cases and most are listed by the queries in Test cases 8.2.0.

In 2007 and early 2008, tests were just wiki pages, e.g. Tests/Browse. Those older test cases are mostly in Category:Test Plans and/or Category:Tests.

Test case management

To add categories to the Test Case pull down menu, modify Property:Test_category

To add streams to the Test Case form, modify Property:Build_stream

To build queries, modify TestCase Queries

For other examples of queries, see Testcase Query Examples

Comments at Semantic MediaWiki#Issues for Test cases.

An old test case format

This is temporary place for a sample of the test case format. Test area: Sugar Control Panel

Number/Title 1/Change Timezone
Objective Verify that the user can change their XO's timezone from the default UTC setting.
Feature Users are able to change their XO's timezone to match the local time without having to go into a terminal to do so.
Source http://wiki.laptop.org/go/Sugar_Control_Panel#Date_.26_Time]
Approach Act as an end-user trying to change the XO's timezone to match the local time.
Test Tools No test tools required.
Test Setup One XO laptop running an 8.2.0 (pre-)release build.
Test Procedure 1. Open the graphical Sugar Control Panel from the Home view.

2. Click on the "Date & Time" panel.
3. Find the desired timezone in the list and click on it.
4. Click the check-mark on the top-right. Select either "Later" or "Restart now".
4a. If you picked "Later", restart the laptop after a minute or two.
5. After the XO reboots, check that the timezone changed by opening a terminal and typing 'date'.

Expected Results & Pass Criteria The timezone for the laptop has been changed correctly and the timezone is represented properly by the 'date' command.
Comments

Testing areas

Items to test

Old?

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

  • All keyboards. - Test: Keyboard Settings
    • Keys match the layouts designed
    • Language, keyboard, keymappings match the settings
    • All language and keyboard settings are preserved across updates
  • Languages - Test: Language Settings
  • Firmware
    • WPA - Richardo/Michailis
    • WEP - Richardo/Michailis
    • Mesh - upgrade under loaded network - Scott
    • Suspend/resume - Wad - Test: Suspend/resume
  • Scaling/performance
    • Jabber server scaling - OLPC/Collabora
    • Link local presence (Salut) - OLPC/Collabora
    • Journal/datastore
  • Upgrades /backward compatibility
  • Security

Other test plans

Schedule

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

Test setups

This section covers generic ways to set up before running different kinds of tests. (These are not specific test cases, but can be used as shorthand references to common procedures that are used across many test cases.

See also

Older notes

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