From Fedora Project Wiki
< QA
m (→Activities: fix link formatting) |
(Correct plural) |
||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
__NOTOC__ | |||
= Fedora Quality Assurance = | = Fedora Quality Assurance = | ||
| Line 9: | Line 10: | ||
* 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 | * [[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. | |||
== Related Projects == | |||
Other quality-related activities are handled elsewhere | Other quality-related activities are handled elsewhere. | ||
* [[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. | * [[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. | ||
* [[PackageMaintainers]] fix bugs identified by the QA Project, with the help of upstream authors and patches proposed by testers. | * [[PackageMaintainers]] fix bugs identified by the QA Project, with the help of upstream authors and patches proposed by testers. | ||
Latest revision as of 15:00, 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.
Related Projects
Other quality-related activities are handled elsewhere.
- 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.
- PackageMaintainers fix bugs identified by the QA Project, with the help of upstream authors and patches proposed by testers.
- Special Interest Group activities are interdisciplinary, involving everything from development to quality assurance.
Get Involved
- See QA/Join for information on how to officially join the QA Project.
- Jump right into one of the above activities listed above.
- See the Testing page for setup information on the Rawhide and updates-testing repositories.
- See the BugsAndFeatureRequests for information on how to file bugs effectively.
Communications
- fedora-test-list is the mailing list for the QA and Bug Zappers projects.
- QA meetings are occasionally held on IRC. They are open for everyone to attend and participate in.
- The #fedora-qa channel is always open.
See How to use IRC if the above links don't work, or if you need more information.