From Fedora Project Wiki

(Fedora 12 Installation Test Plan)
(Test Cases (Non-Functional))
Line 61: Line 61:
 
* x86_64
 
* x86_64
  
== Test Cases (Non-Functional) ==
+
== Test Cases/Priority ==
  
{| 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_Results_Template#Test_Areas]]
! colspan="3" align="left" | Image Sanity
 
|-
 
! colspan="3" align="left" style="font-weight: normal;" | Tests to check sums of Media
 
|-
 
| [[QA:Testcase_Mediakit_ISO_Size  ]] || [[QA:Testcase_Mediakit_ISO_Checksums  ]] || [[QA:Testcase_Mediakit_Repoclosure ]]
 
|-
 
| [[QA:Testcase_Mediakit_FileConflicts ]] || ||
 
|-
 
 
 
! colspan="3" align="left" | Boot Methods
 
|-
 
! 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
 
|-
 
! 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/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
 
|-
 
! 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
 
|-
 
! colspan="3" align="left" style="font-weight: normal;" | Designed to exercise the most common package dependency and conflict pathways.
 
|-
 
| [[QA/TestCases/PackageSetsDefaultPackageInstall]] ||[[QA/TestCases/PackageSetsMinimalPackageInstall]]||
 
|-
 
 
 
! colspan="3" align="left" | Partitioning
 
|-
 
! 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
 
|-
 
! 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
 
|-
 
! 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
 
|-
 
! 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
 
|-
 
! 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==
 
== Reporting Bugs and Debugging Problems==

Revision as of 08:44, 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

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