Latest revision as of 12:42, 18 January 2024

In other languages: English (en) español (es) italiano (it) 한국어 (ko) português (pt) português do Brasil (pt-br) 中文（中国大陆） (zh-cn) română (ro) русский (ru) [edit]

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:

Testing of software as it is released into Rawhide, Branched pre-releases, updates-testing, or as it appears in a supported public release
Testing all updates to 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 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
Managing the release process along with the ReleaseEngineering team, including requesting candidate composes, performing release validation, and managing blocker and freeze exception bugs
Working with the Working Groups to plan to test for the Fedora Products

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://calendar.fedoraproject.org//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

There are multiple ways how to talk to Fedora Quality members and other people interested in this area. You are welcome to join us.

Our communication channels are listed below. See Communication in Fedora for more general details.

Discussion (forum)

At Fedora Discussion you can find our topics under the quality team tag. (You can also subscribe to this tag, when logged in).

Matrix (chat)

At Fedora Chat you can find us in the #quality:fedoraproject.org^{(other clients|?)} room.

We regularly hold Quality meetings, where important quality-related issues are discussed and plans are being made. Feel free to join us. Read more in QA/Meetings.

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.
test-reports is the mailing list for receiving automated reports summaries from Fedora tooling which are related to development and testing activities
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.

@@ Line 1: / Line 1: @@
+{{header|qa}}
+{{autolang|base=yes}}
+__NOTOC__
 = 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? ==
-{{ Template:message/notice | Fedora 9 Preview is out. Please help test it! Check out the [[QA/TestPlans/Fedora9Install|  installer test plan]]  and [[QA/TestResults/Fedora9Install/FinalRelease|  current test status]] .
-}}
-=== 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.
-We are replacing the old [[QA/TreeTestingTemplate|  TreeTestingTemplate]]  with a detailed [[QA/TestPlans/Fedora9Install|  test plan]]  for Fedora 9. This plan will be maintained and improved by the QA team.
-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
-=== 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 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.
-=== Join the QA discussions and meetings ===
+== Activities ==
-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.
+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
-Join #fedora-qa for discussions and #fedora-meeting for weekly IRC meetings. The QA meeting is usually '''Wednesdays at 1500UTC''' - check ["Communicate/FedoraMeetingChannel"]  for more details about the use of #fedora-meeting, and watch fedora-test-list for meeting agendas and summaries.
+Pending and completed tasks are listed in [https://pagure.io/fedora-qa/issues Pagure].
-{{Anchor|GetAFedoraAccount}}
+== Get Involved ==
-=== Get a Fedora Account ===
-Create an account in the [[Infrastructure/AccountSystem|  Fedora Account System]] :
+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.
-. Visit the account system home: https://admin.fedoraproject.org/accounts/
+=== Stay informed ===
-. Click on 'Apply for a new account' and fill in the blanks.
+{{anchor|calendar}}
+You can follow important QA events by subscribing to the [https://calendar.fedoraproject.org/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://calendar.fedoraproject.org//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).
-. After you create your account, request an email with instructions to sign the [http://fedoraproject.org/wiki/Legal/Licenses/CLA Contributor License Agreement]  (CLA): https://admin.fedoraproject.org/accounts/send-cla.cgi
+{{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.
-. Request membership in the 'fedorabugs' group in the account system.
+== Communicate ==
-=== Create a Bugzilla Account ===
+There are multiple ways how to talk to Fedora Quality members and other people interested in this area. You are welcome to join us.
-Make sure you have an account in [http://bugzilla.redhat.com/ Bugzilla] .
+Our communication channels are listed below. See [https://docs.fedoraproject.org/en-US/project/communications/ Communication in Fedora] for more general details.
-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.
+=== Discussion (forum) ===
-=== Join the Wiki ===
+At [https://discussion.fedoraproject.org Fedora Discussion] you can find our topics under the [https://discussion.fedoraproject.org/tag/quality-team quality team] tag. (You can also subscribe to this tag, when logged in).
-Refer to WikiEditing page for more information. Add yourself as [[QA/Contributors| QA contributor]]
+=== Matrix (chat) ===
-== Further Info and Links ==
+At [https://chat.fedoraproject.org Fedora Chat] you can find us in the {{matrix|#quality:fedoraproject.org}} room.
-=== Regular Meetings ===
+We regularly hold ''Quality meetings'', where important quality-related issues are discussed and plans are being made. Feel free to join us. Read more in [[QA/Meetings]].
-* [[QA/Meetings]]
+=== Mailing lists ===
-* QA Meeting / Bug Day Schedule: [http://www.google.com/calendar/ical/kkl79p5br3l4icbiethofjfpcc%40group.calendar.google.com/public/basic.ics ICAL] , [http://www.google.com/calendar/render?cid=kkl79p5br3l4icbiethofjfpcc%40group.calendar.google.com Google Calendar]
-=== Manual Test Matrix ===
+* [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/test-reports@lists.fedoraproject.org/ test-reports] is the mailing list for receiving automated reports summaries from Fedora tooling which are related to development and testing activities
+* [https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org/ qa-devel] is the mailing list for QA tooling development
-* ["QA/TreeTestingTemplate"]
+=== Tickets ===
-=== Fedora Release Criteria ===
+* [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
-* ["QA/ReleaseCriteria"]
+----
+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.
-=== Test HowTo ===
-* ["QA/HowToTestTemplate"]
+[[Category:Fedora sub-projects]] [[Category:QA]]

Search

QA: Difference between revisions