From Fedora Project Wiki
< QA
m (Fixed template) |
mNo edit summary |
||
Line 4: | Line 4: | ||
This page describes the various workflows that QA engineers will go through. In other words, this is Stuff That QA People Do. | This page describes the various workflows that QA engineers will go through. In other words, this is Stuff That QA People Do. | ||
{{ | {{Admon/caution | Feel free to help define the things here - talk to WillWoods if you've got other ideas.}} | ||
Each of the bullet points below should eventually have some links for further information. | Each of the bullet points below should eventually have some links for further information. |
Latest revision as of 19:33, 3 June 2008
QA Workflows
This page describes the various workflows that QA engineers will go through. In other words, this is Stuff That QA People Do.
Each of the bullet points below should eventually have some links for further information.
Bug Triage
- Monitor new bugs
- Adjust priorities and severity
- Request extra info where needed
- Close duplicates
Update Testing
- Enable the updates-testing repo
- Install the packages therein
- Report on the stability of the packages
Release Testing
- Install from 'development' (aka 'rawhide') and/or install Test releases
- Continue getting updates from development
- Report problems
Process Refinement
- Write test plans
- Write release criteria
- Define bug priorities and severity
Tool Improvement / Engineering
- Write tools to make the above tasks easier (automated testing, etc)
- Improve tools
- Maintain tools
- Evaluate new tools
FUTURE: Automated testing
- Write new tests
- Review proposed tests