QA:Fedora 12 Install Test Plan

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

Introduction

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

Testing will include:

• Manually execute test cases using a live image of rawhide or DVD/CD install media
• 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

New features of Fedora 12

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

• Anaconda/Features at Anaconda/Features
• Fedora 12 Accepted Features at Releases/12/FeatureList

Schedule/Milestones

• 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

FIXME
Need to add a link to the FUDCon10 rawhide acceptance 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

Beta criteria

• Entrance criteria have been met
• All tier#1 tests have been executed

Preview criteria

• Beta criteria have been met
• All tier#1 tests pass
• All tier#2 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

Community Testing

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

• Test cases for Testing ,please refer to QA:Fedora_12_Install_Results_Template#Test_Areas
• Please select and test the test cases that best match your test environment for Fedora 12 milestone Release Candidate,and post test results according to template at QA:Fedora_12_Install_Results_Template
• Reference of posting test results at post test results
• As usual,Testing will be announced in mailing list fedora-test-list

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

• Bug Reporting Process - Bugs_and_feature_requests
• Anaconda Bug Reporting Guide - Anaconda/BugReporting

Test Environment/Configs

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

• i386
• ppc
• x86_64

Communicate

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

• IRC: #fedora-qa on irc.freenode.net
• Mailing list: fedora-test-list
• Reference of ways to communicate at Communicate

References

• Fedora 11 Installation Guide
• Previous test plans available at Category:Test_Plans
• Fedora Project QA test cases
• Anaconda Documentation
  • Supported command-line options
  • Kickstart options
  • How to Create and Use an updates.img
  • Source Code Overview
  • Anaconda Stage1 Guide
  • Anaconda Stage2 Guide