Testing draft: Difference between revisions
m (New page: {{draft}} {{TOCright}} == Current status == <big><big><big><big>'''Next release: 9.1.0, March 15, 2008'''</big></big></big></big> These images are automatically generated from Trac....) |
mNo edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{draft}} |
{{draft}} |
||
{{Testing}} |
|||
{{TOCright}} |
{{TOCright}} |
||
<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> |
|||
== |
== Introduction == |
||
Text goes here, incl. something about how we do our coordinating with the internal OLPC test team. |
|||
<big><big><big><big>'''Next release: [[9.1.0]], March 15, 2008'''</big></big></big></big> |
|||
| ⚫ | |||
These images are automatically generated from Trac. '''Note: This is a draft page, so these images are actually totally fake. Also, the above links to the next release and the release date should be pulled from a template.''' |
|||
* Update snippet from last test meeting |
|||
<table> |
|||
* Pointer to meeting notes in general |
|||
<tr><td><big>Bugs:</big></td><td>[[Image:Progress-bar-1.png]]</td></tr> |
|||
* Activity of the week |
|||
<tr><td><big>Features:</big></td><td>[[Image:Progress-bar-2.png]]</td></tr> |
|||
</table> |
|||
=== Key === |
|||
* '''done''' - The feature has been verified to work, or the bug has been verified to be closed. We know the status of this bug/feature and it is what we want. Nothing further needs to be done with this item. (Hooray!) Ideally, by the release date, everything will fall into this category. |
|||
* '''to fix''' - The feature has been verified to not exist/work, or the bug has been verified to be not closed. Things in this category fall into the domain of [[Developers]]. |
|||
* '''to test''' - These are features or bugs whose status is not known. Please help us test this (this includes writing test cases, building testing tools, and running test cases) and then put into the "done" and "to fix" categories as appropriate. '''''This is where [[#How you can help|testers can help!]]''''' |
|||
* '''to triage''' - These are new feature requests/enhancements or reported bugs that have not yet been looked at, but are currently reported against this component/build. These should be tackled in the next [[Triage]] meeting. |
|||
== How you can help == |
== How you can help == |
||
We welcome everyone to the community test group regardless of background, experience, or how much free time you have available; there are tasks for a broad range of skill and commitment levels, and if you don't yet know how to do something for a task you want to take on, we'll work with you to find a way to learn. |
|||
== How you can learn == |
|||
| ⚫ | |||
Whether you're looking for a [[Test_cases_8.2.0#Smoke_Test|quick smoke test]] you can run and report in less than 45 minutes, have an hour to spend [[Activity testing|testing an Activity]], can spend an afternoon helping us [[creating test cases|create test cases]], want to work on [[testing tools]] or [[automated testing]], or are searching for a potential research or student class project, you'll find it here. |
|||
=== Joining the community === |
|||
== Resources == |
|||
* OLPC test scripts |
|||
=== Resources === |
|||
* Basic "about testing" portals |
|||
* Common QA-relevant Trac queries |
|||
* Where to ask questions and get help |
|||
Latest revision as of 22:16, 5 November 2008
|
NOTE: The contents of this page are not set in stone, and are subject to change! This page is a draft in active flux ... |
|
Translate this page with Google -español -български -中文（中国大陆） -中文（臺灣） -hrvatski -čeština -dansk -Nederlands -suomi -français -Deutsch -Ελληνικά -हिन्दी -italiano -日本語 -한국어 -norsk -polski -português -română -русский -svenska
Introduction
Text goes here, incl. something about how we do our coordinating with the internal OLPC test team.
Recent news
- Update snippet from last test meeting
- Pointer to meeting notes in general
- Activity of the week
How you can help
We welcome everyone to the community test group regardless of background, experience, or how much free time you have available; there are tasks for a broad range of skill and commitment levels, and if you don't yet know how to do something for a task you want to take on, we'll work with you to find a way to learn.
Whether you're looking for a quick smoke test you can run and report in less than 45 minutes, have an hour to spend testing an Activity, can spend an afternoon helping us create test cases, want to work on testing tools or automated testing, or are searching for a potential research or student class project, you'll find it here.
Resources
- OLPC test scripts
- Basic "about testing" portals
- Common QA-relevant Trac queries
- Where to ask questions and get help