Acceptance criteria verification in Testing Fundamentals - Full Explanation

Introduction

When building software, it is important to know when a feature is truly finished and works as expected. Acceptance criteria verification helps check if the software meets the agreed requirements before it is accepted.

Explanation

Purpose of Acceptance Criteria

Acceptance criteria define the specific conditions that a software feature must satisfy to be considered complete. They act as a checklist to ensure the feature behaves as intended and meets user needs.

Acceptance criteria set clear goals for what the software must do to be accepted.

Verification Process

Verification involves testing the software against each acceptance criterion. This can include manual testing, automated tests, or demonstrations to stakeholders to confirm the feature works correctly.

Verification confirms the software meets all acceptance criteria through testing or review.

Role in Development Cycle

Acceptance criteria verification usually happens near the end of a development cycle or sprint. It ensures that the feature is ready to be delivered and reduces the chance of defects or misunderstandings.

Verification ensures quality and readiness before software delivery.

Benefits of Verification

By verifying acceptance criteria, teams avoid releasing incomplete or faulty features. It improves communication between developers, testers, and stakeholders by providing a shared understanding of done.

Verification improves product quality and team alignment.

Real World Analogy

Imagine ordering a custom sandwich with specific ingredients. When the sandwich arrives, you check if it has all the ingredients you asked for before you start eating. This check is like acceptance criteria verification.

Purpose of Acceptance Criteria → The list of ingredients you want in your sandwich.

Verification Process → Checking the sandwich to see if it has all the requested ingredients.

Role in Development Cycle → Checking the sandwich right before you eat it to make sure it’s correct.

Benefits of Verification → Ensuring you get exactly what you ordered and enjoy your meal.

Diagram

Diagram

┌───────────────────────────────┐
│       Acceptance Criteria      │
│          Defined List          │
└──────────────┬────────────────┘
               │
               ▼
┌───────────────────────────────┐
│      Verification Process      │
│  Test each criterion carefully │
└──────────────┬────────────────┘
               │
               ▼
┌───────────────────────────────┐
│    Ready for Delivery Check    │
│   Confirm feature is complete  │
└──────────────┬────────────────┘
               │
               ▼
┌───────────────────────────────┐
│         Benefits Gained        │
│  Quality and team alignment    │
└───────────────────────────────┘

This diagram shows the flow from defining acceptance criteria to verifying them and gaining benefits before delivery.

Key Facts

Acceptance Criteria → Specific conditions a software feature must meet to be accepted.

Verification → The process of checking if the software meets the acceptance criteria.

Definition of Done → A shared understanding that a feature is complete and meets all criteria.

Stakeholders → People who have an interest in the software and its features.

Common Confusions

Acceptance criteria verification is the same as general testing.

Acceptance criteria verification is the same as general testing. Acceptance criteria verification specifically checks if agreed conditions are met, while general testing can include many other checks like performance or security.

Verification means the feature is perfect and bug-free.

Verification means the feature is perfect and bug-free. Verification confirms criteria are met but does not guarantee the absence of all bugs or issues.

Summary

Acceptance criteria verification checks if software features meet agreed conditions before acceptance.

It involves testing or reviewing each criterion to confirm completeness and correctness.

This process improves product quality and ensures everyone agrees on when work is done.

Practice

1. What is the main purpose of acceptance criteria in software testing?

easy

A. To write code for the feature

B. To define what 'done' means for a feature

C. To design the user interface

D. To create test automation scripts

Solution

1. Step 1: Understand acceptance criteria role

   Acceptance criteria specify the conditions that must be met for a feature to be considered complete.

2. Step 2: Differentiate from other tasks

   Writing code, designing UI, and creating automation are separate activities, not the main purpose of acceptance criteria.

3. Final Answer:

   To define what 'done' means for a feature -> Option B

4. Quick Check:

   Acceptance criteria = Definition of done [OK]

Hint: Acceptance criteria define 'done' clearly [OK]

Common Mistakes:

• Confusing acceptance criteria with coding tasks
• Thinking acceptance criteria are test scripts
• Mixing acceptance criteria with UI design

2. Which of the following is the correct way to write an acceptance criterion?

easy

A. Users might be able to reset passwords sometimes.

B. Reset password feature is cool and works well.

C. The system shall allow users to reset their password via email.

D. Password reset should be fast and secure.

Solution

1. Step 1: Identify clear, testable criteria

   The system shall allow users to reset their password via email. clearly states a specific, testable behavior: users can reset passwords via email.

2. Step 2: Evaluate other options for clarity and testability

   The other options are vague or subjective and cannot be directly tested.

3. Final Answer:

   The system shall allow users to reset their password via email. -> Option C

4. Quick Check:

   Clear and testable = The system shall allow users to reset their password via email. [OK]

Hint: Look for clear, testable statements [OK]

Common Mistakes:

• Choosing vague or subjective statements
• Ignoring testability of criteria
• Confusing feature description with acceptance criteria

3. Given the acceptance criterion: The login button must be disabled until both username and password fields are filled. Which test case will verify this criterion correctly?

medium

A. Check if login button is disabled when username is filled but password is empty.

B. Check if login button is enabled when both fields are empty.

C. Check if login button is disabled when both fields are filled.

D. Check if login button is enabled when username is filled but password is empty.

Solution

1. Step 1: Understand the criterion condition

   The login button should be disabled until both fields have values.

2. Step 2: Identify the correct test case

   Check if login button is disabled when username is filled but password is empty. tests that the button is disabled when only username is filled, which matches the criterion.

3. Final Answer:

   Check if login button is disabled when username is filled but password is empty. -> Option A

4. Quick Check:

   Button disabled until both fields filled = Check if login button is disabled when username is filled but password is empty. [OK]

Hint: Test partial inputs to check button state [OK]

Common Mistakes:

• Testing button enabled when fields are empty
• Expecting button disabled when both fields filled
• Ignoring partial input cases

4. You have this acceptance criterion: The search results must display within 2 seconds after submitting a query. Which of the following is the best way to debug a failing test that shows results after 5 seconds?

medium

A. Check network speed and server response times.

B. Ignore the delay since results eventually appear.

C. Change the acceptance criterion to 5 seconds.

D. Remove the timer from the test case.

Solution

1. Step 1: Analyze the cause of delay

   Since results take 5 seconds, check network and server performance to find bottlenecks.

2. Step 2: Avoid ignoring or changing criteria improperly

   Ignoring delay or changing criteria without cause is incorrect; removing timer hides the problem.

3. Final Answer:

   Check network speed and server response times. -> Option A

4. Quick Check:

   Debug performance issues first = Check network speed and server response times. [OK]

Hint: Investigate environment before changing criteria [OK]

Common Mistakes:

• Ignoring the delay problem
• Changing acceptance criteria without reason
• Removing test validations

5. A feature has these acceptance criteria:
1. Users can add items to the cart.
2. Cart updates total price correctly.
3. Cart shows an error if quantity exceeds stock.
During testing, you find the cart updates price but does not show an error when quantity is too high. What should you do next?

hard

A. Change acceptance criteria to remove error message requirement.

B. Mark the feature as complete since price updates correctly.

C. Ignore the error message since it is not critical.

D. Report a bug for missing error message and retest after fix.

Solution

1. Step 1: Verify all acceptance criteria

   The feature meets price update but fails to show error for quantity exceeding stock.

2. Step 2: Take appropriate action

   Since one criterion fails, report a bug and plan to retest after the fix.

3. Final Answer:

   Report a bug for missing error message and retest after fix. -> Option D

4. Quick Check:

   Failing criteria means report bug = Report a bug for missing error message and retest after fix. [OK]

Hint: Failing any criterion means report bug [OK]

Common Mistakes:

• Ignoring failed criteria
• Marking incomplete features as done
• Changing acceptance criteria to hide bugs