From Fedora Project Wiki

No edit summary
(obsolete (old release))
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{header|qa}}
{{header|qa}}


{{admon/note|DRAFT|This page is currently a draft.  It has not been finalized yet.  Stay tuned ...}}
= Introduction =
= Introduction =
This document describes the tests that will be created and used to verify the functions/components of {{FedoraVersion|long|14}}.
This document describes the tests that will be created and used to verify the functions/components of {{FedoraVersion|long|14}}.
Line 11: Line 10:


= Test Strategy =
= 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.
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, software raid0 partitioning using 3 physical disks, and a minimal package installation on a virtual guest all in single installation.  Scenarios where the ''stages'' are dependent will be grouped by different installation media.


= New features of {{FedoraVersion|long|14}} =
= New features of {{FedoraVersion|long|14}} =


As with Fedora 13, Fedora 14 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.
As with Fedora 13, Fedora 14 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.
* [[Anaconda/Features/StorageFiltering|Continued Storage Filtering]] changes
* [[Features/MultipathInstall|Multipath Install]] changes
* [[Anaconda/Features/UICleanup|Storage UI]] changes
* Replacing internal URL handling with {{package|libcurl}}


Additional features outside the scope of testing can be found at:
Additional features outside the scope of testing can be found at:
Line 32: Line 29:
This test plan prioritizes tests according to the major release milestones for Fedora 14, 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.   
This test plan prioritizes tests according to the major release milestones for Fedora 14, 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.   


== [[QA/TestPlans/Fedora12InstallTier1|Alpha test cases]] ==
{| class="wikitable"  border="1"
 
|-
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 [[Fedora_14_Alpha_Release_Criteria#Alpha_Release_Requirements|Alpha Release Requirements]].  
! [[QA/TestPlans/Fedora12InstallTier1|Alpha test cases]] !! [[QA/TestPlans/Fedora12InstallTier2|Beta test cases]] !![[QA/TestPlans/Fedora12InstallTier3|Final test cases]]
 
|-
Verification includes:
| 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 [[Fedora_14_Alpha_Release_Criteria#Alpha_Release_Requirements|Alpha Release Requirements]].  
| Beta (formerly tier#2) priority tests take a step further to include additional use cases and installation methods.  These tests also attempt to validate [[Fedora_14_Beta_Release_Criteria#Beta_Release_Requirements|Beta Release Requirements]].
| Final (formerly tier#3) priority tests capture all remaining use cases and installation pathways.  These tests also attempt to validate [[Fedora_14_Final_Release_Criteria#Final_Release_Requirements|Final Release Requirements]].
|-
| Verification consists of:
* Common boot media
* Common boot media
* Common Installation source
* Common Installation source
Line 42: Line 43:
* Default Partition options
* Default Partition options
* Default package installation
* Default package installation
 
| Verification consists of:
== [[QA/TestPlans/Fedora12InstallTier2|Beta test cases]] ==
 
Beta (formerly tier#2) priority tests take a step further to include additional use cases and installation methods.  These tests also attempt to validate [[Fedora_14_Beta_Release_Criteria#Beta_Release_Requirements|Beta Release Requirements]].
 
Beta verification consists of:
* All boot media
* All boot media
* All installation sources
* All installation sources
Line 53: Line 49:
* Some architecture specific verification
* Some architecture specific verification
* Some upgrade validation
* Some upgrade validation
 
| Verification consists of:
== [[QA/TestPlans/Fedora12InstallTier3|Final test cases]]  ==
 
Final (formerly tier#3) priority tests capture all remaining use cases and installation pathways.  These tests also attempt to validate [[Fedora_14_Final_Release_Criteria#Final_Release_Requirements|Final Release Requirements]].
 
Final verification consists of:
* More exhaustive partitioning schemes
* More exhaustive partitioning schemes
* More complex networking scenarios
* More complex networking scenarios
Line 65: Line 56:
* Storage device
* Storage device
* Upgrade testing
* Upgrade testing
|}


= Test Pass/Fail Criteria =
= Test Pass/Fail Criteria =
Line 85: Line 77:
Testing will include:
Testing will include:


* Manually execute test cases using DVD,CDROM,rawhide boot or live image media
* Manually executed test cases using DVD, CDROM, {{filename|boot.iso}} or live image media
* Automatically execute test cases with auto-test system. More information about install auto-test ,please see [[Is_anaconda_broken_proposal]]
* Automatically executed test cases via the [[AutoQA]] system. For more information about automatic testing, please see [[Is_anaconda_broken_proposal|Is Anaconda Broken Proposal]] and the [https://fedorahosted.org/autoqa/milestone/Automate%20installation%20test%20plan install automation roadmap].
 
<!--Items outside the scope of this test plan include:
Items outside the scope of this test plan include:
* Functional verification of software installed on the system
* Functional verification of software installed on the system
* Installation from media not generated by fedora release engineering
* Installation from media not generated by fedora release engineering
* [[Architectures#Secondary_Architectures|Secondary hardware platforms]]
* [[Architectures#Secondary_Architectures|Secondary hardware platforms]]-->


= Test Deliverables =
= Test Deliverables =
Line 115: Line 106:
= Responsibilities =
= Responsibilities =


Fedora QA team members are responsible for executing this test plan. Contributions from Rawhide testers and other interested parties are encouraged.  
Fedora QA team members are responsible for executing this test plan. Contributions from Branched testers and other interested parties are encouraged.


= Risks and Contingencies =
= Risks and Contingencies =


* If ''new'' physical media are provided for an already ''inprogress'' test run, a new test run '''must''' be initiated.  Test results from the previous run may be carried forward to the new test run if they are not affected by the changes introduced by the new physical media.
If ''new'' physical media are provided for an already ''inprogress'' test run, a new test run '''must''' be initiated.  Test results from the previous run may be carried forward to the new test run if they are not affected by the changes introduced by the new physical media.
* If physical media are '''not''' available for testing, it is acceptable to use a {{filename|boot.iso}} or PXE boot images from Rawhide.  For more information, see [[Releases/Rawhide#Using_daily_Rawhide_Anaconda_build]].


= Reporting Bugs and Debugging Problems =
= Reporting Bugs and Debugging Problems =
Line 129: Line 119:


= Reviewers =
= Reviewers =
* [[User:Jlaska|jlaska]] 19:52, 7 February 2010 (UTC)
 
* [[User:Jlaska|jlaska]] 13:16, 9 July 2010 (UTC)


= References =
= References =
* [[QA:Installation_validation_testing|Installation Validation Testing Introduction Page]]
* [http://docs.fedoraproject.org/install-guide/f{{FedoraVersion||13}}/en-US/html/ {{FedoraVersion|long|13}} Installation Guide]
* [http://docs.fedoraproject.org/install-guide/f{{FedoraVersion||13}}/en-US/html/ {{FedoraVersion|long|13}} Installation Guide]
* [https://fedoraproject.org/wiki/Category:Installer_Test_Cases Fedora Install test cases]
* [https://fedoraproject.org/wiki/Category:Installer_Test_Cases Fedora Install test cases]
Line 141: Line 133:
** [[Anaconda/SourceOverview|Source Code Overview]]
** [[Anaconda/SourceOverview|Source Code Overview]]


[[Category:Test Plans]]
[[Category:Obsolete_Test_Plans]]

Latest revision as of 08:22, 6 August 2014

Introduction

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

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 14 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, software raid0 partitioning using 3 physical disks, and a minimal package installation on a virtual guest all in single installation. Scenarios where the stages are dependent will be grouped by different installation media.

New features of Fedora 14

As with Fedora 13, Fedora 14 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:

Schedule/Milestones

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

Test Priority

This test plan prioritizes tests according to the major release milestones for Fedora 14, 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 test cases Beta test cases Final test cases
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. 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. Final (formerly tier#3) priority tests capture all remaining use cases and installation pathways. These tests also attempt to validate Final Release Requirements.
Verification consists of:
  • Common boot media
  • Common Installation source
  • Installation using default installation options
  • Default Partition options
  • Default package installation
 Verification consists of:
  • All boot media
  • All installation sources
  • All kickstart delivery methods
  • Some architecture specific verification
  • Some upgrade validation
 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 14 should conform these 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

Milestone specific criteria

Scope and Approach

Testing will include:

Test Deliverables

  • This test plan
  • test summary documents for each major milestone of F14: Category:Fedora_14_Test_Results
  • A list of defects filed
  • Any test scripts used for automation or verification

Testing Tasks

Testing will execute test cases to verify installation of Fedora 14 on different hardware platforms and gather installation test feedback.

Test Environment/Configs

For Fedora 14, test cases will be executed on the primary supported hardware platforms. This includes:

  • i386
  • x86_64

Responsibilities

Fedora QA team members are responsible for executing this test plan. Contributions from Branched testers and other interested parties are encouraged.

Risks and Contingencies

If new physical media are provided for an already inprogress test run, a new test run must be initiated. Test results from the previous run may be carried forward to the new test run if they are not affected by the changes introduced by the new physical media.

Reporting Bugs and Debugging Problems

If defects/problems are encountered, please go ahead and file the bugs following the guide below:

Reviewers

  • jlaska 13:16, 9 July 2010 (UTC)

References

Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Fedora_14_Install_Test_Plan&oldid=383538"