QA:Rawhide Acceptance Test Plan

Revision history

First draft: WillWoods 20:54, 17 June 2009 (UTC)

Introduction

This test plan documents the process used to check the basic requirements for a Rawhide tree to be acceptable for further testing. It aims to check whether Rawhide is installable, usable as a package repo for updating, and whether critical packages are present and functional.

In short, this is how we decide if Rawhide is broken or not.

Test Strategy

There are three main components here: Repo sanity, Installability, and Basic Functionality. These three categories can be tested mostly independent of one another.

Scope

This plan seeks to answer three basic questions:

1. Can current Rawhide users update their systems using this repo?
2. Can this Rawhide tree be installed?
3. Does the basic system (a subset of the "critical path") work as expected for simple testing?

It is not intended to be an exhaustive test of any part of the system.

Test Pass/Fail Criteria

Rawhide will be considered Good for each purpose if all of the underlying conditions are met:

Repo Sanity

• Contains valid yum metadata (repodata)
• Contains key packages (kernel, glibc, coreutils)
• No unresolved dependencies in critical packages
• comps.xml exists and is valid

Installability

• installer images (kernel, initrd, install.img, and boot.iso) exist
• kernel boots on most machines of the primary architectures
• initrd is able to find stage2 (install.img) by at least one method (network, local CD)
• stage2 is able to detect the presence of disks attached to most common controllers

Basic Functionality

• Kernel/X is able to set up common display configurations
  • At least 2 out of 3 of the most common video drivers (intel, nouveau, radeon) must be functioning
• Kernel/X properly handle input from standard USB keyboard/mouse
• System is able to establish a wired network connection
  • As with video, this should work for most common network drivers. Individual chipset failures may be waived.
• yum is able to install simple updates

Test Deliverables

This test plan should produce:

• A summary report on whether Rawhide is broken or not
• Bug reports for broken dependencies / missing files / etc.
• A list of test cases used to verify the expected results. (see below)

Test Cases

TODO: write test cases for each of these. See tickets here.

Repo Sanity

1. Repodata validity
2. comps.xml validity
3. Core package existence
4. Core package dependency closure

Installability

1. Installer image existence
2. Kernel boot
3. Anaconda loader fetching stage2
4. Anaconda stage2 disk probe

Basic Functionality

1. X startup/basic display configuration
2. X basic input handling
3. Basic network connectivity
4. yum update functionality

Test Environment

• Tests will run on a host which has the Rawhide tree accessible on the local filesystem. It may be network-mounted.
• The test host will be no older than RHEL5/CentOS5 or currently supported Fedora releases.

Responsibilities

Fedora QA team members are responsible for executing this test plan. Contributions from Rawhide testers and other interested parties are encouraged.

Schedule

Ideally this test plan should be run for every new Rawhide tree - i.e. daily.

Risks

• Testing kernel boot and X startup is currently tricky to automate.

Reviewers

• jlaska 11:13, 19 June 2009 (UTC)
• viking-ice 16:14, 24 June 2009 (UTC)

References

• JohnPoelstra/ImproveRawhideF10#Defining_GOOD - A previous discussion of Rawhide requirements
• Critical Path Packages Proposal - Proposal to define the most critical packages - required for some repo sanity test cases