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 ==
@@ Line 6: / Line 7: @@
 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 Rawhide, updates-testing, or as it appears in a supported public release
-* Developing and executing [[QA/TestPlans]] to test important functionality in a systematic way, usually with multiple cooperating testers.
+* [[ BugZappers | Review ]] and act as bridge between users and developers that aids in fixing and closing bugs
-* Developing and run [[QA/Tools]], which use automation to find potential bugs.
+* Developing and executing [[QA/TestPlans | test plans ]] to test important functionality in a systematic way, usually with multiple cooperating testers.
-* [[QA/Test Days]] are typically held on Thursdays to coordinate focused testing on a specific feature or component.
+* 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.
+* 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.
-== Related Projects ==
+== Get Involved ==
-Other quality-related activities are handled elsewhere.
+*[[Join#QA|Join QA]]
-* [[BugZappers]] handle bug triage - they examine bugs reported by other people and resolve duplicates, incomplete reports, etc.  BugZappers share the fedora-test-list mailing list with the QA Project.
+*[[QA/Test_Days|Participate in a Testday]]
-* [[PackageMaintainers]] fix bugs identified by the QA Project, with the help of upstream authors and patches proposed by testers.
+*[http://fedoraproject.org/join-fedora Join other Fedora projects]
-* [[:Category:SIGs|Special Interest Group]] activities are interdisciplinary, involving everything from development to quality assurance.
 == Communicate ==
@@ Line 30: / 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 ==
-*[[Join#QA|Join QA]]
-*[[User:Johannbg/Draft/QA/Test_Days|Participate in a Testday]]
-*[http://fedoraproject.org/join-fedora Join other Fedora projects]
-The QA team would like to thank you for taking your time to reading about the QA project.

Search