Acceptance testing in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Acceptance Testing

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

A To check the internal code quality and adherence to coding standards

B To verify the software meets the business requirements and is ready for delivery to the user

C To test the software's performance under heavy load conditions

D To find and fix syntax errors in the source code

💡 Hint

Think about who acceptance testing is done for and what it confirms.

Acceptance testing ensures the software meets the agreed business needs and is acceptable to the user before release.

❓ Predict Output

intermediate

Acceptance Test Result Interpretation

Given this acceptance test result summary, what is the overall test outcome?

Test Case 1: Passed
Test Case 2: Passed
Test Case 3: Failed
Test Case 4: Passed

A The test results are inconclusive without performance test results

B The software is accepted because most tests passed

C The software is accepted because failed tests are ignored in acceptance testing

D The software is rejected because at least one acceptance test failed

💡 Hint

Acceptance testing requires all critical tests to pass for acceptance.

If any acceptance test fails, the software does not meet the acceptance criteria and is rejected.

❓ assertion

advanced

Correct Assertion for Acceptance Criteria

Which assertion best verifies that a user login feature meets acceptance criteria?

Testing Fundamentals

def test_user_login():
    result = login('user1', 'password123')
    # Which assertion below is correct?

A assert result == True # Checks boolean success

B assert result is not None # Checks only that something is returned

C assert result == 'Login successful' # Checks exact success message

D assert 'error' not in result.lower() # Checks no error word in message

💡 Hint

Acceptance criteria usually specify exact expected outcomes.

Checking the exact success message ensures the feature behaves as the user expects.

🔧 Debug

advanced

Identify the Acceptance Test Bug

Find the bug in this acceptance test code for a shopping cart feature:

def test_add_item():
    cart = ShoppingCart()
    cart.add_item('apple')
    assert 'apple' in cart.items  # Check item added
    assert len(cart.items) == 0  # Check cart size

A The second assertion is wrong; it should check for length 1, not 0

B The first assertion is wrong; 'apple' should not be in cart.items

C The cart object is not initialized correctly

D The add_item method is missing parentheses

💡 Hint

Think about what happens after adding one item to the cart.

After adding 'apple', the cart should have one item, so length should be 1, not 0.

❓ framework

expert

Best Practice for Automating Acceptance Tests

Which approach is best for automating acceptance tests to ensure maintainability and clarity?

A Use a behavior-driven development (BDD) framework with clear feature files and step definitions

B Write acceptance tests as long, complex scripts mixing UI and API calls without separation

C Automate acceptance tests only after the software is released to production

D Use random test data without documenting expected outcomes

💡 Hint

Think about readability and collaboration between testers and business stakeholders.

BDD frameworks use plain language to describe acceptance criteria, making tests clear and maintainable.

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