Nice. Very helpful. I'll forward these thoughts to the team. Thanks,
-=michael=- -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Kohl Sent: Thursday, August 18, 2005 9:55 AM To: [email protected] Subject: RE: [Wtr-general] A general question about the role ofscriptedtestswithin the responsibilities of QA. > I guess I've assumed that code thoroughly tested by > developers would reduce the time QA spends documenting > issues, but that the QA engineer would still have an > obligation to manually exercise all the simple test cases. > Is this not true? Well tested and testable code reduces the length of feedback cycles. The days of bad builds, things that won't install, and basically untestable software that leaves testers twiddling their thumbs is greatly reduced. Instead of logging a lot of the easy, obvious bugs, testers can focus on areas of risk, and some of the trickier bugs. At some point, hopefully this becomes common place, and the testers can start spending time designing the really (as Chris McMahon would say) hairy test cases. Instead of doing basic tests, they can stretch out and really get their minds and skills behind more testing. Then you get a nice diverse, thorough test instead of a rush near the end once the code stabilizes. -Jonathan > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Bret > Pettichord > Sent: Thursday, August 18, 2005 9:30 AM > To: [email protected] > Subject: Re: [Wtr-general] A general question about the role > ofscripted tests within the responsibilities of QA. > > > With little developer testing, testers often have to run lots > of simple tests to uncover simple bugs. > > Getting the developers more involved in testing should allow > the testers to move to more complex tests more quickly. > > At 11:21 AM 8/18/2005, Michael Kelly wrote: > >Content-class: urn:content-classes:message > >Content-Type: multipart/alternative; > > boundary="----_=_NextPart_001_01C5A410.E2FD8D11" > > > >My developer chums and I use Watir as part of our test-driven > >development. As such, we're giddy to be able to finally write unit > tests > >for the UI. But the presence of these developer written UI test > scripts > >raises questions about what impact, if any, they will have > on what our > QA > >engineer will focus on. It's tempting to suggest that there > is a whole > > >set of functionality that they simply don't have to test manually > >anymore. But clearly this is just wrong, wrong, wrong. The > developers > > >will only write tests for the things they think of, and we all know > that > >developers tend to be optimistic about their code. In addition, the > unit > >tests themselves can have flaws that cause a test to pass > when the code > is > >not, in fact, functioning properly. > > > >So, it seems that we still need the QA engineer to do a full > manual QA > >pass on the software. At what point do these scripts allieviate some > of > >the QA engineer's manual testing burden? > > > >Thanks for your thoughts, > > > >-=michael=- > > > >-- > >Michael Kelly > >Sr. Software Engineer > >Eleven Wireless Inc. - The Possibilities are Wireless > ><http://www.elevenwireless.com/>http://www.elevenwireless.com > ><?xml:namespace prefix = o ns = > >"urn:schemas-microsoft-com:office:office" /> > > > > > > > >_______________________________________________ > >Wtr-general mailing list > >[email protected] > >http://rubyforge.org/mailman/listinfo/wtr-general > > _____________________ > Bret Pettichord > www.pettichord.com > > _______________________________________________ > Wtr-general mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/wtr-general > > _______________________________________________ > Wtr-general mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/wtr-general > _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general _______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
