From Fedora Project Wiki

(Test Strategy)
Line 79: Line 79:
= Communicate =
= Communicate =
If you want to participate test day of Fedora 12,you can get help or give feedback by any of these ways:
If you want to participate the testing of Fedora 12,you can get help or give feedback by any of these ways:
* IRC: #fedora-qa on
* IRC: #fedora-qa on
* Mailing list: [ fedora-test-list]
* Mailing list: [ fedora-test-list]

Revision as of 07:55, 15 June 2009

This page is currently a draft. This test plan has not been finalized yet. Stay tuned ...


This document describes the tests that will be created and used to verify the functions/components of Fedora 12.

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 12 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.

New features of Fedora 12

Need confirmation on the following list of features for Fedora 12

As Fedora 11,Fedora 12 will bring us some new features.The following list of features was obtained from Anaconda/Features. Test plans for these features will be designed/developed on each feature page.


  • The Fedora 12 release schedule is available at Releases/12/Schedule
  • Each major milestone(Alpha,Beta,Preview,etc..) will demand a full regression run

Test Pass/Fail Criteria

This test plan will use a 3 tier classification for test execution priority.3 tier Priority of test cases ,please refer to 3 tier priority

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

Beta criteria

  • Entrance criteria have been met
  • All tier1 tests have been executed

Preview criteria

  • Beta criteria have been met
  • All tier1 tests pass
  • All tier2 tests have been executed

GA criteria

  • Preview criteria have been met
  • All test tiers must pass
  • Any open defects have been documented as release notes

Scope and Approach

Testing will include:

  • Manually execute test cases of Test Day using a live image of rawhide or updated system to rawhide
  • Manually/kickstart boot the installation program to execute the installation
  • Automatically execute installation testing via cobbler/koan etc..,cobbler guide and scripts,please refer to cobbler

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

Community Testing

We verify installation against Fedora 12 milestone Release Candidate builds on different hardware platforms.

Reporting Bugs and Debugging Problems

If you catch some bugs during testing,we encourage you to go ahead and file the bugs.If you a new person here,please follow the guide below

Test Environment/Configs

For Fedora 12, we will execute test cases on these hardware platforms:

  • i386
  • ppc
  • x86_64


If you want to participate the testing of Fedora 12,you can get help or give feedback by any of these ways: