Testing

  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.

For the latest tests, see Update.1 tests.

Release info

Major Release 8.2.0

• 8.2.0 Features, on top of XO_Base_Features of 8.1.1
• TestPlan_8.2.0
• Test cases 8.2.0
• TestResults_8.2.0
• New features in 8.2.0

Minor releases 8.1.x

• Release 8.1.3, OLPC_SW-ECO_7, More Amharic support
• Release 8.1.2, OLPC_SW-ECO_6, Nand-full, SD card corruption, support of C3 production boards
• Release 8.1.1, OLPC_SW-ECO_5, Amharic and Kreyol support
  • Release notes for 8.1.1

Community Testing

• Community testing (main page)
• Friends in testing
• Systematic testing

Test beds:

• Creating a testbed
• Wireless Sparse Testbed - Universidade Federal Fluminense, Brazil
• Ejabberd resource tests/try_5 school server jabber testing

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

• Activity Testing Project
• Activity Testing Matrix
• Activity Testing Template

Links of Interest to Testing

• Test Config Notes - Links to configuration info that are useful in testing
• Test Group Release Notes - Quick info/smoke test on the latest builds. Read this before you bother to load a build
• Different upgrade paths and which to use
  • Also see Builds of Interest below
• Multi-hop mesh network in MIT campus
• Networking scenarios
• Simple mesh test (Cerebro)
• School Server general info: XS
  • Schoolserver Testing
• Update.1 tests - test process for the 8.1.0/Update.1 builds (builds 691...703)
  • Release Notes/8.1.0 - release notes for 8.1.0 also known as "Update.1"
  • Testing_Update.1_Results - some test results for Update.1 (in progress...)
  • OLPC Ship.2 Software Release Notes - release notes for Ship2, build 650
• 100 Laptop Testbed:
  • Collaboration_Network_Testbed
  • Peabody Setup - 100 laptop test setup in Peabody, MA
• Activation and Developer Keys - how to activate or get a developer key
• Scenario taxonomy
• Requirements (no longer used)

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:

• OLPC Archives
• "8.2" builds
• Recent stable builds
• "Update.1" builds
• "Bleeding-edge" builds
  • "Joyride" builds
  • "Faster" builds
  • "Meshtest" builds
  • "Ship.2" builds
• "Candidate" builds before they go public

Activities script/latest activities:

• From a laptop that is connected to the internet, start a Terminal Activity and type: wget http://dev.laptop.org/~erikos/sucrose-activities.py
• Then type: python sucrose-activities.py
• Link to Latest Activities

Notes and minutes

• Test meeting Minutes - Weekly meetings of interested test people, Mondays 1pm EDT

General navigation

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

This is temporary place for a sample of the test case format. Actual test cases, created in a different format, can be found here: http://wiki.laptop.org/go/Test_cases_8.2.0

Test results are reported here: http://wiki.laptop.org/go/TestResults_8.2.0

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

Items to Test

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:

• 802.11s Connectivity Test Plan - Connectivity, wifi protocol
• File:B3-B4 OLPC Test Plan.xls - Low Level Test Plan
• Tinderbox Testing - automated testing for each build (outdated) --Chihyu 13:58, 29 January 2008 (EST)
• XMPP collaboration and scalability testing - XMPP collaboration and scalability testing

Test Case Management System

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

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

How to build queries: TestCase_Queries

For other examples of queries, see Testcase Query Examples

Comments at Semantic MediaWiki#Suggestions_for_test_cases.

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.

• Memory leak testing
• Olpc-update
• Clean-install procedure

Also See

GSOC08 OLPC Project Automated Testing

Older notes

• Test process sprint- Wed, Oct 17th, 2007

Reporting test results

See Reporting test results.