tag:blogger.com,1999:blog-7722108.post7900967059308398808..comments2024-03-28T12:11:07.539+05:30Comments on Thinking Tester: A catalogue of Test Automation Benefits ...Shrini Kulkarnihttp://www.blogger.com/profile/10782753752478547381noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-7722108.post-2840756326865703392008-06-15T12:32:00.000+05:302008-06-15T12:32:00.000+05:30@shrini, Our test are developed at the GUI level....@shrini,<BR/> Our test are developed at the GUI level. Developers have their own set of test at the class/api level and they are good at detecting unit and integration defects. However our experience has shown the developer tests often fail to detect bugs in end user scenarios.Rajesh Kazhankodathhttps://www.blogger.com/profile/00776206192461021082noreply@blogger.comtag:blogger.com,1999:blog-7722108.post-42609468993613043492008-06-13T20:40:00.000+05:302008-06-13T20:40:00.000+05:30@Markas -James' List of resons to repeat is a grea...@Markas -<BR/><BR/>James' List of resons to repeat is a great article to read. Every time I read, I discover new intepretation of the paradigm of regression, repitition and scripted tests.<BR/><BR/>I am not sure how that list is related to this ..(other than common point that all automation is repitition of some previously executed test.<BR/><BR/>ShriniShrini Kulkarnihttps://www.blogger.com/profile/10782753752478547381noreply@blogger.comtag:blogger.com,1999:blog-7722108.post-49156359133884275792008-06-13T20:16:00.000+05:302008-06-13T20:16:00.000+05:30@Rajesh ...Yes, there are automated tests that are...@Rajesh ...<BR/><BR/>Yes, there are automated tests that are developed at Class/API level and used for daily builds and smoke tests. These are typical in Software product scenarios.<BR/><BR/>Are your tests developed at Class/API level or GUI level (I suppose it is the later)? <BR/><BR/>Automation Smoke tests to check if the build is stable for rigurous testing or not is a another benfit .. that comes under "Real" category.<BR/><BR/>Thanks for pointing out that.<BR/><BR/>ShriniShrini Kulkarnihttps://www.blogger.com/profile/10782753752478547381noreply@blogger.comtag:blogger.com,1999:blog-7722108.post-19986646699074960242008-06-13T19:59:00.000+05:302008-06-13T19:59:00.000+05:30My project performs automated test executions on d...My project performs automated test executions on daily builds everyday. These are the very basic end-to-end system test scenarios. This most important benefit we've got from this practice is 1) ensure if testing team need to pick the new build for testing 2) In case a defect is detected in the execution, developers know with enough certainty "when/how/who" of the defect.Rajesh Kazhankodathhttps://www.blogger.com/profile/00776206192461021082noreply@blogger.comtag:blogger.com,1999:blog-7722108.post-75708273422628620422008-06-13T16:48:00.000+05:302008-06-13T16:48:00.000+05:30You should reference James Bach's list of Reasons ...You should reference James Bach's list of <A HREF="http://www.satisfice.com/repeatable.shtml" REL="nofollow">Reasons to repeat a test</A> as well. But nice list so far. I hope I have the time to look through it at home.<BR/><BR/>Regards Markus GärtnerAnonymousnoreply@blogger.com