QA

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Get Involved)
(fix meeting time)
(23 intermediate revisions by 10 users not shown)
Line 1: Line 1:
 +
{{header|qa}}
 +
 +
{{autolang|base=yes}}
 
__NOTOC__
 
__NOTOC__
 +
 
= Fedora Quality Assurance =
 
= Fedora Quality Assurance =
  
{{header|qa}}
 
  
 
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 12:
  
 
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]], [[QA:Updates_Testing|updates-testing]], or as it appears in a supported public release
 +
* Through the [[Proven_tester|proven testers]] system, testing all updates to [[Critical_Path_Packages_Proposal|critical path]] packages before they are accepted
 
* Through the [[BugZappers]] group, acting as a bridge between users and developers that aids in fixing and closing bugs  
 
* Through the [[BugZappers]] group, 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 [[QA/ReleaseCriteria|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 [[:Category:Release_validation|release validation]], and managing [[QA:SOP_blocker_bug_process|blocker]] and [[QA:SOP_freeze_exception_bug_process|freeze exception]] bugs
  
 
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].
Line 26: Line 31:
 
== Communicate ==
 
== Communicate ==
  
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.
+
QA project meetings are held '''Mondays''' at '''15.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]].
  
* [irc://irc.freenode.net/fedora-meetings Attend QA meeting] on IRC (if you join the channel at a different time, you'll find another group's meeting)
+
* Attend QA IRC meeting on time (if you join the channel at a different time, you'll find another group's meeting)
* [irc://irc.freenode.net/fedora-qa Talk to other QA members] on our permanent IRC channel
+
* Talk to other QA members on our permanent IRC channel {{fpchat|#fedora-qa}}
* [https://www.redhat.com/mailman/listinfo/fedora-test-list fedora-test-list] is the mailing list for the QA and BugZappers projects
+
* {{fplist|test}} is the mailing list for the QA and [[BugZapper]] project
* [https://admin.fedoraproject.org/mailman/listinfo/test-announce test-announce] is the mailing list for QA and BugZappers project announcements - if you want to stay up-to-date on QA and BugZappers events, subscribe!
+
* {{fplist|test-announce}} is the mailing list for QA and [[BugZapper]] project announcements - if you want to stay up-to-date on QA and BugZappers events, '''subscribe''' !
 +
 
 +
If you don't know how to use IRC, please click the question mark whick links to a page full of IRC help.
  
See [[How to use IRC]] if the IRC links don't work, or if you need more information.
+
[[Category:Fedora sub-projects]] [[Category:QA]]

Revision as of 12:56, 30 July 2013

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 Trac.

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 15.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 and BugZapper project
  • test-announce is the mailing list for QA and BugZapper project announcements - if you want to stay up-to-date on QA and BugZappers events, subscribe !

If you don't know how to use IRC, please click the question mark whick links to a page full of IRC help.