From Fedora Project Wiki

(→‎Further Info and Links: major consolidation)
(→‎Communicate: add Tickets)
 
(47 intermediate revisions by 16 users not shown)
Line 1: Line 1:
 +
{{header|qa}}
 +
{{autolang|base=yes}}
 +
__NOTOC__
 +
 
= 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.
+
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.
 
 
 
 
 
 
== 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.
 
 
 
There are four major tasks that the QA Team performs: Bug Triage, Update Testing, Release Testing, and Tool Development.
 
 
 
If you want to join the Fedora QA Team, you should consider getting an account in the Fedora Account System. See below for more info!
 
 
 
== 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.
 
 
 
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.
 
 
 
(Note that you currently need a Fedora Account to log in to Bodhi.)
 
 
 
<!-- 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:
 
 
 
* [[QA/TestPlans]]
 
* [[: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 ===
 
 
 
See [[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] .
+
== Activities ==
  
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.
+
The Quality Assurance project is engaged in the following activities:
 +
* Testing of software as it is released into [[Releases/Rawhide|Rawhide]], [[Releases/Branched|Branched]] pre-releases, [[QA:Updates_Testing|updates-testing]], or as it appears in a supported public release
 +
* Testing all updates to [[Critical_Path_Packages_Proposal|critical path]] packages before they are accepted
 +
* Acting as a bridge between users and developers that aids in fixing and closing bugs
 +
* Developing and executing [[:Category:Test Plans|test plans]] and [[:Category:Test Cases|test cases]] to test important functionality in a systematic way, usually with multiple cooperating testers
 +
* Developing and running [[QA:Tools|tools]] which use automation to find potential bugs
 +
* Running [[QA/Test Days|test days]] to co-ordinate focused testing on a specific feature or component
 +
* Working with developers and [[ReleaseEngineering|release engineers]] to maintain the [[Fedora_Release_Criteria|release criteria]], which are used to determine what bugs should be fixed before a pre-release or final release of Fedora is made
 +
* Managing the release process along with the [[ReleaseEngineering]] team, including [[QA:SOP_compose_request|requesting candidate composes]], performing [[QA:Release_validation_test_plan|release validation]], and managing [[QA:SOP_blocker_bug_process|blocker]] and [[QA:SOP_freeze_exception_bug_process|freeze exception]] bugs
 +
* Working with the [[Fedora.next#Working_groups|Working Groups]] to plan to test for the Fedora Products
  
== How Do I Join? ==
+
Pending and completed tasks are listed in [https://pagure.io/fedora-qa/issues Pagure].
  
=== Join the Mailing List ===
+
== Get Involved ==
  
Join the [https://www.redhat.com/mailman/listinfo/fedora-test-list fedora-test-list@redhat.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.
+
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 every level of expertise and available spare time.
  
=== Join the QA discussions and meetings ===
+
=== Stay informed ===
  
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.
+
{{anchor|calendar}}
 +
You can follow important QA events by subscribing to the [https://apps.fedoraproject.org/calendar/QA/ QA calendar]. To do that, open your favorite calendar software (Google Calendar, Thunderbird, etc), choose to add a remote calendar using URL, and input <code><nowiki>https://apps.fedoraproject.org//calendar/ical/QA/</nowiki></code>. You should now see QA events in your calendar. (Note: Do not download the {{filename|.ical}} file from that URL and feed it to the calendar software, that would only show a static snapshot of our calendar).
  
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.
+
{{anchor|test-announce}}
 +
You are also advised to subscribe to the [https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org/ test-announce] mailing list. All our QA events and also important [[Releases/Branched|Fedora Branched]] composes nominated for testing are announced in there.
  
{{Anchor|GetAFedoraAccount}}
+
== Communicate ==
  
=== Get a Fedora Account ===
+
=== IRC ===
  
Create an account in the [[Infrastructure/AccountSystem|  Fedora Account System]] :
+
'''Our permanent QA channel''' is {{fpchat|#fedora-qa}}. You can connect any time and talk to QA members and anyone else interested in Fedora quality there.
  
# Visit the account system home: https://admin.fedoraproject.org/accounts/
+
'''QA meetings''' are held on Mondays at 16.00 UTC (or 15.00 UTC during daylight savings time, check our [[#calendar|calendar]] to see a precise time) in the [[Communicate/FedoraMeetingChannel|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 and records from previous meetings can be found at [[QA/Meetings]].
# 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 ===
+
If you need help with running an IRC client a connecting to our channels, see [[How to use IRC]].
  
Make sure you have an account in [http://bugzilla.redhat.com/ Bugzilla] .
+
=== Mailing lists ===
  
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.
+
* [https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/ test] is the main mailing list for the QA project
 +
* [https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org/ test-announce] is the mailing list for QA project announcements. This is a lower-traffic list if you want to keep up with important events but find the ''test@'' volume too high.
 +
* [https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org/ qa-devel] is the mailing list for QA tooling development
  
=== Join the Wiki ===
+
=== Tickets ===
  
You can add your name to the [[QA/Contributors| QA contributor list]].  See [[Help:Editing]] for more information about the wiki.
+
* [https://pagure.io/fedora-qa/issues fedora-qa] project on Pagure is the main place for general task management
 +
* [https://pagure.io/group/fedora-qa fedora-qa group] lists other projects we maintain on Pagure
  
== Further Info and Links ==
+
----
 +
If you'd like to get involved with Fedora but QA doesn't sound like the right group for you, think about [[Join|joining another Fedora project]] instead.
  
* [https://fedorahosted.org/fedora-qa/report/1 QA Trac]
 
* [[QA/Meetings]]
 
* [[QA/ReleaseCriteria]]
 
* [[:Category:Test Cases]]
 
* [[:Category:Test Plans]]
 
* [[:Category:Fonts_and_text_QA|Fonts and text quality assurance]]
 
  
[[Category:Quality assurance]]
+
[[Category:Fedora sub-projects]] [[Category:QA]]

Latest revision as of 10:44, 22 April 2020

QA.png


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.

Activities

The Quality Assurance project is engaged in the following activities:

Pending and completed tasks are listed in Pagure.

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 every level of expertise and available spare time.

Stay informed

You can follow important QA events by subscribing to the QA calendar. To do that, open your favorite calendar software (Google Calendar, Thunderbird, etc), choose to add a remote calendar using URL, and input https://apps.fedoraproject.org//calendar/ical/QA/. You should now see QA events in your calendar. (Note: Do not download the .ical file from that URL and feed it to the calendar software, that would only show a static snapshot of our calendar).

You are also advised to subscribe to the test-announce mailing list. All our QA events and also important Fedora Branched composes nominated for testing are announced in there.

Communicate

IRC

Our permanent QA channel is #fedora-qa[?]. You can connect any time and talk to QA members and anyone else interested in Fedora quality there.

QA meetings are held on Mondays at 16.00 UTC (or 15.00 UTC during daylight savings time, check our calendar to see a precise time) 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 and records from previous meetings can be found at QA/Meetings.

If you need help with running an IRC client a connecting to our channels, see How to use IRC.

Mailing lists

  • test is the main mailing list for the QA project
  • test-announce is the mailing list for QA project announcements. This is a lower-traffic list if you want to keep up with important events but find the test@ volume too high.
  • qa-devel is the mailing list for QA tooling development

Tickets

  • fedora-qa project on Pagure is the main place for general task management
  • fedora-qa group lists other projects we maintain on Pagure

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