http://www.logigear.com/blog/will/automation-adoption/ Software Testing Community Sun, 22 May 2011 19:44:43 +0000 http://wordpress.org/?v=2.9.1 hourly 1 http://www.logigear.com/blog/will/automation-adoption/comment-page-1/#comment-9 Dmitry Wed, 11 Nov 2009 20:54:16 +0000 http://www.logigear.com/blog/?p=291#comment-9 I agree, on division of test engineers and test engineers and their cooperation in building automation, which is (domain knowledge + professional coding expertize). Though must desagree about coining term as "monster package" for QTP. QTP could be utilized to just wrting vbscripts and crelating it with object repository. building smart and effective framework is very important. Also desagree that all tools are equal. Again, most of the less expensive or open source tools have limited features. Though we know that we can build automation without tools at all, just coding in c# or c++, or vb. tools help to achieve goals quicker. Agree completely about companies wasting moneys on byuinng all poasible tools without understanding that they need sckilled enginners to operate them. Most of the skeptisism about automation is comming from the original mistake that qa engineer (you call it line engineer) can develop auto tools. Many QA managers become angry when they hear that it's not true. I beleive that automation tools marketing teams make imperssion when they sell tools that it is for non-techs. And in most cases it works for simple auto tests they build during the demo. The real life automation is a serious task that requires above average programming expertize. From my experience the best model would be Automation Engineer embeded into QA team. Ratio could be 1/4 or 1/3. One auto engineer per 3 or 4 qa. Also important to educate qa engineers how properly investigate test results. The best is to build intellegent configuartion platform to allow qa engineers to reconfigure auto tests for different platforms. Cheers! Dmitry I agree, on division of test engineers and test engineers and their cooperation in building automation, which is (domain knowledge + professional coding expertize). Though must desagree about coining term as “monster package” for QTP. QTP could be utilized to just wrting vbscripts and crelating it with object repository. building smart and effective framework is very important. Also desagree that all tools are equal. Again, most of the less expensive or open source tools have limited features. Though we know that we can build automation without tools at all, just coding in c# or c++, or vb. tools help to achieve goals quicker. Agree completely about companies wasting moneys on byuinng all poasible tools without understanding that they need sckilled enginners to operate them. Most of the skeptisism about automation is comming from the original mistake that qa engineer (you call it line engineer) can develop auto tools. Many QA managers become angry when they hear that it’s not true. I beleive that automation tools marketing teams make imperssion when they sell tools that it is for non-techs. And in most cases it works for simple auto tests they build during the demo. The real life automation is a serious task that requires above average programming expertize. From my experience the best model would be Automation Engineer embeded into QA team. Ratio could be 1/4 or 1/3. One auto engineer per 3 or 4 qa. Also important to educate qa engineers how properly investigate test results. The best is to build intellegent configuartion platform to allow qa engineers to reconfigure auto tests for different platforms. Cheers! Dmitry

]]>