Comments on: The code freeze is killing the dinosaurs http://tynerblain.com/blog/2006/03/01/the-code-freeze-is-killing-the-dinosaurs/ Software product success. Sun, 12 Feb 2012 19:10:25 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Scott Sehlhorst http://tynerblain.com/blog/2006/03/01/the-code-freeze-is-killing-the-dinosaurs/comment-page-1/#comment-467 Scott Sehlhorst Mon, 20 Mar 2006 00:57:55 +0000 http://tynerblain.com/blog/2006/03/01/the-code-freeze-is-killing-the-dinosaurs/#comment-467 Jim, thanks for reading, and for the comments! I completely agree with your point that there is stuff that is impractical to test in an automated fashion (impossible, not justified, etc). I absolutely agree that a mixture of testing is appropriate, and varies from extremely automated to extremely manual - depending on the application's purpose, design, and goals. The most important thing is that the development team shouldn't hide in a cave and write code until they think they are done, but rather incorporate testing iteratively throughout the process. Bricklayers check the level of each row of bricks as they go, and correct any problems as soon as they appear - they don't wait until the entire wall is finished to discover that they are an inch out of level. Great zinger with the the bug-eating! And thanks again, please - keep it coming and keep me honest. Scott Jim, thanks for reading, and for the comments!

I completely agree with your point that there is stuff that is impractical to test in an automated fashion (impossible, not justified, etc). I absolutely agree that a mixture of testing is appropriate, and varies from extremely automated to extremely manual – depending on the application’s purpose, design, and goals.

The most important thing is that the development team shouldn’t hide in a cave and write code until they think they are done, but rather incorporate testing iteratively throughout the process.

Bricklayers check the level of each row of bricks as they go, and correct any problems as soon as they appear – they don’t wait until the entire wall is finished to discover that they are an inch out of level.

Great zinger with the the bug-eating!

And thanks again, please – keep it coming and keep me honest.

Scott

]]> By: Jim Hancock http://tynerblain.com/blog/2006/03/01/the-code-freeze-is-killing-the-dinosaurs/comment-page-1/#comment-459 Jim Hancock Sun, 19 Mar 2006 10:30:35 +0000 http://tynerblain.com/blog/2006/03/01/the-code-freeze-is-killing-the-dinosaurs/#comment-459 This article sounds great if we are working in an ideal world, but there are several exposures: 1) At least GUI automation testing requires script creation/maintenance AFTER the new code is created. 2) There is some testing that is hard (or even impossible) to automate. 3) It may not be cost efficient to automate everything. 4) Manual testing often yields more complexity and diversity with regards to testing (google Exploratory Testing). 5) Manual Testing also produces more of a "user experience" giving a better sense of user acceptance and a broader view of the app. Anyway, I feel in most cases that it is important to have some mix of automation and manual testing to be most successful. After all, don't both reptiles and mammals eat bugs? :) This article sounds great if we are working in an ideal world, but there are several exposures:

1) At least GUI automation testing requires script creation/maintenance AFTER the new code is created.

2) There is some testing that is hard (or even impossible) to automate.

3) It may not be cost efficient to automate everything.

4) Manual testing often yields more complexity and diversity with regards to testing (google Exploratory Testing).

5) Manual Testing also produces more of a “user experience” giving a better sense of user acceptance and a broader view of the app.

Anyway, I feel in most cases that it is important to have some mix of automation and manual testing to be most successful.

After all, don’t both reptiles and mammals eat bugs? :)

]]>