Testing matrix: Difference between revisions

NOTE: STILL A WORK IN PROGRESS.

Drop me a line with any feedback, please. --Gregdek 16:37, 9 November 2007 (EST)

Activity Name is obviously the name of the activity. A link to a specification, a UI mock up, or other reference as to how the activity works is very useful for testing.
Link must be a clickable link directly to the activity .xo file itself. We don't want testers to have to go looking for the right file. Exception: If the activity is in the core build, just put "core" in the field. If you are not sure, or you want a newer version tested, then please link directly to the .xo for testing.
Test plan is a link to the test plan submitted by the developer.
Developer Contact and Test Contact are email addresses. It is crucial that developers and testers know how to reach one another!
Build version indicates the version of the OLPC build upon which the tests should take place. Developers, if you require testing on multiple versions, create multiple entries in the matrix. Until we stabilize a bit, this will just be "latest build" and we'll link to the latest build from here.
Emulator OK means it's okay to test this activity under qemu emulation. Developers, if a test will require a physical XO unit to test your activity -- like camera applications, for instance -- your answer in this column should be NO.
Status is for testers. The default status should be unclaimed. Testers, when you claim an activity for testing, mark this in progress. When the activity has passed all tests, change the status to complete.

To file a bug:

Go to the new ticket page in Trac.
For type, select "Defect".
For component, select the activity. If you do not find the activity in the list, select "new component".
For assign-to, select the developer contact. If you do not find your developer contact in the list, leave it unassigned.
For priority, use your best judgment.
Be sure to update the test plan document with a link to the bug.

Activity Name	Link	Test Plan	Developer Contact	Test Contact	Build Version	Emulator OK?	Status
Browse	(core)	Tests/Browse	mpgritti gmail com	digitaldybbuk gmail com	joyride 258	unknown	in progress
Calculate	Download	Tests/Calculate	unknown	unknown	Latest	yes	unclaimed
Flipsticks-RC-1.4.xo	Download	No Activity Testplan Found	unknown	unknown	Latest	yes	unclaimed
CartoonBuilder-RC-1.7.xo	Download	No Activity Testplan Found	unknown	unknown	Latest	yes	unclaimed
JokeMachine-5.xo	Download	No Activity Testplan Found	unknown	unknown	Latest	yes	unclaimed
Poll-11.xo	Download	No Activity Testplan Found	unknown	unknown	Latest	yes	unclaimed
JigsawPuzzle-1_20071030.xo	Download	No Activity Testplan Found	unknown	unknown	Latest	yes	unclaimed
SliderPuzzle-3_20071030.xo	Download	No Activity Testplan Found	unknown	unknown	Latest	yes	unclaimed
StoryBuilder-8.xo	Download	No Activity Testplan Found	unknown	unknown	Latest	yes	unclaimed
MikMik-8.xo	Download	No Activity Testplan Found	unknown	unknown	Latest	yes	unclaimed
PegSolitaire.xo	Download	No Activity Testplan Found	unknown	unknown	Latest	yes	unclaimed
Kuku.xo	Download	No Activity Testplan Found	unknown	unknown	Latest	yes	unclaimed

For help:

@@ Line 6: / Line 6: @@
 == Notes ==
-* '''Activity Name''' is obviously the name of the activity.
+* '''Activity Name''' is obviously the name of the activity. A link to a specification, a UI mock up, or other reference as to how the activity works is very useful for testing.
-* '''Link''' must be a clickable link '''directly to the activity .xo file itself'''.  We don't want testers to have to go looking for the right file.  '''Exception:''' If the activity is in the core build, just put "core" in the field.
+* '''Link''' must be a clickable link '''directly to the activity .xo file itself'''.  We don't want testers to have to go looking for the right file.  '''Exception:''' If the activity is in the core build, just put "core" in the field. If you are not sure, or you want a newer version tested, then please link directly to the .xo for testing.
 * '''Test plan''' is a link to the test plan submitted by the developer.
 * '''Developer Contact''' and '''Test Contact''' are email addresses.  It is '''crucial''' that developers and testers know how to reach one another!