From Fedora Project Wiki

(Save page-in-progress)
(obsolete (lots of ancient details here, not really usable as written, but could be refreshed))
 
(27 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{admon/note|Obsolete (but updateable)|This test plan is obsolete in many details; it has not been significantly updated since 2009 and refers to many obsolete details of Fedora installation, tree creation etc. The basic concept is still valid, however, and should still be implemented in [[Taskotron]].}}
= Revision history =
= Revision history =


First draft: [[User:Wwoods|WillWoods]] 19:46, 17 June 2009 (UTC)
First draft: [[User:Wwoods|WillWoods]] 20:54, 17 June 2009 (UTC)


= Introduction =
= Introduction =
Line 17: Line 19:
TBD. No clear priorities exist yet.
TBD. No clear priorities exist yet.
-->
-->
= Scope =
= Scope =


Line 24: Line 25:
# Can current Rawhide users update their systems using this repo?
# Can current Rawhide users update their systems using this repo?
# Can this Rawhide tree be installed?
# Can this Rawhide tree be installed?
# Does the basic system (the [[Critical_Path_Packages_Proposal|"critical path"]]) work as expected for simple testing?
# Does the basic system (a subset of the [[Critical_Path_Packages_Proposal|"critical path"]]) work as expected for simple testing?


It is ''not'' intended to be an exhaustive test of any part of the system.
It is ''not'' intended to be an exhaustive test of any part of the system.
Line 30: Line 31:
= Test Pass/Fail Criteria =
= Test Pass/Fail Criteria =


Rawhide will be considered Good if all of the following conditions are met:
Rawhide will be considered ''Good'' for each purpose if all of the underlying conditions are met:


=== Repo Sanity ===
* Contains valid yum metadata (repodata)
* Contains valid yum metadata (repodata)
* Contains key packages (kernel, glibc, coreutils)
* Contains key packages (kernel, glibc, coreutils)
* No unresolved dependencies in critical packages
* No unresolved dependencies in critical packages
* comps.xml exists and is valid
* comps.xml exists and is valid
* installer images (kernel, initrd, install.img, and boot.iso) exist
 
=== Installability ===
* installer images (kernel, initrd,and boot.iso) exist
* kernel boots on ''most'' machines of the primary architectures
* kernel boots on ''most'' machines of the primary architectures
* initrd is able to find stage2 (install.img) by at least one method (network, local CD)
* initrd is able to find stage2 by at least one method (network, local CD)
* stage2 is able to detect the presence of disks attached to most common controllers
* stage2 is able to detect the presence of disks attached to most common controllers
* Kernel/X is able to set up common display configurations for at least 2 out of 3 of the most common video drivers (intel, nouveau, radeon)
* installer can write packages to disk storage
* installer can setup up bootloader correctly for common boot systems


'''TODO FINISH BELOW HERE'''
=== Basic Functionality ===
* Kernel/X is able to set up common display configurations
** At least 2 out of 3 of the most common video drivers (intel, nouveau, radeon) must be functioning
* Kernel/X properly handle input from standard USB keyboard/mouse
* System is able to establish a wired network connection
** As with video, this should work for ''most'' common network drivers. Individual chipset failures may be waived.
* {{package|yum}} is able to install simple updates


= Test Deliverables =
= Test Deliverables =


Describe what the consumables will be from testing.  Examples include:
This test plan should produce:
* This test plan
* A summary report on whether Rawhide is broken or not
* A test summary document for each major milestone
* Bug reports for broken dependencies / missing files / etc.
* A list of defects filed
* A list of test cases used to verify the expected results. (see below)
* Any test scripts used for automation or verification


= Test Cases  =
= Test Cases  =
Using the level of detail required by this test plan, outline test areas and test cases to be exercised.
 
''TODO: Automate these test cases. See [https://fedorahosted.org/autoqa/query?status=new&status=assigned&status=reopened&component=tests&summary=~Automate&milestone=israwhidebroken.com&order=priority tickets for each test here].
 
=== Repo Sanity ===
# [[QA:Repodata validity test case|Repodata validity]]
# [[QA:Comps Validity Test Case|comps.xml validity]]
# [[QA:Core package dependency closure test case|Core package dependency closure]]
# [[QA:Core package existence test case|Core package existence]]
 
=== Installability ===
# [[QA:Installer image presence test case|Installer image existence]]
# [[QA:Kernel simple boot test case|Kernel boot]]
# [[QA:Anaconda stage2 fetch test case|Anaconda loader fetching stage2]]
# [[QA:Anaconda storage probe test case|Anaconda stage2 disk probe]]
# [[QA:Anaconda package install test case|Anaconda package install]]
# [[QA:Anaconda bootloader setup test case|Anaconda bootloader setup]]
 
=== Basic Functionality ===
# [[QA:X basic display test case|X startup/basic display configuration]]
# [[QA:X basic input handling test case|X basic input handling]]
# [[QA:Network basic test case|Basic network connectivity]]
# [[QA:Yum simple update test case|yum update functionality]]


= Test Environment =
= Test Environment =
Describe the environment tests will be executed in
 
* The tests will be run on a host which has the Rawhide tree accessible by HTTP or FTP.
** The tests will download a lot of data, so ideally the host should have a very fast network link to the HTTP/FTP mirror.
* The test host will be no older than RHEL5/CentOS5 or currently supported Fedora releases.
* The test host will have at least 1GB free disk space:
** critical path packages (~300MB)
** their associated metadata (~200MB)
** all of the boot images (~300MB)
** plus some extra scratch space for rebuilding images etc.


= Responsibilities =
= Responsibilities =
High-level detail of who is accountable for different phases of testing.
 
Fedora QA team members are responsible for executing this test plan. Contributions from Rawhide testers and other interested parties are encouraged.


= Schedule =
= Schedule =


Outline the scheduled milestones.
Ideally this test plan should be run for ''every new Rawhide tree'' - i.e. daily.


= Risks =
= Risks =


Given the current scope and test priority, what are some potential risks.  Are there any other contingencies should problems arrise?  How will issues be dealt with when they surface.
* Testing kernel boot and X startup is currently tricky to automate.
* [[Critical_Path_Packages_Proposal]] - while exact list of packages may change, it is possible that no agreement on the exact list can be made.  In this event, a temporary subset of critical packages will be used


= Reviewers =
= Reviewers =


 
<!-- Add a line like this:
* ~~~~
This will automatically be expanded to your username and timestamp. Preview to check it. -->
* [[User:Jlaska|jlaska]] 11:13, 19 June 2009 (UTC) <!-- jlaska -->
* [[User:Johannbg|viking-ice]] 16:14, 24 June 2009 (UTC)


= References =
= References =
* [[JohnPoelstra/ImproveRawhideF10#Defining_GOOD]] - A previous discussion of Rawhide requirements
* [[Critical Path Packages Proposal]] - Proposal to define the most critical packages - required for some repo sanity test cases
* [[Israwhidebroken.com Proposal]] - This test plan is a central part of this proposal.
<references/>


<references/>
[[Category:Obsolete Test Plans]]
[[Category:Rawhide Acceptance Test Cases]]

Latest revision as of 09:11, 6 August 2014

Obsolete (but updateable)
This test plan is obsolete in many details; it has not been significantly updated since 2009 and refers to many obsolete details of Fedora installation, tree creation etc. The basic concept is still valid, however, and should still be implemented in Taskotron.

Revision history

First draft: WillWoods 20:54, 17 June 2009 (UTC)

Introduction

This test plan documents the process used to check the basic requirements for a Rawhide tree to be acceptable for further testing. It aims to check whether Rawhide is installable, usable as a package repo for updating, and whether critical packages are present and functional.

In short, this is how we decide if Rawhide is broken or not.

Test Strategy

There are three main components here: Repo sanity, Installability, and Basic Functionality. These three categories can be tested mostly independent of one another.

Scope

This plan seeks to answer three basic questions:

  1. Can current Rawhide users update their systems using this repo?
  2. Can this Rawhide tree be installed?
  3. Does the basic system (a subset of the "critical path") work as expected for simple testing?

It is not intended to be an exhaustive test of any part of the system.

Test Pass/Fail Criteria

Rawhide will be considered Good for each purpose if all of the underlying conditions are met:

Repo Sanity

  • Contains valid yum metadata (repodata)
  • Contains key packages (kernel, glibc, coreutils)
  • No unresolved dependencies in critical packages
  • comps.xml exists and is valid

Installability

  • installer images (kernel, initrd,and boot.iso) exist
  • kernel boots on most machines of the primary architectures
  • initrd is able to find stage2 by at least one method (network, local CD)
  • stage2 is able to detect the presence of disks attached to most common controllers
  • installer can write packages to disk storage
  • installer can setup up bootloader correctly for common boot systems

Basic Functionality

  • Kernel/X is able to set up common display configurations
    • At least 2 out of 3 of the most common video drivers (intel, nouveau, radeon) must be functioning
  • Kernel/X properly handle input from standard USB keyboard/mouse
  • System is able to establish a wired network connection
    • As with video, this should work for most common network drivers. Individual chipset failures may be waived.
  • yum is able to install simple updates

Test Deliverables

This test plan should produce:

  • A summary report on whether Rawhide is broken or not
  • Bug reports for broken dependencies / missing files / etc.
  • A list of test cases used to verify the expected results. (see below)

Test Cases

TODO: Automate these test cases. See tickets for each test here.

Repo Sanity

  1. Repodata validity
  2. comps.xml validity
  3. Core package dependency closure
  4. Core package existence

Installability

  1. Installer image existence
  2. Kernel boot
  3. Anaconda loader fetching stage2
  4. Anaconda stage2 disk probe
  5. Anaconda package install
  6. Anaconda bootloader setup

Basic Functionality

  1. X startup/basic display configuration
  2. X basic input handling
  3. Basic network connectivity
  4. yum update functionality

Test Environment

  • The tests will be run on a host which has the Rawhide tree accessible by HTTP or FTP.
    • The tests will download a lot of data, so ideally the host should have a very fast network link to the HTTP/FTP mirror.
  • The test host will be no older than RHEL5/CentOS5 or currently supported Fedora releases.
  • The test host will have at least 1GB free disk space:
    • critical path packages (~300MB)
    • their associated metadata (~200MB)
    • all of the boot images (~300MB)
    • plus some extra scratch space for rebuilding images etc.

Responsibilities

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

Schedule

Ideally this test plan should be run for every new Rawhide tree - i.e. daily.

Risks

  • Testing kernel boot and X startup is currently tricky to automate.
  • Critical_Path_Packages_Proposal - while exact list of packages may change, it is possible that no agreement on the exact list can be made. In this event, a temporary subset of critical packages will be used

Reviewers

References

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