tag:blogger.com,1999:blog-6109540481725463028.post7830353017492854993..comments2024-01-07T04:38:06.600+00:00Comments on Creating Software - A Sisyphean Task?: A Set of Principles for Automated TestingAdam Knighthttp://www.blogger.com/profile/01392120495059443531noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-6109540481725463028.post-22856474050809593182012-01-26T09:15:49.704+00:002012-01-26T09:15:49.704+00:00Thanks Kobi, any time is a good time to add useful...Thanks Kobi, any time is a good time to add useful tips to a blog post!<br /><br />The principles that I follow grew very much out of Keyword Driven Testing, which I have used on previous projects driving tests out of Excel in just the way you describe. Given that the main inputs to our system are file based we've simply made the natural progression from Excel structure to a file driven Adam Knighthttps://www.blogger.com/profile/01392120495059443531noreply@blogger.comtag:blogger.com,1999:blog-6109540481725463028.post-79804776130545083542012-01-26T09:15:36.681+00:002012-01-26T09:15:36.681+00:00Forgot another issue in earlier post:
Automation R...Forgot another issue in earlier post:<br />Automation Results must be easy to investigate !<br />Quite quickly one reach the state where automation runs quickly but investigating the results takes lot's of time...<br />Special attention should be given to the ATE produced Logs and means for viewing them.<br />I prefer Drill-Down tree-like logs viewing, which allows to view the high level halperinkohttp://www.blogger.com/profile/02746116081985463537noreply@blogger.comtag:blogger.com,1999:blog-6109540481725463028.post-38478346494494085782012-01-26T09:14:48.778+00:002012-01-26T09:14:48.778+00:00Sorry for late reply, but better late than never :...Sorry for late reply, but better late than never :-)<br />(Some readers might find the great post above and still make use of additional ideas).<br />1. I fully agree with the notion that testers should be able to write their own tests (even if they don't have programming knowledge), and for that Keyword Driven Testing was "invented" - We find it very easy for testers to define testhalperinkohttp://www.blogger.com/profile/02746116081985463537noreply@blogger.comtag:blogger.com,1999:blog-6109540481725463028.post-83938465032867071802012-01-26T09:09:47.808+00:002012-01-26T09:09:47.808+00:00Sorry for late reply, but better late than never :...Sorry for late reply, but better late than never :-)<br />(Some readers might find the great post above and still make use of additional ideas).<br />1. I fully agree with the notion that testers should be able to write their own tests (even if they don't have programming knowledge), and for that Keyword Driven Testing was "invented" - We find it very easy for testers to define testhalperinkohttp://www.blogger.com/profile/02746116081985463537noreply@blogger.comtag:blogger.com,1999:blog-6109540481725463028.post-1561447480864763262011-03-20T22:45:33.359+00:002011-03-20T22:45:33.359+00:00Just found a comment from Adam Goucher here
A Set...Just found a comment from Adam Goucher <a href="http://seleniumhq.wordpress.com/2010/11/01/a-smattering-of-selenium-30/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Selenium+%28The+Official+Selenium+Blog%29" rel="nofollow">here</a><br /><br /><b><i>A Set of Principles for Automated Testing is not a bad list. I completely disagree with the second one, and the last one is Adam Knighthttps://www.blogger.com/profile/01392120495059443531noreply@blogger.comtag:blogger.com,1999:blog-6109540481725463028.post-5810576024407322812010-10-22T21:23:14.335+01:002010-10-22T21:23:14.335+01:00Albert. Thanks for the comments. I agree with most...Albert. Thanks for the comments. I agree with most of them, particularly the last one. Automation only works if you are taking mindless effort away. If maintaining the automation requires more effort than manually testing, don't go there.<br /><br />Not sure about "checking is not a purpose". I feel that checking is not <b>the only</b> purpose, however for my automation a huge Adam Knighthttps://www.blogger.com/profile/01392120495059443531noreply@blogger.comtag:blogger.com,1999:blog-6109540481725463028.post-2015929741560205372010-10-22T15:46:02.065+01:002010-10-22T15:46:02.065+01:00Hi Adam,
I totally agree, introducing and educati...Hi Adam,<br /><br />I totally agree, introducing and educating your stakeholders on the process you established is critically important. Having answers ready for your reasoning helps building credibility and trust on automation solutions.<br /><br />My variation of principles in a short version is.<br /><br />* Separate core automation framework, test object recognition, test logic and test data<Albert Gareevhttp://automation-beyond.com/noreply@blogger.comtag:blogger.com,1999:blog-6109540481725463028.post-46322621336948957192010-09-22T08:48:50.460+01:002010-09-22T08:48:50.460+01:00Thanks for the feedback Glen. Excellent additions ...Thanks for the feedback Glen. Excellent additions to the principles too.<br /><br />With regard to designing for debug I wrote a post earlier this year on why <a href="http://a-sisyphean-task.blogspot.com/2010/05/why-automated-testing-is-more-than-just.html" rel="nofollow">automated testing is more than just checking</a> and the information to debug and diagnose faults was a key element to this.<Adam Knighthttps://www.blogger.com/profile/01392120495059443531noreply@blogger.comtag:blogger.com,1999:blog-6109540481725463028.post-85933316214602584192010-09-22T00:03:27.147+01:002010-09-22T00:03:27.147+01:00Nice post Adam, I'm very much 'on page'...Nice post Adam, I'm very much 'on page' with your thoughts.<br /><br />Principles are vital and test developers need to understand the principles so they can implement the pertinent ones as their tests require. I often find test developers asking for rules that can be always applied, where as principles need to be understood and intelligently applied, exceptions to the principles areGlenn Halsteadhttps://www.blogger.com/profile/05433555037717687693noreply@blogger.com