Behavior-driven development (BDD) concept in Testing Fundamentals - Test Execution Trace

Test Overview

This test checks a simple login feature using Behavior-driven development (BDD). It verifies that when a user enters correct credentials, they successfully log in and see a welcome message.

Test Code - Behave with Selenium

Testing Fundamentals

from behave import given, when, then
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

@given('the user is on the login page')
def step_impl(context):
    context.driver = webdriver.Chrome()
    context.driver.get('https://example.com/login')

@when('the user enters valid username and password')
def step_impl(context):
    username_input = context.driver.find_element(By.ID, 'username')
    password_input = context.driver.find_element(By.ID, 'password')
    username_input.send_keys('validUser')
    password_input.send_keys('validPass123')
    login_button = context.driver.find_element(By.ID, 'login-btn')
    login_button.click()

@then('the user should see the welcome message')
def step_impl(context):
    WebDriverWait(context.driver, 10).until(
        EC.presence_of_element_located((By.ID, 'welcome-msg'))
    )
    welcome_text = context.driver.find_element(By.ID, 'welcome-msg').text
    assert welcome_text == 'Welcome, validUser!'
    context.driver.quit()

Execution Trace - 5 Steps

Step	Action	System State	Assertion	Result
1	Test starts and opens Chrome browser	Browser window opens at 'https://example.com/login' showing login form with username and password fields	—	PASS
2	Find username and password input fields and enter valid credentials	Username field filled with 'validUser', password field filled with 'validPass123'	—	PASS
3	Find and click the login button	Login button clicked, page starts loading the user dashboard	—	PASS
4	Wait for welcome message element to appear	Welcome message element with id 'welcome-msg' appears on the page	Check that welcome message text equals 'Welcome, validUser!'	PASS
5	Close the browser and end test	Browser window closes	—	PASS

Failure Scenario

Failing Condition: Welcome message element 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 is disabled

B That the welcome message with correct text appears

C That the username field is cleared

D That the password is visible

Key Result

BDD tests use simple language to describe user behavior, making tests easy to read and understand by both technical and non-technical team members.

Practice

1. What is the main purpose of Behavior-driven development (BDD)?

easy

A. To write code faster without testing

B. To improve communication by using plain language to describe software behavior

C. To replace all manual testing with automated scripts

D. To focus only on the user interface design

Solution

1. Step 1: Understand BDD's communication goal

   BDD uses simple language to describe how software should behave, making it easier for everyone to understand.

2. Step 2: Compare options with BDD purpose

   Only To improve communication by using plain language to describe software behavior matches this goal; others focus on unrelated aspects like speed or UI only.

3. Final Answer:

   To improve communication by using plain language to describe software behavior -> Option B

4. Quick Check:

   BDD = plain language communication [OK]

Hint: BDD means plain language for behavior, not just coding [OK]

Common Mistakes:

• Thinking BDD is only about automation
• Confusing BDD with UI design
• Believing BDD skips manual testing

2. Which of the following is the correct syntax style used in BDD scenarios?

easy

A. Try-Catch-Finally

B. If-Else-End

C. Start-Process-End

D. Given-When-Then

Solution

1. Step 1: Recall BDD scenario structure

   BDD scenarios use the "Given-When-Then" format to describe context, action, and outcome.

2. Step 2: Match options with BDD syntax

   Only Given-When-Then matches this format; others are programming constructs or unrelated terms.

3. Final Answer:

   Given-When-Then -> Option D

4. Quick Check:

   BDD syntax = Given-When-Then [OK]

Hint: BDD always uses Given-When-Then steps [OK]

Common Mistakes:

• Confusing BDD syntax with programming keywords
• Using If-Else as BDD steps
• Mixing error handling terms with BDD

3. Consider this BDD scenario snippet:

Given the user is logged in
When the user clicks the logout button
Then the user should be logged out

What is the expected outcome of this scenario?

medium

A. The user is logged out after clicking logout

B. The user remains logged in

C. The logout button is disabled

D. An error message is shown

Solution

1. Step 1: Analyze the 'When' action

   The user clicks the logout button, which triggers logout behavior.

2. Step 2: Check the 'Then' expected result

   The user should be logged out, meaning the session ends successfully.

3. Final Answer:

   The user is logged out after clicking logout -> Option A

4. Quick Check:

   When logout clicked, Then user logged out [OK]

Hint: Match 'Then' outcome with expected behavior [OK]

Common Mistakes:

• Ignoring the 'Then' step result
• Assuming logout button disables instead
• Confusing error messages with normal flow

4. Identify the error in this BDD scenario:

Given the user is on the homepage
When the user clicks the login button
And the user enters valid credentials
Then the user should see the dashboard
But the user sees an error message instead

medium

A. The scenario mixes expected and unexpected outcomes in 'Then' and 'But'

B. The 'Given' step is missing a URL

C. The 'When' step should not have multiple actions

D. The scenario lacks a 'Background' section

Solution

1. Step 1: Review 'Then' and 'But' steps

   'Then' states the user should see the dashboard (expected), but 'But' says the user sees an error (unexpected).

2. Step 2: Understand BDD scenario clarity

   BDD scenarios should describe one clear expected outcome; mixing expected and unexpected causes confusion.

3. Final Answer:

   The scenario mixes expected and unexpected outcomes in 'Then' and 'But' -> Option A

4. Quick Check:

   BDD expects clear outcomes, not conflicting ones [OK]

Hint: Avoid conflicting expected results in BDD steps [OK]

Common Mistakes:

• Thinking multiple actions in 'When' are invalid
• Believing 'Background' is mandatory
• Assuming 'Given' must include URLs

5. You want to write a BDD scenario for a shopping cart feature that applies a discount only if the total price is above $100. Which scenario correctly uses BDD style to describe this behavior?

hard

A. Start cart
Check total
Apply discount if total > 100
End cart

B. If cart total > 100 then apply discount else no discount

C. Given the cart total is $120
When the user applies a discount code
Then the discount should be applied

D. User adds items
Discount applied automatically

Solution

1. Step 1: Identify proper BDD format

   Given the cart total is $120 When the user applies a discount code Then the discount should be applied uses Given-When-Then steps clearly describing context, action, and expected result.

2. Step 2: Evaluate other options for BDD style

   Options B, C, and D use programming logic or vague steps, not BDD's plain language format.

3. Final Answer:

   Given the cart total is $120 When the user applies a discount code Then the discount should be applied -> Option C

4. Quick Check:

   BDD scenario = Given-When-Then clear steps [OK]

Hint: Use Given-When-Then to describe behavior clearly [OK]

Common Mistakes:

• Writing code logic instead of plain language
• Skipping the 'Then' expected outcome
• Using vague or incomplete steps