5 reasons why you missed bugs and how to stop them

Tram Ho

Many people believe that testers are responsible for finding all errors in the system. If any errors occur when the product reaches the customer and causes loss of sales, the company’s reputation, potential customers, … then the tester is also responsible in it. Therefore, missing bugs is a pretty bad thing for testers.

This article provides 5 reasons why we often miss bugs in software testing and what we can do to prevent the bugs from happening again.

1. Missing bug because you didn’t test that part.

This is obvious. If you haven’t tested through a feature yet or missed the test case, chances are the error will be passed on to the customer. Of course, there are a number of reasons why you might not have tested the feature, because you forgot it or because your test design was bad. But these are common reasons:

  • The Developers team made changes in the code and you were not aware. Developers may intentionally hide it, or they simply think that the changes are small, have no effect, so there is no need to test or report changes.
  • Due to a communication error: the leader has not reported that change to you for testing.

What can you do to prevent that?

  • Keep track of all possible changes in every release, especially changes of important components or last-minute changes. If you are in trouble, ask about the changes and, if possible, pose risks if testing is ignored for those changes.
  • Thanks to the leader to discuss issues with all components of the project, regularly communicate, exchange to convey necessary information, talk more about risks and quality of the system.

2. Not all cases are covered.

Bug is always hidden in the system, so it is not easy to find, requires a lot of effort, good testing methods.

In many cases, complex steps or combinations must be performed to find the error. Technically, software is becoming more and more complex to serve and meet today’s business needs. With Blackbox testing, you may not be aware of the complexity of the system or how its components work together. As a result, you have not fully identified the test scope or the test cases where many bugs are difficult to find. These bugs sometimes make people wonder “why did this happen? Who caused it?”.

What can you do to prevent that?

  • As a tester, put yourself in the shoes of a user to understand how they usually use the product, and unusual actions are also ways to find bugs.
  • Learn about how the system works. In many cases, you do not need to know how the components of the system communicate with each other, or understand each line of code. However, understanding the system overview from a technical perspective will help you find bugs better.
  • If you have a lot of time, take the time to design and cover as many combination conditions as possible. Of course, this will take time, but it will bring certain efficiency.

3. Ignore obvious and visible bugs.

Sometimes the bugs that are missed are very obvious, obvious ones in front of us but we don’t notice them.

There are several reasons why you do not see such obvious errors:

  • Too focused on testing a specific area of ​​the system without taking care of the problems of other parts.
  • Focus on a different task, so you do not pay attention to error detection. For example, you are writing test designs and test cases and may still be interacting with the system. But because it’s focused on the main thing and you might miss the obvious bugs, it’s easy to see.
  • The bugs are obvious, easy to see, sometimes many testers think has been discovered before they can see.
  • Test the same method and repeatedly with a feature.

What can you do to prevent that?

  • Practice to be a “multi-tasking” tester, always sensitive to bug detection, so as not to ignore the smallest bugs.
  • You can also try to approach the system from a different perspective, applying different techniques to test.

4. Time pressure

Many customers want to launch software products to market as soon as possible. The downside of this is that the testing team is under pressure of having to complete the test in time for the deadline. That means they have to work overtime or accept to skip some test cases in this release. When the testing team is “running” to keep up, they ignore some cases, and bugs are hidden in the cases that they missed.

What can you do to prevent that?

  • In fact, the only solution is to find a way that you don’t feel pressured by the pressure of time, so you can ensure software quality and limit the number of bugs missed.
  • If the delivery time is fixed, communicate more with people to analyze risks and limit bugs in some simple test cases that you intend to ignore. Talk to the leader about the testing progress, the risks that may be encountered when not performing the test for that case.

5. Identify the problem but do not report it.

There are definitely bug encounters, you think will report it later. But then moving on to another job, testing another part and then “later” became “never” (never). You completely forgot to report the bug.

In other cases, it is suspected to be a bug and you may not be sure to report it (for example, I don’t want to disturb Dev because it is not necessarily a bug, want to check further) or you evaluate the level. The severity of the bug is low, the user doesn’t care much, so he skips it. As a result, you decided not to report the bug. But that bug may not be important (to you, to this section) but a serious error (to someone, to another).

What can you do to prevent that?

If you think it’s a bug, report it (of course, always explain why you think it’s a bug). It is a necessary action that testers should perform more often. And report as soon as possible when problems are detected.

Conclude

As a tester, our job is to test and deliver valuable, quality products to software product managers. In some cases, testers act as the final gateway to assess product quality before handing over to customers.

Here, there are important points to note: Ignoring bugs is not good, can have many serious consequences. If that happens, consider the process of testing, drawing lessons to prevent it from happening again.

Reference: https://www.asktester.com/5-simple-reasons-missed-bugs-prevent/

Share the news now

Source : Viblo