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}}</noinclude>{{stub}}{{TOCright}}
+
<noinclude>{{GoogleTrans-en}}{{TeamHeader|BugSquad}}</noinclude>{{stub}}{{TOCright}}
  
  
Line 7: Line 7:
 
==Teaching Bug Reporters How to Follow Up==
 
==Teaching Bug Reporters How to Follow Up==
 
* Many bug reports rot because of lack of follow up from reporters and users.
 
* Many bug reports rot because of lack of follow up from reporters and users.
* Describe the work flow and balance between Gitorius, Trac, Wiki, Mailing Lists, IRC.
+
* Describe the work flow and balance between Gitorious, Trac, Wiki, Mailing Lists, IRC.
  
 
==Creating Best Practices for Developer Testing==
 
==Creating Best Practices for Developer Testing==
Line 15: Line 15:
 
* Develop Pre-release test strategies
 
* Develop Pre-release test strategies
 
* Test cases
 
* Test cases
 +
* [[{{Upcoming Stable Release}}/Testing]]
  
 
[[Category:BugSquad]]
 
[[Category:BugSquad]]

Revision as of 23:29, 11 September 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

  • 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