= Fedora Quality Assurance =
= Fedora Quality Assurance =
Fedora is a rapidly progressing distribution and collection of Free software. We have detailed quality assurance procedures to help maintain a robust platform.
== What is QA, anyway? ==
It's short for Quality Assurance. In general, software QA involves monitoring every stage of the software development process to ensure quality.
The Fedora QA team helps hunt down bugs in Fedora. We work with the Fedora developers, release engineers, and community members at every stage of the Fedora lifecycle to help prevent bugs from getting into the software, and to help find and fix the bugs that slip through the cracks.
four major tasks that the QA Team performs: Bug Triage, Update Testing, Release Testing, and Tool Development.
There are tasks , and .
want to join the Fedora QA Team, you should consider getting an account in the Fedora Account System. See below for more info!
If youto Fedora QA , Fedora .
How Can I Help? ==
=== Update Testing ===
This is the process of testing newly-built updates for the stable releases, in order to catch incomplete fixes and regressions and other nastiness. All you need to do to start getting test updates is enable the 'fedora-updates-testing' repository.
for and .
New updates are listed in the Bodhi tool at http:// bodhi. fedoraproject. org/. The QA team tests the new updates and adds comments about whether they work or not. The better- tested an update is , the sooner it can be released.
..-is the .
(Note that you currently need a Fedora Account to log in to Bodhi.)
See [[to use ]] if the IRC ', you more information.
<!-- TODO: further information at QA/UpdateTesting -->
=== Bug Triaging ===
Bug Triage is the art of filtering new bug reports in Bugzilla to make sure they get to the right people. We hope to start training sessions to help new folks get involved soon (February 2008).
All you need to help with bug triage is a good eye for detail and some account sign-ups. More information about bug triage is at the [[BugZappers]] page.
=== Release Testing ===
Release Testing is the process of testing [[Releases/Rawhide| Rawhide]] - that's the codename we give to the next release before it gets a ''real'' name.
Release Testing has two key tasks: 1) testing installation and upgrades, and 2) testing new features in the release and making sure key applications behave as expected. This testing helps decide which features will make it into the release, and what bugs will block the release.
Test plans for alpha, beta, and final releases will be maintained and improved by the QA team. Current info:
* [[:Category:Fedora 10 Test Results]]
* [[QA:Fedora 11 Alpha Install Test Results]]
The QA team also works with developers and release engineers to maintain the [[QA/ReleaseCriteria| ReleaseCriteria]] , which is used to determine what bugs count as release blockers.
Release testing is exciting work - you get to play with new Fedora releases before they're finished! Ideally you should have a spare computer to test installations on. You should definitely join the fedora-test-list mailing list - that's where other people running Rawhide gather to talk about what's working and what isn't.
You can be a big help by testing bugs that the Fedora developers have tagged as needing to be tested. This is where a fix is believed to exist, however confirmation is desired by independent testers. The list of bugs is [http://tinyurl.com/22jyrc here.] An RSS feed is also available at http://feeds.feedburner.com/NeedsRetesting
=== Information for Testers ===
Testing]] for how to get set up and how to use the mailing list.
See [[BugsAndFeatureRequests]] for information on how to use Bugzilla effectively.
=== Tool Development ===
The QA Team also develops tools to make testing easier and more reliable. Some example tools are [https://fedorahosted.org/snake/ SNAKE] and [https://fedorahosted.org/python-bugzilla/ python-bugzilla] . We're also involved in development of [https://fedorahosted.org/bodhi/ Bodhi] and improvements to [https://bugzilla.redhat.com/ Bugzilla] .
There are some very interesting plans for QA tools - [[QA/Beaker]] is an idea for a fully automated test lab. Developing Open Source QA tools is complex, challenging stuff at the cutting edge of the field. Contact [[WillWoods|Will]] if you're up to the challenge of building new tools for Fedora QA.
== How Do I Join? ==
=== Join the Mailing List ===
Join the [https://www.redhat.com/mailman/listinfo/fedora-test-list email@example.com] email list -- QA meetings, agendas and summaries are posted to this list regularly. If you have questions about QA and testing, this is the place to ask.
=== Join the QA discussions and meetings ===
Fedora testers and developers can be found on the Freenode Internet Relay Chat (IRC) network. See [[Communicate#IRC|this page]] for more information about IRC and Fedora.
Join #fedora-qa for discussions and #fedora-meeting for weekly IRC meetings. The QA meeting is usually ' ''Wednesdays at 1500UTC''' - check the [[Fedora meeting channel]] page for more details about the use of #fedora-meeting, and watch fedora-test-list for meeting agendas and summaries.
=== Get a Fedora Account ===
Create an account in the [[Infrastructure/AccountSystem| Fedora Account System]] :
# Visit the account system home: https://admin.fedoraproject.org/accounts/
# Click on 'Apply for a new account' and fill in the blanks.
# After you create your account, request an email with instructions to sign the [[Legal/Licenses/CLA | Contributor License Agreement]] (CLA): https://admin.fedoraproject.org/accounts/send-cla.cgi
# Request membership in the 'fedorabugs' group in the account system.
=== Create a Bugzilla Account ===
Make sure you have an account in [http://bugzilla.redhat.com/ Bugzilla] .
The email address that you use for your bugzilla account should be the same email address as you use for all things related to Fedora QA.
=== Join the Wiki ===
You can add your name to the [[QA/Contributors| QA contributor list]]. See [[Help:Editing]] for more information about the wiki.
== Further Info and Links ==
* [https://fedorahosted. org/fedora-qa/report/1 QA Trac]
* [[:Category:Test Cases]]
* [[:Category:Test Plans]]
* [[:Category:Fonts_and_text_QA|Fonts and text quality assurance]]
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.
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.