Friday, 24 November 2017

41 Definitions of Software Testing

41 Definitions of Software Testing is the first write-up I wrote for a Software Testing e-magazine.
I was asked to share an article (including the Bio) for the Testing Circus e-magazine, I had under an hour to write, review and share. I submitted 40 definitions and was glad to have made it in time. The article completes 4 years and I am re-sharing it on this medium. Thanks to Testing Circus e-magazine for publishing it. I still believe Testing is all of this. The 41st definition was contributed by Testing Circus e-magazine editor Ajoy Singha.

What is Software Testing?
Heck! Define it yourself. I have been thinking about an answer for the same but have found it hard to convey in one statement. Am I a born, reborn or a resurrected tester? I hope to find out for myself and the below article is an attempt at this.

Testing – I will be using the word testing as I continue to write and as you readers read, read it as Software Testing. Here are my definitions of software testing.

1) Testing is a responsibility of representing information which is essential for bettering the application/product under test.

2) Testing is learning to think well.

3) Testing is to understand the various contexts a system can be applicable in.

4) Testing is identifying the subtleties and extremities where the system can be used.

5) Testing is craving to dig deep into the system to look in the nook and corner in order to project the information that can awaken the product owner and the user to surprises and a wow-ness(that a product can be used to perform)

6) Testing is to provide the consumer with an application which re-ensures confidence in the consumer and for the business.

7) Testing is that ability which the whole team is entitled to with an opportunity to grab the consumers attention, supply the consumers demand and to deliver well.

8) Testing is to convert that dormant thought into an active on-going action oriented process.

9) Testing is to continuously collect aids which aims at delivering quality information to anyone equipped to better build the product.

10) Testing is remembering to act in unison with the vision and mission reflecting in the consumable product.

11) Testing is questioning, challenging, being biased and up-rooting the biases about how the product is presumed to be built and used.

12) Testing is having an eye for details however miniature or magnanimous.

13) Testing is buying yourself a microscope and a telescope to look at how a product is consumed today and in future.

14) Testing is building a lifelong insanity to learn in all sanity.

15) Testing is a role play of that of an investigator, a doctor, a builder, a victim, a crime fighter, an intruder, a seeker, an evangelist, a doer.

Do you see such attributes in a tester? – Hire that person.

16) Testing is being in a context all assuming and continuously judging.

17) Testing is testing the assumptions and then falling prey for the judgements made.

18) Testing is re-opening a concluded case.

19) Testing is to don the hat of someone other than you, change perspective and test with a prejudice.

20) Test to KNOW.

21) Testing is time boxed and at-times unleashing the you, learning to think in a way which is not brand you.

22) Testing is building credibility for yourself, your organisation which serves you and which you are serving.

23) Testing is learning to explore the path which you are willing to tread and paths which are road less travelled.

24) Testing is defining, redefining and un-defining.

25) Testing is breaking barriers to test.

26) Testing is a courageous act of preparing oneself to tread a new path, take another challenge.

27) Testing is taking ownership of mistakes with a pitcher of gratitude, that I learnt what not to do and what to do in this context.

28) Testing is story telling via testing and the experience reports.

29) Testing is diminishing confusion and expanding the confidence of a user.

30) Testing is that walk down the memory lane and think if this issue has occurred or is a déjà vu.

31) Testing is that feeling when you love yourself for learning to learn new every day.

32) Testing is together untying and revealing the product/application to itself.

33) Testing is you emerging out of the bath tub with a ‘Eureka’ moment.

34) Testing is a knock on the door of a developer to help undertake measures to provide a fix.

35) Testing is a wake-up call to innovation, to time travel back into the future.

Did you relate to any one or more of these?

36) Testing is an unconventional mode of transport to the minds of a user.

37) Testing is at-times masking the status quo.

38) Testing is closing in on the ‘I’ the consumer, ‘I’ the tester, ‘I’ the developer, ‘I’ the owner and illuminating the path of ‘We’ the team.

39) Testing is that run down the rabbit hole to discover the wonderland of Alice/Alfred to sketch the tomorrow of testing.

40) Testing is Learning.

41) Testing is Circus :) [This definition is contributed by Testing Circus]

I am sure you have moulded yourself into a tester with your own definition of testing and tester, do share your thoughts on the same. Come, join and be a part of this community of information seekers and providers. 

What is your definition of testing?

Jyothi Rangaiah, a trespasser into the minds of users, dons many hats that a tester should in order to test. She who has made learning a way of living. Continues to inspire herself by constantly connecting with the learned from the newly introduced community of testers. Willing to make way, where there is no way she finds herself fighting the crime scene in her vicinity. And on this journey bugs bump into her. Unwilled to take no for an answer without judgement, reasoning and questioning has helped her in her way of testing. Jyothi Rangaiah is a budding blogger who writes at A fan of defining art who's favorite English word is genuine.

Originally published here:

Thursday, 16 November 2017


Some of the attendees at the conference and those who wished to be a part of the pre-conference registered to be at the meetup that was held a day before the Copenhagen CDT conference, courtesy Danske Bank.

Pre-conference meetup was kicked off by Paul Holland who used the United States as software testing analogy and routes to different states in the USA as the test environment. It was an interesting and eye-opening session for most of us present learning about ‘The Potholes of Automating too much’ and on how NOT to test. Paul being an ex-pilot and with over 20 years of experience in testing, had several gems of lessons to share with us.
Points to ponder:
How to make sense out of the test environment when performing testing?
If the investigation does not happen then why run the tests?

The second session was by Keith Klain whom I idolize, his talk was about ‘How to "Sell" Testing to C-level Management?’
I, along with the other audience members asked questions and found ways to overcome the challenges we face selling testing to the CXO's.
Key takeaways:
Do not sell testing, instead use a language that the management understands and speak in terms of business and revenue generated, and the cost saved if possible for your voice to be heard.
I noted that Keith rarely used or referred the slides, he has been speaking about this topic for a while now and we all testers need to yet learn the tact of 'How to not sell testing to CXO's'.
Many times we fail by spending the limited time we get to educate the management on testing. Instead prepare yourself to speak in a language, and using terms that makes sense from a business perspective.

I opted to attend the tutorial on 'HOW TO COACH TESTERS TO BE BETTER TESTERS'
Carsten Feilberg and Cindy Carless with their brilliant approach to run the tutorial took us participants on a path of learning to coach self and others.
It was a fantastic full day learning by examples and models to learn how to coach.
I learned about ways to coach self which isn't all that easy and the others.
How to be and not to be a coachee was demonstrated at the end of the day by practical examples.
This exercise brought out many key lessons for us all to learn from.
I was glad to have had this opportunity and to learn from both Carsten and Cindy.
Point to note here was the pace of this full-day tutorial, breaks which allowed us all to question, learn from each other.
The icebreaker at the beginning of the session was an excellent way to introduce self to others when we first meet.
Few of the icebreaker questions are as follows:
Where is home? Siblings?1st job? Worst job?, Challenges growing up? Interesting hobbies?. It helped build trust and honor all present.

Carsten and Cindy were/are very well equipped and shared practical examples, do's and don'ts of coaching.
Lessons shared:
Coaching: Assist person A to go from X to Y in your own best way and not the coaches way.
Mentoring: A mentor helps with your existing skills.
A coach can wear a mentoring hat.
Have goal-directed conversations with your coach.
Refine the goals - Know when you get there. Build connection / rapport. Learn by matching/mirroring.
Be involved in coaching as a coach and as a coachee, know that they are with you and you with them. So that they can go through this process with you.
Coaching takes two willing participants: Coach and the coachee.
Include stakeholder when coaching.
Deal with the coachee's emotional imbalance if they come to you with it.
Coaching requires an equal level of emotion to begin coaching.
Meet the coachee at their emotional level.
Deal with the emotions, then start coaching. This for me is an excellent piece of suggestion that I learned and registered.
If feasible, invite an observer when you coach the coachee initially, as you take up coaching.
Be a guide and not a problem solver.
Do not force a coach on others.
Coaching may not be for all.
Know that some do not need a coach.
Whilst coaching, feelings and emotions can come to play, keep them at bay.
Patience is the key along this journey.
Structure of the coaching process, do not derail. Learn and refer to various models of coaching and use different models for different scenarios.
And many more gems of wisdom was shared by the coaches in this tutorial. Gratitude and love to both of them for arranging and running this tutorial with us all.
Personally, I have been briefly coached by Carsten Feilberg and he is an excellent coach one can be associated with. Kudos to them both.

Day 2 began by shedding light on the what, why, where, when, who and how of the context-driven testing community in Copenhagen.
It was an absolute honor to know about Morten Hougaard who has been a torchbearer of this education in Denmark. And with contributions from Michael Bolton, COCO2017 was made possible.

The first keynote of the day was by Keith Klain, who has adopted a great style of delivery and an excellent way of sharing lessons learned.
Few gems from the keynote:
Focus on business risks.
Test managers need to be hands-on testers too.
Think deeply about your work.
TRUST your team to do a great job.
Learn and spread the word about CDT.
Be not a tool fetish.

Having heard Keith on earlier occasions too, his talk did strike a chord with the audience and he did engage the participants very well with his notations on 'I don't think deeply about my work', 'I don't trust my team', 'I don't like testing'. Thinking testers understand this and need support from those who "don't". Let us be wise and support each other to "I do".

Next up was my talk on 'Testers role as requirement gatherers' I was fortunate to have my coach, Carsten in the audience who would later share first-hand feedback on the talk.
It was my second talk in the European region and I did not know what to expect from this audience. But the participants did give a listening ear and asked questions relevant at the end of the session. I wish I had more time to also do a practical exercise. Nevertheless, it was a great day attending other talks at the conference and this made me happy -- the seamless transition from the keynote to my talk in the same hall and with the infrastructure setup. No hassle faced. No pre-check required.
Ruud Cox was at my talk and made this sketch note. Thank you, Ruud.

To have Keith K, Duncan N, Jokin A, Elizabeth Z, Carsten F, Mike L, Smita M, from the awesome testing community present at the talk, some of who later shared feedback was helpful. Happy to have made new friends in Corey and Soren from the tutorial day, who made it to the talk.

I sat in a few other talks through the day, most promising speakers - Elizabeth Zagroba, Ash Winter, Jokin Aspiazu and Tomislav Delalic who shared their learning.

‘How to succeed as an introvert' I felt like I met my twin in Elizabeth - her talk was profound and I came back home inspired to share the knowledge with others around who feel stuck and challenged for being an introvert amidst the very vocal extroverts. Her talk encourages introverts to be just themselves and not necessarily cripple their introvert-ism or change for who they aren’t to grow and succeed as testers.
Knowledge of Testing below the application, hardware testing, infrastructure testing, deep diving into discussions on logistics, performance, logs, and the Star Wars themed slide designs by Ash Winter was brilliant.
Building Local Testing Community Out Of Nothing - Forming and growing a testing community, challenges faced, how to grow beyond these challenges made for an excellent learning opportunity to build a testing community around us. Very well presented by two testers Jokin and Tomislav from Spain, who make a fantastic speaking duo.
The last keynote ‘Implementing Context-Driven Testing Keeps Kicking My Ass - But I Think I'm Finally Winning!’ on implementing CDT at different organizations by Nancy Kelln was amazing. She is a rock star in the testing world, her brave and yet at times vulnerable ways of dealing with tough situations and people at work and to educate testers and others on testing call it CDT or otherwise is worthy of noting and following. And we need more Nancy Kelln 's from around the place I come from, someone who can Kick-Ass and be epic about it. She is awe-inspiring, thank you program committee for bringing her to COCO.

About the conference itself:
It was a very well paced conferring experience. I found time to meet and greet many friends from the testing community at the conference - Meeting Ben Kelly and family, Janet Gregory, Martin Hynie, Ash Coleman, Smita Mishra, Mike Lyles, Helena Jeret-Mäe, Nancy Kelln, Jokin Aspiazu, Tomislav Delalic, and other friends during this conferring experience was hyggelig. Testing talks during and post the conference with the other testers made it all the more worthy of being at this event despite the tons of challenges that I had to face to get to the conference. My immense gratitude and Kudos to Morten Hougaard, Duncan Nisbet, Paul Holland, Maria Kedemo, Keith Klain, Michael Bolton and others from the community who made it possible for me to be at Copenhagen Context-driven testing conference 2017.

I must confess to two things here:
  1. The challenges that I faced to get myself to this conference had affected me and the talk delivered. Learned an important lesson by the end of it all to only next submit to talk at a conference, when I am holistically well placed to make it without the multitude of issues bogging me down.
  2. Amidst the hurdles, I felt home with this specific testing community. Thank you all for making this experience of conferring happen for me which helped me make a worthy decision in my career and to move on and be better at my work and improve what I do. Thank you for the encouragement and for the inspiration COCO.

Until next time, keep TESTING which is a synonym to learning or as Ash Winter puts it 'Testing is believing'. If you are reading this, I urge you to look up this conference to learn and share your learning on CDT with the testers who wish to learn it. Special thanks to James Bach, Parimala Hariprasad, Vivien Ibiyemi, and AST without whose wise words and support this experience would not have been possible.