Skip to main content
Strategy & Process

What Is Acceptance Criteria?

Acceptance criteria are specific, testable conditions that a user story or feature must satisfy to be considered complete and accepted by the product owner.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

In Depth

Acceptance criteria define the boundaries of a user story. They answer "How will we know this is done?" with concrete, verifiable conditions. Good acceptance criteria are specific (not vague), measurable (pass/fail), achievable (within scope), relevant (tied to user value), and independent (testable in isolation).

The most popular format is Given-When-Then (from BDD): "Given a logged-in user with items in cart, When they click checkout with a valid credit card, Then the order is created and a confirmation email is sent within 5 minutes." This format makes criteria directly translatable into automated test scenarios.

QA engineers play a critical role in acceptance criteria by joining backlog refinement sessions to ask clarifying questions, identifying missing criteria (error states, edge cases, performance expectations), and ensuring criteria are testable. Vague criteria like "the page should load fast" become "the page should load within 2 seconds on a 3G connection." Well-written acceptance criteria reduce ambiguity, prevent scope creep, and give testers clear targets.

Why Interviewers Ask About This

Interviewers ask about acceptance criteria to see whether you collaborate effectively with product and development. Writing good criteria is a skill that prevents bugs before code is written.

Example Scenario

A story reads: "As a user, I want to reset my password." The QA engineer adds acceptance criteria: the reset email must arrive within 60 seconds, the reset link must expire after 24 hours, using an expired link must show a clear error message, and the user must be logged out of all sessions after a password change.

Interview Tip

Show that you actively contribute to acceptance criteria during refinement, not just consume them during testing. Give an example of criteria you improved or added.

Related Terms

Explore related glossary terms to deepen your understanding.

Definition of DoneThe Definition of Done (DoD) is a shared checklist of quality conditions that every user story, feature, or increment must meet before it can be considered complete, covering aspects like testing, documentation, code review, and deployment readiness.
Test CaseA test case is a documented set of preconditions, inputs, execution steps, and expected results designed to verify that a specific feature or behavior of the application works correctly.
Exploratory TestingExploratory testing is a testing approach where the tester simultaneously learns about the system, designs tests, and executes them in real time without predefined scripts.
Test PlanA test plan is a detailed document that describes the scope, approach, resources, schedule, and deliverables for testing a specific feature, release, or project.
Quality GatesQuality gates are checkpoints in the software delivery process where predefined quality criteria must be met before work can proceed to the next stage, enforcing minimum standards at each phase.

Related Resources

Dive deeper with these related interview prep pages.

Manual Testing QuestionsQA Mock Interview PracticeSoftware Testing InterviewQA Methodology Questions

Ready to Ace Your QA Interview?

Practice explaining acceptance criteria and other key concepts with our AI interviewer.

Join 1,200+ QA engineers already practicing with AssertHired.

Start Your Free QA Interview

Free to start · 7-day trial on paid plans

Written by Aston Cook, Senior QA EngineerLast updated: March 2026