Sunny afternoon, an IT company, two testers at the vending machine –
Tester 1: This job sucks. For a whole day, I keep executing the same test cases that I did yesterday and still most of them are failing. The product manager is not happy with me because test cases are failing and I am clueless about what to do.
Tester 2: I agree. I am facing same problem too. I do not find anything new to do. I am expected to write test cases every day and whenever I present new ideas, they get rejected with different excuses.
Tester 1: I am searching for a new job, which would give me an opportunity to grow and explore… … ….
Tester 2: Please do let me know wherever you apply as I am keen to find a new opportunity too.
What do you understand from the above discussion?
- Both testers are looking for new jobs
- Both testers are tired of the current work
- For both testers, current work is not interesting
- Both testers assume that they will find something interesting in their new job
Well, the truth is – No job is monotonous, definitely NOT software testing. It’s the person’s perception that makes them feel so. I know, there may be tons of arguments.
Let me present my case –
As a tester, you are supposed to test login page for the application. The application is supposed to work across different platforms and you are supposed to test it thoroughly.
- Do you think the job is monotonous?
- Do you think you are not learning anything new?
- Do you think there is nothing to explore about?
Let’s see –
- What if the user provides login credentials and closes the browser? Are the credentials getting retained?
- What if the same user tries to login from different platforms at the same time?
- What if the user has to wait two minutes before being navigated to the home page, after providing valid credentials?
- What if user provides valid login credentials and the database server does not respond? What will be displayed to user?
- What if the user has provided valid credentials and did not click OK or Submit button and left the page as it is for half an hour?
- What if user had provided valid credentials and clicked on OK or Submit button 10 times consecutively?
- What if user had provided valid credentials and clicked on Forgot Password?
- What if user changes the URL of login page by appending some SQL injection query?
- Will knowing about how other application’s login page works make a difference?
- Will knowing UX (User Experience) updates from the industry make any difference to the tester?
Do the above points seem interesting? Of course , yes. But they could seem routine, when you have to execute them for all supported platforms.
OK, let’s strategize.
Execute all for one platform. Find out major problems and confirm them for other two platforms. If they exist, just do not test further and reject the build.
Reasons for monotony as a software tester –
So, if I have to conclude the reasons for monotony as a software tester, I would like to mention the following points:
- May be the tester is NOT thinking out of box
- May the tester is too lazy to execute the same cases again and again
- May be the tester is not interested in learning something new.
- May be the tester does not know how to implement their newly acquired knowledge
- May be the tester is not passionate about testing
- May be the tester is not able to motivate himself/herself
- May be the tester is not able to find bugs and feels guilty about it
- May be the tester is not sure about real time testing and is just aware of the
- May be the tester just does not want to think anything else than scripted test cases
- May be the tester is not allowed to explore due to workload or access issues
- May be the tester is under pressure in terms of deadlines and deliverables
- May be the tester has lost interest in whatever he is doing
- May be the tester has not taken a break since long
How to work on yourself, if you think your work is monotonous –
Analyzing the root cause for the monotony and curing it is the solution.
Realize that, while being in the most happening field, if you feel monotony, you need to work on yourself. How to do that? Well, there are many ways –
#1) Discuss and discuss: Healthy discussion can result in you and the others involved in the discussion, learning something new.
Being a tester, discussing a scenario, discussing result, discussing behaviour of the application, discussing the bug fix has been always helpful to me to understand and think about the points that I might have missed out and I am sure, most of the testers will not deny this fact.
Also read =>
#2) Explore and understand: Software testing is about generating ideas, as I have mentioned many times in the past. Anyone can execute the documented test cases. But think about generating different test scenarios and not everyone can do that. It needs constant learning from other applications, other team members, other teams and the industry too.
When one can train himself to see everything with an eye for testing, a real tester emerges and that tester can surely make a positive difference.
#3) Read and learn: Software is the industry, which continuously changes. New technologies, new challenges and new experiences gear up every day and as a tester, it is very necessary to learn constantly, to be well-versed with whatever you know and to discover what you do not know and get an idea of it.
#4) Self-motivation: Self-motivation is the most needed tool for software testing. Most of the time, people hate you or ignore you when you try to criticize or find issues in their work. And believe me, it takes time to train yourself to see those negativities positively and motivate yourself every time.
#5) Finally, you should read this => 16 Things to Do When You’re Bored of Testing
So, from now onwards, whenever you feel your job as a tester is monotonous, take solace in the fact that we are lucky to get a chance to think out of box, to execute ideas, to analyze things and finally, to announce whether something is fit for use or not…a big satisfaction? Of course, YES!!!
Author: This encouraging post is written by STH team member Bhumika M. Now she is in software testing field for more than 10 years.
Happy testing readers…. let’s cheer for ourselves :)