Difference between revisions of "0.90/Testing"

From Sugar Labs
Jump to navigation Jump to search
m (link updates)
 
(16 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
<noinclude>{{TOCright}}
+
<noinclude>[[Category:Testing]]
−
[[Category:Testing]]
 
 
</noinclude>
 
</noinclude>
  
 
==Install testing environment==
 
==Install testing environment==
 +
===Fedora 14===
 +
 +
* {{Iframe|See this testing request for [[0.90/Testing|Sugar 0.90]] |http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg15705.html|900|700|1}}
 +
 +
* See also [[Fedora]].
  
 
===SoaS===
 
===SoaS===
Line 9: Line 13:
 
See [[Sugar on a Stick/Beta]].
 
See [[Sugar on a Stick/Beta]].
  
−
Also see: [http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation/Variations]
+
Also see: [[Sugar on a Stick/Installation/Variations]]
  
−
===Fedora 13===
+
*Testing Suggestions for v4:[[Talk:0.90/Testing]]
  
−
See [[Community/Distributions/Fedora]].
+
*Up to Date Testing Results: '''[[Talk:Sugar_on_a_Stick_release_process#Test_Matrix]]'''
  
 
===Ubuntu 10.04 (Lucid Lynx)===
 
===Ubuntu 10.04 (Lucid Lynx)===
  
−
Follow instructions at http://wiki.ubuntu.com/UbuntuSugarRemix to install the latest Sugar packages and keep them up-to-date.
+
Follow instructions at the [http://wiki.ubuntu.com/Sugar Ubuntu wiki] to install the latest Sugar packages and keep them up-to-date.
  
 
==Testing plans==
 
==Testing plans==
Line 34: Line 38:
  
 
=== Ad-hoc network ===
 
=== 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.
 
Flash at least two XOs with the latest version of Sugar and the latest version of NetworkManager.
 
==== Autoconnect ====
 
==== Autoconnect ====
Line 44: Line 51:
 
==== Connect both machines to the same channel ====
 
==== Connect both machines to the same channel ====
 
---> ''the buddies should be present on the neighborhood view of the other machine''
 
---> ''the buddies should be present on the neighborhood view of the other machine''
 +
 +
[[File:Adhoc network connected.png]]
 +
 
==== Share an activity ====
 
==== Share an activity ====
 
---> ''the shared activity is displayed correctly in the neighborhod view and the sharing does work''
 
---> ''the shared activity is displayed correctly in the neighborhod view and the sharing does work''
−
* Population: The Ad-hoc iconsin 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.
+
==== 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]]
  
 
===0.90 Features===
 
===0.90 Features===
Line 54: Line 72:
  
 
* '''Enhanced Gettext'''
 
* '''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.
+
[[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
 
Name, result, comments
Line 61: Line 79:
  
 
* '''Allow the Sugar user to connect to 3G networks'''
 
* '''Allow the Sugar user to connect to 3G networks'''
−
[http://wiki.sugarlabs.org/go/Features/3G_Support#How_To_Test 3G Support Testing plan] - This Feature allows the Sugar user to connect to 3G networks using a device in the frame.
+
[[Features/3G_Support#How_To_Test|3G Support Testing plan]] - This Feature allows the Sugar user to connect to 3G networks using a device in the frame.
  
 
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
 
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
Line 74: Line 92:
  
 
* '''Font configuration'''
 
* '''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.
+
[[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;"
 
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;"
Line 153: Line 171:
 
* steps to reproduce
 
* 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 [http://wiki.sugarlabs.org/go/BugSquad/Get_Logs here].
+
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 [[BugSquad/Get_Logs|here]].
  
 
==Meetings==
 
==Meetings==
Line 189: Line 207:
 
|}
 
|}
  
−
====Testing image====
 
−
[http://shell.sugarlabs.org/~erikos/soas-testing-day-13-02-10.iso Soas Testing day build]
 
  
−
(This is the [http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ latest soas nightly build]. At the moment starting activities is broken in that build. As this is a daily snapshot it will not be fixed in time for the meeting, hence use the build from the link above.)
+
[http://shell.sugarlabs.org/~erikos/soas-testing-day-13-02-10.iso Soas Testing day build]  Very old see below:
 +
 
 +
==Current Testing image==
 +
 
 +
* '''Weekly Test Image: http://download.sugarlabs.org/soas/test/'''
 +
 
 +
* latest soas nightly build''' http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/'''
 +
:  currently f14 sugar 0.90.0  (10/08/2010)

Latest revision as of 14:33, 3 July 2012


Install testing environment

Fedora 14

SoaS

See Sugar on a Stick/Beta.

Also see: Sugar on a Stick/Installation/Variations

Ubuntu 10.04 (Lucid Lynx)

Follow instructions at the Ubuntu wiki to install the latest Sugar packages and keep them up-to-date.

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

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

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. Adhoc network XO-1.png

0.90 Features

For instructions how to test the Features listed below please have a look at the section "How to test" of each Feature page. Please add yourself with your test result to the table of each Feature.


  • Enhanced Gettext

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

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


  • Font configuration

Font configuration - Distributors/deployers can use a GConf preference to customize the Sugar font size.

Name Works Comment
Marko Marković yes/no None


Language Tests

  • Test your own native language (can be set using the Control Panel).
    • is the 3G Feature listed in the section above fully translated?
Name Language Works Comment
Max Mustermann German yes/no 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
#1 Example yes, no, yes Walter Bender, Tomeu Vizoso, Gary C. Martin None
#1358 Synchronize changes made to a Journal entry yes/no Name None
#330 Several Access Points with the same essid yes/no Name None
#1497 Name input screen is deactivable yes/no Name None
#1602 Can't connect to WEP shared key networks yes/no Name None
#1601 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.

Meetings

Where

Meetings are held online using IRC, Internet Relay Chat. You can read here more how to use IRC to join the meeting. The meeting will be taking place on the channel #sugar on the irc.freenode.net server, irc://irc.freenode.net#sugar, or webchat client.

01 March 2010

When: 14:00 UTC (9 EST)

Testing Day February the 16th

This will be an asynchronous effort, hence "Testing day" :). However we will do two kickstart meetings. One at 14:00 UTC and one at 19:00 UTC. In these meetings we will give a short introduction to what to test and answer questions about how to get the image on a usb-key and of course how to gather the results.

When

  • Kickoff-Meeting 1: 14:00 UTC
  • Kickoff-Meeting 2: 19:00 UTC

Attendees

Are you planning to attend? Add your name and your expertise below!

Name Tester Feature owner Coordinator Special skills
Simon Schampijer yes yes yes
Sebastian Dziallas yes no soas
Ryan Kabir yes no no
Mel chua yes no soas pilot community QA, SMW-based test case systems
Satyaakam Goswami yes no Hindi Translation testing
Gary Martin yes no no


Soas Testing day build Very old see below:

Current Testing image

currently f14 sugar 0.90.0 (10/08/2010)
Retrieved from "https://wiki.sugarlabs.org/index.php?title=0.90/Testing&oldid=80468"