Testing: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
 
(311 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 }}
===User Stories===
== Release info ==
User Stories are meant to provide a narrative description of how the OLPC products will be used in schools and homes. These stories provide the basis for Use Case or System Tests that will help ensure we have prioritized and documented the most important uses of our products in the field.
=== 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]].
High level topics for User Stories can be divided into a few major categories:
=== Testing for release 11.2.0 ===
See [[Test_cases/11.2]] for information about testing the [[11.2.0]] release.
# Start up (out-of-the-box experience)
# Connectivity and Collaboration
# Archive, Backup, Content


=== Testing for the 10.1.x releases ===
* [[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 ===
'''Start up scenario 1: Server support'''<br>
* [[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
Jose is a 6 year-old student at a school in Brazil is being issued his XO laptop today. The school has spent weeks preparing for this day. The school server is set up and has internet connectivity. It contains books and software specific for Jose's grade level. The teacher has a specific activity she asks all the children to work on.
* [[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 ===
Thoughts: Typical start up with a server in a large school...imprinting, download content
* 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 ===
[[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==
'''Start up scenario 2: No server support'''<br>
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].
Maria is a 10 year-old student in a school being issued XOs. This school just received their server and have not set it up yet and have no internet connectivity. The teacher is not prepared with activities or curriculum, but will allow the children time to explore the laptops on their own.


The awesome New Zealand testers use a very simple [[Activity testing template]].
Thoughts: Typical start up with no server...imprinting, running some local apps, simple mesh connectivity to find a friend.


* [[Systematic testing]]


Test beds:
'''Start up scenario 3: Server start up'''<br>
* [[Creating a testbed]]
The server hardware and cables have arrived early at a school in Uruguay. The local administrator takes the hardware out of the box and would like to set up the server and download the curriculum books and software that have been created ahead of time.
* [[Wireless Sparse Testbed]] - Universidade Federal Fluminense, Brazil
* [[Ejabberd resource tests/try_5]] school server jabber testing


''Older'' obsolete community efforts:
Thoughts: How to set up a server...
* [[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]]
* [[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:
'''Connectivity scenario 1: Connectivity with or without a server'''<br>
* Infrastructure_AP: Zoom 4400 AP+2 Wireless-G Access Point (Approx. $50 USD)
Three students are working on a project together using the Journal to track/save their files. They start the project at their 'large' school with 3 mesh channels and internet connectivity. They save their work and get together later at home to continue working. They don't have internet connectivity or access to the server, but they can continue with Abiword and images they previously downloaded.
* Long range Wireless: Wavion’s WS410 Spatially Adaptive Wi-Fi Access Point (Approx. $1600 USD)
* [[XS_Server_Specification#XSX_Specifications|Server HW Specs]]


== Builds of interest==
Thoughts: Ensure that collaboration projects can resume without a server...
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 ===
'''Connectivity scenario 2: Mesh hoping connectivity'''<br>
The school server's wireless connection does not reach to all classrooms in and around the school. Andres is outside the range for a direct connection, but there is a laptop between his and the server that is currently i standby mode. He opens his XO to work on a project that includes downloading images from the internet.


* [http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/ "Update.1" builds]
Thoughts: Ensure connectivity through a standby XO to a server; also ensure it will work with 2 hops, one standby and one active XO...
* [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 ==
'''Connectivity scenario 3: 200 XOs on one server'''<br>
* [[Testing meetings]] - Weekly meetings of interested test people, usually Thursdays
On a particularly well-attended day of school, Uma is the 200th student to open her laptop to get started on a project. She opens the 'shared' document that she worked on at home yesterday. There is only one server in this school.


== General navigation ==
Thoughts: Ensure that 200 laptops can be seen by the server; ensure that the 200th laptop has no more trouble accessing the network than the first ones; is there any automatic updating of shared documents when a version change is detected? How does Uma find her friend if there are 200 other laptops in the mesh...
[[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:
'''Connectivity scenario 4: Two server school'''<br>
{{Community testing}}
School with two servers -- may not be needed for first release


<br clear="all" />
Thoughts: We want to write down the scenerios for using a repeater and multiple hops, but testing and support for more sophisticated connectivity may have to be scheduled while shipping the first release.
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.
'''Backup/Archive scenario 1: Basic backup'''<br>
Parvis goes to a school where he gets connected to the server every day. One day he inadvertently deleted a document that he had spent many days working on.


All these test cases are in [[:Category:Test cases]] and most are listed by the queries in [[Test cases 8.2.0]].
Thoughts: Automatic back up when connected to the server; Retrieval of a lost document


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 ===
'''Other'''

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.


 + 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"