User:Sethwoodworth/frs: Difference between revisions
Jump to navigation
Jump to search
(New page: Functional: * We check that the image actually boots. * We check that the network comes up. * We check that X and sugar started okay. performance tests: * We time how long it took to boot ...) |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
cjb: |
|||
Tinderbox |
|||
Functional: |
Functional: |
||
* We check that the image actually boots. |
* We check that the image actually boots. |
||
* We check that the network comes up. |
* We check that the network comes up. |
||
* We check that X and sugar started okay. |
* We check that X and sugar started okay. |
||
* Check main-pieces-of-software startup times independently |
|||
performance tests: |
|||
Performance tests: |
|||
* We time how long it took to boot up |
* We time how long it took to boot up |
||
* We do a suspend/resume cycle, see hom long it took, whether it worked |
* We do a suspend/resume cycle, see hom long it took, whether it worked |
||
* We run Python/X/cairo benchmarks. |
* We run Python/X/cairo benchmarks. |
||
Functional activity tests: |
|||
* None yet, need automated: Activity X does not work in build Y |
|||
* Possibly Dogtail |
|||
Need community involvement, and perhaps automated testing. |
|||
---- |
|||
[http://www.newegg.com/Product/Product.aspx?Item=N82E16820208058 Newegg 1gb flashdrive $8.99] |
|||
Ubuntu Live-CD + 1 GB USB stick = emululated xo. Camera and TamTam sound don't work. Some other issues. But $300 might make a school computer lab into an xo cluster. We could spin up classes exercising, say, Write's collaboration, and reporting problems. |
|||
---- |
|||
[12:27] <_sj_> everyone should have to publish "What I Did On My XO" reports every week |
|||
---- |
|||
How can we get more unscripted testing? To detect things like 'small child carrying laptop will close it when moving from place to place. even in the midst of taking photos. so a closing-breaks-Record bug is more of an issue than one might expect from adult use'. |
|||
---- |
|||
Latest revision as of 19:35, 17 October 2007
cjb: Tinderbox
Functional:
- We check that the image actually boots.
- We check that the network comes up.
- We check that X and sugar started okay.
- Check main-pieces-of-software startup times independently
Performance tests:
- We time how long it took to boot up
- We do a suspend/resume cycle, see hom long it took, whether it worked
- We run Python/X/cairo benchmarks.
Functional activity tests:
- None yet, need automated: Activity X does not work in build Y
- Possibly Dogtail
Need community involvement, and perhaps automated testing.
Ubuntu Live-CD + 1 GB USB stick = emululated xo. Camera and TamTam sound don't work. Some other issues. But $300 might make a school computer lab into an xo cluster. We could spin up classes exercising, say, Write's collaboration, and reporting problems.
[12:27] <_sj_> everyone should have to publish "What I Did On My XO" reports every week
How can we get more unscripted testing? To detect things like 'small child carrying laptop will close it when moving from place to place. even in the midst of taking photos. so a closing-breaks-Record bug is more of an issue than one might expect from adult use'.