Community testing meetings/Agenda queue

Test tools

We've got some neat ones that could use some work/help. Some details below are definitely fuzzy; please ask questions on things that aren't clear and I'll do my best to fill the details in before the meeting.

• Scripts for testing multiple XOs
• XO Monitor
• Cjb's screencast Activity (no wiki page yet)
• a Test Activity - this is still a vague idea, but some sort of "submit a bug report!" helper
• Finding a way to have XOs more easily (...automatically?) upload test logs to Some Central Server That Is As Of Yet Undefined
• Reuben's "configuration magic" scripts (soon to be in git)
• Others?

(Note that we might discuss this in a future meeting if we run out of time)

Mchua 01:43, 28 October 2008 (UTC)

Test automation

• This is a big deal. We need a lot of work/help here.
• Ideas? Suggestions?

(Note that we might discuss this in a future meeting if we run out of time)

Mchua 01:43, 28 October 2008 (UTC)

Tests that are hard for volunteers to replicate

• Volunteers who don't have XOs
• Volunteers who don't have many XOs

Ok, so things like "50 XO collaboration" are probably not testable by many people... how can (should?) we still keep you up to date on what is going on with testing in the office?

What can you still test without "equipment?"

What tools/equipment/infrastructure/support/encouragement/resources can we provide - both from OLPC, and from volunteers to each other - to help get testing done? LiveCDs and emulators? What do we think is worth our effort to create/maintain, given that everyone has limited resources and time?

(Note that we might discuss this in a future meeting if we run out of time)

Mchua 01:43, 28 October 2008 (UTC)

Learning and teaching testing

Some people have expressed a desire to use this group as a way/motivation to study testing, as a way of building skill - I'd like to get out some ideas for how we might do that; we've had some very generous volunteers who've offered to help teach/mentor new testers in the community.

Mchua 01:43, 28 October 2008 (UTC)

Purpose/charter/mission of community test

We won't finish this discussion on the first meeting it's discussed at. We'll barely even start it. But we can get some thoughts on on the table. I'd like to spend no more than 10 minutes just hearing initial thoughts on this - no judgement, no decisions, just ideas - and send the conversation to the mailing list to get thoughts going in the background as we continue to test. I think this conversation will make much more sense in several weeks once we've gotten a working idea of how we, as a community test group, function.

When developers have a patch to try out

We need a good way to handle these "developers have made something and need people to try it out!" requests, like Erik Garrison's "I think this improves performance; can someone try it?" query earlier. Suggestions for good ways to batch-process/recruit for these? Should we have a Developer Liason lead for the community test group for each build (a 6-month cycle)? Mchua 20:57, 5 November 2008 (UTC)

Test Activity brainstorming (cjb)

What kind(s) of Sugar Activities could we make / request for community testing?

Some notes on infrastructure

• How are these meetings working out for people?
• Feedback on meeting time/place/format?
• Are there any ground rules/procedures we should obviously set? (Answer will probably be no this time - that's great, we'll keep an eye out and bring this up again in a few weeks)