<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
<img src="http://gfx2.hotmail.com/mail/w4/pr01/ltr/emoticons/smile_teeth.gif" width="19" height="19" alt=""> Sounds great! So much better than just poking around to see what works.<div><br></div><div>Caryl<br><br>Date: Tue, 22 Jun 2010 09:37:59 +1000<br>From: quozl@laptop.org<br>To: testing@lists.laptop.org<br>Subject: [Testing] Update on SoaS testing process<br><br><pre>For those yet to discover it, SoaS is a USB stick bootable build of<br>Fedora with Sugar. Testing the activities in the context of SoaS may<br>improve the quality of activities that eventually reach XO builds.<br> <br>-- <br>James Cameron<br><a href="http://quozl.linux.org.au/">http://quozl.linux.org.au/</a><br></pre><br><br>--Forwarded Message Attachment--<br>Date: Mon, 21 Jun 2010 16:26:39 -0400<br>From: mel@melchua.com<br>To: soas@lists.sugarlabs.org<br>Subject: [SoaS] Update on SoaS testing process<br><br><pre>We're getting together a testing process and infrastructure for SoaS <br>(which should be generally adaptable to Sugar and Activities in the <br>future). This is a weekly report of progress; I'll try to do these <br>before SoaS weekly meetings <br>(<a href="http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_meetings">http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_meetings</a>) in the future.<br> <br>Current progress is at <br><a href="http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Testing_process">http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process#Testing_process</a><br> <br>Our test process, which is under construction, will consist of the <br>following:<br> <br># An agreed-upon image each week for testers to attack. This will be the <br>nightly build as of 23:59:59 GMT each Thursday.<br># An agreed-upon set of test cases for them to execute (iow, the "test <br>plan" thing we haven't had before)<br># An agreed-upon place and format for the results from running those <br>test cases to be reported to<br># An agreed-upon $datetime each week by which all test results for that <br>week will be submitted - so that the development team has a chance to <br>look at those results and revise the build before the next test image <br>goes out.<br> <br>The first thing we are doing is getting a weekly image under test to <br>automatically appear at a static link. We are going to set up a cron job <br>so the nightly build (from <br><a href="http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/">http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/</a> - which we <br>need to start up again from the Fedora side) grabs and archives the <br>appropriate image-under-test to <a href="http://download.sugarlabs.org/soas/test/">http://download.sugarlabs.org/soas/test/</a> <br>(which was just created for this very purpose).<br> <br>Once that is working, we will create a place to report test results, <br>write a first example test case, and put out our first weekly call for <br>testing.<br> <br>For those who want to get started helping with testing and don't know <br>where to start, writing test cases for Activities is a fine way to do <br>it. For an example, see <a href="http://wiki.laptop.org/go/Tests/Activity/Analyze">http://wiki.laptop.org/go/Tests/Activity/Analyze</a> <br>- think of test cases as "scripts for human beings rather than <br>computers," and you won't be far off. A newcomer should be able to <br>follow your instructions, start to finish, without needing to ask any <br>questions, and end up completing exactly the same process and getting <br>exactly the same results you did.<br> <br>--Mel<br>_______________________________________________<br>SoaS mailing list<br>SoaS@lists.sugarlabs.org<br><a href="http://lists.sugarlabs.org/listinfo/soas">http://lists.sugarlabs.org/listinfo/soas</a><br></pre></div> </body>
</html>