QA/TestPlans/Fedora10Install

= Fedora 10 Installation Test Plan =

Introduction
This document describes the tests that will be created and used to verify the installation of Fedora 10.

The goals of this plan are to:
 * Organize the 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

Test Strategy
Instead of outlining all possible installation inputs and outputs, this test plan will focus on defining inputs and outputs at different stages in anaconda. This will also allow different tests to be performed independently during a single installation. For example, one may execute a kickstart delivery via HTTP, raid0 partitioning using 3 physical disks, and a minimal package installation on a para-virtualized xen guest all in single installation. Scenarios where the stages are dependent will be indicated as such in the test case.

Where possible, SNAKE will be used to automate and aid in reproducibility.

Test Priority
This test plan will use a 3 tier classification for test execution priority.

Tier1 is intended to verify that installation is possible on common hardware using common use cases. Verification includes:
 * Common boot media
 * Common Installation source
 * Installation using defaults installation options
 * Default Partitioning

Tier2 takes a step further to include more use cases. Tier2 verification consists of:
 * All boot media
 * All installation sources
 * All kickstart delivery methods
 * Some architecture specific verification

Lastly, Tier3 captures the remaining identified use cases:
 * More exhaustive partitioning schemes
 * More complex networking scenarios
 * More architecture specific verification
 * Network device
 * Storage device
 * Upgrade testing

Scope
Testing will include:
 * Various methods of booting the installation program
 * Manual and kickstart execution of the installation program
 * System setup performed by the installation program (networking, modprobe.conf, bootloader, runlevel)
 * Booting the installed system

Items outside the scope of this test plan include:
 * Functional verification of software installed on the system
 * Installation from media not generated by fedora release engineering

Test Pass/Fail Criteria
Entrance criteria
 * Trees must be generated using release engineering tools (not hand crafted)
 * There must be no unresolved dependencies for packages included in the installation tree
 * There must be no dependency conflicts for packages included in the installation tree
 * Any changes in composition of the installation tree are explainable by way of bugzilla

Alpha criteria
 * Entrance criteria have been met
 * All tier#1 tests have been executed

Beta criteria
 * Alpha criteria have been met
 * All tier#1 tests pass
 * All tier#2 tests have been executed

GA criteria
 * Beta criteria have been met
 * All test tiers must pass
 * Any open defects have been documented as release notes

Test Deliverables

 * This test plan
 * A test summary document for each major milestone
 * A list of defects filed
 * Any test scripts used for automation or verification

Test Cases (Functional)
The following list of features was obtained from Anaconda/Features. Test plans for these features will be designed/developed on each feature page.

Test Environment/Configs
Hardware
 * i386
 * ppc
 * x86_64

Responsibilities

 * who's doing what

Schedule/Milestones

 * The Fedora 10 schedule is available at Releases/10/Schedule
 * Each major milestone will demand a full regression run (Alpha, Beta, PreviewRelease)

Risks and Contingencies

 * If a particular build is uninstallable, a updates.img may be used to work around any test blockers. For information on building and using an updates.img please refer to Anaconda/Updates.


 * If a build is uninstallable due to a bad kernel or driver, you may be able to work around the problem. Anaconda provides several scripts for taking a newer kernel, and using that during installation.  For details, please refer to [| scripts/upd-kernel]