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.

Notes and minutes

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

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

Release info

• August Release 8.2.0, on top of 8.1.1
  • Test cases 8.2.0
  • TestResults_8.2.0
  • New Features in 8.2.0
• XO_Base_Features
• Minor Release 8.1.1

Older notes

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

Links of Interest

• Multi-hop mesh network in MIT campus
• Networking scenarios
• Simple mesh test (Cerebro)
• Schoolserver Testing
• Test Group Release Notes - Quick info/smoke test on the latest builds. Read this before you bother to load a build
  • 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
• Test Config Notes - Links to configuration info that are useful in testing
  • Different upgrade paths and which to use
• 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

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 (Approx. $3000 USD)

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

Community Testing:

• Friends in testing
• Activity Testing Project
• Activity Testing Matrix
• Activity Testing Template

Builds of Interest:

• Recent stable builds
• "Update.1" builds
• "Bleeding-edge" builds
  • "Joyride" builds
  • "Faster" builds
  • "Meshtest" builds
  • "Ship.2" builds
• "OLPC-3" 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

Testing teams

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. If you want to help, please refer to the Community Testing page for more details.

Also, the developers ask advanced users to try early builds with new features, see Friends in testing.

OLPC Test Plan/Release Criteria for 8.2.0

This is a work-in-progress...

Major test areas/features to be covered are:

Hardware/Firmware

Robust behavior, ability to operate with user-oriented (touch-pad, keyboard, etc.) and external devices (mouse, etc.)

Power Management (Power Control & Conservation)

When the lid is closed or when the power button is pressed while Sugar is running, suspend in order to conserve power.

Resume from suspend in response to lid opening or power-button presses

Cut power by holding the power button for several seconds

Power off or reset the machine via the Central XO-person's Palette

Control screen brightness and suspend state from the root command-line

Control screen brightness with the brightness keys in Sugar

USB/SD Peripherals

Reliably store user data to and retrieve user data from FAT16/VFAT formatted USB Mass Storage devices.

Reliably store user data to and retrieve user data from FAT16/VFAT formatted SD/SDHC devices.

USB ethernet adapters, keyboards, and mice should function similarly to their normal function on other operating systems.

Login via serial consoles. (very low priority)

Firmware

Developer keys should grant access to OFW.

Should be able to flash any build from OFW.

Should be able to rewrite manufacturing data (e.g. language, write-protect tags) from OFW (Very low priority, not a public feature)

Should respond to gamepad [go/Cheat_codes Cheat codes]

Installation of Software (operating system, Sugar, activities) and firmware. Field upgrades.

W/ internet or preparation: install new activities and library content on a raw OS via the internet or via USB keys.

W/ internet: install new software via 'yum install' or 'rpm -U' on a raw OS via the internet. Data in /home should be PRESERVED.

W/ internet: olpc-update to new versions of the operating system via the internet. Data in /home should be PRESERVED.

W/ preparation: olpc-update to new versions of the operating system via USB. Data in /home should be PRESERVED.

W/ preparation: reflash appropriately signed builds via USB. NO DATA should be preserved.

Access the root account via the virtual terminals or via the Terminal activity (if present.)

Some downstream partners such as Uruguay intend to disable user access to the root account as part of their theft-deterrence plan.

Access to the firmware "ok" prompt w/ developer key, requestable through Browse and installable through the Terminal.

Sugar GUI

TBD

Datastore

Be able to display and edit DOC, ODT, JPEG, PNG, GIF, WAV, OGG, HTML, JS, some SWF, and several other less-well known formats.

We expect NOT to be able to display [go/Restricted_Formats restricted formats] including MP3, MPEG, most AVI, RM, FLV, etc.

Activities

Interact with one activity or "location" at a time

Switch between the current activity and other locations with the view keys or the frame

Switch between activities with Alt-Tab or the activity ring

Start new activities and stop running ones with the frame, ring, or activity toolbar.

Pippy, Record, and TamTam will be able to play and record sounds.

Pippy and Record will be able to take photographs.

Record will be able to record short videos.

Measure will be able to measure signals with or without DC voltage bias.

Volume keys on the keyboard will adjust the speaker volume while Sugar is running.

Control audio volume with the volume keys in sugar

Pictures can be composed with text in a system editor such as Write. (We actually expect [go/Write Write] to do a lot of other things.)

Fancier multimedia like video, audio, and programs can be manipulated in an environment like [go/EToys EToys].

Copy-and-paste media clips between activities

Download media clips into the Journal

Pictures can be composed with text in a system editor such as Write. (We actually expect [go/Write Write] to do a lot of other things.)

Fancier multimedia like video, audio, and programs can be manipulated in an environment like [go/EToys EToys].

Copy-and-paste media clips between activities

Download media clips into the Journal

The section below has to be edited (in progress)… Installing or removing activities should never change the ability of the system to run.

1 - Start activities at the same speed (including but not limited to all

fructose activities)

2 - Boot to home at the same speed.

3 - Cursor control the same, including number of XOs where it moves

without input or moves without correlation to finger on touchpad

3 - Connect to the same APs in the same time and with the same user

feedback. (e.g. blinks then shows white circle).

4 - Connect to active antennas in the same time and with the same user

feedback (e.g. blinks then shows white circle).

5 - Run all the same activities (can require activity upgrade within

documented bounds). Includes allowing activities to mesh the same way.

6 - Connect to mesh with the same number of XOs in the same time with

the same failure rate.

7 - Save and open files for all activities. Fructose activities at a

minimum otherwise all activities per 5 above. Including when journal has

thousands of entries.

8 - Use the same NAND space.

9 - Always boots up, especially when there is no space on NAND

10 - Open and close all activities per 5 above.

11 - Must support all languages and keyboards previously supported.

"support" means all previously translated strings still work in

activities and sugar. All language types work the same (e.g. RTL)

12 - No new cases where the XO crashes and needs hard reboot.

13 - No new cases where the cursor stops responding (AKA hangs) for more

than 30 seconds.

14 - Sound and video recording and playback must record at the same

rate. Must playback all the same kinds of files. Must playback with the

same quality (assuming all other variables constant, e.g. network,

RAN=M, disk space, etc.)

15 - Browse must render the same web sites as before. See also

http://dev.laptop.org/ticket/7421

16 - USB read, write, mount and unmount must work the same and for all

the same devices.

17 - Mouse and keyboard must connect and work the same

18 - Journal has the same capabilities.

19 - Must use the same or less power for the same user interaction

20 - Must have the same security mechanisms and be as secure as previous

releases.

21 - Must be installable in the factory and upgradeable from 656, 703

and 708 via USB or network.

---

Collaboration/Connectivity

Between XOs with simple mesh (associate with other XO or Active-Antenna 802.11s meshes).

Between XOs with a school server with an active antenna and an access point (associate with 802.11 b/g access points with or without WEP and WPA1 encryption).

In a mixed environment.'

With non-XO machines ' Security

Laptops should travel through the delivery chain unactivated.

Laptops should not boot until they are activated.

Can be activated wirelessly (with a school server) (not recently tested)

Can be activated via USB.

Performance/scalability

TBD

Localization, including correctness of language-specific icon-related text

Keymaps are correct or are very close to correct for US/International, Amharic, Spanish, Portuguese, and Kreyól keyboards.

Translations of system strings need help!

User documentation - inside XO and online (wiki) available

TBD

Maintaining history '

List, search, and filter records of actions on the system by time

filter records of actions by title

---

These test cases should be on separate pages, transclude them into a master page with {{Test_case/RIPv2}} you want -- Skierpage 19:49, 1 August 2008 (UTC)

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

---

Number/Title	2/Corner Activation
Objective	Verify that a user can change the delay before the frame appears when the cursor is moved into the corner of the screen.
Feature	Sugar Control Panel#Frame
Source	[2] Section 3.1, [9]
Approach	Compliance will be verified using ANVL. ANVL will send a RIP response to the SuperRouter with an incorrectly formatted RIP header. The SuperRouter should ignore these packets. ANVL will then send a couple of valid packets, which the SuperRouter should accept.
Test Tools	* ANVL by Midnight Networks Sun workstation with SunOS 4.1.3 and 2 Ethernet interfaces SuperRouter
Test Setup	* Verify that the SuperRouter and Sun workstation are on a stand-alone network. See RTN Configuration #1.
Test Procedure	* Verify that the ANVL configuration file (create as needed) is updated to reflect the SuperRouter interfaces that are connected to the Sun Workstation. Enter the following command from the ANVL directory: anvl -f <config file name> -l med rip 2.2 Observe the output on the Sun workstation
Expected Results & Pass Criteria	The SuperRouter shall not accept the packets that contain the invalid fields. Pass or failure of this test will be reported by ANVL.
Comments

---

Number/Title	RTN-1004
Objective	Verify that RIPv2 ignores packets with invalid fields.
Feature	RIPv2 should not accept packets containing invalid fields.
Source	[2] Section 3.1, [9]
Approach	Compliance will be verified using ANVL. ANVL will send a RIP response to the SuperRouter with an incorrectly formatted RIP header. The SuperRouter should ignore these packets. ANVL will then send a couple of valid packets, which the SuperRouter should accept.
Test Tools	* ANVL by Midnight Networks Sun workstation with SunOS 4.1.3 and 2 Ethernet interfaces SuperRouter
Test Setup	* Verify that the SuperRouter and Sun workstation are on a stand-alone network. See RTN Configuration #1.
Test Procedure	* Verify that the ANVL configuration file (create as needed) is updated to reflect the SuperRouter interfaces that are connected to the Sun Workstation. Enter the following command from the ANVL directory: anvl -f <config file name> -l med rip 2.2 Observe the output on the Sun workstation
Expected Results & Pass Criteria	The SuperRouter shall not accept the packets that contain the invalid fields. Pass or failure of this test will be reported by ANVL.
Comments

Reporting test results

To report results from a set of test cases, add a line to the appropriate table in the test case pages below with a quick summary; and include details, including setup and test team, on the talk page.

• 8.1.1 Features to be Tested
• Update.1 tests
• Ship2.2 test cases - complete
• User-focused test plans:

  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 the User-Focused Test Plans page to read, review, and help create test plans.

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)

Schedule

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

Also See

GSOC08 OLPC Project Automated Testing