Difference between revisions of "BugSquad/Testing"
< BugSquad
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
Users are often the best source of good bug reports (Trac tickets). | Users are often the best source of good bug reports (Trac tickets). | ||
| − | ==Teaching Bug Reporters How to Follow Up | + | ==Teaching Bug Reporters How to Follow Up== |
| − | Many bug reports rot because of lack of follow up from reporters. | + | * Many bug reports rot because of lack of follow up from reporters and users. |
| + | * Describe the work flow and balance between Gitorius, Trac, Wiki, Mailing Lists, IRC. | ||
==Creating Best Practices for Developer Testing== | ==Creating Best Practices for Developer Testing== | ||
| + | * Efficient testing harnesses | ||
| + | |||
| + | ==Coordinate with Release Managers== | ||
| + | * Develop Pre-release test strategies | ||
* Test cases | * Test cases | ||
| − | |||
| − | |||
[[Category:BugSquad]] | [[Category:BugSquad]] | ||
Revision as of 14:58, 26 March 2009
This article is a stub. You can help Sugar Labs by expanding it.
Teaching Users How to File Good Bug Reports
Users are often the best source of good bug reports (Trac tickets).
Teaching Bug Reporters How to Follow Up
- Many bug reports rot because of lack of follow up from reporters and users.
- Describe the work flow and balance between Gitorius, Trac, Wiki, Mailing Lists, IRC.
Creating Best Practices for Developer Testing
- Efficient testing harnesses
Coordinate with Release Managers
- Develop Pre-release test strategies
- Test cases