Difference between revisions of "BugSquad/Testing"
< BugSquad
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
<noinclude>{{TeamHeader|BugSquad}}{{stub}}{{TOCright}} | <noinclude>{{TeamHeader|BugSquad}}{{stub}}{{TOCright}} | ||
[[Category:Testing]] | [[Category:Testing]] | ||
| + | [[Category:BugSquad]] | ||
</noinclude> | </noinclude> | ||
== Testing Groups == | == Testing Groups == | ||
| Line 14: | Line 15: | ||
==Creating Best Practices for Developer Testing== | ==Creating Best Practices for Developer Testing== | ||
| + | * [[BugSquad/Test Cases]] | ||
* Efficient testing harnesses | * Efficient testing harnesses | ||
| Line 20: | Line 22: | ||
* Test cases | * Test cases | ||
* [[{{Upcoming Stable Release}}/Testing]] | * [[{{Upcoming Stable Release}}/Testing]] | ||
| − | |||
| − | |||
Revision as of 10:41, 1 April 2010
This article is a stub. You can help Sugar Labs by expanding it.
Testing Groups
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
- BugSquad/Test Cases
- Efficient testing harnesses
Coordinate with Release Managers
- Develop Pre-release test strategies
- Test cases
- 0.114/Testing