Difference between revisions of "BugSquad/Testing"
< BugSquad
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
− | <noinclude>{{ GoogleTrans-en | + | <noinclude>{{GoogleTrans-en}}{{TeamHeader|BugSquad}}</noinclude>{{stub}}{{TOCright}} |
Line 7: | Line 7: | ||
==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 and users. | * Many bug reports rot because of lack of follow up from reporters and users. | ||
− | * Describe the work flow and balance between | + | * Describe the work flow and balance between Gitorious, Trac, Wiki, Mailing Lists, IRC. |
==Creating Best Practices for Developer Testing== | ==Creating Best Practices for Developer Testing== | ||
Line 15: | Line 15: | ||
* Develop Pre-release test strategies | * Develop Pre-release test strategies | ||
* Test cases | * Test cases | ||
+ | * [[{{Upcoming Stable Release}}/Testing]] | ||
[[Category:BugSquad]] | [[Category:BugSquad]] |
Revision as of 22:29, 11 September 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 Gitorious, 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
- 0.114/Testing