A Testers Life

There is a plethora of examples explaining about a Developer's life. It is time to show the QA in the same "light". I am a QA and only some of these are my experiences. Which ones can you relate to?

This is what they think QA are like


This is what we wish QA could be like


My first day on the job - I am introduced.

Product training for QA

I am trying to find my way through SharePoint


It has always been like this. It's not a bug, don't log a ticket for it, the existing QA tell me. (Or maybe they do not want to admit that they missed a big fucking bug.)


This is how Devs are trained about the project.


This is how QAs are trained about the project

I finally get my build to test. It is 5:00 pm Friday

I am not given access to anything, but I am expected to test

Setting up Test Data


Smoke Testing (it usually never detects the fire or smoke till we get to production and a customer reports it. But it sounds good.)


Trying to catch a sporadic bug. Arrrrrgh!! 


I test on multiple environments. (One size does not fit all)


All paths do not lead to the destination

I test with all possible scenarios


I also test on IE. (!!Why are the Mac users sitting next to me!?!.)

With every test, I see bugs crawling towards me.


My bugs got closed without justification.


Dev Team meets me for the first time

One of the thingies is spinning. Dev tells me it met the specification!! (They close my bug)

They tell me it is a great space saving design "users" will be happy using it. (Again it is not a bug)

Dev asks me to redo every step that lead me to find the bug. I do it even though I know it is not relevant.


I reproduce the bug for the developers, the PM, the BA, other Stakeholders. (my keyboard is chaffing)

Testing the same thing over and over really feels like this. Dizzy!! (sorry regression testers.)


I really don't want the tests to Fail. But I have to do the right thing.

PM's reaction when I stop the release and Dev supported my decision

Revamped product looks modern. Team agrees it is modern and we are out of time and budget. What the heck, lets release it hope people won't notice it. 

Expected vs. Actual. 

They ask for MY opinion during retrospective. (My contract is often ended for being honest.)


They hate me for logging bugs and doing my job.

Product is released. I got Fired

They told me it's an edge case, none of our users can do that in Production. (deal with the upcoming law suite bitches!!)

To Process or not to Process

A long time ago, there was a land lord who started the tradition of throwing a huge party for all of his town folk in his huge backyard once a year. Right before the party began, the land lord would get his men to catch his pet Cat and put her under a wicker basket and then put a brick on top of the basket. Right after this event, the party would begin.

The landlord passed away and his eldest son took over the family house and the traditions. The eldest son did not have a pet cat. But every year at the time of the party he would instruct his men to get a cat. He would then put the cat under the wicker basket and then put a brick on top of the basket.

This tradition was as important to this landlord’s family as having a real turkey or a fake tofurkey on Thanksgiving to most of us Americans. Nobody had any issues with this process, so they went on carrying out their practices.

Now, let’s try and understand about why the landlord originally used to lock his cat right before the party began?

1. The landlord really loved his pet and did not like to restrict her freedom. 
2.  The landlord liked to devote his time to entertaining his guests at the party.
3.  The landlord was afraid of his cat hurting other kids or even worse someone stomping his cat by mistake.

So, in order to take care of all the three issues, the land lord used to lock his cat up for her own safety and convenience of the guests. He used a wicker basket because he had them in abundance at his house. He used to use the red brick to weigh down the wicker basket restricting the cat to tip over it and run loose.

His son had observed his actions and followed the actions, but did not try to understand the purpose behind the actions.

What is a process?

Process is the practice of executing related tasks in a certain way to accomplish a goal.

1.       This practice could be executing tasks sequentially synchronized.

2.       This practice could be cataloging tasks in a certain way for easy identification.

3.       This practice could be to identify certain annoyances and take care of them.

4.       This practice could be to have gate keepers at certain locations.

5.       Etc.

Example of a process –

Waterfall  

Agile 

Scrum

  Etc.

Q. When to follow and not follow a process?

Many companies and projects like to implement the text book version of process without first understanding if the process will work or break with their core. And this is not necessarily the best way to implement anything.

1. Process for the sake of process does not add any value to the team and the company.
2.  Ever revised process will help the team to be efficient.
3.  Understanding of why to do certain tasks in certain way makes for a better process.

Process is good. Following a suitable process is as effective as epilating regularly (it is less painful with fewer surprises and leaves few chances for public embarrassment). Keep revising your processes and make sure it works for you. 

Test the pencil

(Not to be mistaken for the pencil test)
 If the requirement for a pencil was to write 10 pages, and during testing the pencil ended up writing 12 pages.
What should the testers do? Pass it or fail?
Should the testers PASS the pencil test because the result was better than expected?
Should the testers FAIL the pencil test because the result was not per spec?
May the testers ask for more specs regarding the weight and thickness of the overall pencil?
May the testers ask for more specs regarding the weight and thickness of the lead core?
Should the testers re-test the darkness of the writing?
Should the testers use other kinds of paper for executing re-testing?
What would you do as a tester?
Why should you do anything else besides testing and giving a pass or fail?



Possible defects – 

1. Longer pencil than mentioned in spec
2. Thinner lead core than mentioned in spec;

Possible concerns – 

1. More money is being spent on the pencil
2. Less return of investment may be the result.

A few opinions I collected over the years - 

1. Need more clarification and information
2. It is a FAIL because the company could be losing its return on investment.
3. It is a PASS because more the merrier
4. When the requirement was to test till 10 pages, the tester should have stopped testing at 10 pages. The extra testing is exhaustive testing. We should limit our tests to the resources we are provided only.

What would you suggest and do, if you faced such a situation?

QA in most companies is like Sex Ed in most schools

The movie Mean Girls has a sex Ed class scene in it. The gym coach gets a bunch of teenagers into a room and explains about sex like – “at this age you will have urges to touch each other. If you do you will get pregnant and die. Don’t have sex. Guys promise you won’t do it!!” at the end of the class the coach brings out a bunch of contraceptives and offers to the students to make it look like they are serious about the "education".


Companies have QA teams. The QA team is trained for a release as such - “at this time you will have urges to do boundary value analysis, top down testing. If you do it and find bugs, we do not have resources or permission to fix them. Guys just do testing and nothing more.” At the end of the project they throw in automated testing for regression tell themselves that they are serious about testing.


This is (fortunately) not true with all companies. But if you are dealing with a situation similar, laugh out loud and do your best. You are not alone. Do your best for your product and help your developers do a better job. But don't give up.

Now, I cant say the same to the sex Ed teachers.

Tool is only as good as the user

As a SDET, I believe that the automation tools wrongly called testing tools, can do no testing. It is a tool that does what I tell it to do. I can tell it to go through all the pages and it will. I can tell it to pass a failed test and it will pass. I can tell it to fail the whole application and it will fail. Once again, it is a tool that does what I tell it to do.



Kind of like this story - 
Once upon a time there was a King who owned a device that worked like a lie detector. The device had a pointer that would point to the left when a person wearing it lied, and to the right when the person spoke the truth. The king was very happy that he found a device that will help him in judging people rightfully. The minister was concerned though. He did not believe the device was of such great use. He also feared, if would cause harm in certain cases.

One day the cops brought in a farmer who killed his landlord.  The cops put the device ("lie detector") around the farmer's throat and asked him if had committed the crime. The farmer replied "No". The device pointed to the right, which meant the farmer was telling the truth. The cops released the farmer. But the village folk complained again that they had witnessed the crime.

So, this case went to the King and the minister, where the farmer was asked the same question and the device pointed to the right upon the farmers answer. The King tried the device on himself and lied while wearing it and the device pointed to the left. This got the King confused. The minister stepped in and asked the farmer if had 'indeed killed the landlord?'. To which the farmer replied, "Yes". The device pointed to the right again.

The farmer killed someone, but he did not consider it a crime. So, that explains why the machine reacted the way it did. The machine did its job.


Tools will always be tools. Tools are only as good as the user. To find answers, we have to ask the right questions. To find bugs, we have to ask the right questions. Too many questions or less questions are not the key here. The right question in the right context matters. Even when using Google search or queering data base tables, testing an application, it is our responsibility to choose the words / questions / tests wisely.

If testing was like sex

No wonder most Software out there is f...ed up and violated!!

According to Freud - the unconscious mind and the primary motivation for all things in life is sex. So, I am comparing software testing  behavior to making love during my leisure (bored out of mind) time. One more reason for doing this - both these subjects are kind of taboo even in the most open minded culture.

A first time virgin tester does their best, completes the job as their instincts tell them and from all the
documentation (videos) they had learnt from. But they know there is more to it than just completing the task.

In a stress free environment, the tester is enthusiastic and wants to give their best because the application deserves the best (in order to improve the product, make it bug free). So, they get the book that contains all the various techniques for completing the task. They learn and apply all that they learnt. During the process they understand there is no way in hell they can go through some techniques, due to lack of time or lack of more knowledge or it just does not make sense.

In a stressful environment, the tester does not dare to attempt more than what is expected. The job is complete and that is all that matters. They do not have the luxury of knowing the application more. Besides no on ever got fired for missing a bug.

In a perfect environment, the tester does not just jump in to finish the task. They get to know the application. The more they understand the application, the better they can plan their tests. They may be the one or they may not be the one. They wont know more till they explore.

A knowledgeable tester will realize it is the best thing to step down if they are not equipped to test the product.
An intelligent tester will train themselves to gain the knowledge necessary to test the product.
An average tester will just hang in there and look busy while doing their best.

A tester that takes the time to learn about the application and takes the time to explore it can come up with the best possible tests suitable for the particular application. Every application is unique with certain similarities. They may all look the same but they come from different places. Their needs are different. Their environments are different. They are made differently. They are made with sugar and spice and everything nice. (lol)

Do not assume your application is your female dog. Know your application accept it with all its flaws and respect it. Then custom design your tests. Never stop exploring. There is no stopping you now.