From Fedora Project Wiki

(Test Environment/Configs)
(obsolete (old release))
 
(150 intermediate revisions by 4 users not shown)
Line 1: Line 1:
= Fedora 12 Installation Test Plan =
+
= Introduction =
 +
This document describes the tests that will be created and used to verify the functions/components of {{FedoraVersion|long|12}}.
  
== Revision history ==
+
The goals of this plan are to:
{| border="1"
+
* Organize the test effort
|- style="color: white; background-color: #3074c2; font-weight: bold"
+
* Communicate the planned tests to all relevant stake-holders for their input and approval
| Date || Revision || Comment
+
* Serve as a base for the test planning for future Fedora 12 releases
|-
+
= Test Strategy =
| {{date|2009-06-04}} || 0.1 || Initial version
+
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.
|}
 
  
== Introduction ==
+
= New features of {{FedoraVersion|long|12}} =
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:
+
As with Fedora 11, Fedora 12 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.
* ''Organize'' the test effort
+
 
* ''Communicate'' the strategy, scope and priorities of the planned tests to all relevant stake-holders for their input and approval
+
* [[Anaconda/Features/MDRaid|Use MDRaid instead of dmraid]]
* Serve as a base for the test planning for future Fedora releases
+
* [[Anaconda/Features/StorageFiltering|Select devices better, plus storage cleanup]]
 +
* [[Anaconda/Features/UICleanup|Storage UI Cleanup]]
  
== Test Strategy ==
+
Additional features outside the scope of testing can be found at:
 +
* [[Anaconda/Features|List of anaconda features]]
 +
* [[Releases/12/FeatureList|Fedora 12 Accepted Features]]
  
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.
+
= Schedule/Milestones =
 +
* The {{FedoraVersion|long|12}} release schedule is available at [[Releases/12/Schedule]]
 +
* Each major milestone(Beta,Preview,etc..) will demand a full regression run
  
Where possible, [https://fedorahosted.org/snake SNAKE] will be used to automate and aid in reproducibility.
+
= Test Priority =
  
== Test Priority ==
 
 
This test plan will use a 3 '''tier''' classification for test execution 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:
+
== [[QA/TestPlans/Fedora12InstallTier1|Tier#1 test cases]] ==
 +
 
 +
Tier1 is intended to verify that installation is possible on common hardware using common use cases.   
 +
 
 +
Verification includes:
 
* Common boot media
 
* Common boot media
 
* Common Installation source
 
* Common Installation source
 
* Installation using defaults installation options
 
* Installation using defaults installation options
 
* Default Partitioning
 
* Default Partitioning
 +
 +
== [[QA/TestPlans/Fedora12InstallTier2|Tier#2 test cases]] ==
  
 
Tier2 takes a step further to include more use cases.  Tier2 verification consists of:
 
Tier2 takes a step further to include more use cases.  Tier2 verification consists of:
Line 38: Line 47:
 
* Some architecture specific verification
 
* Some architecture specific verification
  
Lastly, Tier3 captures the remaining identified use cases:
+
== [[QA/TestPlans/Fedora12InstallTier3|Tier#3 test cases]] ==
 +
 
 +
Tier3 captures the remaining identified use cases:
 
* More exhaustive partitioning schemes
 
* More exhaustive partitioning schemes
 
* More complex networking scenarios
 
* More complex networking scenarios
Line 46: Line 57:
 
* Upgrade testing
 
* Upgrade testing
  
== Schedule/Milestones ==
+
= Test Pass/Fail Criteria =
* The Fedora 12 release schedule is available at [[Releases/12/Schedule]]
+
 
* Each major milestone will demand a full regression run (Alpha, Beta, PreviewRelease)
+
The milestone release of Fedora 12 should conform these criteria:
  
== Community Testing ==
+
== Entrance criteria ==
* The Fedora 12 test day is available at [[QA/Test_Days/F12]]
+
* Trees must be generated using release engineering tools (not hand crafted)
* Location of download:please go to test day [[QA/Test_Days/F12]] to download the latest media for testing
+
* There must be no unresolved dependencies for packages included in the installation tree
== Test Environment/Configs ==
+
* 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
  
For Fedora 12,we will execute test cases on these hardware platforms:
+
== Alpha criteria ==
* i386
+
* Entrance criteria have been met
* ppc
+
* All test tiers have have been executed
* x86_64
+
* All tier#1 tests pass
 +
 
 +
== Beta criteria ==
 +
* Alpha criteria have been met
 +
* All tier#2 tests pass
 +
 
 +
== GA criteria ==
 +
* Beta criteria have been met
 +
* All test tiers must pass
 +
* Any open defects have been documented as release notes
  
== Test Cases (Functional) ==
+
= Scope and Approach =
  
{{admon/important|FIXME|Need confirmation on the following list of features for F12 }}
+
Testing will include:
  
The following list of features was obtained from Anaconda/FeaturesTest plans for these features will be designed/developed on each feature page.
+
* Manually execute test cases using a rawhide boot or live image media
 +
* Where possible, the use of virtualization is encouraged to allow for greater test coverage and improve failure diagnosis
 +
* Automated execution of tests is encouraged using kickstarts designed to execute specific test casesAt this time, kickstarts are not provided for every test case.
  
*Anaconda/Features at [[Anaconda/Features]]
+
Items outside the scope of this test plan include:
*Fedora 12 Accepted Features at [[Releases/12/FeatureList]]
+
* Functional verification of software installed on the system
 +
* Installation from media not generated by fedora release engineering
  
== Test Cases (Non-Functional) ==
+
= Test Deliverables =
  
{| style="background-color: #def3fe; border: 1px solid #c5d7e0; color: black; padding: 5px; margin-bottom: 5px; min-height: 35px; padding-left: 45px;"
+
* [[QA:Fedora_12_Install_Test_Plan|This test plan]]
! colspan="3" align="left" | Image Sanity
+
* [[:Category:Fedora_12_Test_Results|A test summary document for each major milestone]]
|-
+
* A list of defects filed
! colspan="3" align="left" style="font-weight: normal;" | Tests to check sums of Media
+
* Any test scripts used for automation or verification
|-
 
| [[QA:Testcase_Mediakit_ISO_Size  ]] || [[QA:Testcase_Mediakit_ISO_Checksums  ]] || [[QA:Testcase_Mediakit_Repoclosure ]]
 
|-
 
| [[QA:Testcase_Mediakit_FileConflicts ]] || ||
 
|-
 
  
! colspan="3" align="left" | Boot Methods
+
= Testing Tasks =
|-
 
! colspan="3" align="left" style="font-weight: normal;" | Tested designed to validate the bootable media
 
|-
 
| [[QA/TestCases/BootMethodsBootIso]] || [[QA/TestCases/BootMethodsCdrom]] || [[QA/TestCases/BootMethodsDvd]]
 
|-
 
| [[QQA:Testcase_efidisk.img]] || [[QA/TestCases/BootMethodsPxeboot]] || [[QA/TestCases/BootMethodsNetboot]]
 
|-
 
| [[QA/TestCases/BootMethodsXenParaVirt]] || [[QA/TestCases/BootMethodsKVM]] ||
 
|-
 
  
! colspan="3" align="left" | Installation Source
+
Testing will execute test cases to verify installation of Fedora 12 on different hardware platforms and gather installation test feedback.
|-
+
* [[QA:Fedora_12_Install_Results_Template#Test_Areas|Installation Test Cases]]
! colspan="3" align="left" style="font-weight: normal;" | The media booted and the installation source used aren't always the same.  These tests verify installation using the described source.
+
* [[QA:Create_Install_Test_Result_Page|Instructions for adding test result page]]
|-
 
| [[QA/TestCases/InstallSourceHttp]] || [[QA/TestCases/InstallSourceNfs]] || [[QA/TestCases/InstallSourceFtpAnonymous]]
 
|-
 
| [[QA/TestCases/InstallSourceFtpNonAnonymous]] || [[QA/TestCases/InstallSourceCdrom]] || [[QA/TestCases/InstallSourceDvd]]
 
|-
 
| [[QA/TestCases/InstallSourceHardDrive]] || [[QA/TestCases/InstallSourceNfsIso]] || [[QA:TestCases/Install Source Live Image]]
 
|-
 
  
! colspan="3" align="left" | Kickstart Delivery
+
= Test Environment/Configs =
|-
 
! colspan="3" align="left" style="font-weight: normal;" | Tests to validate acquiring a kickstart script through supported methods.
 
|-
 
| [[QA/TestCases/KickstartKsFilePathKsCfg ]] || [[QA/TestCases/KickstartKsHdDevicePathKsCfg ]] || [[QA/TestCases/KickstartKsHttpServerKsCfg ]]
 
|-
 
| [[QA/TestCases/KickstartKsNfsServerPathKsCfg ]] || ||
 
|-
 
  
! colspan="3" align="left" | Package Sets
+
For {{FedoraVersion|long|12}},test cases will be executed on these hardware platforms:
|-
+
* i386
! colspan="3" align="left" style="font-weight: normal;" | Designed to exercise the most common package dependency and conflict pathways.
+
* ppc
|-
+
* x86_64
| [[QA/TestCases/PackageSetsDefaultPackageInstall]] ||[[QA/TestCases/PackageSetsMinimalPackageInstall]]||
 
|-
 
  
! colspan="3" align="left" | Partitioning
+
= Responsibilities =
|-
 
! colspan="3" align="left" style="font-weight: normal;" | The more common partitioning scenarios.  These cases ensure that anaconda (and friends) prepare the disk for post-install booting as directed.
 
|-
 
| [[QA:Testcase_Anaconda_autopart_install ]] || [[QA:Testcase_Anaconda_autopart_(encrypted)_install ]] || [[QA:Testcase_Anaconda_autopart_(shrink)_install ]]
 
|-
 
| [[QA:Testcase_Anaconda_autopart_(use_free_space)_install]] || [[QA/TestCases/PartitioningExt4OnNativeDevice ]] || [[QA/TestCases/PartitioningExt3OnNativeDevice ]]
 
|-
 
| [[QA/TestCases/PartitioningExt2OnNativeDevice]] || [[QA/TestCases/PartitioningRootfsOnLvmDevice ]] || [[QA/TestCases/PartitioningRootfsOnRaid1]]
 
|-
 
| [[QA/TestCases/PartitioningNoSwap]] || [[QA/TestCases/PartitioningRaid0OnLvmDevice]] || [[QA/TestCases/PartitioningSwapOnLvmDevice]]
 
|-
 
| [[QA/TestCases/PartitioningUninitializedDisks]] || [[QA/TestCases/PartitioningUsrOnRaid0 ]] || [[QA/TestCases/PartitioningUsrOnRaid5]]
 
|-
 
| [[QA/TestCases/PartitioningUsrOnRaid6]] || [[QA/TestCases/PartitioningRootfsOnDmraidDevice ]] || [[QA/TestCases/PartitioningPreExistingLvm2Lvm2]]
 
|-
 
| [[QA/TestCases/PartitioningPreExistingRaidRaid ]]  || ||
 
|-
 
  
! colspan="3" align="left" | Recovery
+
Fedora QA team members are responsible for executing this test plan. Contributions from Rawhide testers and other interested parties are encouraged.  
|-
 
! colspan="3" align="left" style="font-weight: normal;" | When ''stuff'' goes wrong ... we need to be able to handle it reasonably well.
 
|-
 
| [[QA:Testcase_Anaconda_rescue_mode ]] || [[QA:Testcase_Anaconda_updates.img_via_URL]] || [[QA:Testcase_Anaconda_updates.img_via_installation_source ]]
 
|-
 
| [[QA:Testcase_Anaconda_updates.img_via_local_media]] || [[QA:Testcases Anaconda save traceback to remote system ]] || [[QA:Testcases Anaconda save traceback to bugzilla ]]
 
|-
 
| [[QA:Testcases Anaconda save traceback to disk]] || [[QA:Testcases Anaconda traceback debug mode]] ||
 
|-
 
  
! colspan="3" align="left" | Storage Devices
+
= Risks and Contingencies =
|-
 
! colspan="3" align="left" style="font-weight: normal;" | Are we probing and booting post-install properly in the following scenarios?
 
|-
 
| [[QA/TestCases/StorageDeviceSata ]] || [[QA/TestCases/StorageDeviceScsi ]] || [[QA:Testcase_Install_to_Pata_Device ]]
 
|-
 
| [[QA:Testcase Anaconda iSCSI no authentication ]] || [[QA:Testcase_Anaconda_partitioning_dmraid_rootfs]] ||
 
|-
 
  
! colspan="3" align="left" | User Interface
+
* If no physical media is available for testing, it is acceptable to use a <code>boot.iso</code> or PXE boot images from a current Rawhide release. For more information, see [[Releases/Rawhide#Direct_Rawhide_install]].
|-
 
! colspan="3" align="left" style="font-weight: normal;" | Anaconda provides several user-interfaces for installation, the following cases are designed to ensure the desired interface operates as expected
 
|-
 
| [[QA/TestCases/UserInterfaceGraphical ]] || [[QA/TestCases/UserInterfaceText ]] || [[QA/TestCases/UserInterfaceVnc ]]
 
|-
 
| [[QA/TestCases/UserInterfaceCmdline ]] || [[QA/TestCases/UserInterfaceTelnet ]] ||
 
|-
 
  
! colspan="3" align="left" | Upgrade system
+
= Reporting Bugs and Debugging Problems =
|-
 
! colspan="3" align="left" style="font-weight: normal;" | Tests to validate system upgrade
 
|-
 
| [[QA:Testcase_Anaconda_Upgrade_New_Bootloader ]] || [[QA:Testcase_Anaconda_Upgrade_Skip_Bootloader]] || [[QA:Testcase_Anaconda_Upgrade_Update_Bootloader ]]
 
|-
 
| [[QA:Testcase_Anaconda_Upgrade_Encrypted_Root ]] || [[QA:Testcase_Preupgrade  ]] ||[[QA:Testcase_Preupgrade_from_older_release ]]
 
|-
 
|}
 
  
== Reporting Bugs and Debugging Problems==
+
If defects/problems are encountered, please go ahead and file the bugs following the guide below:
* Anaconda Bug Reporting Guide - [[Anaconda/BugReporting]]
+
* [[Bugs_and_feature_requests|Bug Reporting Process]]
* Anaconda Bug Reporting Process - [[Bugs_and_feature_requests]]
+
* [[How to debug installation problems]]
  
== Communicate ==
+
= Reviewers =
If you want to participate test day,you can get help from any of these ways:
+
* [[User:Jlaska|jlaska]] 19:08, 3 August 2009 (UTC)
* IRC: #fedora-qa on irc.freenode.net
 
* Mailing list: https://www.redhat.com/mailman/listinfo/fedora-test-list
 
* Developers and QA will be available on test day at [[QA/Fedora_12_test_days]]
 
* Reference of ways to communicate at [[Communicate]]
 
  
== References ==
+
= References =
* Fedora 11 Installation Guide - http://docs.fedoraproject.org/install-guide/f11/
+
* [http://docs.fedoraproject.org/install-guide/f11/ {{FedoraVersion|long|11}} Installation Guide]
 +
* Previous test plans available at [[:Category:Test_Plans]]
 +
* [https://fedoraproject.org/wiki/Category:Installer_Test_Cases Fedora Install test cases]
 
* Anaconda Documentation
 
* Anaconda Documentation
** Command-line options - http://fedoraproject.org/wiki/Anaconda/Options
+
** [[Anaconda/Options|Supported command-line options]]
** Kickstart options - http://fedoraproject.org/wiki/Anaconda/Kickstart
+
** [[Anaconda/Kickstart|Kickstart options]]
** Source Code Overview - http://fedoraproject.org/wiki/Anaconda/SourceOverview
+
** [[Anaconda/Updates|How to Create and Use an updates.img]]
** Anaconda updates.img - http://fedoraproject.org/wiki/Anaconda/Updates
+
** [[Anaconda/SourceOverview|Source Code Overview]]
** Anaconda Stage1 Guide - http://fedoraproject.org/wiki/Anaconda/Stage1DevelopmentGuide
 
** Anaconda Stage2 Guide - http://fedoraproject.org/wiki/Anaconda/Stage2DevelopmentGuide
 
  
[[Category:Test Plans]]
+
[[Category:Obsolete_Test Plans]]

Latest revision as of 08:21, 6 August 2014

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

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 12

As with Fedora 11, Fedora 12 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 12 release schedule is available at Releases/12/Schedule
  • Each major milestone(Beta,Preview,etc..) will demand a full regression run

Test Priority

This test plan will use a 3 tier classification for test execution priority.

Tier#1 test cases

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

Tier#2 test cases

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

Tier#3 test cases

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

Test Pass/Fail Criteria

The milestone release of Fedora 12 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

Alpha criteria

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

Beta criteria

  • Alpha criteria have been met
  • All tier#2 tests pass

GA criteria

  • Beta 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 using a rawhide boot or live image media
  • Where possible, the use of virtualization is encouraged to allow for greater test coverage and improve failure diagnosis
  • Automated execution of tests is encouraged using kickstarts designed to execute specific test cases. At this time, kickstarts are not provided for every test case.

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

Test Deliverables

Testing Tasks

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

Test Environment/Configs

For Fedora 12,test cases will be executed on these hardware platforms:

  • i386
  • ppc
  • x86_64

Responsibilities

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.iso or PXE boot images from a current Rawhide release. For more information, see Releases/Rawhide#Direct_Rawhide_install.

Reporting Bugs and Debugging Problems

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

Reviewers

  • jlaska 19:08, 3 August 2009 (UTC)

References