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
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-general
_____________________
Bret Pettichord
www.pettichord.com
_______________________________________________
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-general
