Comments on: So how do we solve the scripting problem? http://www.developsense.com/blog/2007/04/so-how-do-we-solve-scripting-problem/ DevelopSense Blog Tue, 20 Dec 2011 16:15:38 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Michael http://www.developsense.com/blog/2007/04/so-how-do-we-solve-scripting-problem/comment-page-1/#comment-57 Michael Wed, 25 Apr 2007 15:16:00 +0000 http://developsense.com/wordpress/?p=49#comment-57 See what I mean by "very sharp fellow"?<br/><br/>---Michael B. See what I mean by “very sharp fellow”?

—Michael B.

]]> By: Ben Simo http://www.developsense.com/blog/2007/04/so-how-do-we-solve-scripting-problem/comment-page-1/#comment-55 Ben Simo Tue, 24 Apr 2007 21:08:00 +0000 http://developsense.com/wordpress/?p=49#comment-55 Michael,<br/><br/>Thanks for answering my question.<br/><br/><i> who sometimes goes by the name "Ben Simo"</i><br/><br/>I've been called a number of things. However, I do mostly go by the name "Ben" -- Although that's not my first name. :)<br/><br/><i>is a very sharp fellow</i><br/><br/>Can I put that on my resume? :D<br/><br/><i>The second is to remind them that, as a tester, it’s your job to consider questions and possibilities that other people don’t consider.</i><br/><br/>I thought my job was to report as close to 100% test automation as I can -- whether or not the tests bring value. ;)<br/><br/>Seriously, all your suggestions are good. Some I have tried to incorporate. Others I will try next time.<br/><br/>One thing that has helped -- when it doesn't require too much extra work -- is to implement what we (the toolsmiths) believe is best after our first round of questions. Then we feed the details of our implementation and the results back to the script authors for verification.<br/><br/>Joseph "Ben" Simo<br/><a HREF="http://qualityfrog.com" REL="nofollow" rel="nofollow">QualityFrog.com</a> Michael,

Thanks for answering my question.

who sometimes goes by the name “Ben Simo”

I’ve been called a number of things. However, I do mostly go by the name “Ben” — Although that’s not my first name. :)

is a very sharp fellow

Can I put that on my resume? :D

The second is to remind them that, as a tester, it’s your job to consider questions and possibilities that other people don’t consider.

I thought my job was to report as close to 100% test automation as I can — whether or not the tests bring value. ;)

Seriously, all your suggestions are good. Some I have tried to incorporate. Others I will try next time.

One thing that has helped — when it doesn’t require too much extra work — is to implement what we (the toolsmiths) believe is best after our first round of questions. Then we feed the details of our implementation and the results back to the script authors for verification.

Joseph “Ben” Simo
QualityFrog.com

]]>