[Testing] Test Meeting Minutes, 2008-01-07
Chih-yu Chao
chihyu.mit at gmail.com
Mon Jan 7 15:01:47 EST 2008
Another thing I didn't get a chance to mention is the content bundle
for joyride builds. I reported this issue to SJ, but the new bundle
still can't be installed on joyride 1489 (the build I am testing).
http://dev.laptop.org/ticket/5840#comment:2
I will also add this item to the meeting minutes.
Thanks a lot!
Chih-yu
On Jan 7, 2008 2:35 PM, Kim Quirk <kim at laptop.org> wrote:
> http://wiki.laptop.org/go/TestMtg%2C_2008-01-07
>
> Attending: Jim, Kim, Chih-yu, Daniel, Michail
>
> Automated Testing - Tinderbox
> Try to get tinderbox back up and running (talk with Chris about what kind
> of help he can use)
>
>
> Activity Testing - Goal is to push activities into the community for testing
>
> OLPC testing (things that can only be tested at 1CC at this time)
> Connectivity
> Performance
> Scaling
> New features/functionality
>
>
> Testing thoughts for Update1:
> Resurrect the list of B2 exhaustive test spreadsheet to get into major
> release
> Augment one-hour test to include all the new features
> Add known bugs to the test cases: ie. when you change X, you need to test
> scroll pad
> Add scaling and performance tests
> Add school server testing with Laptops
> Signed OS images can be reinstalled from the school server
> Backup from XO to school server; restore
> olpc-update should work with the school server
> local jabber
> Olpc-update on all three supported encryption infrastructure AP (no
> encryption, wep, wpa) and school server.
> New wireless driver testing (need specific test cases)
>
>
> Upcoming changes:
> Security fix in X is coming; will we have to take it in Update1?
> Q2D08, too many bug fixes for the ship2.2 patch - would be good for Update1
> EC code fixes for suspend and resume could go into Update1
> Wireless firmware, p49 (already in Update1)
> Is it going to be possible to turn OFF the automated update - should this
> feature be in ship2.2?
> Can Dennis help with 656 usb missing file?
>
> Chih-yu:
> One-hour smoke test took about 2 days - due to network access and some
> journal interaction.
> One thought is that you should reboot just before you start 656 testing...
> this shouldn't be as bad in joyride/Update1
> If there is still a very slow sugar frame bug; it needs to be logged in
> trac
> If there is still memory hogging after 2 days of no reboots in joyride;
> that is a bug
>
> Michail:
> Wireless driver was entirely rewritten and will need a lot of testing.
> Perhaps this big a rewrite is too risky for Update1
> 5.110.22.p0 is currently under test
> Some timing related issues, such as retries
> Remove some excessive debug events
>
> Control panel feature requests:
> Be able to turn off all probe requests
> mDNS doesn't get repeated by the mesh in a classroom environment
> (dense/classroom scenario) for specific applications
>
>
More information about the Testing
mailing list