From Fedora Project Wiki

(→‎Communicate: advice on how to use the mailing list, adapted from Testing)
(drop the 'bugs must be reported to bugzilla' text, it doesn't belong here (i will add it in other appropriate places))
Line 35: Line 35:

See [[How to use IRC]] if the IRC links don't work, or if you need more information.
See [[How to use IRC]] if the IRC links don't work, or if you need more information.
'''Bugs need to be filed in [[BugsAndFeatureRequests|Bugzilla]]'''.  People on IRC and fedora-test-list can help you diagnose a bug, determine the scope of a bug (who else is seeing it), decide what component to file against, and know whether or not the behavior you see is intentional.  If a bug is reported on the mailing list and not Bugzilla, then the right developer might not see it, might lose the e-mail, or might forget about the report.  The Bugzilla database organizes reports so they are not lost, groups comments in one place for easy reference, and to make it easy to find reports so other testers don't make duplicate reports.
A common practice is to file a bug first, then e-mail the list with a link to the bug report, asking for further assistance.  Many bugs are also filed with no e-mail to the mailing list, so be sure to search Bugzilla for your problem.

Revision as of 19:03, 24 February 2009

Fedora Quality Assurance


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.


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

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.


QA project meetings are held Wednesdays at 1600 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.

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