Difference between revisions of "BugSquad/Testing"

From Sugar Labs
Jump to navigation Jump to search
Line 1: Line 1:
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|BugSquad}}{{stub}}</noinclude>{{TOCright}}
+
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|BugSquad}}</noinclude>{{stub}}{{TOCright}}
  
  

Revision as of 14:45, 26 March 2009

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

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 on Bug Reports

Many bug reports rot because of lack of follow up from reporters.

Creating Best Practices for Developer Testing

  • Test cases

Coordinate with Release Managers to Develop Pre-release test strategies