Difference between revisions of "BugSquad/Testing"

From Sugar Labs
Jump to: navigation, search
(create testing outline)
 
(26 intermediate revisions by 7 users not shown)
Line 1: Line 1:
=Filing Good Bug Reports=
+
<noinclude>{{TeamHeader|BugSquad}}{{stub}}
 +
[[Category:Testing]]
 +
[[Category:BugSquad]]
 +
</noinclude>
  
=Following Up on Bug Reports=
+
See also [[Testing]].
  
=Developer Testing=
+
== Testing Groups ==
 +
* [[olpc:OLPC New Zealand]] & [[olpc:WellyNZTesters]]
  
=Pre-release Testing=
+
==Teaching Users How to File 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==
 +
* 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==
 +
* Develop Pre-release test strategies
 +
* Test cases
 +
* [[{{Upcoming Stable Release}}/Testing]]

Latest revision as of 18: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.


See also Testing.

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

Coordinate with Release Managers