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 me and you 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.
+== Get Involved ==
-What we do can be broken down to 4 categories.
+*[[Join#QA|Join QA]]
+*[[QA/Test_Days|Participate in a Testday]]
+*[http://fedoraproject.org/join-fedora Join other Fedora projects]
-* Quality Control. # Todo create a QC ( testers ) page
+== Communicate ==
-* Defect Management. # Todo create DM ( bug zappers ) page
-* Quality Assurance. # Todo create QA page ( policy etc )
-* Product Enhancement, Innovation and Improvements. # create PEII (developers ) page
-Regular meetings are held weekly on wednesdays at 1500UTC in the fedora-meeting channel
+[[ Communicate/FedoraMeetingChannel| Meetings  ]] are held '''Wednesdays''' at '''1600UTC'''.
-on irc.freenode.net and are open to everyone to view and participate in.
-We ask users to stay on topic until the floor has been open for off topics which is
+The Meetings are open for everyone to attend and participate in.
-always at the end of the meeting.
-If there is something you want to discuss regarding Fedora QA process feel free to drop by at
+General info on QA meetings such as topics for next meeting along with previous meetings can be found [[ QA/Meetings|here. ]]
-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
+* [irc://irc.freenode.net/fedora-meetings Attend QA meeting] on IRC
-which will take you to their relevant page and there you can find information on how to join along with general useful information
+* [irc://irc.freenode.net/fedora-qa Talk to other QA members] on IRC
-about them.
+* [mailto:fedora-test-list@fedoraproject.org Send a Mail to other QA members]

Search