User:Adamwill/Draft Join

From FedoraProject

< User:Adamwill(Difference between revisions)
Jump to: navigation, search
(Reporting bugs in Fedora releases)
(Triaging and managing bugs)
Line 12: Line 12:
 
Another easy way to contribute to Fedora QA is to help test official updates for stable Fedora releases before they're released. See [[QA/Updates_testing|this page]] for instructions on how to test and report issues with these updates.
 
Another easy way to contribute to Fedora QA is to help test official updates for stable Fedora releases before they're released. See [[QA/Updates_testing|this page]] for instructions on how to test and report issues with these updates.
  
== Triaging and managing bugs ==
+
== Triaging and Zapping bugs ==
  
Once bugs are reported, it's important to make sure they're addressed by the right people, and don't get stuck at some point in the process. The [[BugZappers]] group is responsible for triaging bugs (ensuring they are complete and accurate reports, and assigning them to the right developers) and shepherding them through the process from report to fix released. It's an important job, and easy to join in with. See the [[BugZappers/Joining|Joining Bugzappers]] page for details on how you can get involved with the BugZappers group.
+
Once bugs are reported, QA makes sure they are addressed by the right people and don't get stuck in the process. The [[BugZappers]] group is responsible for triaging bugs; ensuring they are complete and accurate reports, and assigning them to the right developers. Experienced BugZappers shepherd the issues through the process from report to fix released. It's a fun, important job. See the [[BugZappers/Joining|Joining Bugzappers]] page for membership details.
  
 
== Testing Fedora pre-releases ==
 
== Testing Fedora pre-releases ==

Revision as of 11:13, 11 February 2009

QA.png


Welcome! This page outlines all the activities you can get involved in to help with Fedora QA. It's easy to get involved and we'd love to welcome more people to the group, so pick one or more of the activities and jump right in. Please consider joining the fedora-test-list and/or the #fedora-qa IRC channel, so your voice can be heard within the Fedora QA community. You can also add your name to the QA contributor list.

Reporting bugs in Fedora releases

You can easily contribute to Fedora QA; just report any issues you find while doing your usual stuff. All you need is a Bugzilla account: create your account. Reporting Fedora bugs as you come across them is a big contribution! We provide some suggestions on reporting bugs . If you want to discuss the bugs before reporting them, our QA Team members are on the fedora-test-list mailing list and the #fedora-qa IRC Channel.

Testing official updates before they are released

Another easy way to contribute to Fedora QA is to help test official updates for stable Fedora releases before they're released. See this page for instructions on how to test and report issues with these updates.

Triaging and Zapping bugs

Once bugs are reported, QA makes sure they are addressed by the right people and don't get stuck in the process. The BugZappers group is responsible for triaging bugs; ensuring they are complete and accurate reports, and assigning them to the right developers. Experienced BugZappers shepherd the issues through the process from report to fix released. It's a fun, important job. See the Joining Bugzappers page for membership details.

Testing Fedora pre-releases

Before an official Fedora release comes out, several alpha, beta and release candidate releases - known collectively as pre-releases - are made available. You can contribute by installing these pre-releases and testing them, just as you would a stable release. For information on getting and installing pre-releases, see this page. Report any issues you find to Bugzilla, following the instructions here.

Testing Rawhide

Rawhide is the development version of Fedora. Running Rawhide isn't for everyone, but for moderately experienced users who have a spare test system available or can run it in a virtual machine, testing Rawhide is a great way to contribute to ensuring future releases will be high quality. See this page for instructions on how to install or upgrade to Rawhide, and this page for information on how best to test Rawhide.

Joining Test Days

The Fedora QA group holds regular Test Days, where we get together on IRC and test a specific aspect of Fedora, often with the involvement of a developer who works in that area. See the Test Days page for more information on when and where these are held, and how to join in or even schedule one of your own.

Creating test cases

As well as simply keeping a look out for problems, the QA group develops structured test cases and test plans. See the Test Case page for information on the test cases currently available, and how to get involved with creating new ones.

Developing tools

Some members of the Fedora QA team are involved in developing and maintaining tools to help make testing more efficient. Some of the tools already developed SNAKE and python-bugzilla, and we also use Bodhi and Bugzilla. Tools currently under development include Nitrate, a system for collecting test cases, and Beaker, an automated test lab system. Tool development is a great way to apply engineering skills to QA. Contact Will if you'd like to get involved with building tools for Fedora QA.