8,288
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + − + + + − ==Teaching Users How to File Good Bugreports==+ − Users are often the best source of good bug reports. − + − + + + + + + + + + + + − + − + − + +
no edit summary
<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}}
<noinclude>{{TeamHeader|BugSquad}}{{stub}}
{{stub}}
[[Category:Testing]]
[[Category:BugSquad]]
</noinclude>
See also [[Testing]].
==Teaching Bug Reporters How to Follow Up on Bugreports==
== Testing Groups ==
Many bugreports rot because of lack of follow up from reporters.
* [[olpc:OLPC New Zealand]] & [[olpc:WellyNZTesters]]
==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==
==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]]