Community testing meetings/2008-11-06: Difference between revisions
Jump to navigation
Jump to search
m (→Test tools) |
mNo edit summary |
||
| Line 11: | Line 11: | ||
=== Status of Analyze testing (mchua, frandog) === |
=== Status of Analyze testing (mchua, frandog) === |
||
[[Analyze]] is the first Activity going through community test |
[[Analyze]] is the first Activity going through community test ([[Paint]] will probably be the second, if [[User:Bjordan]] or someone else is willing to lead). Quick status update on how this is going. |
||
=== Prioritizing Activities to test (gregdek) === |
=== Prioritizing Activities to test (gregdek) === |
||
What options/tools are out there? |
|||
=== Displaying testing metrics in motivating ways (cjl, from notes) === |
=== Displaying testing metrics in motivating ways (cjl, from notes) === |
||
What options/tools are out there? |
|||
=== Current Activity prep-for-test procedure feedback (lfaraone, mchua) === |
=== Current Activity prep-for-test procedure feedback (lfaraone, mchua) === |
||
We'll have a portal page with the current procedure up, so it's a little easier to discuss. |
|||
== Test Activity brainstorming (cjb) == |
== Test Activity brainstorming (cjb) == |
||
What kind(s) of Sugar Activities could we make for community testing? |
|||
== 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) |
|||
[[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 == |
== Some notes on infrastructure == |
||
* How are these meetings working out for people? |
|||
Think of these all as strawmen to be tried out now, revised next week if needed. [[User:Mchua|Mchua]] |
|||
| ⚫ | |||
* 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) |
|||
| ⚫ | |||
* 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]] |
||
Revision as of 05:49, 31 October 2008
This is a pre-meeting agenda.The meeting is in #olpc-meeting on Start date::November 11, 2008 17:00 (Eastern standard time in the USA).
Previous meeting's action items
See Testing meetings/20081030#Action items.
Activity testing
Status of Analyze testing (mchua, frandog)
Analyze is the first Activity going through community test (Paint will probably be the second, if User:Bjordan or someone else is willing to lead). Quick status update on how this is going.
Prioritizing Activities to test (gregdek)
What options/tools are out there?
Displaying testing metrics in motivating ways (cjl, from notes)
What options/tools are out there?
Current Activity prep-for-test procedure feedback (lfaraone, mchua)
We'll have a portal page with the current procedure up, so it's a little easier to discuss.
Test Activity brainstorming (cjb)
What kind(s) of Sugar Activities could we make 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)