From Fedora Project Wiki
m (→Documentation) |
(Adding several sections ... turning into a test plan) |
||
| Line 1: | Line 1: | ||
{{admon/caution|This is a draft|This is a draft of a document that may or may not be migrated into a more sane namespace.}} | {{admon/caution|This is a draft|This is a draft of a document that may or may not be migrated into a more sane namespace.}} | ||
= | = Introduction = | ||
Fedora | 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 | |||
{{admon/important|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: | |||
# Define a set of high-level test areas that group similar functional components together | |||
# Organize volunteers into teams, each team focused on a specific test area | |||
# 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 [http://en.wikipedia.org/wiki/Exploratory_testing 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 = | = Schedule = | ||
| Line 23: | Line 42: | ||
|- | |- | ||
| Tue 2008-11-25 || General Availability | | Tue 2008-11-25 || General Availability | ||
|- | |||
|} | |||
= Test Areas = | |||
= Responsibilities = | |||
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 | |||
| | |||
| | |||
|- | |- | ||
|} | |} | ||
| Line 81: | Line 135: | ||
= Documentation = | = Documentation = | ||
== Installing Fedora to your | == Installing Fedora to your SD card == | ||
Requirements: | |||
* Another computer with an SD reader | |||
* An internet connection | |||
# Download the installation script: <pre># wget http://katzj.fedorapeople.org/olpc/livecd-iso-to-disk.sh</pre> | # Download the installation script: <pre># wget http://katzj.fedorapeople.org/olpc/livecd-iso-to-disk.sh</pre> | ||
# Download a Fedora Live image from: <pre># wget http://download.fedora.redhat.com/pub/fedora/linux/releases/test/10-Beta/Live/i686/F10-Beta-i686-Live.iso</pre> | # Download a Fedora Live image from: <pre># wget http://download.fedora.redhat.com/pub/fedora/linux/releases/test/10-Beta/Live/i686/F10-Beta-i686-Live.iso</pre> | ||
# Write the live image to your SD card: <pre># bash livecd-iso-to-disk.sh --xo-sd F10-Beta-i686-Live.iso /path/to/sd/device | # Write the live image to your SD card: <pre># bash livecd-iso-to-disk.sh --xo-sd F10-Beta-i686-Live.iso /path/to/sd/device | ||
Revision as of 20:14, 30 September 2008
.png){kind=small}
This is a draft
This is a draft of a document that may or may not be migrated into a more sane namespace.
This is a draft of a document that may or may not be migrated into a more sane namespace.
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?
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:
- Define a set of high-level test areas that group similar functional components together
- Organize volunteers into teams, each team focused on a specific test area
- 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 |
Test Areas
Responsibilities
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.
Find NEW Fedora XO bugs
FIXME - provide tinyurl link to NEW Fedora XO Bugs
- Search for all bugzilla bugs with the following criteria:
- status=NEW
- product=Fedora
- version=rawhide
- whiteboard=XO
Triage NEW Fedora XO Bugs
To help with triaging ...
- Start with the list of NEW Fedora XO bugs at http://tinyurl.com/52wclh
For each bug, ask yourself the following questions:
- Is the bug specific to the XO hardware or environment?
- 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:
- Mark the bug as blocking 461806 (FedoraOnXO)
- 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:
- Are you able to confirm that the steps to reproduce no longer trigger the failure?
- Have any new bugs been introduced as a result of the fix?
- Are any release notes required?
When comfortable with the fix:
- Add a comment indicating which build or software packages were tested
- Change the bug state to CLOSED with a resolution of RAWHIDE
If the reported issue has not been addressed:
- Add a comment indicating which build or software packages were tested that still exhibit the failure
- Change the state to ASSIGNED
Documentation
Installing Fedora to your SD card
Requirements:
- Another computer with an SD reader
- An internet connection
- Download the installation script:
# wget http://katzj.fedorapeople.org/olpc/livecd-iso-to-disk.sh
- Download a Fedora Live image from:
# wget http://download.fedora.redhat.com/pub/fedora/linux/releases/test/10-Beta/Live/i686/F10-Beta-i686-Live.iso
- Write the live image to your SD card:
# bash livecd-iso-to-disk.sh --xo-sd F10-Beta-i686-Live.iso /path/to/sd/device