Blog

6 most common reasons bugs are missed

Missing bugs happen to all junior testers. We list the most common reasons that lead the tester to miss bugs and measures to prevent them.
23 May 2017
Quality assurance
The article by a1qa
a1qa

Let’s face it: missing bugs is frustrating. It will be even safe to say a missed bug is the worst nightmare of any tester.

Why so? There is a myth and misconception that testers should hunt all bugs. Testers are viewed as goalkeepers who are the first to blame if there is any bug leakage to the production.

Yes, missing bugs is annoying. But there are reasons behind it. Let’s look at the most common ones and offer solutions that can help testers fix the situation and never let bugs appear in the final version for the same reason.

#1. The pesticide paradox: with the course of time test suites wear out

Almost 20 years ago Boris Beizer, American software engineer and author, formulated the Pesticide Paradox:

Plainly speaking, it means that when tests that are launched hundreds of time, they stop being effective. As a result, a number of bugs that are introduced into the system are not detected by existing tests get to end users.

What can be done?

Never assume that you can build an ultimate test suite that will detect all the bugs in all product versions. What you should do to ensure your tests are working well and perform successful testing is to keep track of the product changes, review and update your test suites regularly.

#2. Lack of time to test that area

It’s not a rare case when software testing team gets under time pressure and has to opt either to burn the midnight oil working overtime, or skip some tests. Even if you are diligent enough to select the first option, you will certainly be in a hurry. And it’s quite natural: when people are in a hurry, they overlook things and miss the bugs, even the most obvious ones.

What can be done?

If the deadline is fixed, communicate with your manager to decrease the scope of testing and analyze risks. Prioritizing testing is also a great plan here as you can suggest skipping low-risks area and focus on the business critical functionality. Tell your manager or any stakeholders what you can test, and what you don’t have time to. Also, inform on the risks entailed.

Be transparent and never hide the issue from the customer hoping that the bugs won’t reach end users.

#3. Missing the most obvious bugs

You can’t even imagine how often the bugs that seem to be right in front of your eyes are missed! And they are the most annoying ones. Testers miss them because they get accustomed to them while looking at the app under testing. It may also happen when a tester is too focused on another task and switch off the “bug hunting mode”.

What can be done?

Practice multi-tasking and attention to details. Try to put yourself in the end user’s shoes and click the application from scratch.

#4. Requirements documentation is improper

At times, the root cause of the missed can be found on the earliest stages of testing projects, when testing itself hasn’t started yet. And it’s about poor requirements documentation. If the documentation doesn’t cover all usage scenarios, testers will not cover these scenarios when testing.

It’s very important that both requirement documentation and test cases prepared should be complete and clear, covering all functions and user scenarios. From our experience, we’ll say for sure that it’s less costly to prepare comprehensive documentation than fixing a bug on late stage of the development.

What can be done?

While establishing proper communication with the customer and asking proper requirements documentation is the responsibility by test managers or business analysts (depending on your organization workflow), there is something you can also do to avoid miscommunication errors. Make sure you know the expected system behavior before getting down to testing. Once the requirements change, make sure you’ve reviewed and updated your test suites as well.

#5. The bug was discovered and reported, but it was too costly to be fixed

Testers are responsible for providing developers and stakeholders with relevant information on the system quality. However, it’s not their responsibility to decide on the developers’ work or product’s release.

Actually, there are many factors to decide on going live (much more than bugs presence). And at times it makes sense to ship the product even with minor bugs in it.

What can be done?

Report all the bugs to the developers in a clear and timely manner. Before the release, provide the stakeholders with the most comprehensive feedback you can on the system functionality, performance, usability and security.

#6. This area is intentionally left blank

It’s up to you to fill it: add any other reason for missing bugs.

Welcome to the comments!

More Posts

QA for fintech
7 May 2024,
by a1qa
5 min read
Navigating the fintech frontier in 2024: QA’s role in delivering high-quality financial software 
Unveil the future of fintech innovations and learn to refine their quality with the help of software testing.
Blockchain app testing
Cybersecurity testing
Quality assurance
Shift-left testing for better software performance
25 April 2024,
by a1qa
4 min read
Optimizing software performance with shift-left testing
Still in doubt whether to include performance testing from the initial development stages? Learn the benefits companies obtain with shift-left performance testing.
Performance testing
QA consulting
Quality assurance
Telecom trends 2024
15 April 2024,
by a1qa
5 min read
QA’s role in adopting telecom trends for 2024 
Let’s dive into the transformative trends set to redefine the telco industry in 2024 and discover QA strategies to adopt them with precision.
Cloud-based testing
Cybersecurity testing
Functional testing
General
Migration testing
Performance testing
QA trends
Quality assurance
Test automation
Zero trust in retail
27 March 2024,
by a1qa
4 min read
Fortifying retail security posture: embracing zero trust to protect customer data
Why adopt zero trust in the retail sector? How can companies ensure increased resilience to cyber incidents? Find out the answers in this article.
General
Quality assurance
Advancing QA and software testing processes with AI
14 March 2024,
by a1qa
4 min read
Advancing QA and software testing processes with AI
Uncovering the benefits companies gain when revolutionizing QA practices with the help of AI and tips to implement it.
General
Quality assurance
Navigating the future: QA trends that will define 2024. Part 2
30 January 2024,
by a1qa
4 min read
Navigating the future: QA trends that will define 2024. Part 2
We continue exploring QA trends, helping businesses remain competitive in 2024.
Cloud-based testing
Cybersecurity testing
QA trends
Quality assurance
Navigating the future: QA trends that will define 2024. Part 1
15 January 2024,
by a1qa
4 min read
Navigating the future: QA trends that will define 2024. Part 1
Discover topical software testing trends that will shape 2024 and empower companies to smoothly implement advanced technologies.
Agile
QA trends
Quality assurance
Test automation
2023-year-end-recap:-a-journey-through-the-a1qa-milestones
20 December 2023,
by a1qa
4 min read
2023 year-end recap: a journey through the a1qa milestones 
As we bid farewell to 2023, join us in recalling noteworthy achievements and unforgettable moments that have defined this year!
General
Quality assurance
The year in valuable conversations: recapping 2023 a1qa’s roundtables for IT executives 
8 December 2023,
by a1qa
3 min read
The year in valuable conversations: recapping 2023 a1qa’s roundtables for IT executives 
From dissecting novel industry trends to navigating effective ways of enhancing software quality — let’s recall all a1qa’s roundtables. Join us!
Big data testing
Cybersecurity testing
Functional testing
General
Interviews
Performance testing
QA trends
Quality assurance
Test automation
Usability testing
Web app testing

Get in touch

Please fill in the required field.
Email address seems invalid.
Please fill in the required field.
We use cookies on our website to improve its functionality and to enhance your user experience. We also use cookies for analytics. If you continue to browse this website, we will assume you agree that we can place cookies on your device. For more details, please read our Privacy and Cookies Policy.