Difference between revisions of "BugSquad/Testing"

From Sugar Labs
Jump to navigation Jump to search
m (moved Walter is a wanker 7/Testing to BugSquad/Testing over redirect: revert)
Line 1: Line 1:
<noinclude>{{GoogleTrans-en}}{{TeamHeader|BugSquad}}</noinclude>{{stub}}{{TOCright}}
+
<noinclude>{{TeamHeader|BugSquad}}</noinclude>{{stub}}{{TOCright}}
 
+
[[Category:Testing]]
 +
</noinclude>
 +
== Testing Groups ==
 +
* [[olpc:OLPC New Zealand]] & [[olpc:WellyNZTesters]]
  
 
==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).
 +
* [[Talk:Sugar_on_a_Stick/Getting_Involved|How to file a ticket]]
  
 
==Teaching Bug Reporters How to Follow Up==
 
==Teaching Bug Reporters How to Follow Up==

Revision as of 08:22, 1 April 2010

Team Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Meetings

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

  • Efficient testing harnesses

Coordinate with Release Managers