Acceptance testing in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Acceptance Testing?

Acceptance Testing is the final level of software testing where the software is tested to ensure it meets the business requirements and is ready for delivery to the user.

beginner

Who usually performs Acceptance Testing?

Acceptance Testing is usually performed by the end users or clients to verify the software works as expected in real-world scenarios.

beginner

What is the main goal of Acceptance Testing?

The main goal is to confirm that the software meets all agreed requirements and is acceptable for release.

beginner

Give an example of Acceptance Testing in real life.

Imagine buying a new phone. Acceptance Testing is like checking if the phone turns on, makes calls, and uses apps as promised before you accept it.

intermediate

What is the difference between Acceptance Testing and System Testing?

System Testing checks if the whole system works technically, while Acceptance Testing checks if the system meets user needs and business goals.

Who typically performs Acceptance Testing?

A Test automation tools

B Developers

C System administrators

D End users or clients

Acceptance Testing is usually done by end users or clients to ensure the software meets their needs.

What is the main purpose of Acceptance Testing?

A To test individual functions

B To find bugs in the code

C To check if the software meets business requirements

D To test hardware compatibility

Acceptance Testing verifies that the software meets the agreed business requirements.

When is Acceptance Testing usually performed?

A Before unit testing

B After system testing and before release

C During coding

D After deployment to production

Acceptance Testing is done after system testing and before the software is released to users.

Which of these is NOT a focus of Acceptance Testing?

A Code style

B Business requirements

C Real-world usage

D User satisfaction

Code style is not checked in Acceptance Testing; it focuses on user needs and business goals.

Acceptance Testing can be best compared to:

A Trying a product before buying it

B Writing code

C Fixing bugs

D Designing software architecture

Acceptance Testing is like trying a product before buying to ensure it works as expected.

Explain what Acceptance Testing is and why it is important.

Think about the last check before software is given to users.

Describe the difference between Acceptance Testing and System Testing.

One focuses on technology, the other on user satisfaction.

Practice

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

easy

A. To test individual functions or methods in isolation

B. To check the internal code quality and structure

C. To verify the software meets user requirements and expectations

D. To find syntax errors in the source code

Solution

1. Step 1: Understand acceptance testing goal

   Acceptance testing focuses on confirming the software meets what users expect and need.

2. Step 2: Compare options to acceptance testing purpose

   Options B, C, and D relate to other testing types like unit or code testing, not acceptance testing.

3. Final Answer:

   To verify the software meets user requirements and expectations -> Option C

4. Quick Check:

   Acceptance testing = user requirements check [OK]

Hint: Acceptance testing checks if users get what they want [OK]

Common Mistakes:

• Confusing acceptance testing with unit testing
• Thinking acceptance testing checks code syntax
• Believing acceptance testing is done after release

2. Which of the following is the correct way to describe an acceptance test scenario?

easy

A. Check if the software's internal functions return correct values

B. Run automated scripts to find syntax errors

C. Write complex code to test each module separately

D. Describe user actions and expected results in simple language

Solution

1. Step 1: Identify acceptance test scenario style

   Acceptance tests use simple, clear descriptions of what users do and expect.

2. Step 2: Eliminate unrelated options

   Options A, C, and D focus on code-level or automated testing, not user-focused scenarios.

3. Final Answer:

   Describe user actions and expected results in simple language -> Option D

4. Quick Check:

   Acceptance test scenario = user steps + expected results [OK]

Hint: Acceptance tests use simple user stories, not code details [OK]

Common Mistakes:

• Writing technical code instead of user steps
• Confusing acceptance tests with unit tests
• Using jargon instead of simple language

3. Consider this acceptance test scenario for a login feature:

Given the user is on the login page
When the user enters valid credentials
Then the user should see the dashboard

What is the expected outcome when this test runs?

medium

A. The user is redirected to the dashboard page

B. The application crashes

C. The login page reloads without changes

D. The user sees an error message about invalid credentials

Solution

1. Step 1: Analyze the acceptance test steps

   The scenario says valid credentials are entered, so login should succeed.

2. Step 2: Determine expected result from scenario

   After successful login, the user should see the dashboard, meaning redirection to dashboard page.

3. Final Answer:

   The user is redirected to the dashboard page -> Option A

4. Quick Check:

   Valid login = dashboard shown [OK]

Hint: Valid login leads to dashboard, not error or crash [OK]

Common Mistakes:

• Choosing error message for valid credentials
• Confusing page reload with successful login
• Assuming crash on valid input

4. A tester wrote this acceptance test scenario:

Given the user is on the homepage
When the user clicks the 'Submit' button
Then the form should be submitted

But during testing, clicking 'Submit' does nothing. What is the most likely cause?

medium

A. The form submission is successful but not visible

B. The 'Submit' button locator is incorrect or missing

C. The user is not on the homepage

D. The acceptance test scenario is invalid syntax

Solution

1. Step 1: Understand the test failure symptom

   Clicking 'Submit' does nothing, so the button action is not triggered.

2. Step 2: Identify common causes for no action on click

   Incorrect or missing locator means the test cannot find the button to click, causing no action.

3. Final Answer:

   The 'Submit' button locator is incorrect or missing -> Option B

4. Quick Check:

   Button not found = no click action [OK]

Hint: No action on click? Check button locator first [OK]

Common Mistakes:

• Assuming form submitted but invisible
• Ignoring locator issues
• Blaming test syntax instead of element identification

5. You are designing acceptance tests for an online shopping cart. Which scenario best fits acceptance testing principles?

hard

A. Check that adding an item updates the cart total and displays the item

B. Test the database query that retrieves product prices

C. Verify the 'Add to Cart' button triggers the correct JavaScript function

D. Ensure the CSS styles for the cart page load correctly

Solution

1. Step 1: Identify acceptance test focus

   Acceptance tests check if the user sees expected results after actions, like cart updates.

2. Step 2: Evaluate each option against acceptance testing

   Check that adding an item updates the cart total and displays the item describes user-visible behavior after adding item, fitting acceptance testing. Options A, B, and D focus on internal code, database, or styling, not user outcomes.

3. Final Answer:

   Check that adding an item updates the cart total and displays the item -> Option A

4. Quick Check:

   User sees cart update = acceptance test [OK]

Hint: Acceptance tests focus on user-visible results, not code details [OK]

Common Mistakes:

• Choosing technical checks over user outcomes
• Confusing acceptance tests with unit or integration tests
• Ignoring visible feedback to users