Posts

Why I prefer Exploratory Testing ?

Image
I have been into Software Testing field for nearly 5.5yrs now. My first 4 years went in writing test cases and executing the same. My initial days as a software tester was something like this: Going through Requirement Spec or Use cases of my modules, Identifying High level scenarios and Low level scenarios for the same, writing test cases and then once the module is ready for test, execute my test cases and test the module. Once I finish writing test cases, A senior or peer tester  would review my test cases and add/update my test cases. After that, test cases freezes for that cycle. I was not supposed to change my test cases for any reason. Now while testing,     If I get any other test ideas which I might have missed during my test case writing period, I have no option to add that in my test ideas list.     If I log a defect without giving reference to the test step which I am executing, Developer won't accept it. Funny part was, We have to shar...

My first post to the software testing world

  Though, I had plans of writing and maintaining a blog of my own on testing, it never started or rather kept postponing thinking of what to write and how to start ? Thanks to PS for Initiating this FNL activity which finally made me DO IT. My first post will be on SBTM (Session Based Test Management). My previous work experience as a tester included testing activities which starts with going through requirement document, writing test cases and executing the same with a pass/fail status. So everything is documented . We know what we are doing and managers also can keep track of what we are upto. When I joined Moolya, I took sometime to adjust myself to Exploratory way of testing applications. Though it does not defines any boundary or limitations of testing,  I myself was unable to keep track of what scenarios I have covered or what I missed out. So It will be even more difficult to justify or defend if customer finds a defect in my module later. So I st...