Test process sprint for 2007 first software release

Purpose

We're going to have to do an awful lot of testing in the run-up to FRS so we can either keep going as we have so far or we can work harder to find or build the tools needed to make this testing go smoothly.

The purpose of this sprint, currently scheduled for Wednesday, October 17, 2007, is to jump-start the "planning, finding, building, and using" strategy.

Proposed Tasks

• Making a "Test Activity" that we can all use to manually execute the test plans stored on the wiki

• Teaching interested people how our Tinderbox works so that you can contribute automated tests.

• Playing with ways to get better feedback out of activities (i.e. special, machine-readable logging, use of accesibility extentions for scripting, embedding small interpreters, etc)

• Figuring out how to centralize the collection and visualization of the reports generated by the "Test Activity"

• Going through all of the old test plans, trying them out, and fixing up the parts that no longer apply

• Working out the exact written instructions, from start to finish, for running a single activity under emulation.

Coordinating

We need to know who's interested in participating, what you want to do, and what medium you're going to be working in.

Therefore, please add your signatures below and, if you see someone you want to work with, please contact them ahead of time so that you're sure to overlap!

(You might also consider "watching" this page so that you stay up to date on how the sprint is shaping up.)

Signup Sheet

• Michael Stone 19:57, 11 October 2007 (EDT)
  • Userland security & incremental update developer
  • m_stone on #olpc, #sugar; michael@laptop.org
  • Interested in Tinderbox and "Test Activity"