QA

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(add a link to the test-announce mailing list)
(Get Involved)
Line 20: Line 20:
 
== Get Involved ==
 
== Get Involved ==
  
If you'd like to get involved with helping to make Fedora better, read the [[QA/Join|What can I do?]] page to find out how to join in with QA activities. There are tasks available for everyone, no matter how little or much time you have available and how experienced you are with Fedora.
+
We're always eager to have new contributors to the QA project, no matter your experience level. If you'd like to get involved with helping to make Fedora better, read the [[QA/Join|What can I do?]] page to find out how to join in with QA activities. There are tasks available for everyone, no matter how little or much time you have available and how experienced you are with Fedora.
  
 
If you'd like to get involved with Fedora but QA doesn't sound like the group for you, think about [http://fedoraproject.org/join-fedora joining another Fedora project] instead.
 
If you'd like to get involved with Fedora but QA doesn't sound like the group for you, think about [http://fedoraproject.org/join-fedora joining another Fedora project] instead.

Revision as of 20:56, 1 October 2009

Fedora Quality Assurance

QA.png


Welcome to the Fedora QA project page. Fedora QA is the project which covers all testing of the software that makes up Fedora. It's our goal to continually improve the quality of Fedora releases and updates.

Activities

The Quality Assurance project is engaged in the following activities:

  • Testing of software as it is released into Rawhide, updates-testing, or as it appears in a supported public release
  • Through the BugZappers group, acting as a bridge between users and developers that aids in fixing and closing bugs
  • Developing and executing test plans and test cases to test important functionality in a systematic way, usually with multiple cooperating testers
  • Developing and running tools which use automation to find potential bugs
  • Running test days to co-ordinate focused testing on a specific feature or component
  • Working with developers and release engineers to maintain the release criteria, which are used to determine what bugs should be fixed before a pre-release or final release of Fedora is made.

Pending and completed tasks are listed in Trac.

Get Involved

We're always eager to have new contributors to the QA project, no matter your experience level. If you'd like to get involved with helping to make Fedora better, read the What can I do? page to find out how to join in with QA activities. There are tasks available for everyone, no matter how little or much time you have available and how experienced you are with Fedora.

If you'd like to get involved with Fedora but QA doesn't sound like the group for you, think about joining another Fedora project instead.

Communicate

QA project meetings are held Mondays at 16.00 UTC in the fedora meeting channel on IRC. Everyone is welcome to come along, especially if you're thinking of getting involved with QA and would like to ask some questions first.

General info on QA meetings such as topics for future meetings and records from previous meetings can be found at QA/Meetings.

  • Attend QA meeting on IRC (if you join the channel at a different time, you'll find another group's meeting)
  • Talk to other QA members on our permanent IRC channel
  • fedora-test-list is the mailing list for the QA and BugZappers projects
  • test-announce is the mailing list for QA and BugZappers project announcements - if you want to stay up-to-date on QA and BugZappers events, subscribe!

See How to use IRC if the IRC links don't work, or if you need more information.