Acceptance testing in Testing Fundamentals - Test Execution Trace

Test Overview

This acceptance test checks if the login feature works as expected for a user. It verifies that a user can successfully log in with valid credentials and reach the dashboard page.

Test Code - Selenium with Python unittest

Testing Fundamentals

from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC
import unittest

class TestLoginAcceptance(unittest.TestCase):
    def setUp(self):
        self.driver = webdriver.Chrome()
        self.driver.get('https://example.com/login')

    def test_valid_login(self):
        driver = self.driver
        # Find username field and enter username
        username_field = WebDriverWait(driver, 10).until(
            EC.presence_of_element_located((By.ID, 'username'))
        )
        username_field.send_keys('validUser')

        # Find password field and enter password
        password_field = driver.find_element(By.ID, 'password')
        password_field.send_keys('validPass123')

        # Find and click login button
        login_button = driver.find_element(By.ID, 'login-btn')
        login_button.click()

        # Wait for dashboard page to load by checking dashboard header
        dashboard_header = WebDriverWait(driver, 10).until(
            EC.presence_of_element_located((By.ID, 'dashboard-header'))
        )

        # Assert dashboard header text is correct
        self.assertEqual(dashboard_header.text, 'Welcome to Your Dashboard')

    def tearDown(self):
        self.driver.quit()

if __name__ == '__main__':
    unittest.main()

Execution Trace - 6 Steps

Step	Action	System State	Assertion	Result
1	Test starts and opens Chrome browser	Browser window opens at 'https://example.com/login' page	—	PASS
2	Waits for username field to be present and enters 'validUser'	Login page shows username and password fields and login button	Username field is present and enabled	PASS
3	Finds password field and enters 'validPass123'	Password field is visible and ready for input	Password field is present and enabled	PASS
4	Finds and clicks the login button	Login button is clickable	Login button is present and clickable	PASS
5	Waits for dashboard header to appear after login	Dashboard page loads with header element	Dashboard header text equals 'Welcome to Your Dashboard'	PASS
6	Test ends and browser closes	Browser window closes	—	PASS

Failure Scenario

Failing Condition: Dashboard header does not appear or text is incorrect after login

Execution Trace Quiz - 3 Questions

What does the test verify after clicking the login button?

A That the login button changes color

B That the username field is cleared

C That the dashboard header with text 'Welcome to Your Dashboard' appears

D That the password field becomes hidden

Key Result

Acceptance tests should simulate real user actions and verify key outcomes to confirm the software meets user needs.

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