Community testing meetings/2008-10-30: Difference between revisions

From OLPC
Jump to navigation Jump to search
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{TOCright}}
{{TOCright}}


'''''This is a pre-meeting agenda. The meeting is in #olpc-meeting on [[Start date::October 30, 2008]] at 2100 UTC.''' Please add suggestions for agenda items to this page - we may not get to everything, but we can make sure to have a list for discussion in future meetings. If you can't make the meeting, please post your thoughts here in the appropriate section, and I'll make sure they're brought up during the meeting. [[User:Mchua|Mchua]] 01:43, 28 October 2008 (UTC)''
'''''This meeting is over - thanks to all those who participated!'' The meeting was in #olpc-meeting on [[Start date::October 30, 2008]] at 2100 UTC.''' Please join the conversation on the [http://lists.laptop.org/listinfo/testing testing mailing list] to talk about what happened (alternatively, you can use the meeting's talk page, but a post to the mailing list is likely to get read faster).

⚫
== Meeting logs ==

See exactly what happened at http://meeting.laptop.org/olpc-meeting.log.20081030_1700.html

== Attendance ==

Listed by IRC nick in order of speaking.

* joef
* mchua
* cjl
* kimquirk
* frandog
* gregdek
* cjb
* lfaraone
* Ian_Daniher
* bjordan


== Previous meeting's action items ==
== Previous meeting's action items ==
Line 7: Line 26:
''None; this is our first meeting.''
''None; this is our first meeting.''


== Activity testing ==
== Pre-meeting agenda ==

'''This was the pre-meeting agenda item - see the [http://meeting.laptop.org/olpc-meeting.log.20081030_1700.html logs] to see what was discussed.'''

=== Activity testing ===


We've been asked to tackle Activity testing as a first Big Task - we thought we'd try an Activity of the Week format, starting with [[Analyze]] (thank you Eduardo!) because that Activity itself would be a useful tool for testers to get log data from.
We've been asked to tackle Activity testing as a first Big Task - we thought we'd try an Activity of the Week format, starting with [[Analyze]] (thank you Eduardo!) because that Activity itself would be a useful tool for testers to get log data from.
Line 19: Line 42:
[[User:Mchua|Mchua]]
[[User:Mchua|Mchua]]


== Test tools ==
== Action items ==


For the next meeting. If you have an action item, you may want to read the meeting logs for context and related ideas discussed before you start.
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.


* '''gregdek''' to compile proposals/ideas/suggestions for "how to prioritize Activities to test" and lead a short discussion on that during next week's meeting
* qa-scripts to set config files, prepare XOs for certain tests
* '''cjl''' <s>to write out a first braindump on testing metrics and how to display them in ways that would be motivators to community testers and activity developers</s> '''(done!)'''
* [[XO Monitor]]
* '''mchua, lfaraone''' <s>to pair on getting a test community portal page up with the current procedure that we're using to get Activities to testable-ness, so we have something concrete to look at next meeting and it's easier to make suggestions for improvements</s> '''(done! [[Community testing]])'''
* Cjb's screencast Activity (no wiki page yet)
* '''mchua, frandog''' to find someone to work with eduardo to push out the Analyze activity testing for a first round (this is a pretty vague action item, but we can start smaller-scale - I'd like to have at least 15 people run through the test case and report results)
* a Test Activity - this is still a vague idea, but some sort of "submit a bug report!" helper
* '''cjb''' to think about how to run a Test Activity brainstorm at next week's meeting, bouncing ideas off of people as needed (kimquirk, mchua interested... others?)
* 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)

[[User:Mchua|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)

[[User:Mchua|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)

[[User:Mchua|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.

[[User:Mchua|Mchua]] 01:43, 28 October 2008 (UTC)

== Some notes on infrastructure ==

Think of these all as strawmen to be tried out now, revised next week if needed. [[User:Mchua|Mchua]]

* Meeting time/place/format?
⚫
* Meeting ground rules?

== Purpose/charter/mission of community test ==

We won't finish this discussion on the first meeting. 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.

[[User:Mchua|Mchua]]
[[Category:Test group meetings]]
[[Category:Test group meetings]]
[[Category:Community testing meetings]]

Latest revision as of 21:28, 6 November 2008

This meeting is over - thanks to all those who participated! The meeting was in #olpc-meeting on Start date::October 30, 2008 at 2100 UTC. Please join the conversation on the testing mailing list to talk about what happened (alternatively, you can use the meeting's talk page, but a post to the mailing list is likely to get read faster).

Meeting logs

See exactly what happened at http://meeting.laptop.org/olpc-meeting.log.20081030_1700.html

Attendance

Listed by IRC nick in order of speaking.

  • joef
  • mchua
  • cjl
  • kimquirk
  • frandog
  • gregdek
  • cjb
  • lfaraone
  • Ian_Daniher
  • bjordan

Previous meeting's action items

None; this is our first meeting.

Pre-meeting agenda

This was the pre-meeting agenda item - see the logs to see what was discussed.

Activity testing

We've been asked to tackle Activity testing as a first Big Task - we thought we'd try an Activity of the Week format, starting with Analyze (thank you Eduardo!) because that Activity itself would be a useful tool for testers to get log data from.

I think we need a 2-pass process; one "rough pass" week where people clean up the Activity's page, feature list, test cases, etc to make them testable by the general public - see http://wiki.laptop.org/index.php?title=Analyze&oldid=115198 and then compare to the current Analyze, and then see http://wiki.laptop.org/index.php?title=Tests/Activity/Analyze&oldid=166270 and compare to Tests/Activity/Analyze.

  • Thoughts?
  • Volunteers to help finish cleaning up Analyze for release to testing public?
  • Suggestions for next Activities to test (or good criteria for selecting one?) I was thinking Log.

Mchua

Action items

For the next meeting. If you have an action item, you may want to read the meeting logs for context and related ideas discussed before you start.

  • gregdek to compile proposals/ideas/suggestions for "how to prioritize Activities to test" and lead a short discussion on that during next week's meeting
  • cjl to write out a first braindump on testing metrics and how to display them in ways that would be motivators to community testers and activity developers (done!)
  • mchua, lfaraone to pair on getting a test community portal page up with the current procedure that we're using to get Activities to testable-ness, so we have something concrete to look at next meeting and it's easier to make suggestions for improvements (done! Community testing)
  • mchua, frandog to find someone to work with eduardo to push out the Analyze activity testing for a first round (this is a pretty vague action item, but we can start smaller-scale - I'd like to have at least 15 people run through the test case and report results)
  • cjb to think about how to run a Test Activity brainstorm at next week's meeting, bouncing ideas off of people as needed (kimquirk, mchua interested... others?)
Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=Community_testing_meetings/2008-10-30&oldid=178825"