10.1.3/Testing: Difference between revisions

From OLPC
Jump to navigation Jump to search
(Init)
 
No edit summary
Line 4: Line 4:
==Testing plans==
==Testing plans==


=== Mesh network ===
* Flash at least two XOs with the latest version of Sugar and the latest version of NetworkManager.
==== Autoconnect ====
* connect to an Access Point on one machine and restart the machine
-> ''the machine does autoconnect with the AP''
* start the machine without having connected to an AP before
-> ''the machine should autoconnect to a mesh network''
==== Connect both machines to the same channel ====
-> ''the buddies should be present on the neighborhood view of the other machine''
==== Share an activity ====
-> ''the shared activity is displayed correctly in the neighborhod view and the sharing does work''

=== Ad-hoc network ===

[[File:Adhoc network Indicate population.png]]

Flash at least two XOs with the latest version of Sugar and the latest version of NetworkManager.
==== Autoconnect ====
* connect to an Access Point on one machine and restart the machine
---> ''the machine does autoconnect with the AP''
* start the machine without having connected to an AP before
---> ''the machine should autoconnect to Ad-hoc network 1''
* start machine A and connect to the Ad-hoc network 6, start machine B without having been connected to an AP before
---> ''machine B should autoconnect to the Ad-hoc network 6''
==== Connect both machines to the same channel ====
---> ''the buddies should be present on the neighborhood view of the other machine''

[[File:Adhoc network connected.png]]

==== Share an activity ====
---> ''the shared activity is displayed correctly in the neighborhod view and the sharing does work''
==== Population ====
The Ad-hoc icons in the neighborhood view do indicate whether the network is "populated" or not, whether it is used by more than one person. It does not indicate the number of people that are connected though. If the fill color of the Ad-hoc icon is set then there is at least one person listening.
* On machine A connect to an Ad-hoc network. Start machine B which has been connected to an access point before.
---> ''On machine B it should automatically connect to the access point and the icon representing the Ad-hoc network machine A is connected to should be colored, the fill color is set.''
* Shut down machine A.
---> ''after 10-15 minutes the icon representing the Ad-hoc network machine A is connected to should be uncolored, the fill color is NOT set. This is indicates that the network is not populated.''

=== Collaborate between XO-1.0 and XO-1.5 without infrastructure ===
The XO-1.5 and XO-1.0 will see adhoc networks in his neighborhood view, so it the XO-1.0 can connect to an adhoc network that has been created by a learner on the XO-1.5.
[[File:Adhoc network XO-1.png]]


===10.1.3 Features===
===10.1.3 Features===
For instructions how to test the Features listed below please have a look at the section "How to test" of each Feature page.
For instructions how to test the Features listed below please have a look at the section "How to test" of each Feature page.

* '''Enhanced Gettext'''
[http://wiki.sugarlabs.org/go/Features/Enhanced_Gettext#How_To_Test Enhanced Gettext Testing plan] - Enhanced Gettext adds an extra search path for translation files for Sugar activities. This allows deployments to add and update activity translations independently of the release process.

Name, result, comments

Juan Pérez, no, none


* '''Allow the Sugar user to connect to 3G networks'''
* '''Allow the Sugar user to connect to 3G networks'''
Line 65: Line 17:
| ''Jane Doe''
| ''Jane Doe''
| ''yes'' || ''None''
| ''yes'' || ''None''
|-
|}


* '''Font configuration'''
[http://wiki.sugarlabs.org/go/Features/Font_configuration#How_To_Test Font configuration] - Distributors/deployers can use a GConf preference to customize the Sugar font size.

{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
|-style="background:#787878; color: white;"
! Name !! Works !! Comment
|-
| ''Marko Marković''
| ''yes/no'' || ''None''
|-
|-
|}
|}

Revision as of 14:38, 9 December 2010

Install testing environment

Follow the instructions at Release_notes/10.1.3.

Testing plans

10.1.3 Features

For instructions how to test the Features listed below please have a look at the section "How to test" of each Feature page.

  • Allow the Sugar user to connect to 3G networks

3G Support Testing plan - This Feature allows the Sugar user to connect to 3G networks using a device in the frame.

Name Works Comment
Jane Doe yes None


Backwards compatibility tests

  • Migrate the Journal

Please verify that the Journal is migrated fine after an update. For example from 0.82 to 0.88.

Name Versions Works Comment
Pierre-Paul-Jacques 0.82-0.88 yes/no None


Connectivity: Different internet connections

You should test here if you can connect with a WEP and WPA/WPA2 network, if a wired connection is possible and the 3G connection test can be logged here, too.

Name Connectivity Type Works Comment
Pierre-Paul-Jacques WEP yes/no None


Bug Fix testing

For particular bugs you can indicate your test results in this section. This can be done by more than one person, just separate name and result by a column.

Bug Description Works? Tester Comment
Template:Bug Example yes, no, yes Walter Bender, Tomeu Vizoso, Gary C. Martin None
Template:Bug Synchronize changes made to a Journal entry yes/no Name None
Template:Bug Several Access Points with the same essid yes/no Name None
Template:Bug Name input screen is deactivable yes/no Name None
Template:Bug Can't connect to WEP shared key networks yes/no Name None
Template:Bug Intro screen doesn't unfreeze dcon yes/no Name None

How to write a good bug report

You should note the following in the bug report:

  • the version you are using
  • steps to reproduce

In most cases it is of interest to the developers to look at the Sugar logs. Instructions how to get the logs can be seen here.

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