From Fedora Project Wiki

(Overview)
(=Proposed Solution)
Line 15: Line 15:
  
  
===Proposed Solution ==
+
==Proposed Solution ==
 
<!-- Describe proposed solution in detail -->
 
<!-- Describe proposed solution in detail -->
  
Line 24: Line 24:
  
  
=== Scope ===
+
== Scope ==
 
<!-- Describe the scope of any project work or properties that will be affected by the proposal -->
 
<!-- Describe the scope of any project work or properties that will be affected by the proposal -->
  
* QA Team members (i.e. testers) will ''need'' to do regular (daily) testing  
+
* Any testers from community can install the testing system and run test cases
* rel-eng will need to move the symlink when requested
+
* After finish testing,testers will post test result to specified wiki
  
=== 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
+
* develop a system to run install system
* Write test cases to check each requirement
+
* convert some of the current install test cases to cases which can be run in auto test system
* Automate test cases wherever possible
+
* Provide a test results presentation layer for manual test result submission
* Set up a system (webapp?) to allow testers to submit results for tests that can't be automated
 
* Public website that shows results of daily rawhide testing
 
* 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 ==
 +
your comments
  
 
== Results ==
 
== Results ==

Revision as of 03:18, 4 November 2009


Overview

provide small auto-test system with a web-based interface which can help to customize autoinstall testing.The test system should be small enough for personal use.

Problem Space

The purpose of auto test is to simplify testing,save time, improve efficiency.So the auto-test should help us to solve the following problems:

  • the system should be small enough for personal use
  • have a very simple interface for user to customize testing or configure testing
  • very easy interface for user to setup some services
  • test result is easy to check


Proposed Solution

  • use the network install to finish install tests one by one.
  • provide web-based interface to customize testing.In the web page,user can specify the path of ISO,select which cases to run or not,edit(import) kickstart file or automaticly generate kickstart file after give some selected parameters (partition,packages,install method).
  • web-based interface help to setup some needed services due to some special cases. Modify,add or delete test cases,
  • Test result display page help to check the test result easily


Scope

  • Any testers from community can install the testing system and run test cases
  • After finish testing,testers will post test result to specified wiki

Active Ingredients

  • develop a system to run install system
  • convert some of the current install test cases to cases which can be run in auto test system
  • Provide a test results presentation layer for manual test result submission


Roadmap

your comments

Results

Discussion Points

Need to list requirements / solicit mockups for the webapp.

Comments?

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

Owner

User:wwoods User:jlaska