Infrastructure/RFR/QA

Project Sponsor

Name: Will Woods

Wiki Name: WillWoods

Fedora Account Name: wwoods

Group: fedoraqa

Infrastructure Sponsor: Mike !McGrath

Secondary Contact info

Name: John Poelstra

Wiki Name: JohnPoelstra

Fedora Account Name: poelstra

Group: fedoraqa

Project Info

Project Name: QA

Target Audience: Testers and other folks who want to help improve the quality of Fedora

Expiration Date (required): We can re-evaluate in one year, so: January 18, 2008

Description/Summary: The ["QA"] project exists to help improve the stability and reliability of Fedora and Open Source software as a whole.

Project plan (Detailed):

(See FedoraTesting for an older writeup of the project plan / goals.)

Currently we have the following projects planned:

1. ["Beaker"] , an automated test system based on RHTS a. web-based test results a. XML-RPC (or similar) service to request test running 1. ["Testify2"] , a general test tracker web application a. Probably turbogears based a. Store test cases - individual things to test, either automatically or manually a. Build test plans - combine a bunch of test cases a. Track the execution of test plans against our various releases - "How much of F7Test1 has been tested?" a. Track the execution of test cases for updated packages 1. Bug Triage / Bugzilla RPG a. Keep track of people who close bugs, triage bugs, write test cases / test plans, etc. a. Pull info from Testify2, Beaker, Bugzilla, the wiki, etc. a. Award points for various tasks, track people's "score"

Goals:

The QA project exists to use and create Open Source software tests, testing tools, and test processes in order to make Fedora (and, by extension, all Open Source software) more awesome. We want to keep Bugzilla clean to help the developers focus on what's most important. We want to write documentation to help others test out Fedora. We want to keep track of what needs testing, what has been tested, and find new ways to make sure that Fedora is as robust and stable as it can be.

Specific resources needed

We need somewhere to put web-based test tools, test packages, and other related things. A fairly normal web-hosting environment with shell access would be perfect. Disk space required will be fairly small - currently I think our repo runs around 1MB. Including automated test results, new and better packages, etc. I anticipate that a year from now it will still be less than 10GB.