Update.1 tests

From OLPC
Jump to navigation Jump to search

this is still under construction --Chihyu 12:30, 17 January 2008 (EST)


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

(under construction)

Major Foci

Power Management

  1. Suspend/resume
  2. Wakeup event is repeated, #2401
    • machine can now only be woken up by pressing the power button again; the generic test cases have covered this. --Chihyu 16:42, 18 January 2008 (EST)
  3. Network mgr SEGV, #4960
  4. ohm logfile #5457, optional
    • need help with a reasonable test case; /etc/olpc-update.d/ does not exist in build 684. --Chihyu 16:51, 18 January 2008 (EST)
  5. Ebook reader should suspend on idleness, #1396

Security/Upgrades

  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)
  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

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)
  2. eJabberd server issues/bugs (#5934, #5313, #5315, #5311 - cut traffic, #5310 - olpc rpm)
  3. Looking into Openfire as backup (#5223, #5224)
  4. Point Update1 to different jabber server, #5933
  5. Link local presence (Salut) - OLPC/Collabora
  6. Journal/datastore

Completed Test Cases

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

These tests need to be done, but I have yet to create test cases that are brief enough for community testing. --Chihyu 14:27, 18 January 2008 (EST)

Others

Testing in Australia


boot up and register

setup

  • machine has to run the same build (Update.1 RC1) and firmware (q2d09a?)
  • remove config file, rebooting, etc. (steps of registering)
[note] re-registering always increase entries in the jabber roster
  • make sure the school server is running
  • power off machine

test

  • boot up the machine, in presence of the school server
  • register the machine

verify

  • XOs connect to the school server
    • how to tell - home view
  • XOs register properly with the school server
    • how to tell - registration option no longer available

network melt in gabble

setup

  • turn off school server
  • remove nm
  • boot up laptop, connect to simple mesh 1
    • olpc-netstatus, ensure XOs in salut
  • suspend the machine (press the power button, look for blinking to ensure suspension)

test

  • turn on school server, ensure it's running
  • unsuspend the XO

verify

  • within 10 mins or so, the XO should connect to the school server mesh

RF saturation test (salut/local link scaling test?)

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

setup

  • on XO, remove nm
  • shut down school server
  • regular laptop: connected to infrastructure network

test

  • regular laptops link to regular access point
  • multiple XOs link to school server???

verify regular laptops are not affected


Test Results

Please report the test results here. When you sign under each reported result, simply type 4 tildes: ~~~~ instead of typing your username, date, and time.

(a better template for reporting results will be created soon. --Chihyu 13:51, 17 January 2008 (EST))


Build Test Item English
684 keyboard good

Chihyu 13:56, 17 January 2008 (EST)

language no
future
candidate
keyboard no
language no


Keyboard/Languages

  • no: not tested
  • good: tested and pasted
  • 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 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