From Fedora Project Wiki

(Created page with '<!-- This is the FESCo proposal template. It is not necessary that you use this template but it is encouraged that you do. It will help FESCo focus on the issue being addressed...')
 
(Problem Space)
 
(88 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
{{header|qa}}
 +
 
<!-- This is the FESCo proposal template.  It is not necessary that you use this template but it is encouraged that you do.  It will help FESCo focus on the issue being addressed and the parts that need discussion, as well as identify the scope of the proposal. You may remove all these comment sections from your proposal. -->
 
<!-- This is the FESCo proposal template.  It is not necessary that you use this template but it is encouraged that you do.  It will help FESCo focus on the issue being addressed and the parts that need discussion, as well as identify the scope of the proposal. You may remove all these comment sections from your proposal. -->
  
 
== Overview ==
 
== Overview ==
  
Provide a single, well-known location with information about whether or not Rawhide is ''broken'', and a link to the ''last known-good'' Rawhide tree.
+
The purpose of AutoQA installation test automation is to simplify testing and improve test efficiency.  The AutoQA install test project should address the following problems:
 +
 
 +
* The system should be easy to allow for tester and developer use
 +
* Have clear documentation for customizing and creating new tests
 +
* Support test execution using existing Fedora infrastructure services, but not require them
 +
* Test results are easy to verify
 +
 
 +
== Scope ==
 +
The Fedora installation test automation project covers the whole installation from retrieving installation media to first boot. Details are below:
 +
# retrieve installation media
 +
# Installation media sanity check
 +
# Install with different system specifications, installation sources and partition etc.
 +
# get the installation output and logs.
  
=== Problem Space ===
+
====Problem Space====
 +
The Fedora installer is a complicated software application that often requires significant setup time to properly and efficiently test.  Installer failures typically come from the following areas:
  
Sometimes Rawhide is ''broken''. Brokenness typically comes in one of these types:
+
''' Image Sanity '''
 +
# ISO file size is too large
 +
# Invalid SHA256 checksum
 +
# Invalid implanted ISO md5sum
 +
# Install environment - anaconda has specific application, library and config file format requirements.
 +
# Versions check
  
* Installer
+
''' Boot Methods'''
** Installer images missing
+
# Boot media improperly built (PXE, boot.iso, DVD, efidisk.img)
** Installer doesn't work
+
# Installer fails to boot as a KVM guest
* Repo
+
# Installer fails to boot as a XEN guest
** Metadata is missing
 
** Package/file conflicts
 
** Dependency problems
 
* Functional
 
** Major bugs with packages in the "Critical Path" (see [[Critical Path Packages Proposal]])
 
  
When Rawhide is broken it's much harder for people to become Rawhide testers, harder for developers to get fixes into the hands of testers, and other such badness.
+
'''Install Source'''
 +
# Unable to detect install.img media
 +
# Unable to transition to stage#2 installer
  
=== Proposed Solution ===
+
'''Kickstart Delivery'''
<!-- Describe proposed solution in detail -->
+
# Ks.cfg could not be obtained from specified location (http, ftp, nfs, hd, initrd)
 +
# Install fails to proceed in accordance with the directives in the ks.cfg file
 +
# Install improperly sets up networking based on command-line and kickstart network parameters (boot with <code>ksdevice=eth1</code>, {{filename|ks.cfg}} contains <code>eth2</code>)
 +
 
 +
'''User Interface'''
 +
# X driver problems while transitioning to graphical install
 +
# Screen corruption during text-mode install
 +
# VNC fails to start
 +
# Serial console redirection improperly setup
 +
 
 +
'''Storage Devices'''
 +
# Fail to detect existing storage device(s)
 +
# Failure to clear stale data off of existing devices
 +
# Unable to add iSCSI volumes
 +
 
 +
'''Partitioning'''
 +
# Failure detecting existing partition scheme (lvm, mdraid, dmraid, luks)
 +
# Failure when attempting to resize existing partitions
 +
# Failures while attempting to re-use existing partitions
 +
# Improperly clearing stale information from disks
 +
# Unable to consistently resize an existing filesystem
 +
# General failures while attempting to manually partition a system
 +
 
 +
'''Package Repository'''
 +
# Unable to read metadata from package repositories (http, ftp, nfs, media)
 +
# Failures while adding or modifying existing package repositories
  
First, we should create test cases for each of the types of breakage described previously. These should be automated or scripted when possible.
+
'''Package Set'''
 +
# Network timeout while retrieving packages
 +
# Dependency problems while resolving package list
 +
# File conflicts during package install
 +
# Package order and install errors in {{filename|install.log}}
 +
# Improperly formatted {{filename|comps.xml}} data
  
These tests should be run regularly (daily if possible) by QA team members and other interested parties. The results should be submitted and displayed prominently on a public website. Kyle McMartin registered [http://israwhidebroken.com/ israwhidebroken.com] for this purpose.
+
'''Boot loader configuration'''
 +
# Unable to properly detect other operating systems
 +
# Failure while setting up chainloader for another OS
  
Second: currently we keep copies of several weeks' worth of daily Rawhide trees in the Koji build system. When a tree is deemed good (i.e. when it passes all the tests) someone from QA should file a ticket with rel-eng to create a "known-good" symlink for that rawhide tree. This link should be public and well-known. Someone suggested the name "chewtoy" for this known-good Rawhide.
+
'''Upgrade system'''
 +
# Failure to detect previously installed systems
 +
# Errors while attempting to update bootloader configuration during upgrade
 +
# Package upgrade errors in {{filename|upgrade.log}}
  
=== Scope ===
+
'''Recovery'''
<!-- Describe the scope of any project work or properties that will be affected by the proposal -->
+
# Rescue mode fails to detect existing installations (lvm, raid, luks)
 +
# Rescue mode fails to establish networking
 +
# Problems saving traceback information (local disk, bugzilla, remote server)
 +
# Anaconda unable to download and use updates.img (from install source, local media or URL)
 +
# Unable to transition to debug mode
  
* QA Team members (i.e. testers) will ''need'' to do regular (daily) testing
+
== Proposed Solution ==
* rel-eng will need to move the symlink when requested
+
<!-- Describe proposed solution in detail -->
 +
The project will be developed based on the AutoQA framework and use the virtualization environment (libvirt,kvm-qemu). The installation automation will be deployed by the Fedora kickstart installation. virt-install will be used to create the guest.virtio is used to get the anaconda logs. The details can be found at [[Is anaconda broken  solution]]
  
=== Active Ingredients ===
+
== Active Ingredients ==
 
<!-- A list of any prerequisites or other materials needed to implement the solution -->
 
<!-- A list of any prerequisites or other materials needed to implement the solution -->
  
* Define requirements for Good vs. Broken
+
* AutoQA must be packaged and available in Fedora infrastructure
* Write test cases to check each requirement
+
* A valid backend test harness is packaged and available in Fedora infrastructure ([[Autotest]] currently being used by [[AutoQA]])
* Automate test cases wherever possible
+
* Knowledge of TurboGears or TurboGears2
* Set up a system (webapp?) to allow testers to submit results for tests that can't be automated
+
* A new [[AutoQA]] test watcher may be required to initiate automated tests whenever CD and DVD ISO images are available for testing (''post-iso-build'')
* Public website that shows results of daily rawhide testing
+
* Adding installer unit test execution and results display is dependent on the availability and environmental requirements of installer unit tests
* Set up a known-good rawhide ("chewtoy") link based on those test results
+
 
* Publicize a link to the "chewtoy" known-good tree
 
* Hosting for [http://israwhidebroken.com/ israwhidebroken.com] - or a redirect.
 
  
=== Roadmap ===
 
  
See https://fedorahosted.org/autoqa/milestone/israwhidebroken.com
+
== Roadmap ==
 +
* Roadmap for development of auto install at:[[Is_anaconda_broken_roadmap]]
 +
* Status for test plan/documentation changes can be seen in the [https://fedorahosted.org/fedora-qa/query?status=new&status=assigned&status=reopened&status=closed&group=status&component=Test+Review&milestone=Fedora+13&order=priority fedora-qa trac system]
 +
* Status for test automation efforts is available in the [https://fedorahosted.org/autoqa/milestone/Automate%20installation%20test%20plan autoqa TRAC system]
  
 
== Results ==
 
== Results ==
 
+
* Meeting information and logs can be found at [[Is_anaconda_broken_meeting]]
* [[QA:Rawhide Acceptance Test Plan]] is used to define Good vs. Broken.
 
* 12 test cases identified in that test plan are listed here: [[:Category:Rawhide Acceptance Test Cases]]
 
* 8 of those test cases have been automated for use with [http://autotest.kernel.org/ autotest]
 
** code: [https://fedorahosted.org/autoqa/browser/rawhide_acceptance https://fedorahosted.org/autoqa/browser/rawhide_acceptance]
 
  
 
== Discussion Points ==
 
== Discussion Points ==
<!-- Describe things which should be discussed regarding the proposal.  Specifics that need narrowing down, or contentions parts of the proposal. -->
+
* List unresolved or active discussion
 
 
Need to list requirements / solicit mockups for the webapp.
 
  
 
== Comments? ==
 
== Comments? ==
Line 68: Line 119:
  
 
== Owner ==
 
== Owner ==
[[User:wwoods]]
+
Fedora QA team
[[User:jlaska]]
+
 
 +
== References ==
 +
<references/>
 +
Other documentation:
 +
# General libvirt home - http://libvirt.org
 +
# Examples on using libvirt and cobbler to aid in semi-automated install testing - http://jlaska.livejournal.com/tag/cobbler
 +
# [[Autotest|General Autotest information]]
 +
# [http://www.linux-kvm.org/page/KVM-Autotestlinux|How KVM is using autotest]
 +
# GUI automation using dogtail - https://fedorahosted.org/dogtail
 +
# GUI automation using autotest step files - http://www.linux-kvm.org/page/KVM-Autotest/Steps
  
 
[[Category:Proposals]]
 
[[Category:Proposals]]
 
[[Category:FAD]]
 
[[Category:FAD]]

Latest revision as of 08:51, 16 November 2011

QA.png


Overview

The purpose of AutoQA installation test automation is to simplify testing and improve test efficiency. The AutoQA install test project should address the following problems:

  • The system should be easy to allow for tester and developer use
  • Have clear documentation for customizing and creating new tests
  • Support test execution using existing Fedora infrastructure services, but not require them
  • Test results are easy to verify

Scope

The Fedora installation test automation project covers the whole installation from retrieving installation media to first boot. Details are below:

  1. retrieve installation media
  2. Installation media sanity check
  3. Install with different system specifications, installation sources and partition etc.
  4. get the installation output and logs.

Problem Space

The Fedora installer is a complicated software application that often requires significant setup time to properly and efficiently test. Installer failures typically come from the following areas:

Image Sanity

  1. ISO file size is too large
  2. Invalid SHA256 checksum
  3. Invalid implanted ISO md5sum
  4. Install environment - anaconda has specific application, library and config file format requirements.
  5. Versions check

Boot Methods

  1. Boot media improperly built (PXE, boot.iso, DVD, efidisk.img)
  2. Installer fails to boot as a KVM guest
  3. Installer fails to boot as a XEN guest

Install Source

  1. Unable to detect install.img media
  2. Unable to transition to stage#2 installer

Kickstart Delivery

  1. Ks.cfg could not be obtained from specified location (http, ftp, nfs, hd, initrd)
  2. Install fails to proceed in accordance with the directives in the ks.cfg file
  3. Install improperly sets up networking based on command-line and kickstart network parameters (boot with ksdevice=eth1, ks.cfg contains eth2)

User Interface

  1. X driver problems while transitioning to graphical install
  2. Screen corruption during text-mode install
  3. VNC fails to start
  4. Serial console redirection improperly setup

Storage Devices

  1. Fail to detect existing storage device(s)
  2. Failure to clear stale data off of existing devices
  3. Unable to add iSCSI volumes

Partitioning

  1. Failure detecting existing partition scheme (lvm, mdraid, dmraid, luks)
  2. Failure when attempting to resize existing partitions
  3. Failures while attempting to re-use existing partitions
  4. Improperly clearing stale information from disks
  5. Unable to consistently resize an existing filesystem
  6. General failures while attempting to manually partition a system

Package Repository

  1. Unable to read metadata from package repositories (http, ftp, nfs, media)
  2. Failures while adding or modifying existing package repositories

Package Set

  1. Network timeout while retrieving packages
  2. Dependency problems while resolving package list
  3. File conflicts during package install
  4. Package order and install errors in install.log
  5. Improperly formatted comps.xml data

Boot loader configuration

  1. Unable to properly detect other operating systems
  2. Failure while setting up chainloader for another OS

Upgrade system

  1. Failure to detect previously installed systems
  2. Errors while attempting to update bootloader configuration during upgrade
  3. Package upgrade errors in upgrade.log

Recovery

  1. Rescue mode fails to detect existing installations (lvm, raid, luks)
  2. Rescue mode fails to establish networking
  3. Problems saving traceback information (local disk, bugzilla, remote server)
  4. Anaconda unable to download and use updates.img (from install source, local media or URL)
  5. Unable to transition to debug mode

Proposed Solution

The project will be developed based on the AutoQA framework and use the virtualization environment (libvirt,kvm-qemu). The installation automation will be deployed by the Fedora kickstart installation. virt-install will be used to create the guest.virtio is used to get the anaconda logs. The details can be found at Is anaconda broken solution

Active Ingredients

  • AutoQA must be packaged and available in Fedora infrastructure
  • A valid backend test harness is packaged and available in Fedora infrastructure (Autotest currently being used by AutoQA)
  • Knowledge of TurboGears or TurboGears2
  • A new AutoQA test watcher may be required to initiate automated tests whenever CD and DVD ISO images are available for testing (post-iso-build)
  • Adding installer unit test execution and results display is dependent on the availability and environmental requirements of installer unit tests


Roadmap

Results

Discussion Points

  • List unresolved or active discussion

Comments?

To leave a comment, use the Talk page for this proposal.

Owner

Fedora QA team

References

Other documentation:

  1. General libvirt home - http://libvirt.org
  2. Examples on using libvirt and cobbler to aid in semi-automated install testing - http://jlaska.livejournal.com/tag/cobbler
  3. General Autotest information
  4. KVM is using autotest
  5. GUI automation using dogtail - https://fedorahosted.org/dogtail
  6. GUI automation using autotest step files - http://www.linux-kvm.org/page/KVM-Autotest/Steps