From Fedora Project Wiki
< User:Johannbg | Draft
No edit summary |
|||
| (13 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{header|qa}} | {{header|qa}} | ||
__NOTOC__ | |||
== Fedora Quality Assurance == | == 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 | |||
* [[ 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 == | |||
* [[ | *[[Join#QA|Join QA]] | ||
* [[ | *[[QA/Test_Days|Participate in a Testday]] | ||
* [ | *[http://fedoraproject.org/join-fedora Join other Fedora projects] | ||
== Communicate == | == Communicate == | ||
| Line 25: | Line 30: | ||
* [irc://irc.freenode.net/fedora-qa Talk to other QA members] 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] | * [mailto:fedora-test-list@fedoraproject.org Send a Mail to other QA members] | ||
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.