QA/TestPlans/Fedora10 On XO

Introduction

This document describes the test process by which Fedora 10 will be verified for operation consistent to that of other common laptop hardware.

The goals of this plan are to:

• Organize a community test effort
• Communicate the strategy, scope and priorities of the planned tests to all relevant stake-holders for their input and approval
• Serve as a base for the test planning for future Fedora releases

FIXME - Outline exit criteria
What bugs should be prioritized by development? How do we know if something should be fixed or not?

Strategy

In an effort to focus testing on specific XO hardware, the test strategy will be to:

1. Define a set of high-level test areas that group similar functional components together
2. Organize volunteers into teams, each team focused on a specific test area
3. Teams will develop a rough test plan for their test area. Each team can dictate the required level of testing (both in terms of depth and breadth)

As no centralized automation is available, test teams are encouraged to leverage exploratory testing and built-in unit-tests where possible.

Use existing tools to facilitate writing new test builds to the XO's SD card (see livecd-iso-to-disk.sh).

Schedule

An up-to-date schedule for Fedora 10 is available at Releases/10/Schedule. A summary of Fedora XO related test milestones is noted below.

Date	Milestone
Tue 2008-09-30	Public beta
Fri 2008-10-10	Snapshot#1
Fri 2008-10-17	Snapshot#2
Fri 2008-10-24	Snapshot#3
Tue 2008-11-04	Preview release
Tue 2008-11-25	General Availability

Scope

The scope of all testing should be representative of the XO hardware under test. No need to test Gigabit ethernet if the XO doesn't provide such an adapter. See the test area break down for more details.

Items not tested:

• Installation of Fedora on an XO - only live image booting from the SD is planned for Fedora 10

FIXME
Do we need to test persistent storage on the live image?

Test Areas

Built-in Camera

• What applications can be used to verify the camera?
  • Possibly Cheese. http://www.gnome.org/projects/cheese/
• Laptop microphone/camera in-use indicators behave as expected

Power Management

• Suspend/resume
• Hibernate
  • close lid
  • low battery
• Use and report findings from powertop
  • Measure battery usage?
• Display brightness configuration (dim when idle)
• Remove/add power adapter while running
• Laptop Power/battery indicators behave as expected

Networking

• Wireless networking
  • laptop wifi status indicator behaves as expected
  • firmware loaded by NM
  • can connect using various methods (None/WEP/WPA)
  • VPN?
  • Sharing an ad-hoc network w/ another XO

Display

• xrandr rotation?
• Using expected driver and resolution settings
• Changing vt's back and forth
• Coming out of suspend?
• touchpad interface?
• gamepad interface?
• Brightness up/down accelerator key?
• plymouth graphical boot enabled+working by default?

Audio

• pulse audio default settings (not muted)
• various mixer settings visible/editable (ala gnome-volume-control)
• gnome system sounds enabled
• Recording (ala gnome-sound-recorder)
• headphone jack / internal speaker
• Volume up/down accelerator key?

Other

• test USB port
• Anything specific to boot processing (plymouth noted above)
• Default configured services?

Responsibilities

This section outlines the test teams and various community points of contact.

• User:gdk
• User:katzj
• User:jlaska

Each test area is being split up for a different team of experts to deep dive into. The table below will be used to outline the teams and their focus areas.

Test Area	Team Name	Team Members
Example: Orbital Laser	Team Dunder Mifflin	Jim, Pam, Stanley
Built-in Camera
Power Management
Networking
Display
Audio

HOWTO's

The following sections are intended to provide high-level instructions for common tasks encountered by a Fedora XO tester.

File Fedora XO bugs

All bugs will be tracked in Bugzilla.

Please file all bugs found while testing Fedora on the XO with the following parameters:

• product = Fedora
• version = rawhide
• blocks = FedoraOnXO

For convenience, you can file an new Fedora XO bug by clicking here.

Triage NEW Fedora XO Bugs

To help with triaging ...

1. Start with the list of NEW Fedora XO bugs at http://tinyurl.com/52wclh

For each bug, ask yourself the following questions:

1. Is the bug specific to the XO hardware or environment?
2. Was the following information provided?
   • Build tested (rawhide-YYYYMMDD or package versions)
   • Clear steps to reproduce the problem

If the above requirements have been met, please:

1. Mark the bug as blocking 461806 (FedoraOnXO)
2. Change to bug state to ASSIGNED

For further reading, the bug triage process is described in more detail at BugZappers.

Test a MODIFIED Fedora XO Bug

FIXME - provide tinyurl link to MODIFIED Fedora XO Bugs

Ask the following questions:

1. Are you able to confirm that the steps to reproduce no longer trigger the failure?
2. Have any new bugs been introduced as a result of the fix?
3. Are any release notes required?

When comfortable with the fix:

1. Add a comment indicating which build or software packages were tested
2. Change the bug state to CLOSED with a resolution of RAWHIDE

If the reported issue has not been addressed:

1. Add a comment indicating which build or software packages were tested that still exhibit the failure
2. Change the state to ASSIGNED

Documentation

Getting Started

FIXME
need more docs!

• What are we trying to accomplish?
  • According to OLPC/Fedora_on_XO, allow users to run a standard Linux desktop, based on Fedora 10, on their XO system.

• What are the requirements for testing?
  • List matching hardware
  • Known issues on older XO's?

• How to sign-up for a team?
• How to communicate issues?

• Where to go for help?
  • fedora-test-list
  • #fedora-qa

• Where are test images posted?

Before you get an XO

• Visit http://laptopgiving.org/start to familiarize yourself with the XO hardware and OLPC mission.

• Download the OS images mentioned in the sections below.

• Purchase a Sandisk Extreme III SD card SD card if you do not already have one

When you get an XO

1. Try out the hardware (sound should play at boot, webcam should take a picture)
2. Update the Sugar OS with the "general public" clean-install procedure
   • Install build 767 located at - http://download.laptop.org/xo-1/os/candidate/767/jffs2/
   • Note that the new build will not have any applications until you run Software update
3. Boot the XO and connect to a nearby wireless network
   • To find OLPC mac address ... press <ctrl><alt><Neighborhood>. Then type

     ip addr list eth0

   • You may need to manually configure your SSID with

     iwconfig eth0 mode managed essid MYSSID

4. Go to Software update in the Control Panel and apply any updates
5. Obtain a developer key (see http://wiki.laptop.org/go/Developer_key#Getting_a_developer_key_for_your_running_XO_laptop)
   1. Load the Browse activity
   2. Navigate to file:///home/.devkey.html
      • Follow the instructions on the page
   3. Wait for developer key activation (more information at https://www.redhat.com/archives/fedora-test-list/2008-October/msg00229.html)
   4. Download key using instructions provided
6. Reboot

Installing your SD card

Requirements:

• Another computer to flash the SD card
• SD reader
• SD card - specifically a Sandisk Extreme III SD card (either 2 Gig or 4 Gig capacity).
• An internet connection

To install a live image to your SD card:

1. Download the installation script:

   # wget http://katzj.fedorapeople.org/olpc/livecd-iso-to-disk.sh

2. Download an OLPC Fedora Live image from:

   # wget http://katzj.fedorapeople.org/olpc/olpc-gnome.iso

3. Write the live image to your SD card:

   # bash livecd-iso-to-disk.sh --xo --extra-kernel-args 3 /tmp/olpc-gnome.iso /dev/sdb1

Common Errors
For help resolving common errors found when writing your live image, see FedoraLiveCD/USBHowTo#Errors_and_Solutions.

If you get the error "Error: The flag 'boot' is not available for loop disk labels" when running parted. To fix this run:

syslinux -s /dev/sdb1

which will set the disk label to "msdos".

FAQ

• OLPC Support FAQ