Monday, December 27, 2004

Brian Merricks when to automate paper

http://www.testing.com/writings/automate.pdf

.. courtesy of Joseph King.

Directed at QA people. A fairly long paper that says you should only automate those tests that are going to help you.

Interestingly, it ignores the role of testing in development - especially in an agile environment where things are changing constantly. I think the tradeoffs change quite a bit in this environment. Especially as tests give you confidence that things are OK. Confidence gives you permission to make both small and large changes to the code base.

1 Comments:

Anonymous Anonymous said...

I agree. On an Agile project, I lean much more heavily toward automated tests. For my thinking along those lines, see this:
http://www.testing.com/writings/2004-roadmap.html
and this:
http://www.testing.com/cgi-bin/blog/2004/05/26#directions-toc

5:08 p.m.  

Post a Comment

<< Home