Howdy people, I'm not ignoring you but I'm trying to play catchup with
email and finish coordinating some testing for the iOS app. I'll respond
in detail to this tonight or this weekend.
On Fri, Dec 14, 2012 at 3:17 PM, Chris McMahon <cmcmahon(a)wikimedia.org>wrote;wrote:
>> 2. Decide a mobile area to focus, a way
to run the sprint and a date
>> for it. Define also the goals and how to measure the success of the sprint.
I'm on board too, but I would like to suggest that Michelle spearhead
..."a way to run the sprint" is the tricky part. I think there are
basically two options: synchronous and asynchronous. Synchronous is
arguably more difficult, so lets' talk about that option first...
Synchronous test event: we did this successfully for AFTv5. Here is the
test plan that I used:
. That test
plan is based on ideas from "Session Based Test Management",
(Just btw, the
software testing articles on enwiki are pretty awful, someday I'd like to
clean them all up, but it's a big job)
I borrowed a lot of details for synchronous test events from the Weekend
Testing Americas group. They found some time ago that Saturdays from
10AM-1PM Pacific time is generally more successful than other times. We
had a dedicated test environment and an irc channel. Everyone worked at
the same time and collaborated on IRC simultaneously, and it was more fun
than you might imagine.
Asynchronous test event: For a period of time (a day? a week?) I'm not
sure...) everyone participating is testing on their own, pending whatever
collaboration they can create among themselves I guess. I think a test
plan with "charters" would be required for an async test event, as well as
a coordinator to field information, feedback, questions, etc. from
participants. I think Yuvi has done this before for mobile, but I don't
know any details.
Brain dump complete, comments welcome.