tag:blogger.com,1999:blog-19627873267897029092012-02-16T19:02:04.206-08:00This blog is about the real world of software testing.Saneesh.Shttp://www.blogger.com/profile/14076238237499254722noreply@blogger.comBlogger21100tag:blogger.com,1999:blog-1962787326789702909.post-40937489701573125262008-08-11T06:51:00.000-07:002008-08-12T23:24:04.006-07:00Well, You might have heard this word..even applied it.. Even though, I would like to share my thoughts and ideas... I have heard this buzz word, some time back when I was going through a blog named 'Testertested' by Mr. Pradeep Soundararajan.<br /><br />I have done a considerable amount of learning on the same and it seemed like,really good to implement. Exploratory Testing, a.k.a (ET) could be explained as simultaneous learning,test design and execution, which is really contradictory to the conventional scripted testing( both manual and automated). In the conventional scripted testing, first we understand the functional as well as business flow of the application or system to be tested. The learning( ie, functional and business flow understanding ) is doing with the help of SRS( Software Requirement Specification)/ Functional Specification. After, learning or functional understanding completes, the tester will design tests(ie, test cases) and execute those tests against the product or application to be tested. There are some pros and cons in scripted testing. The pros is, it is really good that we can find out design flaws before development starts so that it prevents from the bug to be occurred and which inturn save the entire SDLC time. The cons is that, if client or product owner changes the requirement, the entire tests(test case) will have to be redesigned. Apart from that the since we are bound to the test case( I meant the 'Expected Result'), testing will become a confined process and the no of bugs also will be less( from my experience)<br /><br />But, on the other hand , as the name depicts we are really exploring the product or application to be tested, without the help of a pre-scripted test case. Let me steal the words of James Bach :), the veteran exploratory tester, " ET - is simultaneous learning,test design and execution". This where the skill of tester matters rather than pre-scripted test cases and it is really good to implement in projects, which follows 'Agile' development life cycle. The cons is that, it will not possible to find out design flaws before development starts.<br /><br />Since there are some pros and cons in both the approaches , I would like to suggest a blended approach of scripted as well as ET is followable in a project.<br /><br />PS: I have been engaged in a project, which make use of a blended approach of scripted as well as exploratory testing.<br /><br />Wishing you all a very happy ET :)<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1962787326789702909-4093748970157312526?l=softwarecritiques.blogspot.com' alt='' /></div>Saneesh.Shttp://www.blogger.com/profile/14076238237499254722noreply@blogger.com0tag:blogger.com,1999:blog-1962787326789702909.post-75662228134134177952008-08-09T00:10:00.000-07:002008-08-11T06:24:59.170-07:00Well, I have to start some where, here it goes....My first blog entry<br /><br />I am sure that this will be the first step towards a big leap...Big leap towards the real world of software<br />Testing.<br /><br />So, my dear friends, encourage me, criticize me, provide your valuable suggestions...<br /><br />Till then...wishing you all a very happy testing...<br /><br /><br />Saneesh.S<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1962787326789702909-7566222813413417795?l=softwarecritiques.blogspot.com' alt='' /></div>Saneesh.Shttp://www.blogger.com/profile/14076238237499254722noreply@blogger.com2