OLPC New Zealand/Test Requests: Difference between revisions

From OLPC
Jump to navigation Jump to search
m (tidied list)
No edit summary
Line 3: Line 3:
This document is to help communication between software developers & testers.
This document is to help communication between software developers & testers.


== Instructions for devs ==
== Instructions ==

⚫
=== General ===

==== Test request format ====

⚫
* '''Test description'''<br />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'''<br />Indicate whether Internet connectivity is required, SoaS, XO-1, XO-1.5, virtual machine image, etc.
⚫
* '''Download location'''<br />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 ===

{| class="wikitable"
|-
! 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.
Please add tests in the table on this page. NZ folk will take responsibility for maintenance of this page.
Line 10: Line 45:
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.
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 ==
=== Instructions for testers ===


=== Selecting a test ===
==== Selecting a test ====


Find the next test with a status "TODO"
* 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.
⚫
== Tests ==
* 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.


⚫
==== Format ====


⚫
== Tests ==
⚫
* '''Test description'''<br />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'''<br />Indicate whether Internet connectivity is required, SoaS, XO-1, XO-1.5, virtual machine image, etc.
⚫
* '''Download location'''<br />Where we get the file to test. Direct links are best.
⚫
* '''Status'''
⚫
* TODO
⚫
* Claimed (name): (name) will be doing this on the weekend
* In progress (name): (name) is testing now
⚫
* Completed: including link to test result write-up page, often a link to OLPC-NZ mailing list archive.




==== Current tests ====
==== Current tests ====



{| class="wikitable"
{| class="wikitable"
Line 40: Line 70:
! Status
! Status
|-
|-
|
| row 1, cell 1
|
| row 1, cell 2
|
| row 1, cell 3
|
|-
|-
|
| row 2, cell 1
|
| row 2, cell 2
|
| row 2, cell 3
|
|}
|}

Revision as of 22:41, 29 September 2010

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.


Tests

Current tests

Test description Required equipment Download location Status
Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=OLPC_New_Zealand/Test_Requests&oldid=246643"