Anaconda/Features/StorageTesting

From FedoraProject

< Anaconda | Features(Difference between revisions)
Jump to: navigation, search
(Current status)
(Detailed Description)
Line 15: Line 15:
  
 
== Detailed Description ==
 
== Detailed Description ==
 +
 +
I have developed a test framework that can be hooked into autoqa and exercises the storage code external to the installer environment.  Tests can be chained together so that the output of one test (a set of disks) is the input of another test.  The entire framework runs under virtualization.  This set of features means tests can be run completely without user intervention (making it perfect to run weekly, nightly, at build time, or even commit time though that would be very slow), from a known preexisting disk state (making failures reproducible), and without damaging existing hardware.
 +
 +
The real strength of this framework is first that we can automate the entirety of the storage section of the release test matrix, and second that we can develop regression tests from bug reports given enough detail.  Making use of this strength requires writing a lot of tests, though.
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==

Revision as of 18:03, 18 January 2011

Contents

Finish storage testing frameworks and put to use

Summary

Finalize storage testing frameworks and integrate in to a continual test system as well as QE's larger testing frameworks.

Owner

Current status

  • Targeted release: Fedora 15
  • Last updated: 2011-01-18
  • Percentage of completion: 75%

Detailed Description

I have developed a test framework that can be hooked into autoqa and exercises the storage code external to the installer environment. Tests can be chained together so that the output of one test (a set of disks) is the input of another test. The entire framework runs under virtualization. This set of features means tests can be run completely without user intervention (making it perfect to run weekly, nightly, at build time, or even commit time though that would be very slow), from a known preexisting disk state (making failures reproducible), and without damaging existing hardware.

The real strength of this framework is first that we can automate the entirety of the storage section of the release test matrix, and second that we can develop regression tests from bug reports given enough detail. Making use of this strength requires writing a lot of tests, though.

Benefit to Fedora

Scope

Test Plan

User Experience

Dependencies

Contingency Plan

Documentation

Release Notes