Testing
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
- Release 8.2.0, on top of 8.1.1
- XO_Base_Features
- Minor Release 8.1.1
- Release 8.1.2, ECO-6
- Release 8.1.1, ECO-5
Older notes
- Test process sprint- Wed, Oct 17th, 2007
Community Testing:
Older community efforts (should be updated to the new test template):
Links of Interest to Testing
- Test Config Notes - Links to configuration info that are useful in testing
- 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)
- 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
- 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:
Builds of Interest:
- Recent stable builds
- "Update.1" builds
- "Bleeding-edge" 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.
Notes and minutes
- Test meeting Minutes - Weekly meetings of interested test people, Mondays 1pm EDT
Many related pages need to be merged:
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. | |
| Expected Results & Pass Criteria | The timezone for the laptop has been changed correctly and the timezone is represented properly by the 'date' command. | |
| 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)- XMPP collaboration and scalability testing - XMPP collaboration and scalability testing
Schedule
Please see the official roadmap (from the trac main page) for schedule dates and features for each release.