From Fedora Project Wiki
No edit summary
m (internal link cleaning)
 
(9 intermediate revisions by 2 users not shown)
Line 7: Line 7:
I added a TOC so that we can see what's there easily.
I added a TOC so that we can see what's there easily.


__NOTOC__ -->
--> __NOTOC__


= Welcome!=
= Welcome!=
Line 13: Line 13:
This page outlines all the activities you can get involved in to help with [[QA|Fedora QA]] and is meant to guide you through the QA ecosystem. It's easy to get involved and we love to welcome people to the group! The first thing you probably want to do is get plugged in to all the right sources of information for Fedora QA.  
This page outlines all the activities you can get involved in to help with [[QA|Fedora QA]] and is meant to guide you through the QA ecosystem. It's easy to get involved and we love to welcome people to the group! The first thing you probably want to do is get plugged in to all the right sources of information for Fedora QA.  


At the very least, it involves these three things:
At the very least, it involves these four things:
* Create a [[Account_System?rd=FAS|FAS Account]] and join the FAS QA Group
* Subscribe to the {{fplist|test}} mailing list
* Subscribe to the {{fplist|test}} mailing list
* Join the {{fpchat|#fedora-qa}} IRC channel on Freenode
* Join the {{fpchat|#fedora-qa}} IRC channel on Freenode
Line 20: Line 21:
= What are you looking to do? =
= What are you looking to do? =


Whether you are looking to test a [http://fedoraproject.org/wiki/Releases?rd=Releases/ stable release], new packages from [http://fedoraproject.org/wiki/QA:Updates_Testing updates-testing], or the bleeding edge [http://fedoraproject.org/wiki/Releases/Rawhide Rawhide], QA has a way for you to contribute and get involved! We need people who like to push all the buttons, use all the command line options, verify all the documentation, review things for usability, and suggest future features - especially for anything that's undergone major changes recently. <!-- it would be great to have a link for anything that has undergone changes. This could be bodhi or something, I hesititate to make or request another tracking tool - unless we need a consolidated change tracker -->
Whether you are looking to test a [[Releases?rd=Releases/|stable release]], new packages from [[QA:Updates_Testing|updates-testing]], or the bleeding edge [[Releases/Rawhide|Rawhide]], QA has a way for you to contribute and get involved! We need people who like to push all the buttons, use all the command line options, verify all the documentation, review things for usability, and suggest future features - especially for anything that's undergone major changes recently. <!-- it would be great to have a link for anything that has undergone changes. This could be bodhi or something, I hesititate to make or request another tracking tool - unless we need a consolidated change tracker -->


If you want to:
'''If you want to:'''
* Triage Bugs
* Triage Bugs
** Read this [https://fedoraproject.org/wiki/BugZappers/Joining Guide]
** Read [[#triage | this]]
* Work on an upcoming stable release
* Work on an upcoming stable release
** Read this --> [[#release-validation|Release Validation Testing]]
** [[#release-validation|Release Validation Testing]]
** And this --> [https://fedoraproject.org/wiki/Bodhi#How_to_help_test_important_updates_using_Bodhi Bodhi Testing]
** [[Bodhi#How_to_help_test_important_updates_using_Bodhi|Bodhi Testing]]
* Work on testing new packages
* Work on testing new packages
** Read this --> [https://fedoraproject.org/wiki/Bodhi#How_to_help_test_important_updates_using_Bodhi Bodhi] and [https://fedoraproject.org/wiki/QA:Updates_Testing#What_to_test.2C_testing.2C_and_reporting_results Updates Testing]
** [[Bodhi#How_to_help_test_important_updates_using_Bodhi|Bodhi]] and [[QA:Updates_Testing#What_to_test.2C_testing.2C_and_reporting_results|Updates Testing]]
** [https://fedoraproject.org/wiki/Fedora_Easy_Karma Fedora Easy karma]
** [[Fedora_Easy_Karma|Fedora Easy karma]]
** [https://fedoraproject.org/wiki/Fedora_Gooey_Karma Fedora Gooey Karma]
** [[Fedora_Gooey_Karma|Fedora Gooey Karma]]
* Work on Rawhide
* Work on Rawhide
** All of the above
** All of the above
'''I want to do something else!'''
* [[#test-days | Join a Test Day]]
* [[#create-testcases | Create Test Cases]]
* [[#develop-tools | Develop Tools]]


For all of those tasks, it would be good to have some familiarity with our Bugzilla instance. A lot of contribution to Fedora QA comes through bug reports. All you need is a [http://bugzilla.redhat.com Bugzilla] account: [https://bugzilla.redhat.com/createaccount.cgi create your account]. Our [[BugsAndFeatureRequests| bug reporting practices]] provide some good background for filing bugs. If you want to discuss the bugs before reporting, QA members can be found on the {{fplist|test}} mailing list and the {{fpchat|#fedora-qa}} IRC channel.  
For all of those tasks, it would be good to have some familiarity with our Bugzilla instance. A lot of contribution to Fedora QA comes through bug reports. All you need is a [http://bugzilla.redhat.com Bugzilla] account: [https://bugzilla.redhat.com/createaccount.cgi create your account]. Our [[BugsAndFeatureRequests| bug reporting practices]] provide some good background for filing bugs. If you want to discuss the bugs before reporting, QA members can be found on the {{fplist|test}} mailing list and the {{fpchat|#fedora-qa}} IRC channel.  


= Specifics =
{{Anchor|self-introduction}}
== Introduce yourself and join the team! ==
Before getting stuck in, why not introduce yourself? It's not compulsory, but we like to say "hi!" to new members. Just subscribe to the {{fplist|test}} mailing list and send a mail with a topic like "Self-introduction: (Your Name)". Just say that you're interested in helping with QA, include your IRC nickname if you have one, and, if you like, include some information on your Fedora / Linux background. Here's an [http://www.redhat.com/archives/fedora-test-list/2009-March/msg00671.html example mail].
{{Anchor|triage}}
== Triaging and managing bugs ==
== Triaging and managing bugs ==


Once bugs are reported, QA should make sure they are addressed by the right people and don't get stuck in the process. The [[BugZappers]] group was responsible for triaging bugs - ensuring they are complete and accurate reports, and assigning them to the right developers. That group is currently inactive, but we would welcome someone with the enthusiasm to rejuvenate the bug triage process under the QA banner.
Once bugs are reported, QA should make sure they are addressed by the right people and don't get stuck in the process.  


== Testing official updates before they are released ==
=== What is Involved in Bug Triaging? ===


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]] for instructions on how to test and report issues with these updates.
Bug triagers make sure that:


== Release validation ==
* Bug reports have the information developers need to reproduce and fix them.
* Bugs are assigned to the right component and version.
* Duplicate bugs are found and labelled.
* Feature requests reported as bugs are properly reported.
* Bugs already fixed are closed.


The QA group co-ordinates planned testing of the installation process and basic functionality before each Fedora release and pre-release is made, to ensure they reach certain standards known as the [[Fedora_Release_Criteria]]. See the [[QA:Installation_validation_testing|installation validation testing]] and [[QA:Desktop_validation_testing|desktop validation testing]] pages for more information on these processes and how you can contribute to them. Also look out for mails to the list that announce 'TC' and 'RC' builds for testing - these mails contain instructions.
The [https://admin.fedoraproject.org/mailman/listinfo/test mailing list] is a great place to raise any questions or problems you are having. Experienced QA Members are more than happy to act as mentors for new members to help them get started with QA. Triaging bugs does '''not''' mean that you have to understand the bugs and solve them yourself. It simply means you should be able to look at new bugs, and report if they are duplicates, if more information is needed, or if it is filed under the wrong component.


== Testing Fedora pre-releases ==
There is no requirement of programming knowledge. However, being familiar with Fedora and Linux in general will be extremely useful. A more complete guide is [[User:Roshi/QA/Triage|here]]. <!-- This could also just point to the mailing list or irc, but I figured they would just get pointed back to this -->


Before an official Fedora release comes out, Alpha and Beta builds - 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. If you keep running the pre-release and installing updates regularly, you can also help test the release as it is developed, and provide karma for candidate packages for the eventual release just as you can with candidate updates for stable releases - see [[#Testing official updates before they are released|the earlier section]]. For information on getting and installing pre-releases, see [http://fedoraproject.org/get-prerelease this page]. Report any issues you find to [http://bugzilla.redhat.com Bugzilla], following the instructions at [[BugsAndFeatureRequests]].
{{Anchor|updates}}
== Testing official package updates before they are released ==


== Testing Rawhide ==
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]] for instructions on how to test and report issues with these updates.


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 [[Releases/Rawhide|Rawhide]] page for instructions on how to install or upgrade to, and test. You can test Rawhide without ever needing to install it by using the [http://alt.fedoraproject.org/pub/alt/nightly-composes/ nightly live builds].
== Testing Fedora pre-releases ==


== Creating test cases ==
Before an official Fedora release comes out, Alpha and Beta builds - 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. If you continuously run the pre-release and update regularly you can also provide karma to update candidates - effectively doubling the number of things you can test. Check out the [[#updates|updates]] section for more information. For information on getting and installing pre-releases, see [http://fedoraproject.org/get-prerelease this page]. Report any issues you find to [http://bugzilla.redhat.com Bugzilla] - complete instructions are here: [[BugsAndFeatureRequests]].


As well as simply keeping a look out for problems, the QA group develops structured test cases and test plans. See the [[:Category:Test Cases]] and [[:Category:Test Plans]] pages for information on the test cases currently available. The [[QA:SOP_test_case_creation|test case creation process]] will tell you how to create test cases.
{{Anchor|release-validation}}
== Release validation ==


== Developing tools ==
The QA group co-ordinates planned testing of the installation process and basic functionality before each Fedora release and pre-release is made, to ensure they reach certain standards known as the [[Fedora_Release_Criteria]]. See the [[QA:Installation_validation_testing|installation validation testing]] and [[QA:Desktop_validation_testing|desktop validation testing]] pages for more information on these processes and how you can contribute to them. Also look out for mails to the list that announce 'TC' and 'RC' builds for testing - these mails contain instructions.


Some members of the Fedora QA team are involved in developing and maintaining tools to help make testing more efficient. Some of the tools we wrote that are already in use (but under constant development!) include [[AutoQA]], [https://fedorahosted.org/python-bugzilla/ python-bugzilla] and the [http://qa.fedoraproject.org/blockerbugs/ blocker bug tracking web app]. We also use [https://fedorahosted.org/bodhi/ Bodhi], [https://bugzilla.redhat.com/ Bugzilla] and [[Fedora Easy Karma|fedora-easy-karma]]. Tool development is a great way to apply engineering skills to QA.  Contact [[User:Tflink|Tim Flink]] if you'd like to get involved with building tools for Fedora QA.
{{Anchor|testing-rawhide}}
== Testing Rawhide ==


= Details =
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 [[Releases/Rawhide|Rawhide]] page for instructions on how to install or upgrade to, and test. You can test Rawhide without ever needing to install it by using the [http://alt.fedoraproject.org/pub/alt/nightly-composes/ nightly live builds].


{{Anchor|self-introduction}}
{{Anchor|test-days}}
== Introduce yourself and join the team! ==
== Joining Test Days ==


Before getting stuck in, why not introduce yourself? It's not compulsory, but we like to say "hi!" to new members. Just subscribe to the {{fplist|test}} mailing list and send a mail with a topic like "Self-introduction: (Your Name)". Just say that you're interested in helping with QA, include your IRC nickname if you have one, and, if you like, include some information on your Fedora / Linux background. Here's an [http://www.redhat.com/archives/fedora-test-list/2009-March/msg00671.html example mail].
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 [[QA/Test_Days|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.


== Reporting bugs in Fedora releases ==
{{Anchor|create-testcases}}
== Creating test cases ==


Many people are already involved in Fedora QA, just by reporting problems as you do your regular tasks on Fedora. All you need is a [http://bugzilla.redhat.com Bugzilla] account: [https://bugzilla.redhat.com/createaccount.cgi create your account]. Reporting Fedora bugs as you come across them is a big contribution! We provide some suggestions on [[BugsAndFeatureRequests|reporting bugs]]. If you want to discuss the bugs before reporting them, we can be found on the {{fplist|test}} mailing list and the {{fpchat|#fedora-qa}} IRC channel.
As well as simply keeping a look out for problems, the QA group develops structured test cases and test plans. See the [[:Category:Test Cases]] and [[:Category:Test Plans]] pages for information on the test cases currently available. The [[QA:SOP_test_case_creation|test case creation process]] will tell you how to create test cases.


== Joining Test Days ==
{{Anchor|develop-tools}}
== Developing tools ==


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 [[QA/Test_Days|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.
Some members of the Fedora QA team are involved in developing and maintaining tools to help make testing more efficient. Some of the tools we wrote that are already in use (but under constant development!) include [[AutoQA]], [https://fedorahosted.org/python-bugzilla/ python-bugzilla] and the [http://qa.fedoraproject.org/blockerbugs/ blocker bug tracking web app]. We also use [https://fedorahosted.org/bodhi/ Bodhi], [https://bugzilla.redhat.com/ Bugzilla] and [[Fedora Easy Karma|fedora-easy-karma]]. Tool development is a great way to apply engineering skills to QA.  Drop by the {{fpchat|#fedora-qa}} IRC Channel or the {{fplist|qa-devel}} mailing list if you want to get involved building tools.

Latest revision as of 06:07, 20 September 2016

QA.png



Welcome!

This page outlines all the activities you can get involved in to help with Fedora QA and is meant to guide you through the QA ecosystem. It's easy to get involved and we love to welcome people to the group! The first thing you probably want to do is get plugged in to all the right sources of information for Fedora QA.

At the very least, it involves these four things:

What are you looking to do?

Whether you are looking to test a stable release, new packages from updates-testing, or the bleeding edge Rawhide, QA has a way for you to contribute and get involved! We need people who like to push all the buttons, use all the command line options, verify all the documentation, review things for usability, and suggest future features - especially for anything that's undergone major changes recently.

If you want to:

I want to do something else!

For all of those tasks, it would be good to have some familiarity with our Bugzilla instance. A lot of contribution to Fedora QA comes through bug reports. All you need is a Bugzilla account: create your account. Our bug reporting practices provide some good background for filing bugs. If you want to discuss the bugs before reporting, QA members can be found on the test mailing list and the #fedora-qa[?] IRC channel.

Specifics

Introduce yourself and join the team!

Before getting stuck in, why not introduce yourself? It's not compulsory, but we like to say "hi!" to new members. Just subscribe to the test mailing list and send a mail with a topic like "Self-introduction: (Your Name)". Just say that you're interested in helping with QA, include your IRC nickname if you have one, and, if you like, include some information on your Fedora / Linux background. Here's an example mail.

Triaging and managing bugs

Once bugs are reported, QA should make sure they are addressed by the right people and don't get stuck in the process.

What is Involved in Bug Triaging?

Bug triagers make sure that:

  • Bug reports have the information developers need to reproduce and fix them.
  • Bugs are assigned to the right component and version.
  • Duplicate bugs are found and labelled.
  • Feature requests reported as bugs are properly reported.
  • Bugs already fixed are closed.

The mailing list is a great place to raise any questions or problems you are having. Experienced QA Members are more than happy to act as mentors for new members to help them get started with QA. Triaging bugs does not mean that you have to understand the bugs and solve them yourself. It simply means you should be able to look at new bugs, and report if they are duplicates, if more information is needed, or if it is filed under the wrong component.

There is no requirement of programming knowledge. However, being familiar with Fedora and Linux in general will be extremely useful. A more complete guide is here.

Testing official package 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 QA:Updates Testing for instructions on how to test and report issues with these updates.

Testing Fedora pre-releases

Before an official Fedora release comes out, Alpha and Beta builds - 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. If you continuously run the pre-release and update regularly you can also provide karma to update candidates - effectively doubling the number of things you can test. Check out the updates section for more information. For information on getting and installing pre-releases, see this page. Report any issues you find to Bugzilla - complete instructions are here: BugsAndFeatureRequests.

Release validation

The QA group co-ordinates planned testing of the installation process and basic functionality before each Fedora release and pre-release is made, to ensure they reach certain standards known as the Fedora_Release_Criteria. See the installation validation testing and desktop validation testing pages for more information on these processes and how you can contribute to them. Also look out for mails to the list that announce 'TC' and 'RC' builds for testing - these mails contain instructions.

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 Rawhide page for instructions on how to install or upgrade to, and test. You can test Rawhide without ever needing to install it by using the nightly live builds.

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 Category:Test Cases and Category:Test Plans pages for information on the test cases currently available. The test case creation process will tell you how to create test cases.

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 we wrote that are already in use (but under constant development!) include AutoQA, python-bugzilla and the blocker bug tracking web app. We also use Bodhi, Bugzilla and fedora-easy-karma. Tool development is a great way to apply engineering skills to QA. Drop by the #fedora-qa[?] IRC Channel or the qa-devel mailing list if you want to get involved building tools.