Difference between revisions of "BugSquad/Testing"
< BugSquad
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | <noinclude>{{TeamHeader|BugSquad}}{{stub | + | <noinclude>{{TeamHeader|BugSquad}}{{stub}} |
[[Category:Testing]] | [[Category:Testing]] | ||
[[Category:BugSquad]] | [[Category:BugSquad]] | ||
</noinclude> | </noinclude> | ||
| + | |||
| + | See also [[Testing]]. | ||
| + | |||
== Testing Groups == | == Testing Groups == | ||
* [[olpc:OLPC New Zealand]] & [[olpc:WellyNZTesters]] | * [[olpc:OLPC New Zealand]] & [[olpc:WellyNZTesters]] | ||
| Line 8: | Line 11: | ||
==Teaching Users How to File Good Bug Reports== | ==Teaching Users How to File Good Bug Reports== | ||
Users are often the best source of good bug reports (Trac tickets). | Users are often the best source of good bug reports (Trac tickets). | ||
| − | * [[ | + | * [[BugSquad/Bug Report]] - How to file a ticket |
==Teaching Bug Reporters How to Follow Up== | ==Teaching Bug Reporters How to Follow Up== | ||
Latest revision as of 17:39, 8 July 2012
This article is a stub. You can help Sugar Labs by expanding it.
See also Testing.
Testing Groups
Teaching Users How to File Good Bug Reports
Users are often the best source of good bug reports (Trac tickets).
- BugSquad/Bug Report - How to file a ticket
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