A bug was found in the product that the test cases did not highlight. As a QA Engineer, what would you do?

  1. Update the test script to cover that issue
  2. Use your product knowledge to update the test case for that particular issue and other problems you might foresee
  3. Don't change the test script as the bug was already a problem
  4. None of the above

What do you guys think?

  • HI @Jay pesticide paradox principle of testing says you have to keep modifying your test scripts as the product gets mature as there may be more issues being produced but is undetectable by current test scripts. So i am not sure what stopping you from doing point 2
    – PDHide
    Commented Nov 5, 2021 at 10:10
  • Hm, 1/, 2/, and study the product more, and skill up, and start some conversations with other peopoe like dev. Also, what bug? Not every bug gets treated in the same way - e.g. a typo in a static text is simply fixed and no other action is likely needed. This is a kind of question that can mean almost anything and you need to read so much context in it to be able to answer it in some way. So it's more about guessing what the author of this exam question had in mind in the time of creating it.
    – pavelsaman
    Commented Mar 22, 2022 at 22:12

3 Answers 3


A bug was found in the product that the test cases did not highlight.

Of course it was. QA cannot guarantee that we can find all the bugs in a product. It simply can't be done. That means there is always a high chance that a bug escapes QA and makes it to production. These tend to be regression bugs. That's OK! What's important is how you deal with those bugs.

First, no one should blame QA for missing a bug. This is detrimental to a safe team environment. As humans, anything we create is flawed. Software is complicated and it's really difficult to test an unlimited set of pathways and integration points software creates.

So, how does QA handle a bug that escaped to production? Before you do anything else, you need to understand how it happened. Here you have some options:

  • Perform a root cause analysis. This needs to be done to fix the bug anyway, so QA needs to know how the bug was caused so they can update their test cases.
  • Use 5 Whys. This can be really effective in finding the cause in a short amount of time.

Questions to ask yourself in this situation:

  • Was the bug directly related to the feature/story being tested?
  • Did you only test the requirements/acceptance criteria directly, one-for-one? Did you go beyond what's listed as a requirement?
  • Did you test the integration points of that feature? What other features touch the feature you are testing?
  • Was the bug in the UI, API, backend?
  • Did you do any regression testing?
  • Do you have any test automation that covers this feature? If not, can you write an automated test to cover this bug?
  • Does your test cases cover the positive/happy path? Do they cover the negative paths? Do they cover edge cases and corner cases?
  • Are you performing only black-box testing? Or are you doing any gray-box and white-box testing?

So really, the answer to the OPs question is #1 and #2. You should never do nothing. And whether your test cases are written down in a test case management system or are automated test scripts, you should always update them if bugs are found. They are living documents and you want to assure quality for the long term.


I would write a test case for that bug or if it is a condition missing, will add it to the existing test case.


Point 1 and point 2.

Just update your test case suite right away with that specific bug and then give some more time to see if you need to update some more test cases.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.