Skip to content
  • Services
  • About
  • Partners
  • Work
  • Insights
  • Careers
  • Contact
  • Services
  • About
  • Partners
  • Work
  • Insights
  • Careers
  • Contact
June 16, 2017

Why Didn’t QA Catch This?

Agile Software Development, Quality Assurance
A Look at Broken Processes

Quality Assurance (QA) can get a lot of flack throughout a release cycle, naturally. Isn’t QA the gatekeeper for an application? If a bug is found after a release by a customer then many look to that team first. If bugs continue to pop up then tests – from manual test cases to automation – can be placed under scrutiny and questions arise about the level of experience with the team.

How often these types of situations pop up and how they are handled can reveal a lot about a team’s processes. If bugs are consistently making their way past testing then it could be time to take a step back and dig into potential root causes.

So why isn’t QA catching all the bugs? Here are a few things that could be happening:

Missing Phases or Environments in Testing Workflows

One of the first things to look at is the testing process itself. Maybe there is a critical step in the workflow that is missing and needs to be incorporated. For example, is QA only testing individual feature branches? A crucial aspect of testing involves seeing how well these individual features will interact with one another once released. This is also where QA can flush out regressions in the system before customers get access to it.

So is an integration environment or testing phase missing in the workflow? If so, then it may be time to talk about spinning up a new environment to deploy the set of features that will become candidates for a release.

Incomplete Acceptance Criteria for New Features

Stories help define development and what should be tested. If the set of acceptance criteria for a feature is incomplete then things will be missed in testing. Anything from permissions levels to expected notification messages can be overlooked if they are not defined or if the team isn’t well acquainted with the application.

Work with the whole team to determine what makes a complete story and include QA in that discussion. Having well-defined acceptance criteria will help them create the best plan of action for thorough testing before a release.

Lack of Business Knowledge

Sometimes, a bug makes it past testing simply because the team isn’t as well-versed in the application they are working in. That knowledge grows with time and experience, but there are ways that can help support everyone, not just QA, in the meantime.

For new features, demos or training can be incredibly helpful for the whole team. This gives everyone from Project Managers to Customer Support the opportunity to learn about what is planned for a release. Knowledge sharing keeps the lines of communication open across each team and helps ensure that silos are not being created.

When a bug is found post-release due to that lack of knowledge, document it in a place that is easily accessible and share that with the team. Turn it into a learning opportunity.

Too Many Shifts in Priorities

It’s to be expected that priorities shift, especially in an Agile environment. Shifts in priorities are not necessarily an indicator of an unhealthy process. If they happen too often then they really are more of a distraction and can throw the entire rhythm of a team off, including testing.

What do these unhealthy shifts in priorities look like? Last minute changes to a feature, new features that need to be incorporated in the next release (that happens to be a day away), and scope creep are a few common ones. QA can’t thoroughly test if priorities are constantly shifting without adequate communication or if they are not given enough time before a release.

It’s important to protect everyone involved with the development of new features and candidates for an upcoming release from these distractions and changes as much as possible.
There is a reason why something was missed in testing. The health and stability of an application doesn’t fall on any one team, so if there are a lot of bugs popping up post-release then look at current processes and work towards finding and fixing any gaps found.

What are some gaps you’ve found that contributed to missing bugs and how did you fix it? Let us know in the comments!

Posted in Agile Software Development, Quality Assurance
Share this

Mallory Mooney

Mallory Mooney was a QA Engineer at Modus Create until 2018. She has experience in developing test automation for a broad range of technologies as well as establishing QA processes for projects. She’s an advocate for open source automation tools and believes in building the “right” tests for the job - not just an arbitrary number of them. Aside from her work, Mallory enjoys photography, Texas BBQ, and a good hard cider.
Follow

Related Posts

  • QA Resolutions for 2018
    QA Resolutions for 2018

    The start of a new year gives us the opportunity to look at what we…

  • QA Resolutions for 2018
    QA Resolutions for 2018

    The start of a new year gives us the opportunity to look at what we…

Subscribe to the Modus Newsletter

Receive the latest blog articles and insights every month from the Modus team.

Let's Chat

If forms aren’t your thing, you can always call us (+1-855-721-7223).

Modus-Logo-Primary-White.svg
  • Services
  • About
    • Newsroom
  • Partners
  • Work
  • Insights
    • Blog
    • Modus Labs
  • Careers
Virginia (US)

12100 Sunset Hills Road
Suite 150
Reston, Virginia, 20190
Tel: +1-855-721-7223

California (US)
12130 Millennium Dr

Los Angeles, CA 90094

Missouri (US)
609 E High St

Jefferson City, MO 65101

Romania

Str. Mihai Veliciu, no. 17
Cluj-Napoca, Romania
Tel: +40-0786-887-444

Costa Rica

2nd Floor, Plaza Koros, Av 3
San José, Santa Ana, Costa Rica

© 2021 Modus. All Rights Reserved.

Privacy Policy | Accessibility Statement | Sitemap

This website uses cookies.
These cookies are used to collect information about how you interact with our website and allow us to remember you. We use this information in order to improve and customize your browsing experience, and for analytics and metrics about our visitors both on this website and other media. To find out more about the cookies we use, see our Privacy Policy.

Accept
Privacy & Cookies Policy

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary
Always Enabled

Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.

Non-necessary

Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.

Scroll To Top