This is a great question and a tough one too. One of my philosophies during my career has always been to make myself replaceable so that I can move onto other more interesting things. In your situation, it sounds like you've accomplished that. You introduced a tool and a desire to move testing back towards the development staff. That's a great success, isn't it?
That aside, I work in a small agile development shop and my boss understands the value provided by having independent software testers on the R&D team. Using a scripting tool to assist in the testing effort is not the same as automating testing. I don't believe that you can automate the complexity involved in real Testing. (And not in the foreseeable future either.) So the question I would pose back to you is this: can you articulate to the CTO what the difference is between testing software and computer assisted testing (i.e. otherwise called 'test automation')? Hint: the value you provide is not in the scripting. If your CTO can't understand that, then you might be better off looking for a new contract elsewhere anyway. Best wishes! Cheers. Paul C. On 16/03/07, Tunde Jinadu <[EMAIL PROTECTED]> wrote:
Help, I've introduced Watir to a small software house i'm contracted with and now they love it so much, they want to get rid of me and include watir scripts in their build process. The CTO's comments are "Thank you for introducing us to Watir, WatirN, Goodbye". How can I convince them that they need a tester to write Watir, Watin scripts to ensure an independant eye and approach to testing. What are your suggestions
_______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
