Difference between revisions of "BugSquad/Testing"

From Sugar Labs
Jump to navigation Jump to search
m (moved Walter is a wanker 7/Testing to BugSquad/Testing over redirect: revert)
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
<noinclude>{{GoogleTrans-en}}{{TeamHeader|BugSquad}}</noinclude>{{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==
 
==Teaching Users How to File Good Bug Reports==
 
Users are often the best source of good bug reports (Trac tickets).
 
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==
 
==Teaching Bug Reporters How to Follow Up==
Line 10: Line 18:
  
 
==Creating Best Practices for Developer Testing==
 
==Creating Best Practices for Developer Testing==
 +
* [[BugSquad/Test Cases]]
 
* Efficient testing harnesses
 
* Efficient testing harnesses
  
Line 16: Line 25:
 
* Test cases
 
* Test cases
 
* [[{{Upcoming Stable Release}}/Testing]]
 
* [[{{Upcoming Stable Release}}/Testing]]
 
[[Category:BugSquad]]
 

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