User:Mchua/Sandbox: Difference between revisions
m (Walter's rectum 21/Sandbox moved to User:Mchua/Sandbox over redirect: revert) |
|||
(7 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
⚫ | |||
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 == |
== 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. |
|||
== Documentation == |
|||
[[Release notes/8.2.1]] needs to be updated with things like... |
|||
* instructions on how to use OFW's new multi-key + nand-blaster support |
|||
* ALL laptops show the 'pretty boot' animation now... not just secured laptops, this isn't a bug. |
|||
== Wireless == |
== 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 == |
== Activity compatibility == |
||
Line 14: | Line 35: | ||
Some specific bugs to look for: |
Some specific bugs to look for: |
||
* [http://lists.laptop.org/pipermail/testing/2009-January/000694.html in Etoys] |
* [http://lists.laptop.org/pipermail/testing/2009-January/000694.html in Etoys] |
||
* [http://lists.laptop.org/pipermail/testing/2009-January/000701.html in Browse] [http://lists.laptop.org/pipermail/testing/2009-January/000696.html more in Browse] |
* [http://lists.laptop.org/pipermail/testing/2009-January/000701.html in Browse] [http://lists.laptop.org/pipermail/testing/2009-January/000696.html more in Browse] [http://dev.laptop.org/raw-attachment/ticket/9112/ filed in Browse] |
||
== 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. |
Latest revision as of 16:01, 20 December 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.
Documentation
Release notes/8.2.1 needs to be updated with things like...
- instructions on how to use OFW's new multi-key + nand-blaster support
- ALL laptops show the 'pretty boot' animation now... not just secured laptops, this isn't a bug.
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.