Wednesday, 31 August 2016

About testing conferences - Part 1

The beginning
It all began in the year 2012, when I was googling for software testing related learning materials. I recollect the intent of this search, I wished to learn from knowledge sources other than the ones that I was exposed to in the confinement of my work place. Being bogged down by listening to the process obsessed people, it finally pushed me to look for other learning sources.
This search lead me to link to ISSTA 2012 software testing conference. I began my learning by researching on how to apply, what to fill in, and to do my best and hope for the best. Post this preparation and submitting my statement on why I wish to attend ISSTA 2012, this happened -  an email from General Chair of ISSTA’12,Mats Heimdahl landed in my inbox. It was my first attempt at applying for any conference and this response was treasured. 
The awardees for the Google ISSTA'12 Diversity Grant have been selected!  I read and re-read this email.

My happiness knew no bounds, from around the world and amongst us learners, educators, graduates, professionals, 3 applicants had been granted this opportunity.
Google awarded the selected candidates a grant to participate in the International Symposium on Software Testing and Analysis.

The Aftermath
My colleagues were clearly excited about my selection. I then had to check with my manager for his approval. I did not then know this would be a hurdle! The tough part of applying, submitting, being selected was done as per my knowledge. I arranged for a meeting with my immediate manager and went to him with this news. If you are from the typical “power obsessed professionals” background, you can guess what this manager’s response was. What followed was utter disgust, it’s repulsive to even think about that response today. I came out sad and my colleagues advised me to go ahead and not wait for anyone’s approval. You have this opportunity and you shouldn’t miss it. They said.
I was not as courageous as I am today, so I had to let go of this opportunity due to the huge expenses that I had to incur for this trip. I am glad that the Test Lead, a sensible person stood by me that day. I thank him for his guidance.
I thought about reasons why the manager’s response was negative. Leaving the reasoning to rest (for then), but not my attempts to look out for different knowledge sources I met few critical thinking testers, learners and test practitioners that same year who introduced me to the WORLD OF TESTING. The vibrant testing community, to whom I am indebted to date.

Since this event, I have been at the receiving end of the wealth of knowledge from several mentors / gurus. And doing my best to give back to the community from whom I have received so much.
The first ever software testing conference that I attended is STePIN-Summit, which was a year later post the aforementioned aftermath.
I have shared that experience here - Why should we attend software testing conference?
Since then I have been on this journey of learning from varied knowledge sources. Listening to many learned test practitioners is what I look forward to when am at conferences and learn from every person and situation is what keeps me happy and going strong. If you have seen me all quiet, this is one of the reason :) I like to listen.

Fast forward to year 2016
The most recent conference that I have attended also happens to be STePIN-Summit, Bangalore.
What’s the major difference from then to now?
I know from my own experience that being brave, investing in self learning and asking with an intent to know, learn, negotiating are skills that are needed for any learner. Some testers (Parimala Hariprasad, Dhanasekar, Ajay Balamurugadass to name a few) I know invest heavily in self learning and it is all worth it (if the reader wishes to know). If you need help the testing community is supportive. There are several sponsorships offered for testers willing to attend conference and who can contribute in their own way to this vibrant community of testing. Maaret Pyhäjärvi, a pioneer at sponsoring is someone who I became aware off. She runs conferences and sponsors every speaker to get to it without having to worry about the huge (if you are trying to go from one continent to another) expenses incurred. In another instance, our community came together to help Kim Engel attend Let’s Test.

Tips to new testers attending conferences
     Bring your thinking hat and wear it too
     Take what teachings / learnings fits your need as a learner and leave the rest for later (or when equipped to make decisions on such matters)
     Attend all conferences initially, learn which ones to frequent and which ones to not
     Inspire your colleagues / friends to attend conferences. There is an added advantage, you can split among yourselves which talks you attend and learn from the other parallel tracks
     Learn with people who share from their own experiences of failure and success
     Network and SHARE what you learn at conferences with other learners

STePIN-Summit 2016
A bird view of what I learned at this conference.

Note: Click on the images below to view it in it's original size.

Web, mobile analytics - All about data

UI / UX Learning - Micro Interactions

To Automate or Not to automate - what, how and when to automate!

Above all, network and learn

Hope this attempt to draw the attention of testers to the world of software testing conferences has inspired the reader to attend meetups, arrange, organize, speak, participate, volunteer in your own capacity.

Sunday, 21 August 2016

TESTING - Struggle, Strategy and Solution

A Survey conducted by Mike Lyles - Answers by me.

Question 1: What are the major struggles that you have within your testing organization (or organizations that you support/consult with)?

The struggle that I personally encountered was with the knowledge transfer when I joined an organization as a tester. People who lead and their limited knowledge on testing which then trickles down to the next generation of testers, this is an on-going problem which translates to a struggle for next generation testers. If we continue to not think critically and encourage such dark patterns, that is a problem every organization faces testing or not. Many testers lookup for guidance as they join an organization and most of them come with limited / no knowledge on testing as testing is/may not be a part of their academic course. In such scenario, if people who lead do not help them then they will be lost and/or will grow into a replica of their leads/managers. Educating the educated is the struggle here.

Question 2: Can you think of and/or describe a time when you had to modify your plan/approach/strategy so that you could ensure success? (whether it be keeping the project on schedule, reducing the risks, reducing the defects released to production, etc).

In a process obsessed environment, yes there is a need to change the plan and think individualistically and for the whole good of the project / organization. In order to be able to do so, the change initiator needs to have had an experience of running the project in a holistic view.
To quote an example: A project that I was working on demanded the need to follow a template which was not well researched. The template itself had gaps which needed to be filled. I was asked to blindly follow the template and when I questioned the template itself to know more, I learned that it is not suitable for every domain but needed changes when there is a domain shift. Ultimately I had to quit this job, because the management did want to stick to the template than make any changes to it. This is a risk that I took to uphold my values and integrity and deprive myself of the suffocation in that environment.

Question 3: What do you think is the "next big thing" that is going to require a change or a strategic re-alignment from the testing organizations?

Train the testers at all levels. And learned testers to educate not just the testers but the management and clients. Unless the basic know-how of testing is not known, the next big thing is far from reach to us all. Testers are not mere testers but *product engineers. This should be our aim, if we limit our roles to being testers and not product engineers then there is a chance of us remaining stagnant in a particular firm which does not require thinking testers.

*Product engineer is someone with a holistic view of the product right from the requirements gathering to the release and beyond.

Question 4: What do you think is one thing most test organizations are the most confused / segregated / indifferent about (e.g. there are various beliefs involved)?

     Following the footsteps of a MNC without doing their own research on what tools/processes/metrics to use, when and if it suits our context
     Being business oriented and not investing on learning and development on their main source of profit

Question 5: What do you think is at least one CORE thing EVERY team should do to be successful?

     Simply by creating a fearless environment in which we can all learn from each other and thrive without competing amongst ourselves
     Treating everyone equally is something which even this generation of professionals need to learn to be able to work towards one common goal
     Making the ultimate goal for testers to be product engineers can help the future of testing and test engineers