Difference between revisions of "Testing"

From Sugar Labs
Jump to navigation Jump to search
(Created page with '#REDIRECT [[{{Upcoming Stable Release}}/Testing]]')
 
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
#REDIRECT [[{{Upcoming Stable Release}}/Testing]]
+
<noinclude>[[Category:Testing]]</noinclude>
 +
 
 +
* Testing of all forms is welcome.
 +
* Testing is at the base of discovery.
 +
* When you try or test something, you learn what it has to offer.
 +
 
 +
If in the course of your Sugar adventures, you discover something you want to share, you can report on your experiences here under one of the [[/Reports]] categories (or create a new one).
 +
 
 +
If you find software bugs, you can help the Sugar developers and others if you register a bug in our [http://bugs.sugarlabs.org bug tracker].
 +
 
 +
You will get a wider readership if you also report to the [http://lists.sugarlabs.org/listinfo/sugar-devel Sugar-devel mailing list].
 +
* Testing requests - [[{{Previous Stable Release}}/Testing]], [[{{Current Stable Release}}/Testing]], [[{{Upcoming Stable Release}}/Testing]]
 +
 
 +
== Page naming convention ==
 +
When you create a report as a sub page of Testing/Reports/, think of including (but not limited to) some of the following in your page title. Sugar variant | host OS | version | machine. Use the subject of you report at the start of the page title, with other information qualifying the subject. To make your report part of an existing set by title, take, as a start, the beginning of an existing page title, and qualify it with your update.
 +
 
 +
== Testing Groups ==
 +
* [[olpc:OLPC New Zealand]] & [[olpc:WellyNZTesters]] use the [http://lists.laptop.org/listinfo/Testing Testing mailing list].
 +
* Sugar Labs [[BugSquad]] & [[BugSquad/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
 +
 
 +
== Subpage index ==
 +
{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Latest revision as of 14:17, 14 November 2014


  • Testing of all forms is welcome.
  • Testing is at the base of discovery.
  • When you try or test something, you learn what it has to offer.

If in the course of your Sugar adventures, you discover something you want to share, you can report on your experiences here under one of the /Reports categories (or create a new one).

If you find software bugs, you can help the Sugar developers and others if you register a bug in our bug tracker.

You will get a wider readership if you also report to the Sugar-devel mailing list.

Page naming convention

When you create a report as a sub page of Testing/Reports/, think of including (but not limited to) some of the following in your page title. Sugar variant | host OS | version | machine. Use the subject of you report at the start of the page title, with other information qualifying the subject. To make your report part of an existing set by title, take, as a start, the beginning of an existing page title, and qualify it with your update.

Testing Groups

Teaching users how to file good bug reports

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

Subpage index