The ideal actually would be to capture something like this in a test case and plan management tool like test link (<a href="http://www.testlink.org">http://www.testlink.org</a>). Do we have any plans to utilize such a tool in OLPC Testing? <br>
<br>The objective of such granular test cases is really about predictable regression testing and to have some sense of test coverage and a quantitative measure of the overall stability of a particular build. In test link these reports are auto generated once you run a series of test cases (e.g. % test cases that have failed/passed/blocked on a particular activity, or on the whole product). Based on this you can make decisions on weather you are ready to make a public release and if you should include/not include a particular activity in the release. <br>
<br>I still do not think it is effective to put this level of granularity each as a seperate test case in the WIKI as is as
it just creates one long page, that is far less usable for a testing
than quickly updating a spreadsheet. Also please note that each build will have a new updated set of WIKI pages (or spreadsheets) or test case results, so this approach is really messy to implement in the WIKI. Test link however effectively manages different build/release test results separately in it's database.<br>
<br>BTW the value of navigation structure I shared before, was again a
mechanism for verifying coverage. ie the doc can be used to check with developers/community if we
have covered all aspects of a particular activity at a high level (with the test cases giving more detail).<br><br>-- <br>Chamindra de Silva<br>Home:
<a href="http://chamindra-de-silva.blogspot.com">http://chamindra-de-silva.blogspot.com</a><br><br><br><br><br><br><br><div class="gmail_quote">On Mon, Apr 12, 2010 at 10:30 PM, Richard Smith <span dir="ltr"><<a href="mailto:richard@laptop.org">richard@laptop.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">> recreating these test cases in the WIKI (which might not be scalable), we<br>
> felt the best would be to upload the spreadsheet against each activity in<br>
> something like the test matrix page here<br>
> <a href="http://wiki.laptop.org/go/Testing_matrix" target="_blank">http://wiki.laptop.org/go/Testing_matrix</a>. Additionally subsequent for future<br>
> builds, testers can then just download these test templates and go through<br>
> the spreadsheets, perform the tests and report summaries only to the matrix.<br>
> This then gives you some degree of coverage and test predictability and will<br>
> be IMO be much easier for testers to work with.<br>
<br>
</div>Could you use google documents for this and share the spreadsheets<br>
that way rather than templates off of the wiki?<br>
<font color="#888888"><br>
--<br>
Richard A. Smith<br>
</font></blockquote></div><br><br>