Testing: Difference between revisions

From OLPC
Jump to navigation Jump to search
Line 200: Line 200:
==== Older notes ====
==== Older notes ====
* [[Test process sprint]]- Wed, Oct 17th, 2007
* [[Test process sprint]]- Wed, Oct 17th, 2007

=== Reporting test results (Old; deprecated)===

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_Test|8.1.1 Features to be Tested]]
* [[Update.1 tests]]
* [[Ship2.2|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 Stories Testing|User-Focused Test Plans]] page to read, review, and help create test plans.





Revision as of 15:05, 25 September 2008

  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

Minor releases 8.1.x

Community Testing:


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

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

Builds of Interest:

Activities script/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

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


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.


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:

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.

Also See

GSOC08 OLPC Project Automated Testing


Older notes

Reporting test results (Old; deprecated)

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.