<div class="gmail_quote">On Thu, Feb 25, 2010 at 7:07 AM, Mel Chua <span dir="ltr"><<a href="mailto:mel@melchua.com">mel@melchua.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="im">
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Seconded, as we are all volunteers an asynchronous model might make most<br>sense. Especially when there is little time to do things one has to be<br>
organized well and the teams must have a process they can follow and be<br>sure others get to the results.<br></blockquote><br></div>Yep. One thing I think might be helpful is making the weekly test/development cycle more explicit - sounds like we already have one (we have weekly dev meetings, there are weekly QA meetings in Welly) but I'm not exactly clear on the timing of the two, or when each group is reporting results back and forth to each other.<br>
</blockquote>
<div> </div>
<div>Just to update everyone on NZ's progress.. we now have two testing groups meeting weekly: one in Auckland (led by Tabitha), one in Wellington (led by a small consortium/tbc/is that important?) & another small cadre in Christchurch. We meet every Saturday our time, which is late Friday afternoon in the USA or about midnight Friday in Europe.</div>
<div> </div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>So being able to say "at each week's development meeting, we'll look at <list>, and email <this stuff!> to the testing list", and vice versa for each week's QA meeting, may be useful for getting us into a rhythm. </blockquote>
<div> </div>
<div>I don't think anyone from here (NZL) will ever be able to regularly attend any of the Sugar/OLPC weekly meetings. They're generally on around 1300-1500 UTC, which is roughly 1am - 3am here.. </div>
<div> </div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="im">
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I would love there to be one webpage for test requests that has some<br>visual indicator of how many people testing it and how close to<br>
finished testing it is, with a big tick next to it when it has been<br>tested thoroughly.<br></blockquote></blockquote></div>
<div class="im">
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Yes, that sounds very good indeed. I guess we do not have any<br>infrastructure for the working scenario you describe (yet)?<br>
</blockquote><br></div>Not that I know of - though I'd love this as well. I'm setting up a Semantic MediaWiki test case system similar to the one we had at OLPC, just to have something to get started on. No firm date on when that's going to be completed, though I'm going to be tackling getting that infrastructure up this coming Friday.
<div class="im"> </div></blockquote>
<div> </div>
<div>I'm against bespoke development in this area, unless the alternatives are untenable. I would prefer if we evaluate some of the current UAT testing tools - if they're unsuitable for our needs, then building something ourselves makes sense.</div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="im"><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I know Mel wanted to do QA for her upcoming pilot and was involved in<br>the QA efforts at olpc. Mel, do you have any thoughts about testing<br>
tools that allows what Tabitha describes? Testlink [1] was mentioned<br>already, for example.<br></blockquote></div>Not off the top of my head... general consensus of the past year or so asking QA folks about FOSS testing platforms is "there aren't any *really* good ones, FOSS or non-FOSS." Something we should keep pushing on, though.<br>
<br>My questions:<br><br>1. Where's the mailing list for Sugar Labs testing (on any platform - XO, SoaS, other)? (I'm guessing <a href="mailto:testing@lists.laptop.org" target="_blank">testing@lists.laptop.org</a> - that's fine, we should let everyone know that's the canonical location.)<br>
<br></blockquote>
<div>I think most testing discussion happens on the sugar devel list. Don't know if there is a specific Sugarlabs testing list. In keeping with my message to coordinate things between OLPC/Sugarlabs/Activity developers - I promote huddling around the <a href="mailto:testing@lists.laptop.org" target="_blank">testing@lists.laptop.org</a>.</div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">2. What's the weekly report that SL dev will give testing (and testing wants/needs to get from dev)? (Someone on the devel list should have the responsibility of pinging the testing list once a week to relay this over.) When will this be sent?<br>
</blockquote>
<div> </div>
<div>I don't know if there is a weekly report.. this might generate quite a lot of admin overhead. </div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">3. What's the weekly report that SL testing will give dev (and dev wants/needs to get from testing)? (Someone on the testing list should have the responsibility of pinging the devel list once a week to relay this over.) When will this be sent?<br>
<br></blockquote>
<div> </div>
<div>Since testing is often more than Sugar, I don't know if this could be achieved. I support each group/individual reporting back once she or they have something to report. Once we have a more formal structure established, then we can consolodate on email traffic.</div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">4. Is everyone hanging out in #sugar as they have questions on Sugar QA? If not, how do we get them there?<br>
</blockquote>
<div> </div>
<div>I've found #sugar to be pretty unresponsive when I'm active, because few other people are. Planning around an asynchronous model was suggested earlier in the thread.</div>
<div> </div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Basically, I'm trying to figure out the rhythm and the back-and-forth we already have - because we do already have it - so we can use it more effectively.<br>
<font color="#888888"><br>--Mel</font></blockquote></div>