“ Boundary Value Analysis is done when you know the range of Inputs and Outputs; Black box testing is performed when you do not know the internals of a product, load testing is done as to check what extent the product can bear the stress.... ”
There is a developer. There is a product. There are plenty of clients, stakeholders, end users and your product can’t go wrong. And here goes... A tester comes into the picture.
I will tell you, the things running in tester’s gray cells from here on.
Is the product specification right, do clients and end users get what they require?
Has the product developed in right way?
How can I break the product? What might be the loophole(s) of the same?
Is the documentation for the product and usage guidelines proper?
How to convince developer(s) about the bug/anomaly I found?
How to achieve faster testing mechanism to find bugs?
.......
A tester has to know everything, right, left and center. A to Z. As the days went by I came closer to this truth.You are not actually finding mistakes but it’s just the way for the product to get better. So the user of the product gets good night sleep for a better product.
I am going to share some of my findings in this regard. I being a tester (Never wanted to be one, but I was the one as fate had)
First I was of the opinion that, it’s all about breaking a developer’s ego. He develops the product mammoth size and you find a pinhole. He is hurt.
Rather than testing, Developing is more interesting. In reality, trust me both are challenging. Developing product from nothing is interesting and learning the same and bettering the product is similarly interesting.
A tester has no scope for scripting/coding. Wrong.! He has to create scenarios for the products, write the code on product (as the developer did) and then automate the same. Find a way for product to go wrong in quicker way.
A tester should think like a villain. Yes. A badman can only break the product.
Let me give an analogy, a developer is like a teacher who preaches student what to follow and a tester teaches what NOT to follow. Both are working for betterment of the student by their own methodologies. Their attempts are genuine, unique and equally challenging. And I will tell you li’l secret; it’s always what not to follow things are attractive and interesting. ;)
........
Human being always lives with dvandva (meaning duality).White and black together are contrasting to each other. Importance of each other is known when both are present. You can always develop a habit (meaning a product here) like a developer. But for little while think like a tester.
Is that habit/state of mind serving your presence, is it representing the real you?
What makes you uncomfortable with this state of mind under test? What’s your limiting point?
Is there any other way I can get improved?
And here you are not breaking your developer’s ego but you are happy being realistic to find your mistakes on your own and if you will, that loophole can be miraculously get rid of.
Here is a legend from Mahabharata which I would like to share,
Arjuna was on his chariot with his chauffeur Krishna, warring against Karna who was almost defeated. One arrow shot from Arjuna, propelled Karna’s chariot to a hundred units of distance. And now, Karna in reply, propelled Arjuna’s chariot just one unit of distance.
Even being at the rival side, Krishna couldn’t stop applauding for Karna’s deed. Everyone at battle field including Arjuna were taken by surprise.
The reason: Karna had displaced Arjuna’s chariot by one hundredth of what Arjuna did for Karna’s chariot.
And the Krishna explained that, Arjuna’s chariot (refer here as product) was actually owned by Lord Soorya, created and tested by the great architect of Gods Vishwakarma, boarding currently Arjuna and supergod Krishna ( this was post Vishwaroopa darshana) was thrown by tired Karna’s one stupid arrow. Just imagine how much powerful Karna was when compared with Arjuna who propelled an ordinary chariot containing two normal human beings a Karna and one Shalya the chauffeur for Karna.
Arjuna felt shameful .
Moral :
There was still scope for improvement with Arjuna’s chariot ;)
