MIS-S-TAKE

OOOO…, as scripted in my previous post, I really had a long break but my learning process had enough(sometimes more than enough) to digest.

“Rough patches always teach you many lessons” -> I had many patches to scribble about… and I am here now with some of my mistakes (that will not be a nice idea!!!) but considering the fact that, it will help OTHERS.. I will unzip some of my mistakes in upcoming “MISS TAKE” posts..

Once, I was in a situation to set up some critical Testing trap, with all necessary matching criteria, I decided to do it myself because explaining the trap to someone and seeking their help will be a time consuming process.

I have started setting up the trap in a hurry(time is always a constrain) and as always, I had some time left after setting up all the things, so I shared the core of the trap with one of my colleague(fortunately) with intent of sharing my testing knowledge (and also to show my testing EGO.. ), --> But then came my downfall..

He figured out a vital misStake which would have easily spoiled my entire testing.

In the making, I had to execute a system command that will trigger things in backend and send back a message “Everything has been executed successfully”. I executed that system command and I got the cheers message “Everything has been executed successfully”… BUT in the backend the required thing doesn’t happen.. :(

Yes of course, Testers should not believe in any system (even though it is not the built to test).

I am really worried after that incident and the reason is simple that I would have re- checked/assured everything went well behind the screen as well.

Its really important to recheck and assure that we have done a nice job because it will definitely save time and extra effort.So I came to a conclusion that, I want to make sure everything I do for testing purpose should be double checked. But how to assure that you have checked + rechecked your test activities.

Old idea but evergreen .. Checklist ..
Don’t take it in a wrong way, I am not saying you to do checklist testing but to use a checklist just to make sure you test everything perfectly…:)

I have implemented the above in some of my daily activities and it really works.. there will be “n” number of ideas to fix any issue.. hopefully one of you can help me out with something new and innovative... :)

Some interesting Q’s on mistakes..
a)If you commit a mistake then it indicates that you are working (not Idle).

b)When others make mistakes, we say “they are incapable”, but when we make mistakes we say “we learn from mistakes” -> tweeted by Viru … I hope, he has learnt so much from his patches…. Just for fun … :)

Be united to be an Independent.

Happy Independence day.

Lets key down our mistakes to help ourselves and others,
Venkat
All izz well….
Catch me @kpvenkatesan84@gmail.com