Difference between revisions of "BugSquad/Testing"

From Sugar Labs
Jump to: navigation, search
m (relace bugsquad header with team header)
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 }}</noinclude>{{BugSquad/Header}}
+
<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 }}</noinclude>{{TeamHeader|BugSquad}}
 
{{stub}}
 
{{stub}}
  

Revision as of 10:00, 25 June 2008

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 Bugreports

Users are often the best source of good bug reports.

Teaching Bug Reporters How to Follow Up on Bugreports

Many bugreports rot because of lack of follow up from reporters.

Creating Best Practices for Developer Testing

Coordinate with Release Managers to Develop Pre-release test strategies