5 Excuses Every Software Tester Must Stop Giving

In this article, I have listed down some very common excuses that every software tester should immediately stop giving.

I have unlocked a pattern from my experience of hiring around a few hundred testers and interviewing a thousand others over a long period of time .

From all the discussions I had with fellow testers during interviews, I felt happy numerous times seeing the quality talent that we have in our community of testers.

But let me also share the other side of the story, the pattern that I am talking about makes me sad. I’ve never felt happy watching potential performers being locked into a virtual cage of responsibilities. I feel discontent seeing the rock stars performing on a controlled stage.

If you are still wondering what the matter and the baseline is, it is this – a considerably large part of our testing community is not having enough growth on multiple fronts after they start their testing career. Forget 360 degree, it is not even nearly half of that.

Sorry for being harsh, but it is real.

Who is to blame for this? Maybe awareness in the industry to some extent. Company policies and senior management too may be. But more than anything else, it is the Tester himself/herself.

Read it again, it is YOU. It is us. Because we become victims of the excuse.

Given below are a few patterns/excuses I have discovered:

5 Excuses Every Software Tester Must Stop Giving

Note: I nowhere mean that this is the case with every tester and every organization. But I have seen enough examples to say most of us are victims here.

#1) We don’t control our Test Environment, we have (read ‘very’) limited access

I often hear the statements/excuses- ‘We have just Read-only access to the environment’. Even worse – ‘We only have access to logs and nothing else’.  Everything else is done by either a Development team or some other team.

The work that will give us so many beautiful and fruitful insights about testing and many other technical kinds of stuff is not done by us. And maybe we are happy this way, but we should not.

Tell me one reason why you shouldn’t control your test environment and take maximum benefits of the same.

Here are a few possible benefits if you are wondering what I am talking about-

1. You have full control over your test environment to make sure personally that it is an exact or near replica of the production environment. This will help you avoid a few surprises when your deliverables hit production.
2. Know all involved components and all software used along with their versions for your product to function. With time, trust me you will have many insights about their work, limitations and possible failure points.
3. You have enough access to do at least first level debugging in case there are Infra level issues. E.g.: Setup running slow, checking CPU, memory utilization and logs at every level of flow is not rocket science.
4. You own control over the setup so you know what you are changing and what build you are deploying. You are much more confident than before while shipping the release ahead.
5. You learn it and you learn it all. Though it is Linux based or Windows based.

Makes sense? Let me continue if you have at least agreed that there are benefits.

Now the question is what changes you can make to your team/organization to make this work. And that’s exactly how you will do it.

Well, as I don’t know your team, your leads/managers, or your organization, I won’t be able to help you with this. Sure, I can definitely share a few things that might work. Try working very closely with your Dev or whichever team owns this and see what and how they do stuff.

The way they login to the environment (server), the way they logout and everything in between. Once you gain some knowledge, you will have the confidence to say few words and give some suggestions when a similar situation occurs again or if a similar activity is to be done again.

Obviously sooner or later this confidence will be seen by your developers/leads/managers. That is the time you can ask for control. And tell me one strong reason why they won’t give you that? They should be more than happy to do so if you have shown the needed capabilities.

Believe me, they have much more work to do, so it shouldn’t be hard for them to release the control to you. I hope that is the case.

#2) We don’t deploy a build, some other team does it for us

You can come to the office on a Monday morning. You will notice there are a few issues in the build causing blocker. You need a new build from your Build repository. You can raise a request or contact your Dev or deployment team. Oh, they are busy with something. But they manage and do it after some time.

Now tell me, why all this? It is not as complex as it looks.

When to take a new build is surely something a Developer can suggest as he is the one who will be committing a feature or a bug fix. But when you simply need to trigger it and deploy it, why should you wait or depend on someone?

Recommended read => Know About Release and Deployment Management Processes

Having the ability and authority to deploy whenever you want makes your work lot easier without any wait. Do you see that? This will also increase your Turnaround time for daily testing. However, we are debugging some defects with added loggers or taking the new build to verify resolved bugs. Or be it taking a fresh build and starting with testing a new feature.

Let me tell you something from my personal experience. It is not only about time. Deployment teaches you so many things that you can’t imagine. The reason is, it fails often. The application sometimes stops working with the new code. Often deployment itself fails. And every time something fails, it pushes you to debug it. It pushes you to search for something on Google or ask someone a question or the best ask yourself a question.

It makes you think.

Of course, it is not really a software testing, but it surely is testing your abilities.

I would say a large portion of my learning apart from pure software testing is from Deployment and Maintenance of environments.

• I don’t remember how many trial and error attempts I performed for something, the count must be a few hundred.
• I don’t remember how many times I went to check some release manual of some software.
• I don’t remember how many times I hit that Google search button or navigated to that stack overflow link.

All I know is- it gave me a lot, taught me a lot.

The remedy for this is very similar to the first excuse we talked about.

Learn it, show it and ask for it. It might work.

#3) We don’t debug an issue, we found the steps and logged it

I won’t go very hard on this as in an interview you don’t get a chance every time to discuss particular defect from candidate’s own experience and investigation/debugging done by him/her.

However, I can surely say that not all of us challenge our senses before passing on the defect to the developer.

Many times the log says it all. Often the pattern of an issue says it all. Many times it fails because some prerequisite service was down.

So in short, many times it is possible for us to get to the exact root cause or at least reach near it.

So please ask yourself a few questions, not to help developers but to make your test cycles faster and for your own growth.

You are the remedy and no one else.

#4) I don’t know why it happened. The developer resolved the issue and I simply verified it

Sorry but I get annoyed hearing this.

Every single time, it annoys me when I ask Tester a question- Why particular defect was faced or what was the RCA (Root Cause Analysis) and he/she answers ‘I don’t know’.

Have we taken the black box word this literally? How can we not ask the Developer what exactly he fixed? Why can’t we ask if authority is an issue?

I am damn sure that 99% times we don’t know the Root Cause Analysis (RCA) or fix because we don’t ask for it.

Believe me, knowing the exact fix, module in which the fix was done, whether it was in the front end or back end, whether it was injected in any feature development or some other defect’s fix, will always help you in your testing. Always.

Apart from this, this information helps you know a lot of technical stuff which may be otherwise you will never come across.

Remedy? Ask for it. Demand it. Whichever works.

#5) I didn’t get the opportunity to work on anything other than Manual Testing

This excuse may be valid to some extent considering the possible workload on you or the restricted responsibilities given, but not completely valid.

The problem here is, we say that we didn’t get the opportunity to perform non-functional types of testing, or we are not supposed to do it or we don’t have time.

Agreed, learning always demands time. But isn’t there anything you can change?

While testing that new feature or while testing that one API,

• Isn’t it possible for you to keep a watch on the response time?
• Isn’t it possible to ask your Business Analyst about the load this particular feature/module/API is expected to handle in production so that you can test it?
• Isn’t it possible to at least perform basic security checks like session expiry, URL tampering or XSS handling on that website form you are supposed to test?
• Isn’t it possible to at least say that this particular ‘Submit’ or ‘Help’ button doesn’t seem to be properly located or not easily noticeable and plays your small role in making the product more usable?
• Isn’t it possible for you to start with something and then keep learning it more and more?

The answer is YES, small or big depending on various factors surrounding you but it is surely not NO.

If your responsibility doesn’t demand it (because there is some other team for it), no one will stop you investing extra time for your own learning. Self-learning in extra or free time is always possible I think. So find those possible extras and start doing it. Now.

Conclusion

I hope I was able to trigger some thoughts and learning ambitions in you.

Please forgive me if you find me harsh, but believe me, my intention was to be 100% clear so that the message reaches out to you with the needed seriousness. Hope it works well for you all.

I will be more than happy to know any uncovered aspects around the possibilities I talked about.

About the author: This article was written by STH team member Mahesh C. He is currently working as a Senior Quality Assurance Manager with experience leading the testing front for multiple complex products and components.

Thanks a lot for reading this article. Feel free to share your views/feedback in the comments section. We would love to hear from you.