Testing: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
 
(302 intermediate revisions by 68 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.


{{Latest Releases | firmware = inline | devel = inline | rc = inline | livecd = inline |server = inline }}
=== Test Strategy ===
== Release info ==
There are many people and organizations who are helping out with the test effort for the XO, network communications, the server, performance and system testing. This page will summarize all the test efforts and link to more details where ever possible.
=== 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]].
The open source community is providing a good test effort for much of the open source code. In our local test plans we need to concentrate on areas that are not easy or possible for the community due to lack of physical XO, Server, or other OLPC specific equipment.
=== 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 ===
Trac is being used to track bugs found during test. We currently don't have a system for test case management, but we may want to implement something for that as well.
* [[10.1.3/Testing]] for [[:Category:Community testing]] of the [[Release notes/10.1.3|10.1.3 release]]
* [[Smoke_test/10.1.x/1_hour_smoke_test]]


=== 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]]


=== Testing for minor releases 8.1.x ===
'''Release Criteria for Trial-2, mid July:'''
* 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 ===
The release criteria for Trial-2 software is based on meeting the expectations of as many as 2000 children and teachers using OLPC products to evaluate whether this is the right product for their school/country.
[[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]].


==Community testing==
With that in mind, we need to focus on a few good features to demonstrate 'explore', 'express', 'communicate', and 'collaborate' with good quality. This translates to prioritizing the following features:
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].
# Writing (AbiWord)
# Drawing (Paint)
# Video create (Camera)
# Programming (eToys)
# Browser (Web)


The awesome New Zealand testers use a very simple [[Activity testing template]].
Collaboration and communication should work across these activities.


* [[Systematic testing]]
[[Release Criteria Trial-2]]


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 ==
'''Test plans/pages:'''
* [[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]]
* [[Networking scenarios]]
* [[Simple mesh test (Cerebro)]]
* School Server general info: [[XS]]
** [[Schoolserver Testing]]
* 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:
# Quanta HW test plan - One time test per build. This test is aimed at environmental conditions (thermal, humidity, altitude, shake)
* Infrastructure_AP: Zoom 4400 AP+2 Wireless-G Access Point (Approx. $50 USD)
# Quanta SW Test plan - One time test per SW release to Quanta. This test is aimed at basic functionality of XOs.
* Long range Wireless: Wavion’s WS410 Spatially Adaptive Wi-Fi Access Point (Approx. $1600 USD)
# OLPC Test Plan - One time test per build. Written for B2, to be modified for B3 so as not to overlap Tinderbox or Quanta testing. Detailed manual testing for camera, keyboard, USB, mouse pad, other devices, power management.
* [[XS_Server_Specification#XSX_Specifications|Server HW Specs]]
# [[Tinderbox Testing]] - Regression after all new SW builds. This test is aimed at boot up, X drivers, low level device testing, network, and performance at the CPU level, and power management.

# [[User Stories Testing]] - One time test per SW release. This testing is aimed at system level testing based on real user stories.
== 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 ===

* [http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/ "Update.1" builds]
* [http://xs-dev.laptop.org/~cscott/olpc/streams/ship.2 "Ship.2" builds]

Activities script/latest activities for 8.1:
* http://dev.laptop.org/~erikos/sucrose-activities.py'''
* [http://dev.laptop.org/~erikos/bundles/0.81.4/ Latest 0.81.4 activities] (July 2008)

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

== General navigation ==
[[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]]

The {{tl|Community testing}} navigation template is shown below:
{{Community testing}}

<br clear="all" />
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 ==
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 <tt><nowiki>{{#ask:&nbsp;...&nbsp;}}</nowiki></tt> 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''
<!--
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
-->
High level topics for "User stories testing" can be divided into a few major categories:

=== One Hour Smoke Test ===

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

=== Networks ===
# [[Tests/100 laptops]]

=== Views and visualizations ===

#[[Tests/Home view|Home view]]
#[[Tests/Groups view|Groups view]]
#[[Tests/Neighborhood view|Neighborhood view]]
#[[Tests/Frame|Frame]]

<!--
{|
|-
! Tests !! Results !!
|-
| [[Tests/Mesh view]] || [[Results/Mesh view]]
|-
| [[Tests/Neighborhood view]] || [[Results/Neighborhood view]]
|-
|}
-->

=== Mime Types ===

# [http://www.yolinux.com/TUTORIALS/LinuxTutorialMimeTypesAndApplications.html Mime Types test] from ''yolinux.com''
:*[[What should go into Mime Type tests]]

===Battery Life===
Base line test for battery life. Boot up the machines, fully charge, remove the adapters and see how long the battery lasts.
* [[Battery Results]]
**[[Image:Baseline_battery_test.pdf | Battery Life Test 1 Results]] <br>

=== Regular processes ===

# [[Tests/Start up and Activation]]
# [[Test Basic Operation]]
# [[Tests/Connectivity and Collaboration]]
# [[Tests/Archive, Backup, Content]]
# [[Tests/Invite]]

=== International Laptops ===
# [[Tests/Keyboard mappings]]
# [[Tests/Language settings]]

=== Upgrading ===
# [[From last stable build]]
# [[Tests/Backward_Comp]]

=== 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]]
# [[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. - [[Tests/Keyboard_mappings|Test: Keyboard Settings]]
** Keys match the layouts designed
** Language, keyboard, keymappings match the settings
** All language and keyboard settings are preserved across updates
* Languages - [[Tests/Language_settings|Test: Language Settings]]
* Firmware
** WPA - Richardo/Michailis
** WEP - Richardo/Michailis
** Mesh - upgrade under loaded network - Scott
** Suspend/resume - Wad - [[Tests/Suspend_Resume|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 from 2007
*[[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)
*[[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==

Please see the [http://dev.laptop.org/roadmap 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.
* [[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]
* [[Test process sprint for 2007 first software release]]- Wed, Oct 17th, 2007

[[Category:Developers]]
[[Category:Software]]
[[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.



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