From Fedora Project Wiki

(mention 1500 UTC for meetings during DST)
(→‎Communicate: add Tickets)
 
(8 intermediate revisions by 5 users not shown)
Line 14: Line 14:
 
* Acting as a bridge between users and developers that aids in fixing and closing bugs  
 
* 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 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
+
* 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
 
* 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
 
* 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
 
* 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 testing for the Fedora Products
+
* Working with the [[Fedora.next#Working_groups|Working Groups]] to plan to test for the Fedora Products
  
Pending and completed tasks are listed in [https://fedorahosted.org/fedora-qa/report/1 Trac] and, for tooling, [https://phab.qadevel.cloud.fedoraproject.org/ Phabricator].
+
Pending and completed tasks are listed in [https://pagure.io/fedora-qa/issues Pagure].
  
 
== Get Involved ==
 
== Get Involved ==
Line 26: Line 26:
 
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.
 
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.
  
If you'd like to get involved with Fedora but QA doesn't sound like the group for you, think about [http://fedoraproject.org/join-fedora joining another Fedora project] instead.
+
=== Stay informed ===
 +
 
 +
{{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).
 +
 
 +
{{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.
  
 
== Communicate ==
 
== Communicate ==
  
QA project meetings are held '''Mondays''' at '''16.00 UTC''' (or '''15.00 UTC''' during daylight savings 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.
+
=== IRC ===
 +
 
 +
'''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.
 +
 
 +
'''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]].
 +
 
 +
If you need help with running an IRC client a connecting to our channels, see [[How to use IRC]].
 +
 
 +
=== Mailing lists ===
 +
 
 +
* [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
 +
 
 +
=== Tickets ===
  
General info on QA meetings such as topics for future meetings and records from previous meetings can be found at [[QA/Meetings]].
+
* [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
  
* Attend QA IRC meeting on time (if you join the channel at a different time, you'll find another group's meeting)
+
----
* Talk to other QA members on our permanent IRC channel {{fpchat|#fedora-qa}}
+
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.
* {{fplist|test}} is the mailing list for the QA project
 
* {{fplist|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
 
* {{fplist|qa-devel}} is the mailing list for QA tooling development
 
  
If you don't know how to use IRC, please click the question mark which links to a page full of IRC help.
 
  
 
[[Category:Fedora sub-projects]] [[Category:QA]]
 
[[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.