From Fedora Project Wiki

(Test Cases/Priority)
(Test Cases/Priority)
Line 66: Line 66:
 
**level 2 takes a step further to include more use cases.  
 
**level 2 takes a step further to include more use cases.  
 
**level 3 captures the remaining identified use cases
 
**level 3 captures the remaining identified use cases
[[QA:Fedora_12_Install_Results_Template#Test_Areas]]
+
*Test cases for Fedora 12 ,please refer to [[QA:Fedora_12_Install_Results_Template#Test_Areas]]
  
 
== Reporting Bugs and Debugging Problems==
 
== Reporting Bugs and Debugging Problems==

Revision as of 08:53, 10 June 2009

Fedora 12 Installation Test Plan

Introduction

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

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

New features of Fedora 12

Important.png
FIXME
Need confirmation on the following list of features for F12

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

Schedule/Milestones

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

Community Testing

Test Environment/Configs

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

  • i386
  • ppc
  • x86_64

Test Cases/Priority

  • This test plan will use priority of 3 level for test cases
    • level 1 is intended to verify that installation is possible on common hardware using common use cases.
    • level 2 takes a step further to include more use cases.
    • level 3 captures the remaining identified use cases
  • Test cases for Fedora 12 ,please refer to QA:Fedora_12_Install_Results_Template#Test_Areas

Reporting Bugs and Debugging Problems

Communicate

If you want to participate test day,you can get help from any of these ways:

References