Ideas for testers (what needs testing?)
This Sunday I will be hosting a small Happy Dev House event in Wellington (NZ) and an ex-colleague who is a top-notch professional software tester will be coming around with possibly some more testers. Are there areas or builds that needs special focus? I have given Shaun links to the Testing pages in the wiki, and what we have available is - 1 B4 - 1 MP - As many qemu VMs as we want ;-) Should they go through the smoketest on joyride? Or faster? Note that they are new to the XO+Sugar, though familiar with linux. For testing on the XOs I need to know what image they'll need to have on the XOs so I can prepare them beforehand ;-) (Of course I'll bring an XS with me to the event ;-) but it doesn't have that much test surface specially for new testers.) cheers, m -- [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: Ideas for testers (what needs testing?)
This seems like a smart place to start devoting some time. I will have a look into it tonight... see if I can help with a test plan or something in that direction. Shaun From: Wade Brainerd [mailto:[EMAIL PROTECTED] Sent: Thursday, 1 May 2008 18:12 To: Martin Langhoff Cc: Boyce, Shaun (WELLBSD); OLPC Devel Subject: Re: Ideas for testers (what needs testing?) On Thu, May 1, 2008 at 2:09 AM, Martin Langhoff [EMAIL PROTECTED] wrote: On Thu, May 1, 2008 at 5:37 PM, Wade Brainerd [EMAIL PROTECTED] wrote: I would really appreciate testing in Colors! and Bounce (still waiting for #6766 to get them into joyride). Particularly, reliable steps to reproduce any bugs in Colors! collaboration mode. http://wiki.laptop.org/go/Colors%21 http://wiki.laptop.org/go/Bounce Cool. Any guidance as to what to look for? Can we cc the devel list about this? No real test plan guidance has been developed, they are just activities that I developed on my own without much feedback from the community. When I get a feature working I move on to the next one, but there hasn't been extensive testing on either. If you do come up with a test plan for these, I would love to see it get added to their wiki pages so future testers can repeat them. Thanks! Wade The information in this message is the property of the New Zealand Department of Corrections. It is intended only for the person or entity to which it is addressed and may contain confidential or privileged material. Any review, storage, copying, editing, summarising, transmission, retransmission, dissemination or other use of, by any means, in whole or part, or taking any action in reliance upon, this information by persons or entities other than intended recipient are prohibited. If you received this in error, please contact the sender and delete the material from all computers.___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Ideas for testers (what needs testing?)
On Fri, May 9, 2008 at 4:17 AM, Steve Holton [EMAIL PROTECTED] wrote: Is there a set of requirements against which testers should be testing? I don't think we have that. We do have some test guides that show some basic steps that are expected to work. We work to high-level specs. It seems a recipe for dumping the designers into the hell of constantly, interactively explaining to the testers what was expected, what wasn't, and why. It's not *that* bad ;-) Explore it, figure it out - after all, that's what we expect our end users to do! - and of needed, ask the original designers and developers for some explanation (that can hopefully be captured in the wiki as documentation). This approach has worked fantastic for Moodle and other projects. The alternative is to line up an army of technical writers, and I've only heard of one around here so far... cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Ideas for testers (what needs testing?)
On Thu, May 8, 2008 at 4:19 PM, Martin Langhoff [EMAIL PROTECTED] wrote: On Fri, May 9, 2008 at 4:17 AM, Steve Holton [EMAIL PROTECTED] wrote: It seems a recipe for dumping the designers into the hell of constantly, interactively explaining to the testers what was expected, what wasn't, and why. It's not *that* bad ;-) Explore it, figure it out - after all, that's what we expect our end users to do! - and of needed, ask the original designers and developers for some explanation (that can hopefully be captured in the wiki as documentation). This approach has worked fantastic for Moodle and other projects. The alternative is to line up an army of technical writers, and I've only heard of one around here so far... That seems to be the case. And it's hard to argue with success. As long as nobody is going to get upset when I test, then I suppose I'll be as happy as a clam. -- Steve Holton [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Ideas for testers (what needs testing?)
On Thu, May 1, 2008 at 2:09 AM, Martin Langhoff [EMAIL PROTECTED] wrote: On Thu, May 1, 2008 at 5:37 PM, Wade Brainerd [EMAIL PROTECTED] wrote: I would really appreciate testing in Colors! and Bounce (still waiting for #6766 to get them into joyride). Particularly, reliable steps to reproduce any bugs in Colors! collaboration mode. http://wiki.laptop.org/go/Colors%21 http://wiki.laptop.org/go/Bounce Cool. Any guidance as to what to look for? Can we cc the devel list about this? No real test plan guidance has been developed, they are just activities that I developed on my own without much feedback from the community. When I get a feature working I move on to the next one, but there hasn't been extensive testing on either. If you do come up with a test plan for these, I would love to see it get added to their wiki pages so future testers can repeat them. Thanks! Wade ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Ideas for testers (what needs testing?)
Hi all, In the wiki there are testing guides that could do as reference for Colors and other activities. http://wiki.laptop.org/go/Activity_testing_guide. 2008/5/1 Wade Brainerd [EMAIL PROTECTED]: Actually I should mention that Colors! has a bug list going on its Development page: http://wiki.laptop.org/go/Colors%21/Development Some of those may have regressed since they were marked fixed, I feel like I have seen the blank toolbar happen recently. -Wade ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Rafael Enrique Ortiz Guerrero One Laptop Per Child [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Ideas for testers (what needs testing?)
[resend - now via the list properly] This Sunday I will be hosting a small Happy Dev House event in Wellington (NZ) and an ex-colleague who is a top-notch professional software tester will be coming around with possibly some more testers. Are there areas or builds that needs special focus? I have given Shaun links to the Testing pages in the wiki, and what we have available is - 1 B4 - 1 MP - As many qemu VMs as we want ;-) Should they go through the smoketest on joyride? Or faster? Note that they are new to the XO+Sugar, though familiar with linux. For testing on the XOs I need to know what image they'll need to have on the XOs so I can prepare them beforehand ;-) (Of course I'll bring an XS with me to the event ;-) but it doesn't have that much test surface specially for new testers.) cheers, m -- [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
