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

Overview of BDD and Gherkin Syntax

By
Behavior Driven Development (BDD): aims to create a shared understanding between developers, testers, and business stakeholders by describing how the application should behave from the user’s perspective.

Gherkin Syntax: is a simple, structured language used by Cucumber to describe behaviors in a human-readable format. It uses keywords like Feature, Scenario, Given, When, Then, And, and But to write test cases.

Writing Feature Files with Gherkin:
A Feature File contains multiple test scenarios in Gherkin syntax. Each scenario explains one use case of the application.

✓Feature: Defines the functionality under test.

✓Scenario: Represents individual test cases.

✓Given: Sets up the preconditions or initial context for the test.

✓When: Describes the action or event that triggers the behavior.

✓Then: Specifies the expected result or outcome of the action.

✓And/But: Extend steps for clarity

Example:

Feature: User Authentication
  Scenario: Login with valid credentials
    Given The user navigates to the login page
    When The user submits correct login                details
    Then The user should see the dashboard

Framework Structure for BDD
BDD Framework Structure is designed to separate test definitions, implementation, and configurations, ensuring clarity and maintainability.

Folder Structure 
Project/
│
├─── src/
│ ├─── test/
│ │ ├─── java/
│ │ │ ├─── StepDefinitions/
│ │ │ │ ├─── StepDefinitions.java
│ │ │ │ └─── ...
│ │ │ │
│ │ │ └─── runners/
│ │ │ ├─── TestRunner.java
│ │ │ └─── ...
│ │ │
│ │ └─── resources/
│ │ ├─── features/
│ │ │ ├─── Feature1.feature
│ │ │ ├─── Feature2.feature
│ │ │ └─── ...
│ │ │
│ │ └─── config/
│ │ └─── configuration.properties
│ │
│ └─── ...
│
└─── target/
└─── ...

Folder and File Descriptions

1.src: Main source directory containing all code and resources.

2.test: Contains test-related code and resources.

3.java: Directory for Java code.
  • StepDefinitions: Houses Java methods mapped to Gherkin steps.

  • runners: Includes test runner classes for executing tests.
4.resources: Non-code resources.
  • features: Stores feature files written in Gherkin syntax.
  • config: Contains configuration files like configuration.properties.
5.target: Holds compiled code, test results, and generated files during build or test execution.

Key Components of a BDD Framework

1.Feature Files:
  • Written in Gherkin syntax to define test scenarios.
  • Located in the features directory.
Example:
Feature: User registration
  Scenario: Register with valid details
    Given The user is on the registration page
    When The user provides valid details
    Then The user should be registered                   successfully

2.Step Definitions:
Implemented in Java and stored in the StepDefinitions directory.

Example:
@Given("^The user is on the registration page$")
public void userIsOnRegistrationPage() {
    driver.get("https://example.com/register");
}

3.Test Runners:
  • Executes feature files.
  • Configured with @CucumberOptions to specify feature locations, step definitions, and reporting
Defining Configuration for Running Cucumber Tests for more details Refer the below post link 

https://softwaretestingbugblab.blogspot.com/2024/09/how-to-configure-cucumberoptions.html?m=1

Benefits of Using BDD:
  • Encourages collaboration between stakeholders.
  • Improves test case readability with Gherkin syntax.
  • Reduces misunderstandings through clear behavior descriptions.
  • Supports automation integration seamlessly.
By structuring your project effectively and leveraging the power of BDD with Gherkin syntax, you can create a robust testing framework that aligns technical implementation with business requirements

Conclusion:
BDD simplifies collaboration between developers, testers, and business stakeholders by focusing on user behavior. With Gherkin syntax, tests become easier to write and understand, aligning technical efforts with business needs.

A well-structured BDD framework, with organized folders for feature files, step definitions, and test runners, ensures clarity and efficiency. Configurations like @CucumberOptions make running and managing tests straightforward and customizable.

By adopting BDD, teams can improve communication, enhance test coverage, and deliver user-friendly software faster and more effectively.

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»