Testing: Difference between revisions

From OLPC
Jump to navigation Jump to search
m (subsection)
No edit summary
 
(103 intermediate revisions by 18 users not shown)
Line 1: Line 1:
{{outdated}}
{{OLPC}}
{{OLPC}}
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.
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.


{{Latest Releases | firmware = inline | devel = inline | rc = inline | livecd = inline |server = inline }}
For the latest tests, see [[Update.1 tests]].
== Release info ==
=== Testing for release 11.3.1 ===
Testers are reporting test results on the testing [[Mailing lists|mailing list]] or by [[reporting bugs]].


They are ''not'' using [[Test group release notes]].
== Notes and minutes ==
=== Testing for release 11.2.0 ===
* [[Test meeting Minutes]] - Weekly meetings of interested test people, Mondays 1pm EDT
See [[Test_cases/11.2]] for information about testing the [[11.2.0]] release.
* [[Requirements]]


=== Testing for the 10.1.x releases ===
== General navigation ==
* [[10.1.3/Testing]] for [[:Category:Community testing]] of the [[Release notes/10.1.3|10.1.3 release]]
Many related pages need to be merged:
* [[Smoke_test/10.1.x/1_hour_smoke_test]]
{{Test-nav}}


=== Testing for major release 8.2.0 ===
* [[Release_notes/8.2.0#New_features_in_8.2.0|New features in 8.2.0]], on top of [[XO_Base_Features]] of 8.1.1
* [[TestPlan 8.2.0]]
* [[Test cases 8.2.0]], a set of test cases developed in the wiki
* [[TestResults 8.2.0]]


=== Release info ===
=== Testing for 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/8.1.1|Release notes for 8.1.1]]


=== Testing for release 8.1.0 ===
* August Release 8.2.0, on top of 8.1.1
[[Release notes/8.1.0|Release 8.1.0]] was also known as "Update.1", see [[Update.1 tests]] for tests and [[Testing Update.1 Results]].
** [[TestCases_8.2.0]]
** [[TestResults_8.2.0]]
** [[Release_Notes/8.2.0#New_Features_in_8.2.0|New Features in 8.2.0]]
* [[XO_Base_Features]]
* [http://wiki.laptop.org/go/OLPC_SW-ECO_5 Minor Release 8.1.1]


==Community testing==
==== Older notes ====
People interested in testing should join the [http://lists.laptop.org/listinfo/testing Testing mailing list], which is also mirrored on an external [http://olpc.396210.n2.nabble.com/Testing-f1469263.html forum].
* [[Test process sprint]]- Wed, Oct 17th, 2007


The awesome New Zealand testers use a very simple [[Activity testing template]].
== Links of Interest ==

* [[Systematic testing]]

Test beds:
* [[Creating a testbed]]
* [[Wireless Sparse Testbed]] - Universidade Federal Fluminense, Brazil
* [[Ejabberd resource tests/try_5]] school server jabber testing

''Older'' obsolete community efforts:
* [[Community testing]]
* [[Friends in testing]]
* [[Activity testing project]]
* [[Testing matrix]]
* [[Activity testing template]]

== Links of Interest to Testing ==
* [[Creating new test cases]]
* [[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
* [[Upgrading the XO| Different upgrade paths and which to use]]
** Also see Builds of Interest below
* [[Multi-hop mesh network in MIT campus]]
* [[Multi-hop mesh network in MIT campus]]
* [[Networking scenarios]]
* [[Networking scenarios]]
* [[Simple mesh test (Cerebro)]]
* [[Simple mesh test (Cerebro)]]
* School Server general info: [[XS]]
* [[Schoolserver Testing]]
** [[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
** [[Upgrade Paths| Different upgrade paths and which to use]]
* 100 Laptop Testbed:
* 100 Laptop Testbed:
**[[Collaboration_Network_Testbed]]
** [[Collaboration_Network_Testbed]]
**[[Peabody Setup]] - 100 laptop test setup in Peabody, MA
** [[Peabody Setup]] - 100 laptop test setup in Peabody, MA
* [[Activation and Developer Keys]] - how to activate or get a developer key
* [[Activation and Developer Keys]] - how to activate or get a developer key
* [[Scenario taxonomy]]
* [[Scenario taxonomy]]
* [[Requirements]]
* [[Requirements]] (no longer used)


Equipment specs:
Equipment specs:
* Infrastructure_AP: Zoom 4400 AP+2 Wireless-G Access Point (Approx. $50 USD)
* 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)
* Long range Wireless: Wavion’s WS410 Spatially Adaptive Wi-Fi Access Point (Approx. $1600 USD)
* [[XS_Server_Specification#XSX_Specifications|Server HW Specs]] (Approx. $3000 USD)
* [[XS_Server_Specification#XSX_Specifications|Server HW Specs]]


== Builds of interest==
Check out these new links to test plans and result matrices -- Get involved and help test some activities:
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]].
==Community Testing:==

* [[Friends in testing]]
===Older builds and activities ===
* [[Activity Testing Project]]
* [[Activity Testing Matrix]]
* [[Activity Testing Template]]


== Builds of Interest:==
* [http://download.laptop.org/xo-1/os/official/ Recent stable builds]
* [http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/ "Update.1" builds]
* [http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/ "Update.1" builds]
* [http://xs-dev.laptop.org/~cscott/olpc/streams/ "Bleeding-edge" builds]
* [http://xs-dev.laptop.org/~cscott/olpc/streams/ship.2 "Ship.2" builds]
** [http://xs-dev.laptop.org/~cscott/olpc/streams/joyride "Joyride" builds]
** [http://xs-dev.laptop.org/~cscott/olpc/streams/faster "Faster" builds]
** [http://xs-dev.laptop.org/~cscott/olpc/streams/meshtest "Meshtest" builds]
** [http://xs-dev.laptop.org/~cscott/olpc/streams/ship.2 "Ship.2" builds]
* [http://pilgrim.laptop.org/~pilgrim/olpc/streams/olpc3/ "OLPC-3" builds]
* [http://download.laptop.org/xo-1/os/candidate/ "Candidate" builds] before they go public


Activities script/latest activities:
Activities script/latest activities for 8.1:
* From a laptop that is connected to the internet, start a Terminal Activity and type: '''wget http://dev.laptop.org/~erikos/sucrose-activities.py'''
* http://dev.laptop.org/~erikos/sucrose-activities.py'''
* [http://dev.laptop.org/~erikos/bundles/0.81.4/ Latest 0.81.4 activities] (July 2008)
* Then type: '''python sucrose-activities.py'''
* [http://dev.laptop.org/~erikos/bundles/0.81.4/ Link to Latest Activities]


== Testing teams ==
== Notes and minutes ==
* [[Testing meetings]] - Weekly meetings of interested test people, usually Thursdays


== General navigation ==
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|Community Testing]]''' page for more details.
[[Test cases 8.2.0]] lists the test cases created for the recent [[Release notes/8.2.0|release 8.2.0]].


Test results are in [[TestResults 8.2.0]]
===Testing at OLPC===


The {{tl|Community testing}} navigation template is shown below:
'''Test Plan/Release Criteria for 8.2.0'''
{{Community testing}}


<br clear="all" />
This is a work-in-progress...
The navigation template {{tl|Test-nav}} is shown below, it should be updated and many related pages need to be merged:
{{Test-nav}}


== Test cases and test results ==
Major test areas/features to be covered are:
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.
'''Hardware/Firmware (robust behavior, ability to operate with user-oriented (touch-pad, keyboard, etc.) and external devices (mouse, etc.)
'''Power Management (Power Control & Conservation)


All these test cases are in [[:Category:Test cases]] and most are listed by the queries in [[Test cases 8.2.0]].
When the lid is closed or when the power button is pressed while Sugar is running, suspend in order to conserve power.


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]].
Resume from suspend in response to lid opening or power-button presses


=== Test case management ===
Cut power by holding the power button for several seconds


To add test categories to the pull down menu in [[Form:Test case]], modify
Power off or reset the machine via the Central XO-person's Palette
[[Property:Test category]]


To add stream checkboxes to [[Form:Test case]], modify
Control screen brightness and suspend state from the root command-line
[[Property:Build stream]]


To build queries that list test cases, edit [[TestCase Queries]] and copy the <tt><nowiki>{{#ask:&nbsp;...&nbsp;}}</nowiki></tt> markup.
Control screen brightness with the brightness keys in Sugar
For other examples of queries, see [[Testcase Query Examples]]


Comments at [[Semantic MediaWiki#Issues for Test cases]].
Peripherals


== Testing areas ==
Reliably store user data to and retrieve user data from FAT16/VFAT formatted USB Mass Storage devices.
:''These "User stories" tests date from 2007-2008''
<!--
These are tests for the builds, materials on them, networks, school servers, and any global synchronization. There is a [[Test activity]] being designed to make testing on an XO simple, and independent of the details of the backend that tracks test results.


Any volunteer who is willing to test should be directed to one single portal: [[Test_issues|Testing]], and s/he can choose which tasks s/he would like to execute. --Chih-yu, Jan 2008
Reliably store user data to and retrieve user data from FAT16/VFAT formatted SD/SDHC devices.
-->
High level topics for "User stories testing" can be divided into a few major categories:


=== One Hour Smoke Test ===
USB ethernet adapters, keyboards, and mice should function similarly to their normal function on other operating systems.


# [[Smoke test]] links to the 1-hour smoke test for different releases, and other smoke tests.
Login via serial consoles.


=== Networks ===
We do not have strong expectations about the behavior of other peripherals.
# [[Tests/100 laptops]]


=== Views and visualizations ===
Firmware


#[[Tests/Home view|Home view]]
Developer keys should grant access to OFW.
#[[Tests/Groups view|Groups view]]
#[[Tests/Neighborhood view|Neighborhood view]]
#[[Tests/Frame|Frame]]


<!--
Should be able to flash any build from OFW.
{|

Should be able to rewrite manufacturing data (e.g. language, write-protect tags) from OFW

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

<div>The section below has to be edited (in progress)…

Installing or removing activities should never change the ability of the system to run.</div>

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 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 <nowiki>{{Test_case/RIPv2}}</nowiki> you want'' -- [[User:Skierpage|Skierpage]] 19:49, 1 August 2008 (UTC)

Test area: Sugar Control Panel

{| cellspacing="0" cellpadding="0" border="1"
| '''Number/Title'''
| 1/Change Timezone
|
|-
|-
! Tests !! Results !!
| '''Objective'''
| colspan="2" | Verify that the user can change their XO's timezone from the default UTC setting.
|-
|-
| [[Tests/Mesh view]] || [[Results/Mesh view]]
| '''Feature'''
| colspan="2" | Users are able to change their XO's timezone to match the local time without having to go into a terminal to do so.
|-
|-
| [[Tests/Neighborhood view]] || [[Results/Neighborhood view]]
| '''Source'''
| colspan="2" | http://wiki.laptop.org/go/Sugar_Control_Panel#Date_.26_Time]
|-
|-
| '''Approach'''
| colspan="2" | Act as an end-user trying to change the XO's timezone to match the local time.
|-
| '''Test Tools'''
| colspan="2" | No test tools required.
|-
| '''Test Setup'''
| colspan="2" | One XO laptop running an 8.2.0 (pre-)release build.
|-
| '''Test Procedure'''
| colspan="2" | 1. Open the graphical Sugar Control Panel from the Home view.<br>
2. Click on the "Date & Time" panel.<br>
3. Find the desired timezone in the list and click on it.<br>
4. Click the check-mark on the top-right. Select either "Later" or "Restart now".<br>
4a. If you picked "Later", restart the laptop after a minute or two.<br>
5. After the XO reboots, check that the timezone changed by opening a terminal and typing 'date'.<br>
|-
| '''Expected Results & Pass Criteria'''
| colspan="2" | The timezone for the laptop has been changed correctly and the timezone is represented properly by the 'date' command.
|-
| '''Comments'''
| colspan="2" |
|}
|}
-->


===============
=== Mime Types ===


# [http://www.yolinux.com/TUTORIALS/LinuxTutorialMimeTypesAndApplications.html Mime Types test] from ''yolinux.com''
{| cellspacing="0" cellpadding="0" border="1"
:*[[What should go into Mime Type tests]]
| '''Number/Title'''
| RTN-1004
|
|-
| '''Objective'''
| colspan="2" | Verify that RIPv2 ignores packets with invalid fields.
|-
| '''Feature'''
| colspan="2" | RIPv2 should not accept packets containing invalid fields.
|-
| '''Source'''
| colspan="2" | [2] Section 3.1, [9]
|-
| '''Approach'''
| colspan="2" | 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'''
| colspan="2" | * ANVL by Midnight Networks
* Sun workstation with SunOS 4.1.3 and 2 Ethernet interfaces
* SuperRouter
|-
| '''Test Setup'''
| colspan="2" | * Verify that the SuperRouter and Sun workstation are on a stand-alone network.
* See RTN Configuration #1.
|-
| '''Test Procedure'''
| colspan="2" | * 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:


===Battery Life===
'''anvl -f <config file name> -l med rip 2.2'''
Base line test for battery life. Boot up the machines, fully charge, remove the adapters and see how long the battery lasts.
* Observe the output on the Sun workstation
* [[Battery Results]]
|-
**[[Image:Baseline_battery_test.pdf | Battery Life Test 1 Results]] <br>
| '''Expected Results & Pass Criteria'''
| colspan="2" | The SuperRouter shall not accept the packets that contain the invalid fields. Pass or failure of this test will be reported by ANVL.
|-
| '''Comments'''
| colspan="2" |
|}


============
=== Regular processes ===


# [[Tests/Start up and Activation]]
{| cellspacing="0" cellpadding="0" border="1"
# [[Test Basic Operation]]
| '''Number/Title'''
# [[Tests/Connectivity and Collaboration]]
| RTN-1004
# [[Tests/Archive, Backup, Content]]
|
# [[Tests/Invite]]
|-
| '''Objective'''
| colspan="2" | Verify that RIPv2 ignores packets with invalid fields.
|-
| '''Feature'''
| colspan="2" | RIPv2 should not accept packets containing invalid fields.
|-
| '''Source'''
| colspan="2" | [2] Section 3.1, [9]
|-
| '''Approach'''
| colspan="2" | 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'''
| colspan="2" | * ANVL by Midnight Networks
* Sun workstation with SunOS 4.1.3 and 2 Ethernet interfaces
* SuperRouter
|-
| '''Test Setup'''
| colspan="2" | * Verify that the SuperRouter and Sun workstation are on a stand-alone network.
* See RTN Configuration #1.
|-
| '''Test Procedure'''
| colspan="2" | * 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:


=== International Laptops ===
'''anvl -f <config file name> -l med rip 2.2'''
# [[Tests/Keyboard mappings]]
* Observe the output on the Sun workstation
# [[Tests/Language settings]]
|-

| '''Expected Results & Pass Criteria'''
=== Upgrading ===
| colspan="2" | The SuperRouter shall not accept the packets that contain the invalid fields. Pass or failure of this test will be reported by ANVL.
# [[From last stable build]]
|-
# [[Tests/Backward_Comp]]
| '''Comments'''

| colspan="2" |
=== Hardware and firmware ===
|}

# [[Tests/SD card]]
# [[Tests/SD card acting as a usb drive in card reader]]
# [[Tests/USB stick]]
# [[Tests/Manufacturing Data]]
# [[Tests/Suspend_Resume|Tests/Suspend and resume]]

=== Network/Time Sync ===


# [[Tests/Time sync]]
=== Reporting test results ===
# [[Tests/Network mgr]]


=== SchoolServer ===
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.


===In-house testing (from 2007?) ===
====Items to Test====
''Old''?


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


Other Test plans:
=== Other test plans ===


*[[802.11s Connectivity Test Plan]] - Connectivity, wifi protocol
*[[802.11s Connectivity Test Plan]] - Connectivity, wifi protocol from 2007
*[[Image:B3-B4 OLPC Test Plan.xls]] - Low Level Test Plan
*[[Image:B3-B4 OLPC Test Plan.xls]] - Low level test plan from 2007
*<strike>[[Tinderbox Testing]] - automated testing for each build</strike> (outdated) --[[User:Chihyu|Chihyu]] 13:58, 29 January 2008 (EST)
*<strike>[[Tinderbox Testing]] - automated testing for each build</strike> (outdated) --[[User:Chihyu|Chihyu]] 13:58, 29 January 2008 (EST)
*[[XMPP collaboration and scalability testing]] - XMPP collaboration and scalability testing
* see [[:Category:Tests]] and [[:Category:Test Plans]] ''TODO: These older test plans should be marked obsolete or merged into test cases.''


==Schedule==
==Schedule==
Line 481: Line 236:
Please see the [http://dev.laptop.org/roadmap official roadmap] (from the trac main page) for schedule dates and features for each release.
Please see the [http://dev.laptop.org/roadmap official roadmap] (from the trac main page) for schedule dates and features for each release.


== Also See ==
==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.
* [[Test Config Notes]]
* [[Memory leak testing]]
* [[Olpc-update]]
* [[Clean-install procedure]]

== See also ==


[http://code.google.com/soc/2008/psf/appinfo.html?csaid=F89A4969030B59E6 GSOC08 OLPC Project Automated Testing]
* [http://code.google.com/soc/2008/psf/appinfo.html?csaid=F89A4969030B59E6 GSOC08 OLPC Project Automated Testing]
* [[Test process sprint for 2007 first software release]]- Wed, Oct 17th, 2007


[[Category:Test Plans]]
[[Category:Tests]]
[[Category:Developers]]
[[Category:Developers]]
[[Category:Software]]
[[Category:Software]]
[[Category:Hardware]]
[[Category:Hardware]]
[[Category:Subsystems]]
[[Category:Testing]]

Latest revision as of 05:17, 6 August 2013

The contents of this page are considered outdated and some of the information may be stale. Please use information here with caution, or update it.
  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.


 + Software 
XO
13.2.11 2020-01-29
XS
xs-0.7 2012-02-20


Release info

Testing for release 11.3.1

Testers are reporting test results on the testing mailing list or by reporting bugs.

They are not using Test group release notes.

Testing for release 11.2.0

See Test_cases/11.2 for information about testing the 11.2.0 release.

Testing for the 10.1.x releases

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 Testing Update.1 Results.

Community testing

People interested in testing should join the Testing mailing list, which is also mirrored on an external forum.

The awesome New Zealand testers use a very simple Activity testing template.

Test beds:

Older obsolete community efforts:

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:

XO Checkbox


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

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 test categories to the pull down menu in Form:Test case, modify Property:Test category

To add stream checkboxes to Form:Test case, modify Property:Build stream

To build queries that list test cases, edit TestCase Queries and copy the {{#ask: ... }} markup. For other examples of queries, see Testcase Query Examples

Comments at Semantic MediaWiki#Issues for Test cases.

Testing areas

These "User stories" tests date from 2007-2008

High level topics for "User stories testing" can be divided into a few major categories:

One Hour Smoke Test

  1. Smoke test links to the 1-hour smoke test for different releases, and other smoke tests.

Networks

  1. Tests/100 laptops

Views and visualizations

  1. Home view
  2. Groups view
  3. Neighborhood view
  4. Frame


Mime Types

  1. Mime Types test from yolinux.com

Battery Life

Base line test for battery life. Boot up the machines, fully charge, remove the adapters and see how long the battery lasts.

Regular processes

  1. Tests/Start up and Activation
  2. Test Basic Operation
  3. Tests/Connectivity and Collaboration
  4. Tests/Archive, Backup, Content
  5. Tests/Invite

International Laptops

  1. Tests/Keyboard mappings
  2. Tests/Language settings

Upgrading

  1. From last stable build
  2. Tests/Backward_Comp

Hardware and firmware

  1. Tests/SD card
  2. Tests/SD card acting as a usb drive in card reader
  3. Tests/USB stick
  4. Tests/Manufacturing Data
  5. Tests/Suspend and resume

Network/Time Sync

  1. Tests/Time sync
  2. Tests/Network mgr

SchoolServer

In-house testing (from 2007?)

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

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