QA:Fedora 13 Install Test Plan
This document describes the tests that will be created and used to verify the functions/components of Fedora 13.
The goals of this plan are to:
- Organize the test effort
- Communicate the planned tests to all relevant stake-holders for their input and approval
- Serve as a base for the test planning for future Fedora 13 releases
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.
New features of Fedora 13
As with Fedora 12, Fedora 13 will bring us some new features. The following list outlines the larger changes that affect installation. Test plans for these features will be designed/developed on each feature page.
Additional features outside the scope of testing can be found at:
- The Fedora 13 release schedule is available at Releases/13/Schedule
- Each major milestone (Alpha, Beta, Final, etc..) will demand a full regression run
This test plan prioritizes tests according to the major release milestones for Fedora 13, including the Alpha, Beta and Final release milestones. All test cases are intended for execution at every milestone. However, priority should be given to tests specific to the milestone under test.
Alpha (formerly tier#1) priority tests are intended to verify that installation is possible on common hardware using common use cases. These tests also attempt to validate Alpha Release Requirements.
- Common boot media
- Common Installation source
- Installation using default installation options
- Default Partition options
- Default package installation
Beta (formerly tier#2) priority tests take a step further to include additional use cases and installation methods. These tests also attempt to validate Beta Release Requirements.
Beta verification consists of:
- All boot media
- All installation sources
- All kickstart delivery methods
- Some architecture specific verification
- Some upgrade validation
Final (formerly tier#3) priority tests capture all remaining use cases and installation pathways. These tests also attempt to validate Final Release Requirements.
Final verification consists of:
- More exhaustive partitioning schemes
- More complex networking scenarios
- More architecture specific verification
- Network device
- Storage device
- Upgrade testing
Test Pass/Fail Criteria
The milestone release of Fedora 13 should conform these 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
Milestone specific criteria
Scope and Approach
Testing will include:
- Manually execute test cases using DVD,CDROM,rawhide boot or live image media
- Automatically execute test cases with auto-test system. More information about install auto-test ,please see Is_anaconda_broken_proposal
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
- Secondary hardware platforms
- This test plan
- test summary documents for each major milestone of F13: Category:Fedora_13_Test_Results
- A list of defects filed
- Any test scripts used for automation or verification
Testing will execute test cases to verify installation of Fedora 13 on different hardware platforms and gather installation test feedback.
For Fedora 13, test cases will be executed on the primary supported hardware platforms. This includes:
Fedora QA team members are responsible for executing this test plan. Contributions from Rawhide testers and other interested parties are encouraged.
Risks and Contingencies
- If no physical media is available for testing, it is acceptable to use a
boot.isoor PXE boot images from a current Rawhide release. For more information, see Releases/Rawhide#Using_daily_Rawhide_Anaconda_build.
Reporting Bugs and Debugging Problems
If defects/problems are encountered, please go ahead and file the bugs following the guide below: