Hi Reader,
I don't want to kill your excitement of reading THIS ARTICLE by giving an introduction to it. Feel free to share it with anyone you like, if it is that interesting. I felt it interesting and hence I shared it with you all in my blog.
This article is important in a way that makes you think of how you ......
-- Pradeep Soundararajan - http://testertested.blogspot.com - pradeep.srajan@gmail.com - +91-98451-76817
6 comments:
Hi Pradeep,
Read the article.It was not that interesting.But may be because it was clear from the first point that we should never accept something without questioning or as disscued before ,we should stop believing in best practices.Read this article http://www.exforsys.com/content/view/1494/340/.It was kind of different.The writer says ,she was never born to be a tester and now she understands what are the traits of a true tester.Liked the line where she says there is hidden desire to break the system.Have a Dekho!!.And Please pradeep pass us the knowledge you gained after meeting Michael Bolton.I am in Pune.May be someday you will arrange such meets for us also...Amen!!
~PP
Hi PP,
It is still interesting to me that it did not interest some other tester. This is a story of how I walked through tester's street and not on how you should have walked through :)
Now, here is a learning for you and me as a tester. I see testers biased to something they like about. Ah! so does that mean what you saw first affected you a lot that disallowed you to find something similar as interesting as the second one.
I have been in mobile testing space and I have seen many times, what I call as a Favorite model bias, which means - A tester who loved a particular mobile phone, was in the testing team that involved him to test the music player application. He was so biased that he enjoyed the music than checking the quality of the music.
I observe that you keep coming back to my blog so frequently and that means something is interesting here.
If you prove your passion to test, skills to people like James and Michael they would be pleased to come to your place and create more such people like you. I am not sure how I can pass on the knowledge I gain by meeting Michael Bolton to you all but here is what I can do. If you work through the exercises listed in my blog and other testing blogs... (google it!) I can help you out in bettering your approach. I HAVE ALL TIME FOR THAT!
“Biased hmm “ that was my first reaction. Then I thought might be you are correct or incorrect, so I re-read the whole article. It was good. Only thing that made it uninteresting the first time was that I started predicting the outcome which was not too hard to guess .As for a guy who love testing will always choose the path of exploration .As the joy of testing is not in rotting the standards.And the mobile tester’s example was interesting.
Yesterday was penultimate day of my current project and we were testing some Third party component compatibility with our Firmware/Software.Now as I was about to leave from my office .i saw a showstopper bug in our product.A bug which can seriously dampen the image of our product.We have stopped testing that area of product and were only concentrating on the compatibility with this third part S/W.It was a mixed feeling I was happy that I found it and unhappy because I should have discovered it earlier.There were few points I was thinking about
1.I should report it because it is what I am supposed to do.
2 My PM(I work for a Spanish client) is not tester friendly (she has one aim “meet the shipping dates”) will start creating scene .
3.May be it is only affecting the prototype I am testing and not all the prototypes( I am left with only one prototype ,as other testing prototypes have been upgraded and now a different product.).
The 2 point is something a true tester should not care about.So I reported the bug with comments that it might be affecting only 1-3 prototypes.As They have more protoypes and can check whether it is affecting all or only mine.I am yet to see my PM’s reaction.But I am happy that I reported it.But it also made me understand Jame’s Mine field theory. As I was only concentrating on compatibility it made me overlook other areas .
I daily read your and Jame's blog .Albeit James is not adding new post these days.Hope you don’t stop psoting…:).
Hi Pradeep,
Though this blog do not offer much more to read and enjoy, but it teaches us an important lesson..
"Dont be biased by another persons views or knowledge. Explore yourself & Learn more"
thanks..
Abhishek
@Abhishesk,
Though this blog do not offer much more to read and enjoy, but it teaches us an important lesson.. "Dont be biased by another persons views or knowledge. Explore yourself & Learn more"
Could you please explain the same?
@Pradeep,
there isn't much to explain, your blogs says it all.
what I said is an one liner, about your view on testing mind set. Generally every tester is under influence from his colleagues/senior testers (*Certified or *Skilled) and follow a path traced by them, very few wanted to break it and learn something new(I am one of those few). Hence, they need to come out of 'safe mode', experiment/explore new things and learn new things. It may be about his project, a tool, a testing technique or anything xyz..
Your blog was written in Jan 2007, but I see things didn't change much. Still guys have same dilemma over certifications and are eager to become a toolsmith.
I am reading your blogs regularly. from oldest one in 2006 to the newer one's.
Thanks for such a good and inspiring writing.
Abhishek
Post a Comment