User:Johannbg/Draft/QA: Difference between revisions

Latest revision as of 17:05, 9 February 2009

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.

@@ Line 1: / Line 1: @@
 {{header|qa}}
+__NOTOC__
 == 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 you and me around the world.
+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.
-What we do can be broken down to 3 categories.
+== Get Involved ==
-* [[ User:Johannbg/Draft/QA/QC|Quality Control. ]] A.K.A Bug Hunters...
+*[[Join#QA|Join QA]]
-* [[ User:Johannbg/Draft/QA/SQA|Quality Assurance. ]] A.K.A Bug Zappers...
+*[[QA/Test_Days|Participate in a Testday]]
-* [[ Development|Development ]] A.K.A Bug Breeders...
+*[http://fedoraproject.org/join-fedora Join other Fedora projects]
 == Communicate ==
-[[ Communicate/FedoraMeetingChannel| Meetings  ]] are held '''Wednesdays''' at '''1500UTC'''.
+[[ Communicate/FedoraMeetingChannel| Meetings  ]] are held '''Wednesdays''' at '''1600UTC'''.
 The Meetings are open for everyone to attend and participate in.
@@ Line 25: / Line 30: @@
 * [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]
-== Get Involved ==
-If you wish to get involved with the QA process of Fedora simply click on any of the 3 categories which contain general information about them along with information on how to join.
-[[Join#QA|Join QA]]
-[http://fedoraproject.org/join-fedora Not interested in QA, take a look at other Fedora projects]
-If you already have visited those pages but feel like the QA process is not something you would like to be involved with please take your time time to look at some other interesting parts of the Fedoraproject such as [[ Artwork|artwork]] or [[ DocsProject|documentation ]] and many more...
-The QA team would like to thank you for taking your time to reading about the QA process.

Search