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.

What time? Is this still on for tomorrow? I'm inviting good QA folks to stop by after work to help out, but it's hard without details. MitchellNCharity 18:26, 16 October 2007 (EDT)

Proposed Tasks

1. Making a "Test Activity" that we can all use to manually execute the test plans stored on the wiki
2. Teaching interested people how our Tinderbox works so that you can contribute automated tests.
3. 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)
4. Figuring out how to centralize the collection and visualization of the reports generated by the "Test Activity"
5. Going through all of the old test plans, trying them out, and fixing up the parts that no longer apply
6. Working out the exact written instructions, from start to finish, for running a single activity under emulation (i.e., installing an emulator, importing a bundle, running the bundle -- including networking or mic/camera access).
7. ...

Other ideas:

• Can idle laptops be used in some way?
• Has anyone looked into tools for doing X GUI scripting and snapshots tests?
• Do we know what the threat environment looks like? And what is the testing mission/objectives are? Catch last minute hardware bugs? Help core activity writers shake down their apps? Detect late regressions? Support ofw and kernel development? Determine the top ten things which will make users happier, be they bug fixes or new features or stalled apps? Avoid "problems which would be embarrassing"? What is the relative importance of trials and xogiving? Create infrastructure for FRS? For the next 6 months? Year? Whatever mix gives the biggest bang, in whatever direction, for our highly constrained time and resources? Especially given the constraints, depending on what the goal(s) are, it seems they send us in different directions.
• What exactly are the time and resource constraints?
• What are some innovative brainstormy ideas for breaking out of them?
• 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.
• Create testing jabber/school server? The barrier to set up collaboration is currently rather high. Creating a "everyone here is pretending to be part of the same school, and is here to collaborate and test things" might make it easier.
• Ubuntu 7.10 is coming out. Can we piggy back on that attention to get testers?
• Create a .deb package so running an emulated xo is simply apt-get olpc-xo-emulation; olpc-xo-emulation --run  ?
• Can trial feedback be made more accessible? If lots of people are asking for X, that should perhaps be part of the test picture.

Coordinating

Leave your name below if you are interested in participating. Note what you want to do, whether you'll be at 1CC in person (for ordering food!), and what medium you're going to be working in. If you see someone you want to test with, you can contact them ahead of time to coordinate.

You might also watch this page so that you stay up to date on how the sprint is developing.

There are tentative plans for a shadow meeting on irc. This could be made in #olpc-meeting at a designated hour --200.13.247.18 18:26, 13 October 2007 (EDT)

And if we can find someone running an iceserver, perhaps we could stream video of the meeting from an xo. So remote folks can follow non-irc discussion, see any whiteboard sketches, etc.

Also, if you're planning on joining us in person, feel free to contact Sj at 617-529-4266 for directions.

How to help with going through Test plans

• Install the latest unstable build Autoreinstallation_image
• Go to the Tests page
• Choose a Test to review, and put your name next in the last column, so that others will not update the same test plan.
• Go through the test plan, changing the Actions and things to Verify, so that they match up with the current activity.
  • This is because many of the activities have changed since the test plans were written.
  • If there are new features in the activity, make a new test case for those features.
• Add a results link for the test plan. Use Results/News Reader as an example.
  • Basically, the sample template for the results is just a check list of all the verifications in the test plan.
• Go through your test, and add your results to the results page.

• Also, Feel free to add a test plan that you believe should exist.

Signup Sheet

• Michael Stone 19:57, 11 October 2007 (EDT) | Userland security & incremental update developer
  • m_stone on #olpc, #sugar; michael (at) laptop.org; Interested in Tinderbox and "Test Activity"
• Chris Ball - Tinderbox maintainer, cjb on IRC and at laptop.org
• Sj talk (on IRC)
• Joel Stanley - working as shenki on IRC, joel (at) laptop.org. Working from Adelaide, Australia (GMT+9:30).
• Reynaldo Verdejo reynaldo on #olpc, #sugar and @opendot.cl; Interested in the Tinderbox (on IRC) [UTC/GMT-4]
• MitchellNCharity 20:56, 11 October 2007 (EDT) - Boston-area volunteer. mncharity on IRC and vendian org.
• Shankar (on IRC and wiki)
• Rowen on IRC, #olpc, #olpcph - OLPCPH Project Manager, IT Engineer, needs an extra machine to do mesh testing, "Test Activity", Tinderbox, emulation, porting (Tiny C / tcc has been ported to XO) and others
• RafaelOrtiz Interested in Test Activity, Tinderbox and documenting the process.
• Kim Quirk Planning, execution, Test Actvity
• Alex Latham
• Jessica Baumgart
• ...