Acceptance testing in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the main goal of acceptance testing.

Testing Fundamentals

def acceptance_testing_goal():
    return "To verify the system meets the [1] requirements."

Drag options to blanks, or click blank then click option'

Abusiness

Btechnical

Cperformance

Dsecurity

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing acceptance testing with performance or security testing.

Acceptance testing checks if the system meets business requirements, ensuring it works for the user.

2fill in blank

medium

Complete the code to show who usually performs acceptance testing.

Testing Fundamentals

def acceptance_testers():
    return ['[1]', 'end users', 'stakeholders']

Drag options to blanks, or click blank then click option'

Atest managers

Bcustomers

Cdevelopers

Dsystem admins

Attempts:

3 left

💡 Hint

Common Mistakes

Thinking developers or admins perform acceptance testing.

Acceptance testing is often done by customers or end users to confirm the system meets their needs.

3fill in blank

hard

Fix the error in the acceptance test case description.

Testing Fundamentals

test_case = {
    'id': 101,
    'description': 'Check if login works for valid users',
    'expected_result': 'User logs in [1]'
}

Drag options to blanks, or click blank then click option'

Afails

Bcannot

Csometimes

Dsuccessfully

Attempts:

3 left

💡 Hint

Common Mistakes

Writing negative or unclear expected results.

The expected result should say the user successfully logs in, not fails or cannot.

4fill in blank

hard

Fill both blanks to complete the acceptance test function.

Testing Fundamentals

def run_acceptance_test(test_case):
    if test_case['actual_result'] == test_case['[1]']:
        return '[2]'
    else:
        return 'fail'

Drag options to blanks, or click blank then click option'

Aexpected_result

Bpass

Cerror

Dactual_result

Attempts:

3 left

💡 Hint

Common Mistakes

Comparing wrong keys or returning incorrect status.

The function compares actual result to expected_result. If they match, it returns pass.

5fill in blank

hard

Fill all three blanks to create a dictionary of acceptance test results filtering passed tests.

Testing Fundamentals

passed_tests = {test['[1]']: test['[2]'] for test in tests if test['[3]'] == 'pass'}

Drag options to blanks, or click blank then click option'

Aid

Bactual_result

Cstatus

Ddescription

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong keys or filtering incorrectly.

This dictionary comprehension collects test id and actual_result for tests whose status is 'pass'.

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