User:Mchua/Sandbox: Difference between revisions
Jump to navigation
Jump to search
m (→Smoke testing) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
== Smoke testing == |
== Smoke testing == |
||
| Line 10: | Line 18: | ||
* http://lists.laptop.org/pipermail/testing/2009-January/000758.html |
* http://lists.laptop.org/pipermail/testing/2009-January/000758.html |
||
* http://lists.laptop.org/pipermail/testing/2009-January/000759.html |
* http://lists.laptop.org/pipermail/testing/2009-January/000759.html |
||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
== Activity compatibility == |
== Activity compatibility == |
||
| Line 32: | Line 32: | ||
== Ticket closure == |
== Ticket closure == |
||
See and verify "test in build" items from [http://dev.laptop.org/report/38 trac]. |
See and verify "test in build" items from [http://dev.laptop.org/report/38 trac]; this is mostly bookkeeping. |
||
Revision as of 23:33, 29 January 2009
Firmware
q2e30 is the current one under test; it's new and needs a lot of hammering.
Bug to verify and file: http://lists.laptop.org/pipermail/testing/2009-January/000763.html
Tests to run: http://wiki.laptop.org/go/Firmware_security#Multiple-Key_Support
Smoke testing
Staging-25 could use a formal smoke test run (slimming down and speeding up the smoke test as you run it is acceptable, so long as it's documented) done in parallel with an XO running 8.2.0, to check for regressions and variances.
Wireless
There have been a number of wifi tests that need to be brought up to date and filed (and rechecked against the current build if not yet carried out.)
- http://lists.laptop.org/pipermail/testing/2009-January/000753.html
- http://lists.laptop.org/pipermail/testing/2009-January/000758.html
- http://lists.laptop.org/pipermail/testing/2009-January/000759.html
Activity compatibility
- Gary C. Martin uncovered some Activity compatibility issues with staging-7.
- these need to be checked against the latest staging build, with the Activity version listed in Activities/G1G1.
- ...and if the bugs are still present, they need to be filed in Trac...
- ...and the Activity maintainers contacted. Read http://lists.laptop.org/pipermail/testing/2009-January/000695.html for context before contacting Activity developers; also check to see if a later version of the Activity (which may not be listed in Activities/G1G1) might have the bug fixed.
Some specific bugs to look for:
Ticket closure
See and verify "test in build" items from trac; this is mostly bookkeeping.