[Testing] Test Group meeting minutes, 9/10/07

[Kim Quirk]

Attending: Zack, Kim, Cameron, Alex, Rafael, SJ, Michael Stone

   - We went over the high level schedule: We are a week behind where we
   want to be (wanted to be at code freeze today), but Quanta is 2 weeks behind
   in MP production, so we are ok right now.
   - There are many blocking bugs. This weeks big push is bug fixing. So
   the testers (and developers) need to take a new build, load it, get through
   the smoke test, and write up some notes on things that aren't working well
   in the Test Group Release
Notes<http://wiki.laptop.org/go/Test_Group_Release_Notes>.
   This will help others to know what build they want to be testing with.
   - Alex is going to create a test plan for the International laptops in
   my office. He has already found some problems so we suspect we will have to
   do more detailed testing on these laptops.


Trial-3

   - Zack will act as the lead for Trial-3, to help ensure all our test
   plans have coverage for both updating and execution. Please send him the
   list of test plans you want to update; and he will make suggestions to the
   rest of us to try ensure that all of the plans get covered.
   - When creating test plans, Zack recommends the Record (or Camera)
   test plan as a template


   - Think about the most important activities and capabilities of the
   laptop and if there is no test plan placeholder, please send that to Zack
   and me and we will try to get the placeholder into the test plans page.
   - Here is a link to the test plans we are focused on in the test
   group: Test Plans <http://wiki.laptop.org/go/User_Stories_Testing>


Rainbow:

   - Today, build 571, the first pieces of Rainbow are in the build.
   Currently turned off. 'Touch olpc-security' to turn rainbow on; restart
   sugar. But first you need to get rainbow-daemon started. Michael will
   document how to turn this on for the developer community first.
   - Control access to the filesystem means creating a filesystem with
   only the items that are needed. So the errors will usually fail in the
   activity itself.
   - So how can good information for debug be collected? Strace logs (or
   system tap) for each activity will provide per system call info - generated
   by the kernel, rather than the activity.
   - Might be useful for this reporting interface to filter out all
   errors (as one level of debug). It would be useful to have a security audit
   tab from the Developer's console.


   - Test activity idea: using the same sort of formating as Pippy - a
   tree widget on the left, open window on top right that has the python code,
   and a run button. Add a radio button for pass/fail, and submit button. If it
   was easy to install this activity many others could help out with this
   mostly manual testing. It should automatically grab the logs when tests are
   run. Sync up with latest test plans. Noah can help with the trac side
   (website). Not sure how to resource the rest right now.

- Kim

Minutes: http://wiki.laptop.org/go/TestMtg%2C_Sept_10%2C_2007<http://wiki.laptop.org/go/TestMtg%252C_Sept_10%252C_2007>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.laptop.org/private/testing/attachments/20070910/817bbc91/attachment.htm