Today, I’m going to highlight the major excuses that I made as a tester, and I wish I didn’t! So you don’t end up sounding as careless as I did. Here is a list of excuses that website testers need to forget. 1. I Thought If It Is Working Fine On Chrome Then It Would Work Well On Other Browsers Too! 2. Why Should I Perform Responsive Testing, I already covered Cross Browser Testing? 3. My Job Is To Focus On Merely Predefined Test Case Scenarios 4. Deploying a Build and Debugging An Issue Is Not My Job 5. I Didn’t Have Sufficient Time To Test 6. I Did Not Test On IE As It Has Become Obsolete 7. I Didn’t Realize How Important It Was To Understand The Scope And Requirements Of The Project 8. I Forgot To Ask That Question? 9. I Tested The Feature A Couple Days Back So I Thought I May Not Need To Test It Again! 10. I Don’t Think It Is Possible To Test This Feature 11. The Developers Came Up With An Infeasible Code 12. I Was Told By The Dev Team That This Is How It Is Supposed To Work 13. We’re Just a Startup, There Is Hardly Much To Test! 14. All Hail Beta Testing! Even If I Miss Out On Any Bug Then A User Feedback Should Cover It 15. I Never Thought We’re Going To Be A Target For Hackers 16. Users Don’t Understand How To Use The Application! 17. It Was Working Fine On Stage Environment! To enable the smooth running of a system, it is essential to identify and fix mistakes right away. Therefore, testers play a major role in the Software Development Life Cycle. For a business to prosper, it is a must to deliver impeccable service and flawless products to customers. To ensure that, testers need to test a product and analyze it from the end user’s point of view. After identifying bugs, they need to convey relevant information to the development team. They then work on eliminating shortcomings and deploying various corrective measures. However, testers need to realize that they need to get rid of the habit of making excuses. This will help them prosper in their career as well as result in the upliftment of a company. Analyzing and testing accordingly results in an overall better product and a great customer experience.

1. 10 Excuses Every Website
Tester Should Get Rid Of
Immediately

2. support@lambdatest.comwww.lambdatest.com
1. I Thought If It Is Working Fine On Chrome Then It
Would Work Well On Other Browsers Too!
� If the software works fine on Google Chrome or any other browser, some testers give the green
signal.
� Just like humans have a different interpretation of everything, the same goes with browsers. If a
code is compatible with one browser, it’s not necessary that all browsers interpret code in the same
way.

3. support@lambdatest.comwww.lambdatest.com
2. Why Should I Perform Responsive Testing,
I already covered Cross Browser Testing?
� The process of testing your website across different mobile, desktop, tablet devices are called
responsive testing.
� It is not the same as cross browser testing, you must ensure that the customers are able to view
and use the product clearly, irrespective of the device they are using.

4. support@lambdatest.comwww.lambdatest.com
3. My Job Is To Focus On Merely Predefined
Test Case Scenarios
� The tester has to go way beyond focusing on predefined test case scenarios.
� If executing predefined test cases was the only concern for any organization then they would be
better off with automation testing.
� If you are a website tester then thinking out of the box comes as a part of your job. You have to
analyze the risks of the development plan of the present project & emphasize on exploratory
testing.

5. support@lambdatest.comwww.lambdatest.com
4. Deploying a Build and Debugging An Issue Is
Not My Job.
� If you are thinking that deploying a build is the developer’s headache, think again!
� All you need to do is trigger a build and deploy appropriate measures, there is no reason to wait.
After all, you have the authority and ability to make your work easier. Why can’t you do it yourself?

6. support@lambdatest.comwww.lambdatest.com
5. I Didn’t Have Sufficient Time To Test
� Not having sufficient time is the world’s most common excuse for almost anything!
� The moment someone is not able to accomplish something, here they are, blaming the clock for
their own failure. Everyone has deadlines to meet.
� The organization understands that you can’t conquer the world within a few hours. But that doesn’t
mean you end up being a failure on time management with an excuse.

7. support@lambdatest.comwww.lambdatest.com
6. I Did Not Test On IE As It Has Become Obsolete
� It is true, that IE has become obsolete. Microsoft discontinued IE in 2015, meaning there hasn’t
been any update ever since. But that doesn’t mean you would entirely kick it out of your testing list.
� IE is near a deathbed, but that doesn’t mean you would entirely kick it out of your testing list.
� Testing on IE is necessary as, It consists of 2.29% of the entire browser market share and that can
turn out to be an impactful number when we are looking for potential leads.

8. support@lambdatest.comwww.lambdatest.com
7. I Didn’t Realize How Important It Was To Understand
The Scope And Requirements Of The Project
� You are only responsible for finding errors before the customers and save them from nuisance.
Understanding the scope and requirements would be a hassle for you.
� I can’t oversell the importance of knowing what you are doing. Before you begin testing, it is
imperative that you read the specifications carefully.
� You can even request for a quick knowledge transition session from the product manager or the
developers to help you understand the functionality better.

9. support@lambdatest.comwww.lambdatest.com
8. I Forgot To Ask That Question
� I never really understood why some people are unable to accept that no one is a know-it-all.
� But underestimating the importance of asking questions will make you remain ignorant all along. And
you will end up at a point, where the higher-ups would be questioning you about a recent production
disaster for which you were to blame.
� No matter how experienced or inexperienced you are, you need to ask questions in case you fail to
understand a requirement or if you have some doubts about it.

10. support@lambdatest.comwww.lambdatest.com
9. I Tested The Feature A Couple Days Back So I
Thought I May Not Need To Test It Again!
� If you think your job is done after reporting bugs, you’re wrong.
� You have to realize that reporting a bug sometimes leads to changes in the code. Sometimes, the
change can impact the functioning of previous functionalities.
� It is important to check whether the product works fine after the modifications. You have to be
ready for performing frequent checks and ensuring that there is no regression defects remaining.

11. support@lambdatest.comwww.lambdatest.com
10. I Don’t Think It Is Possible To Test This
Feature
� This is one of the most ridiculous excuses I have come across so far. And surprisingly, there are
many testers who use this to escape testing a feature they don’t understand.
� And I wonder how they muster the courage to come up with such a statement. I mean think about
it, every feature put into your testing environment has already been tested by the Dev team.
� If the developer knows that a particular feature is working, and is able to test it across the sandbox
environment then there has to be a way to test it!

12. support@lambdatest.comwww.lambdatest.com
This Presentation is based on: 17 Excuses Every Website
Tester Should Get Rid Of Immediately