Showing posts with label Michael Bolton. Show all posts
Showing posts with label Michael Bolton. Show all posts

Sunday, October 10, 2010

It's all about tester's mindset


Hurray, it’s Friday and I'm back home after work. It's quite a quiet week, as we met all test deliverables as per scheduled date & time.
 
While I drove back home, a car adjacent to me crossed his lane violating traffic rules and was about to hit me and I slowed down for a while to allow him to overtake, else there would be a great smash-up between us followed by huge traffic Jam. If you know about Chennai traffic you can easily imagine the latter situation very well.

Right away, I questioned my project manager, who accompanied me in the car, that why the hell is he violating the traffic rules. To which he replied calmly It's simple that we Indians take advantage of our circumstances and won't be self-disciplined ( his comment made me to ponder for a while that "Hey Shiva Mathivanan, how self- disciplined are you?, self-critic". Now I realize what is left to improve within myself). My project manager then made an additional comment, that we Indians never trash waste's in dustbin could be biodegradable or non-biodegradable wastes we don't mind in clearing trashes like chocolate wrappers, coke cans, pet bottles, polythene bags, etc in dustbin even if the dustbin's are at reachable proximity. We never even think to spit on roads, and violate traffic rules. Have you also noticed that the same Indian who moves overseas to Singapore and other European countries never even tries to indulge in undisciplined behaviour, that he had done for so many years in India? I sensed his strong emotional feeling that is oriented towards his real grievance. To my surprise, why do we try to adopt with conditions in overseas and sincerely tries to take advantage of our Indian circumstances rather than being self-disciplined all the time? Why do we behave so?

This instance disturbed my consciousness and made to relate our Indian mindset with Indian tester's mindset, of questioning myself "How we are?-Why we are?-The way we are?"

Note: This is about smart Indian testers who are resistive to change, for good. So please don't generalize this about all smart Indian testers.

How we are - Why we are - The way we are?
• We don't want to be blamed from project manager or QA Manager treeing "how did you miss this defect when you tested last month?” while we have all possible reasons to JUSTIFY it. Why do we behave so?

• We don't we want to be damned among everyone in team meetings for our own flaws; however we are very much comfortable if the same curse is fed in privacy. Why do we behave so?

• We always want us to be in comfort zone of 'level B'. I respect the transformation we have earned from 'Level A' to 'Level B', but why aren't we open to learn and advance to other degrees? Do we still want to be in comfort zone of 'Level B' with full knowledge and deliberation than attempting to direct ourselves to other levels? Why do we behave so?

• We don't want to be questioned by anyone in office space. But why aren't we open to questions and have patience to provide worthy answers?

• We will test functionalities/GUI to validate what is detailed in functional specification to confirm testability and we won't question the software product to raise more valid issues, which is not elaborated in user specification? Example -what if the user-friendly error message is accurate but unhelpful?. Why are we not prepared to question the system out-of-heuristics?. Michael Bolton say's a direct violation of a reliable specification is probably a bug and we tester need to change the question "does this test pass or fail? to a question that better addresses a possible threat to someone's values:"Is there a problem here?". Why do we fail to test and raise question to the team, instead we argue that it is not provided in the functional specification, so it was left untested. Although we are very sure that most of the specification won't be reliable for everyone in the team?

• If we aren't open for Idea's, where will we find the room for our own improvements? Why do we behave so?

• There are various models which have been presented in the past 20 years in the field of software engineering for development and testing. Most of the tester's who worked in those famous testing models like Waterfall Model, V Model, W Model, Spiral Model and Butterfly Model are coined as traditional tester's and these models are said to be outdated as it cannot be followed in the current trend of the way we work in Software testing. It is true because testing craft has made us to learn in recent times of "what is the best fit of tests required for the project we get to test" hence most of the companies rely on building agile manifesto - a change for good. How many testers are prepared to change their pattern of testing for good? We always resist to changing. Why do we behave so?

• Why are we not confident enough to test a software application or a product without a functional specification? Michael Bolton say's you don't always need to wait for complete specifications to start your testing effort here. Why are we not up for that yet?

• When have we conceded, recently that 'Yes, It's my mistake. I will correct next time'. Why are we failing to accept our own mistakes? If we cannot consent ourselves, how will we understand the impact of the mistakes that might have affected the team's deliverable and if we can't understand the severity of it how will we amend, next time?


Our way of reacting to a situation is adopted by how we are. Why we are reacting to the way we are? is because we are directly related to instance of our current learning respective to our current level of expertise. The problem here is that we aren't upgrading our learning skills. Get to know why smart people struggle behind reacting to change by Rajesh Setty.

Harry Robinson, Test Architect for Microsoft's Enterprise Management Division predicts the future of testing here.I now foresee that the change he expects has began to infect, BUT the change isn't COMPLETELY infected for good.

Thanks for spending valuable time,
Shiva Mathivanan.

"We learn little from victory, much from defeat. Don't think in terms of Win or Lose. You cannot always win, but you can always learn".-Jerry Weinberg.

Sunday, August 22, 2010

Testing mentors in limelight

I recently met so many experienced test engineers and testers, who are not with engineering background but with different streams of science & math in India. To my surprise most of them aren't aware of neither the context driven school of testing nor the heuristic aspects of testing in general.

‘Ah what does that mean?’ I can sense your interrogative look too, continue reading :)

The most “senior test engineers” or “QA professionals”, in whatsoever designation a ‘software tester (a hominid who tests software products) would like him to be identified, have just learnt how to survive in their jobs, by building test metrics, test case designing, test case execution, test automation, bug reports, traceability matrix, test reports, etc; driven fundamentally based on SDLC & STLC, for days, months & years. Though these testers pertain to be successful testers, they lack the essence of sustaining in this craft for longer period. Why is it so?
It is because, they have been practicing testing just because to uphold their jobs particularly in recession times. Although most of these experienced manual and automation testers in India, who claim they acquire 10+ and more years of experience, are into this craft of testing ONLY either by strange coincidence or by choice and NOT by Interest. So fundamentally they are reluctant to share their knowledge, ideas even to their co-tester, despite of generating teamwork cohesion. Typically, this implies a preservation of nothing.

The outcome of this attitude will conduct a tester to think & preach to his co-testers as follows:

  • Testing is monotonous
  • Testing has lesser scope to learn & earn.
  • Testing is not challenging as programming.
  • Testing is a dumb activity, if worked in the same domain for 3+ years.
  • Testing is theoretical, the one who mug up the definitions can clear interviews easily to get bunch of job offers.
  • Testing is a battle field with programmer. Programmer's always battles with the tester, who injects defects on his code, be prepared. *caution to tester, by senior tester.
  • Testing is a dependent job, always should depend on the programmer & release engineering team.
  • Testing consumes more time, not even 30% of development time is provided for testing. However, they expect 100% test coverage that too in tight deadlines.
  • Testing is reiterative activity, feeling exasperated beyond endurance.
  • Testing is__________________________________________
You can spend invaluable time in virtually filling you’re preserved pessimistic thoughts in your mind, If you had already been advocating the same to your co-testers, programmers & managers.

When you saw the blank straight line after the words 'Testing is" have you had a question in your mind that 'why it's left blank'? Before reading the next line of sentences?
If so, it's good continue reading... If not practice the art of questioning!

From the blog reader, mind’s- Hey, come-on Shiva Mathivanan, you have been cursing me for so long, you were just highlighting the traditional flaws, misapprehension, ambiguous definitions in testing crafts.
How can you prove that I’m wrong? I bet if you prove it will help me to understand where we mutually stand. And also tell us what is context driven school of testing, what's heuristics all about and how is it going to benefit me in this testing craft, how can I be more passionate towards testing?. (Yes, I can hear you)

Shiva Mathivanan - Good question: I can very well prove what you desire. However, I would like you to read what my mentors have already told about testing. Read through my mentor’s views; start contributing to the testing arenas where my mentors participate. I’m sure that your testing genes will regenerate better (like how normal hormonal genes hyper when a hot girl/boy passer-by *wit*) and you will be a self motivated tester soon, someday.

I’m honored to introduce my great testing mentors. I have chosen them as guru in my testing religion is because I have understood their sensible talks, views, approaches and reliable service to testing community. I always have wondered, how limelight testers & mentors like James Bach, Cem Kaner, Michael Bolton & , Jerry Weinberg have never got tired of rendering their service to this software testing community, while most of the Indian testing geeks in various parts of the globe still in obscurity?

To bring the change, I welcome you all to read my mentor’s view:
1. Dr.Cem Kaner, Software Engineering Professor– http://kaner.com
2. James Bach, Principal Staisfice.Inc – http://www.satisfice.com
3. Jerry Weinberg, consultant - http://www.geraldmweinberg.com
4. Michael Bolton, http://www.developsense.com
5. Pradeep Soundararajan, Test consultant - http://testertested.blogspot.com

My dear blog reader’s you too will be the Ekalavya of above testing genius, some day if you ensure realization of their context. Get into the habit of writing blogs, Get to know why good software testers should write blogs by Pradeep Soundararajan. Pradeep is a exceptional Indian, who never set back to consult, coach and serve as prelude to Indian testing community.


The after effects of testers who reads my mentor's blog:
  • Exploratory testing is what I have been doing, but never to this extent.
  • Rapid software testing is WOW.
  • I'm proud to be a sapient tester, rather identified as manual tester.
  • To be a tester is a blessing, I enjoy everyday test activities.
  • Developer versus Tester a win-win kaizen to build quality into the product.
  • I started blogging my test experience, sharing thereby learning more.
  • I understood how to question a product in order to evaluate it - James Bach.
  • My approach towards testing has refined a lot.
  • My confidence boosted, I can be a successful independent test consultant in future.
Who knows some day, someone like me will be highlighting your views to rest of the testing world, like how I showered my tribute. All the best!

Evaluate you're testing experience, how was testing? by www.vettanna.com
Thank you for spending valuable time!
Shiva Mathivanan