Testing matrix
Jump to navigation
Jump to search
NOTE: STILL A WORK IN PROGRESS.
Drop me a line with any feedback, please. --Gregdek 16:37, 9 November 2007 (EST)
Notes
- Activity Name is obviously the name of the activity.
- Link must be a clickable link to the activity itself.
- 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.
- 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.
Filing Bugs
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 |
|---|---|---|---|---|---|---|---|
| foo | Download | testplanfoo | gregdek at redhat dot com | gregdek at fedoraproject dot org | Build 623 | yes | unclaimed |
| bar | Download | testplanbar | bar at laptop dot org | baz at laptop dor org | Build 623 | yes | unclaimed |