TestMtg, Sept 10, 2007
Attending: Zack, Kim, Cameron, Alex, Rafael, SJ, Michael Stone
- We went over the high level schedule: We are one to two weeks behind where we want to be, but Quanta is 2 weeks behind in MP production, so it isn't a
Trial-3
- Zack will act as the lead to help ensure all our test plans have coverage for both updating and execution. Please send him
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. First 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).
