<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#ffffff"> On 03/03/2012 08:51 PM, Thomas C Gilliard wrote: <blockquote cite="mid:4F52F4CC.7040003@bendbroadband.com" type="cite"> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> On 03/03/2012 07:35 PM, S Page wrote: <blockquote cite="mid:CANR8O7a_7vVWZBBHaMusrcrP_a_FBsWZ4dAuf9174tR7BT6DzQ@mail.gmail.com" type="cite"> <pre wrap="">Hey all, @Tabitha, I made your template prominent in <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://wiki.laptop.org/go/Activity_testing_template">http://wiki.laptop.org/go/Activity_testing_template</a> and continued the archivist job of marking old stuff as "{{obsolete|from 2008}}"... Is _anything_ under <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://wiki.laptop.org/go/Tests">http://wiki.laptop.org/go/Tests</a> still a useful test case? Maybe a mass delete or rename to Tests/old crap/Xyz is in order? A lot of those tests are linked from activity pages, e.g. <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://wiki.laptop.org/go/Memorize">http://wiki.laptop.org/go/Memorize</a> has a TST link, but most activities have moved to sugarlabs.org where none (?) of them have testing information. @Sridhar, re: </pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap="">The main piece of advice I'm getting is that we need a good test case management system that allows for linking with defects. The links need to be able to be tracked, searched and sorted. </pre> </blockquote> </blockquote> <pre wrap="">"Passive voice is to be avoided". Before spending time on features like that, be very clear who exactly is going to use them. You can do powerful querying on the 2008 w.l.o test cases, but... AFAICT nobody cared! Maybe all you actually need is to add links to bug reports in testing results, and in bug reports add links to the test case (if any) the tester was following when the bug occurred. On Sun, Feb 26, 2012 at 11:34, Samuel Greenfeld <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:greenfeld@laptop.org"><greenfeld@laptop.org></a> wrote: </pre> <blockquote type="cite"> <pre wrap="">...[lots]... </pre> </blockquote> <pre wrap="">Thanks for the background, very perceptive. As always I'm eager to assist in the wiki side of things. == Comments on various approaches == </pre> <blockquote type="cite"> <pre wrap="">In my case I've been told to use a spreadsheet. </pre> </blockquote> <pre wrap="">(More passive voice, love it ;-) Did you see the spreadsheet in <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://wiki.laptop.org/go/Community_testing_meetings/2008-11-06/Displaying_testing_metrics_in_motivating_ways"><http://wiki.laptop.org/go/Community_testing_meetings/2008-11-06/Displaying_testing_metrics_in_motivating_ways></a> ? One nice thing about using a Google Docs spreadsheet is you can publish a form front-end that anyone can use to add a row for a test result, see Carl Klitscher's form front-end <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="https://spreadsheets.google.com/viewform?key=pyBIsSK_3IlsHBpwk1EFNcQ"><https://spreadsheets.google.com/viewform?key=pyBIsSK_3IlsHBpwk1EFNcQ></a> ? @Tabitha, were you among the Wellington testers that supposedly used this? If so, did you like it? I think the Sugar activity testing spreadsheet </pre> </blockquote> 1-)Tests-Sugar-0.94.1 resulted from a need to find 0.94 sugar compatible activities Authored by Alan Jhonn Aguiar Schwyn It is flexable as a spreadsheet. with most of the features a spreadsheet offers. <blockquote cite="mid:CANR8O7a_7vVWZBBHaMusrcrP_a_FBsWZ4dAuf9174tR7BT6DzQ@mail.gmail.com" type="cite"> <pre wrap=""><a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="https://docs.google.com/spreadsheet/ccc?key=0AntaXnq4oy2_dHpvZHhLeGRQYzc1cDlRZU9Mc1NldGc#gid=0"><https://docs.google.com/spreadsheet/ccc?key=0AntaXnq4oy2_dHpvZHhLeGRQYzc1cDlRZU9Mc1NldGc#gid=0></a> appends columns for each test result, which is not amenable to a form front-end. </pre> </blockquote> 2-) full Open Office spreadsheet <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://people.sugarlabs.org/Tgillard/Activities-Index-ASLO-f13-Mirabelle-f14-rawhide-Soas-tests.ods">http://people.sugarlabs.org/Tgillard/Activities-Index-ASLO-f13-Mirabelle-f14-rawhide-Soas-tests.ods</a> and posting it on sugarlabs.wiki with links. This is hard use for a number of reporters 3-)Another approach for activity testing are this wiki tables split list on the sugarlabs wiki that I have been maintaining: I was guided to the wiki table approach early on as a good compromise. Activity tests A-I <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/Activity_Matrix%28A_to_I%29">http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/Activity_Matrix%28A_to_I%29</a> Activity tests J-Z <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/Activity_Matrix%28J_to_Z%29">http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/Activity_Matrix%28J_to_Z%29</a> An older first attempt is listed here: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_QA">http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_QA</a> fedora for their test day testing uses wiki tables. . Here they do use links to subpages of wiki tables for the actual test descriptions and testing results. <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://fedoraproject.org/wiki/Test_Results:Fedora_17_Alpha_RC4_Base">http://fedoraproject.org/wiki/Test_Results:Fedora_17_Alpha_RC4_Base</a> (is a sample from fedora 17 testing.) </blockquote> Here is an example of testing results: (I had to search for it.) <a class="moz-txt-link-freetext" href="http://fedoraproject.org/w/index.php?title=Test_Results:Fedora_17_Alpha_RC4_Install&oldid=273509#Instructions">http://fedoraproject.org/w/index.php?title=Test_Results:Fedora_17_Alpha_RC4_Install&oldid=273509#Instructions</a> <blockquote cite="mid:4F52F4CC.7040003@bendbroadband.com" type="cite"> These can be complex structures. I am not certain that anything is gained here by the complexity. But you can link to a large number of different tests and list their results This format can be more difficult to use as the reporters have to be familiar with wiki table editing. but it does have sortable columns and can include links to other information. 4-)Fedora also uses a master "tracking bug" in bugzilla that lists all of the outstanding bugs for a release and close them as issues are fixed. this does include links and attachments. . <blockquote cite="mid:CANR8O7a_7vVWZBBHaMusrcrP_a_FBsWZ4dAuf9174tR7BT6DzQ@mail.gmail.com" type="cite"> <pre wrap="">The Fedora Test Day approach on the //fedoraproject.org wiki encourages tabular reporting of test results, but I haven't found a page with any results, e.g. <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://fedoraproject.org/wiki/Test_Day:2010-08-19_Sugar"><http://fedoraproject.org/wiki/Test_Day:2010-08-19_Sugar></a>. It's similar to the external spreadsheet approach. The choice between them depends whether wiki linking (e.g. "What links here" to find out what test days exercised a particular test case) is more important than spreadsheet jockeying. I think <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://wiki.sugarlabs.org/go/Community/Distributions/Fedora-SoaS#Testing_Results"><http://wiki.sugarlabs.org/go/Community/Distributions/Fedora-SoaS#Testing_Results></a> is pretty unusable. It would be much better to create a subpage for each testing result, like SL.o used to e.g. </pre> </blockquote> 5-) <pre wrap=""><a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://wiki.sugarlabs.org/go/Community/Distributions/Fedora-SoaS#Testing_Results">http://wiki.sugarlabs.org/go/Community/Distributions/Fedora-SoaS#Testing_Results</a></pre> a single wiki page as it is more flexible for reporters to edit and for the kind of information it contains. The only indexing is via the table of contents and linking. I hope that this summary of the way I have looked at test result reporting is helpful. Tom Gilliard satellit_ on #sugar IRC freenode <blockquote cite="mid:CANR8O7a_7vVWZBBHaMusrcrP_a_FBsWZ4dAuf9174tR7BT6DzQ@mail.gmail.com" type="cite"> <pre wrap=""><a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://wiki.sugarlabs.org/go/SoaS/Testing/Soas2-200905031329"><http://wiki.sugarlabs.org/go/SoaS/Testing/Soas2-200905031329></a> , and then use {{subst:}} or Special:PrefixIndex to pull in or reference these from other pages. I summarized the four (so far!) ways sl.o has collected test results in <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://wiki.sugarlabs.org/go/SoaS/Testing"><http://wiki.sugarlabs.org/go/SoaS/Testing></a> . Good luck, -- =S Page _______________________________________________ Testing mailing list <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Testing@lists.laptop.org">Testing@lists.laptop.org</a> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.laptop.org/listinfo/testing">http://lists.laptop.org/listinfo/testing</a> </pre> </blockquote> <pre wrap=""> <fieldset class="mimeAttachmentHeader"></fieldset> _______________________________________________ Sugar-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </pre> </blockquote> </body> </html>