From Fedora Project Wiki
(→Communicate: advice on how to use the mailing list, adapted from Testing) |
m (remove extra space) |
||
| (34 intermediate revisions by 11 users not shown) | |||
| Line 1: | Line 1: | ||
{{header|qa}} | |||
{{autolang|base=yes}} | |||
__NOTOC__ | __NOTOC__ | ||
= Fedora Quality Assurance = | = 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. | 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. | ||
| Line 9: | Line 10: | ||
The Quality Assurance project is engaged in the following activities: | The Quality Assurance project is engaged in the following activities: | ||
* Testing of software as it is released into Rawhide, updates-testing, or as it appears in a supported public release | * 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 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 [[ | * 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 the [[Fedora.next#Working_groups|Working Groups]] to plan testing for the Fedora Products | |||
Pending and completed tasks are listed in [https://fedorahosted.org/fedora-qa/report/1 Trac]. | 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]. | ||
== Get Involved == | == Get Involved == | ||
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 | 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. | 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. | ||
| Line 26: | Line 30: | ||
== Communicate == | == Communicate == | ||
QA project meetings are held ''' | QA project meetings are held '''Mondays''' at '''16.00 UTC''' 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 such as topics for future meetings and records from previous meetings can be found at [[QA/Meetings]]. | General info on QA meetings such as topics for future meetings and records from previous meetings can be found at [[QA/Meetings]]. | ||
* | * 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}} | ||
* | * {{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]] | |||
Revision as of 10:56, 9 October 2014
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 the Working Groups to plan testing for the Fedora Products
Pending and completed tasks are listed in Trac and, for tooling, Phabricator.
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.
If you'd like to get involved with Fedora but QA doesn't sound like the group for you, think about joining another Fedora project instead.
Communicate
QA project meetings are held Mondays at 16.00 UTC 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 such as topics for future meetings and records from previous meetings can be found at QA/Meetings.
- 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 #fedora-qa[?]
- test is the 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
If you don't know how to use IRC, please click the question mark which links to a page full of IRC help.