Difference between revisions of "BugSquad/Testing"

Latest revision as of 17:39, 8 July 2012

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

This article is a stub. You can help Sugar Labs by expanding it.

Users are often the best source of good bug reports (Trac tickets).

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.

@@ 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>{{TeamHeader|BugSquad}}{{stub}}{{TOCright}}
+<noinclude>{{TeamHeader|BugSquad}}{{stub}}
+[[Category:Testing]]
+[[Category:BugSquad]]
+</noinclude>
+See also [[Testing]].
+== Testing Groups ==
+* [[olpc:OLPC New Zealand]] & [[olpc:WellyNZTesters]]
 ==Teaching Users How to File Good Bug Reports==
-Users are often the best source of 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 on Bugreports==
+==Teaching Bug Reporters How to Follow Up==
-Many bugreports rot because of lack of follow up from reporters.
+* 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 to Develop Pre-release test strategies==
+==Coordinate with Release Managers==
+* Develop Pre-release test strategies
-[[Category:BugSquad]]
+* Test cases
+* [[{{Upcoming Stable Release}}/Testing]]