From Fedora Project Wiki
No edit summary
No edit summary
 
(45 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{header|qa}}
{{header|qa}}
 
__NOTOC__


== Fedora Quality Assurance ==
== Fedora Quality Assurance ==


Fedora is a rapidly progressing distribution and collection of free software.
== Activities ==
 
We have detailed quality assurance procedures to help maintain a cutting edge, innovating and a robust platform which consist of people like me and you around the world.
 
 
What we do can be broken down to 4 categories.
 
* [[ User:Johannbg/Draft/QA/QC|Quality Control. ]]
* [[ User:Johannbg/Draft/QA/DM|Defect Management. ]]
* [[ User:Johannbg/Draft/QA/QA|Quality Assurance. ]]
* [[ User:Johannbg/Draft/QA/PEII|Product Enhancement, Innovation and Improvements. ]]
 
 
Regular meetings are held weekly on wednesdays at 1500UTC in the fedora-meeting channel
on irc.freenode.net and are open to everyone to view and participate in.
 
Topics for each meeting can be found [[ QA/Meetings/Topics|here ]], Previously held meetings can be found [[ QA/Meetings|here. ]]
 
We ask users to stay on topic until the floor has been open for off topics.
 
 
If there is something you want to discuss regarding Fedora QA process feel free to drop by at fedora-qa on irc.freenode.net where all of the QA team members reside or send us a mail to qa@fedoraproject.org where someone of the QA team will respond to you as fast as possible.
 


If you wish to get involved with the QA process of Fedora simply click on any of the 4 categories
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
* [[ BugZappers | Review ]] and act as bridge between users and developers that aids in fixing and closing bugs
* Developing and executing [[QA/TestPlans | test plans ]] to test important functionality in a systematic way, usually with multiple cooperating testers.
* Developing and run [[QA/Tools| tools]], which use automation to find potential bugs.
* The QA team works with developers and [[ReleaseEngineering|release engineers]] to maintain the [[QA/ReleaseCriteria|release criteria]], which are used to determine what bugs count as release blockers.


which contain general information about them along with information on how to join.
== Get Involved ==


*[[Join#QA|Join QA]]
*[[QA/Test_Days|Participate in a Testday]]
*[http://fedoraproject.org/join-fedora Join other Fedora projects]


If you already have visited those pages but feel like the QA process is not something you would like
== Communicate ==


to be involved with please take your time time to look at some other interesting parts of the Fedoraproject
[[ Communicate/FedoraMeetingChannel| Meetings  ]] are held '''Wednesdays''' at '''1600UTC'''.


such as Art or documentaion #todo links.
The Meetings are open for everyone to attend and participate in.


General info on QA meetings such as topics for next meeting along with previous meetings can be found [[ QA/Meetings|here. ]]


The QA team would like to thank you for taking your time to read reviewing the QA process.
* [irc://irc.freenode.net/fedora-meetings Attend QA meeting] on IRC
* [irc://irc.freenode.net/fedora-qa Talk to other QA members] on IRC
* [mailto:fedora-test-list@fedoraproject.org Send a Mail to other QA members]

Latest revision as of 17:05, 9 February 2009

QA.png


Fedora Quality Assurance

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
  • Review and act as bridge between users and developers that aids in fixing and closing bugs
  • Developing and executing test plans to test important functionality in a systematic way, usually with multiple cooperating testers.
  • Developing and run tools, which use automation to find potential bugs.
  • The QA team works with developers and release engineers to maintain the release criteria, which are used to determine what bugs count as release blockers.

Get Involved

Communicate

Meetings are held Wednesdays at 1600UTC.

The Meetings are open for everyone to attend and participate in.

General info on QA meetings such as topics for next meeting along with previous meetings can be found here.