Latest post from this blog

Test Scenarios vs. Test Cases: Understanding the Basics

By
What Are Test Scenarios Test scenarios represent high-level ideas or conditions that need to be validated to ensure the application works as expected. They provide a broader perspective and are typically used during the test planning phase. Purpose: To capture the "what to test" without going into granular details. Example of a Test Scenario: Verify that a user can successfully log in to the application using valid credentials. Verify the behavior of the login page when invalid credentials are entered. Verify the application behavior when the login button is clicked without entering any credentials. What Are Test Cases Test cases are detailed documents that define the specific steps to execute a test. They cover inputs, execution steps, expected results, and actual outcomes. Purpose: To guide the tester step-by-step on "how to test." Example of a Test Case (for the first scenario): Test Case ID TC_01_Login_Valid_Credentials Test Scenario Verify user login with val...
Post a Comment

What is Background in BDD Cucumber

By
Introduction
The Background keyword in Cucumber allows you to define a set of steps that are executed before every scenario in a feature file. These steps are shared across all scenarios in that file, making it easier to maintain and reducing redundancy.

Why Use Background
In many test cases, there are setup steps that are repeated across multiple scenarios. For example, logging into an application or setting up a test environment might be required for every scenario in a feature file. Instead of repeating these steps for each scenario, you can define them once under a Background section.

Syntax and Example
Here’s the structure of a feature file using the Background keyword:

Feature: User Account Management

  Background:
    Given a user is logged in
    And navigates to the dashboard

  Scenario: View user profile
    When the user clicks on the profile button
    Then the profile page is displayed

  Scenario: Update user settings
    When the user updates their preferences
    Then the changes are saved successfully

How Background Works
  1. Position: The Background section comes after the Feature declaration and before any Scenario or Scenario Outline.
  2. Execution: The steps in the Background section are executed before each scenario or example in the feature file.
  3. Reusability: Steps written in the Background are shared across all scenarios, making the test cases more concise and readable.
Benefits of Using Background
  • Avoids Redundancy: Common steps are written once, avoiding repetition.
  • Improves Readability: Keeps scenarios focused on their specific actions and outcomes.
  • Simplifies Maintenance: Updates to shared steps need to be made in only one place.
Example: Before and After Using Background

Without Background:

Feature: User Account Management

  Scenario: View profile
    Given a user is logged in
    And navigates to the dashboard
    When the user clicks on the profile button
    Then the profile page is displayed

  Scenario: Update settings
    Given a user is logged in
    And navigates to the dashboard
    When the user updates their preferences
    Then the changes are saved successfully

With Background:

Feature: User Account Management

  Background:
    Given a user is logged in
    And navigates to the dashboard

  Scenario: View profile
    When the user clicks on the profile button
    Then the profile page is displayed

  Scenario: Update settings
    When the user updates their preferences
    Then the changes are saved successfully

Key Points to Remember
  • The Background applies only to scenarios in the same feature file.
  • It should only include steps that are common to all scenarios.
  • Avoid using a Background for steps that are specific to only a few scenarios.
By using the Background feature in Cucumber, you can write cleaner, more maintainable test scripts, ensuring your BDD framework remains efficient and readable.

Comments

Post a Comment

Popular posts from this blog

Common Exception in Selenium

By
Introduction Selenium automation testing can throw several types of exceptions due to various issues during the execution of test scripts.  Here are some of the  most common exceptions  encountered in Selenium. 1. WebDriverException  is a base class for all exceptions thrown by the WebDriver API.  2. StaleElementReferenceException  is thrown when trying to interact with an element no longer attached to the DOM (Document Object Model).  This can happen if the element has been deleted or the page has been refreshed since the element was located. "stale" is often used to refer to something that is no longer fresh or current. 3. TimeoutException  is thrown when a command times out. This can occur if the page takes too long to load or if an element is not found within the specified time period. 4. UnreachableBrowserException  is thrown when a connection to a web browser cannot be established. 5. NoSuchElementException  is thrown when it canno...
Read more»

Test Scenarios vs. Test Cases: Understanding the Basics

By
What Are Test Scenarios Test scenarios represent high-level ideas or conditions that need to be validated to ensure the application works as expected. They provide a broader perspective and are typically used during the test planning phase. Purpose: To capture the "what to test" without going into granular details. Example of a Test Scenario: Verify that a user can successfully log in to the application using valid credentials. Verify the behavior of the login page when invalid credentials are entered. Verify the application behavior when the login button is clicked without entering any credentials. What Are Test Cases Test cases are detailed documents that define the specific steps to execute a test. They cover inputs, execution steps, expected results, and actual outcomes. Purpose: To guide the tester step-by-step on "how to test." Example of a Test Case (for the first scenario): Test Case ID TC_01_Login_Valid_Credentials Test Scenario Verify user login with val...
Read more»

Handling Shadow DOM in Selenium WebDriver

By
Image
Introduction Modern web applications often use Shadow DOM to keep parts of the webpage separate from the rest of the document. This helps in creating reusable components, but it also makes it difficult for Selenium WebDriver to access elements inside the Shadow DOM. In this blog, we'll explore what Shadow DOM is, why it's used, and how to handle it in Selenium WebDriver. What is Shadow DOM The Shadow DOM is a way to create a separate, hidden section of the DOM inside a web page. It's like a mini DOM tree attached to an element, which keeps its structure and styles isolated from the rest of the page. This helps developers build reusable web components without worrying about outside styles or scripts affecting them. Challenges in Handling Shadow DOM with Selenium WebDriver Selenium WebDriver typically interacts with the visible DOM. However, elements inside a Shadow DOM are not directly accessible through standard methods like driver.findElement() . This leads to exceptions ...
Read more»

Handling HTTPS Websites and SSL Certificate Errors in Selenium

By
Why SSL Certificate Errors Occur   SSL certificates ensure secure communication between the server and browser. If there's an issue, like an untrusted or expired certificate, the browser shows a warning. In automation, these warnings can interrupt tests, causing them to fail unless managed properly.In this post, we'll explain how to handle SSL certificate errors in Selenium for Chrome, Firefox, and Edge to ensure your tests run smoothly. setAcceptInsecureCerts(true) option allows the browser to ignore SSL certificate errors, enabling Selenium tests to run smoothly on sites with untrusted or invalid certificates. Handling SSL Certificate Errors in Chrome You can configure Chrome to accept insecure certificates by passing the option in ChromeOptions. ChromeOptions.setAcceptInsecureCerts(true)  allows Chrome to skip SSL warnings and continue testing on sites with untrusted certificates.its similar to the Firefox and Edge Browser also. import org.openqa.selenium.WebDriver; import...
Read more»

Normalize-space Function In Xpath

By
Introduction   When working with XPath, handling whitespace in text nodes can sometimes be a challenge. The normalize-space() function is a powerful tool to simplify text processing by removing unnecessary spaces and ensuring consistent string formatting. In this blog, we’ll explore what normalize-space() does, its syntax, and practical use cases in automation. What is the normalize-space() Function: The normalize-space() function in XPath trims leading and trailing whitespaces and reduces multiple spaces between words to a single space. It is useful for matching text nodes with inconsistent whitespace formatting. Syntax: normalize-space(string) string: The input text to be normalized. If omitted, it defaults to the current node’s text. Key Features: Removes leading and trailing spaces. Converts multiple spaces between words into a single space. Works seamlessly with text nodes and string attributes. Example :  <div id="example">   Hello World. </d...
Read more»