Update.1 tests

Schedule & Features

The focus of this build is to

1. fix bugs
2. get the suspend/resume working for better battery life
3. get the first level activity isolation for security
4. backup of laptops to the school server
5. there is a new wireless driver - some rewriting

Please also refer to the milestone and the official roadmap for schedule dates and features for each release.

Test Plans

An 1hr smoke test should be performed with each candidate, and the smoke test results should be reported in Test Group Release Notes.

Major Foci

Power Management

1. Suspend/resume (does not apply to B4 machines)
   • Generic test cases
2. Network mgr SEGV, #4960
   • Tests: NetworkManager
3. ohm logfile #5457, optional
   • The code for this doesn't exist yet, so the testcase doesn't either.  :) Cjb 14:26, 23 January 2008 (EST)

Security/Upgrades

(does not apply to B4 machines)

1. Activation w/USB, w/school server
   • does "activation" mean upgrade to another build? --Chihyu 11:13, 22 January 2008 (EST)
2. olpc-update --usb without manually upgrading olpc-update. (#3881)
   • Type olpc-update --version in the console. Verify that the version is 2.0 or newer.
3. Basic activity isolation (#5033, #5346)
   • need help confirm that Tests: Isolation is testing the correct issues --Chihyu 11:46, 22 January 2008 (EST)
   • need help create a test case for #5346 --Chihyu 11:21, 22 January 2008 (EST)
4. Automatic Time sync (#3359)
   • how to test this without using more than one machine? --Chihyu 12:08, 22 January 2008 (EST)
5. orphaned files, #5637
   • cannot create test cases due to the disappearance of original bug description --Chihyu 12:29, 22 January 2008 (EST)
6. Mesh - upgrade under loaded network - Scott
   • Test: Backward Compatibility

Wireless/USB/Network Manager

Wireless Test Cases - Yani, Ricardo

1. Intermittent connection to jabber service, #4193
2. Network sniffing script, #5153
3. WPA working from sugar, #5258
4. WEP working from sugar, #5485

Tubes/Presence (Scaling/Performance)

1. Remove N squared scaling issue in groups (#4965): test this once #5311 is fixed. --Chihyu 17:05, 24 January 2008 (EST)
   • add other XOs as friends
   • confirm that friends are recorded in /home/olpc/.sugar/default/friends
   • confirm that the school server also keeps the same record
     • has a tool been developed to test this? --Chihyu 18:21, 24 January 2008 (EST)
2. eJabberd server issues/bugs (#5934, #5313, #5315, #5311 - cut traffic, #5310 - olpc rpm)
   • waiting for the fixes from Process One --Chihyu 17:28, 24 January 2008 (EST)
3. Looking into Openfire as backup (#5223, #5224)
   • this is a task, not a bug to be tested --Chihyu 18:21, 24 January 2008 (EST)
4. Point Update1 to different jabber server, #5933
   • this is a task, not a bug to be tested --Chihyu 18:21, 24 January 2008 (EST)
5. Scaling? #5817
6. Link local presence (Salut) - OLPC/Collabora
   • need help with main issues and test cases --Chihyu 18:21, 24 January 2008 (EST)
7. Journal/datastore
   • need help with main issues and test cases --Chihyu 18:21, 24 January 2008 (EST)

Completed Test Cases

1. Browse
2. Other activities
3. Please follow the test cases in User-Focused Test Plans. Some test cases should already be covered in the previous section (#Major Foci).

Incomplete Test Cases

Please help revise/create test cases in

Others

• 802.11s Connectivity Test Plan - Connectivity, wifi protocol
• Tinderbox Testing - automated testing for each build-->

Testing in Australia

Boot up and Register

[note] Re-registering always increases the entries in the jabber roster.

Setup:

1. Every XO has to run the same build (Update.1 RC1) and firmware (q2d09).
2. Remove network manager and config file:
   • In the Terminal activity, type

     cd .sugar/default/

     rm nm/networks.cfg

     rm config

3. Reboot the XO.
4. Make sure the school server is running.

Actions:

1. Reboot the XO again (in the presence of the school server).
2. Click on the "Register" option when mouse over the XO guy in the center of Home View.
3. Reboot the XO (in the presence of the school server).

Verify:

• All XOs are connected to the school server.
  • In Home View, the connection indicator next to the battery icon should read "Connected to a School Mesh Portal".
  • Alternatively, type olpc-netstatus in the Terminal activity (might have to become root), one should see

Telepathy : gabble
Jabber    : schoolserver.laptop.org

• All XOs register properly with the school server.
  • Mouse over the XO guy in the center of Home View, and the "Register" option should no longer be available.

Network Melt Down in Gabble(?)

Setup:

1. Turn off the school server.
2. Remove network manager:
   • In the Terminal activity, type

     rm .sugar/default/nm/networks.cfg

3. Boot up the XO, and it should connect to Simple Mesh 1
   • In the Terminal activity, type olpc-netstatus (might have to become root) to ensure every XO shows Telepathy : salut
4. Suspend the machine by pressing the power button
   • The power indicator LED should be blinking in suspend mode.

Actions:

1. Turn on school server, and ensure it's running.
2. Unsuspend the XO by pressing the power button again.

Verify:

• Within 10 minutes or so, the XO should connect to the School Server Mesh.
  • In Home View, the connection indicator next to the battery icon should read "Connected to a School Mesh Portal".

RF Saturation (salut/local link scaling test?)

This is designed to understand whether the XOs affect other regular laptops connected to wireless network.

Setup:

1. On each XO, remove network manager:
   • In the Terminal activity, type

     rm .sugar/default/nm/networks.cfg

2. Shut down the school server.

Actions:

1. Turn on school server.
2. On a regular laptop, connect to infrastructure network (i.e. regular wireless access point).
3. Connect multiple XOs to the school server simultaneously.

Verify:

• The wireless network connection of the regular laptops are not affected by the XOs.

Test Results

Please report the test results here, following the template.

Template

1. If the table has not been linked to any test cases, either the test cases have not been created, or please help us locate the test cases!
2. When you sign under each reported result, simply type 4 tildes: ~~~~ instead of typing your username, date, and time.
3. Values to fill in:
   • no: not tested
   • good: tested and passed
   • If a defect is found, please file a trac ticket and fill in the ticket number in the table. For example, 5969.

Build	Test Item	English
684	keyboard	good Chihyu 13:56, 17 January 2008 (EST)
	language	5969 Chihyu 17:47, 28 January 2008 (EST)
future candidate	keyboard	no
	language	no

Suspend/resume

Build	Suspend Mode	Sleep Mode (power button)	Sleep Mode (lid closing)	Ebook Mode	Restarting Sugar	Battery Mode	Disable Suspend/Resume
690	no	no	no	no	no	no	no
future candidate	no	no	no	no	no	no	no

Security/Upgrades

Build	Test Item
690	no
future candidate	no

Wireless/USB/Network Manager

Build	Wireless	USB	Network Manager
690	no	no	no
future candidate	no	no	no

Tubes/Presence (Scaling/Performance)

Build	Test Item
690	no
future candidate	no

Core Activity: Browse

Please add the testing results for other core activities below this section!

Build	Browse: test case #1
690	no
future candidate	no

User-Focused Test Plans

Build	SD Card	SD Card as USB drive
690	no	no
future candidate	no	no

Keyboard/Languages

Build	Test Item	English	Spanish	Arabic	Mongolian	Devanagari	Thai	Nigerian	Amharic	Urdu	Nepali	Pashto	Portuguese
future candidate 1	keyboard	no	no	no	no	no	no	no	no	no	no	no	no
	language	no	no	no	no	no	no	no	no	no	no	no	no
future candidate 2	keyboard	no	no	no	no	no	no	no	no	no	no	no	no
	language	no	no	no	no	no	no	no	no	no	no	no	no