From Fedora Project Wiki
< User:Johannbg | Draft
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{header|qa}} | {{header|qa}} | ||
__NOTOC__ | __NOTOC__ | ||
== Fedora Quality Assurance == | == Fedora Quality Assurance == | ||
| Line 6: | Line 7: | ||
The Quality Assurance project is engaged in the following 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. | * [[User:Johannbg/Draft/QC | 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. | * Developing and executing [[QA/TestPlans]] to test important functionality in a systematic way, usually with multiple cooperating testers. | ||
* Developing and run [[QA/Tools]], which use automation to find potential bugs. | * Developing and run [[QA/Tools]], which use automation to find potential bugs. | ||
* [[QA/Test Days]] are typically held on Thursdays to coordinate focused testing on a specific feature or component. | * [[QA/Test Days]] are typically held on Thursdays to coordinate focused testing on a specific feature or component. | ||
* 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. | ||
== Communicate == | == Communicate == | ||
Revision as of 16:26, 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.
- Developing and executing QA/TestPlans to test important functionality in a systematic way, usually with multiple cooperating testers.
- Developing and run QA/Tools, which use automation to find potential bugs.
- QA/Test Days are typically held on Thursdays to coordinate focused testing on a specific feature or component.
- 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.
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.