Why “In QA” Isn’t Always the Right Status

One of the most common misunderstandings in software development is the meaning of the status “In QA.” It may seem like a small detail, but using the wrong status can create confusion for project managers, sales teams, solution consultants, and even customers.

What Does “In QA” Mean?

A feature is considered In QA when the Quality Assurance team is actively testing it to verify that it meets the requirements and is ready for release.

During this stage, QA may:

• Execute test cases
• Verify acceptance criteria
• Perform regression testing
• Report any defects found

What Happens When QA Finds Defects?

Finding defects doesn’t automatically mean the feature is complete. If QA discovers issues that prevent the feature from meeting the expected quality, the feature should be returned to the development team for fixes.

At this point, the feature is no longer actively in QA.

Instead, it is waiting for developers to resolve the reported issues before it can be tested again.

Why Saying “It’s in QA” Can Be Misleading

Imagine a customer asks whether their requested feature is progressing.

If the feature has already failed QA but someone replies:

“It’s in QA.”

The customer or stakeholder may assume:

• Testing is still ongoing.
• The feature is close to completion.
• No major issues have been found.

In reality, development work is still required.

This creates incorrect expectations and may lead to disappointment if the release is delayed.

Better Ways to Communicate the Status

Instead of saying:

“It’s in QA.”

Use more accurate updates such as:

“QA testing identified defects, and the feature has been sent back to Development.”

“The feature completed an initial QA cycle but did not pass.”

“Development is currently fixing issues reported by QA.”

“The feature will return to QA after the fixes are completed.”

These updates clearly explain where the feature stands without creating confusion.

A Simple Feature Lifecycle

A typical development workflow looks like this:

Development → QA Testing → QA Failed → Development Fixes → QA Retest → QA Passed → Release

Only the periods when QA is actively validating the feature should be considered in QA.

Why Accurate Statuses Matter

Using accurate status labels helps everyone involved.

• Customers receive realistic expectations.
• Sales and Solution teams can communicate confidently.
• Project Managers have a clear view of project progress.
• Developers and QA avoid misunderstandings about ownership.

Clear communication builds trust just as much as delivering high-quality software.

Final Thoughts

A feature that has failed QA has certainly been through QA, but it is not currently in QA. Once defects are identified and the work is handed back to developers, the status should reflect that reality.

Using precise status updates may seem like a small improvement, but it helps teams collaborate better, reduces confusion, and keeps everyone aligned throughout the software delivery process.