OLPC New Zealand/Test Requests
Contents
Purpose
This document is to help communication between software developers & testers.
Instructions
General
Test request format
- Test description
Either provide a test case and expected behaviour, a ticket (that includes replication instructions) that you think you've fixed, or just say [General]. - Required equipment
Indicate whether Internet connectivity is required, SoaS, XO-1, XO-1.5, virtual machine image, etc. - Download location
Where we get the file to test. Direct links are best. - Status
- TODO
- Claimed (name): (name} will be doing this on the weekend
- Completed: including link to test result write-up page, often a link to OLPC-NZ mailing list archive.
- Declined {reason} by {name}: test request was declined for {reason} by {name}
Example tests
| Test description | Required equipment | Download location | Status |
|---|---|---|---|
| Example, have released please check SL#0000 | Sugar 0.88 (any platform) | http://www.example.org/example.xo | TODO |
| [General] Example alpha released, please help with general QA | SoaS | http://www.fedoraproject.org/Some/Page | Claimed (Tim) |
For devs
Please add tests in the table on this page. NZ folk will take responsibility for maintenance of this page.
If you would like someone to have a general play on your application to see if there is any weird behaviour, please add a [General] tag to the start of the description.
Instructions for testers
Selecting a test
- Find the next test with a status "TODO", change it to "Claimed (your name)"
Assigning a status
- Please use the declined status to indicate to a developer that something is unclear.
- Try not to add different status codes. For example, if you didn't do something that you said you would, just revert the status to TODO.
