Behavior-driven development (BDD) concept in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding BDD Scenario Structure

Which of the following best describes the correct structure of a Behavior-driven development (BDD) scenario?

A Given some initial context, Then an event occurs, When ensure some outcomes

B When some initial context, Given an event occurs, Then ensure some outcomes

C Then some initial context, Given an event occurs, When ensure some outcomes

D Given some initial context, When an event occurs, Then ensure some outcomes

💡 Hint

Think about the natural flow of setting up context, performing an action, and checking results.

BDD scenarios follow the pattern: Given (setup), When (action), Then (outcome). This helps describe behavior clearly.

❓ Predict Output

intermediate

Output of a Simple BDD Test Result

Given the following BDD test result summary, what is the overall test status?

Testing Fundamentals

Feature: Login functionality
  Scenario: Successful login
    Given user is on login page
    When user enters valid credentials
    Then user is redirected to dashboard

Test result: Given passed, When passed, Then failed

A Fail

B Pass

C Skipped

D Error

💡 Hint

All steps must pass for the scenario to pass.

If any step in a BDD scenario fails, the whole scenario is considered failed.

❓ assertion

advanced

Correct Assertion in BDD Step Definition

Which assertion correctly verifies that a user is redirected to the dashboard page in a BDD step definition?

Testing Fundamentals

def then_user_redirected_to_dashboard():
    current_url = get_current_url()

A assert current_url is None

B assert current_url == '/dashboard'

C assert '/dashboard' in current_url

D assert current_url != '/dashboard'

💡 Hint

The URL should exactly match the dashboard path.

The assertion must confirm the current URL equals the expected dashboard URL to pass.

🔧 Debug

advanced

Identify the Bug in BDD Step Implementation

What is the bug in this BDD step implementation?

Testing Fundamentals

from behave import given

@given('the user is logged in')
def step_impl(context):
    context.logged_in = True
    return True

A Returning True is unnecessary and may cause errors

B Missing context parameter in function

C Decorator @given is used incorrectly

D context.logged_in should be set to False

💡 Hint

Check what step functions should return in behave framework.

BDD step functions in behave should not return any value; returning True can cause unexpected behavior.

❓ framework

expert

Choosing the Best BDD Framework for Python

Which Python BDD framework supports natural language feature files, integrates with pytest, and uses the Given-When-Then syntax?

A Behave

B unittest

C pytest-bdd

D nose

💡 Hint

Look for a framework that combines pytest features with BDD style.

pytest-bdd supports natural language feature files, integrates with pytest, and uses Given-When-Then syntax, making it a modern choice.

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