Hi Bryan,<br>My best advice to you is to document everything you do. Use a spreadsheet or a wiki page if you don't have a good database system.<br><br>Here are some of the thinks I have found useful:<br><br>1 - Document the test case separately from its execution (you'll find some test cases in links below)<br>
2 - For each execution of a test, track the date, time, build information, and any setup, initialization that you might have done before starting, and the result<br>3 - When you do find problems, you can recreate the run -- and you have all the info for a good bug report. Link the test case run to the bug report.<br>
4 - Document the bugs found and how to work around them in human readable form (so the next person, with less technical background doesn't have to go through what you did) - this level of documentation becomes the 'release note' for a build. <br>
<br>Item #4 is really, really important since we never get to a bugless product -- but if we understand the bug and can explain work arounds, then the quality of the system just improved tremendously.<br><br>Since you are doing this focused effort... please add your findings to the release notes that have been started for build 703: <a href="http://wiki.laptop.org/go/OLPC_Update.1_Software_Release_Notes">http://wiki.laptop.org/go/OLPC_Update.1_Software_Release_Notes</a><br>
<br>For things to test, please look at the wiki pages with test scenarios for both the XO and the XS:<br><br><a href="http://wiki.laptop.org/go/User_Stories_Testing">http://wiki.laptop.org/go/User_Stories_Testing</a> (use case testing. This might be where you want to start; including the 1 hour smoke test)<br>
<a href="http://wiki.laptop.org/go/Update.1">http://wiki.laptop.org/go/Update.1</a><br> (links to many other test cases; skim this to decide where you want to focus. Items here are more technical, less 'use case')<br>
<a href="http://wiki.laptop.org/go/Schoolserver_Testing">http://wiki.laptop.org/go/Schoolserver_Testing</a><br><br>Also, use the 'Testing' link from the main page to skim around all the ideas related to testing. Please understand that we haven't had anyone keeping up all these pages so some tests will be out of date. If you can fix any of them up (based on how the product really works today), or if you want to add some, that would be great!<br>
<br>Focus on the things that are important for your deployment first.<br><br>Good luck! Hope you find things to add to the release notes for others!<br>Kim<br><br><br><div class="gmail_quote">On Sat, Apr 12, 2008 at 6:30 AM, Bryan Berry <<a href="mailto:bryan.berry@gmail.com">bryan.berry@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I will spend the next 7 days locked in our office doing QA on 150 XO's,<br>
the XS, and our Access Points.<br>
<br>
I don't have much work experience doing large-scale QA. Can someone<br>
point me to a free on-line resource of how to do it well?<br>
<br>
thanks<br>
<br>
Bryan<br>
Kathmandu<br>
<br>
_______________________________________________<br>
Server-devel mailing list<br>
<a href="mailto:Server-devel@lists.laptop.org">Server-devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/server-devel" target="_blank">http://lists.laptop.org/listinfo/server-devel</a><br>
</blockquote></div><br>