Latest post from this blog

How to Manage Test Execution Across Different Browsers and Environments (QA, UAT, Staging)

By
In real-time automation projects, test execution is never limited to a single browser or a single environment . Applications must be validated across multiple browsers (Chrome, Firefox, Edge) and multiple environments such as QA, UAT, and Staging before going live. A well-designed Selenium + Java + Cucumber automation framework should allow testers to switch browsers and environments easily without changing test scripts . This blog explains how to manage test execution efficiently across different browsers and environments using best practices followed in real projects. Why Multi-Browser and Multi-Environment Testing Is Important Different users use different browsers QA, UAT, and Staging environments have different configurations Bugs may appear only in specific environments or browsers Same test cases must be validated everywhere before production release Common Challenges Testers Face Hardcoded browser names and URLs Maintaining separate test scripts for each environment Browse...
Post a Comment

Understanding the Scenario Outline in Gherkin Language

By
Introduction 
In Gherkin language, scenario outline is the keyword which is used to run the same scenario multiple times.

It is also defined as "Scenario outlines are used when the same test is performed multiple times with a different combination of values."

The keyword scenario outline can also be used by the name Scenario Template. In other words, the keyword Scenario Template is a synonym of scenario outline.

Scenario outline is exactly similar to the scenario structure, but the only difference is the provision of multiple inputs. In order to use scenario outlines, we do not need any smart idea, we just need to copy the same steps and re-execute the code.

Key Features of Scenario Outline
  • Parameterization: Variables are defined in angle brackets (< >) and replaced with values from the Examples table during execution.
  • Reusability: Instead of writing separate scenarios for each data set, a single scenario outline can handle all cases.
  • Clarity: The Examples table makes it easy to understand the different input combinations.
Structure of a Scenario Outline
A Scenario Outline consists of:
  • Scenario Outline: The generic scenario definition.
  • Steps: Regular Gherkin steps with placeholders (e.g., <username>, <password>).
  • Examples Table: A table listing the values for placeholders.
Example:
Feature: Login Functionality

  Scenario Outline: Verify login with.                  different  credentials
    Given The user is on the login page
    When The user enters "<username>"            and ".   <password>"
    Then The user should see the "<result>"        message

  Examples:
    | username | password | result |
    | admin | admin123 | Login Successful |
    | user | user123 | Login Successful |
    | invalidUser | invalidPass | Login Failed |

Difference between Scenario and Scenario Outline

Scenario:
  1. Definition: Represents a single concrete example of a functionality to be tested.
  2. Purpose: Used for testing a specific situation with fixed input data.
  3. Data Handling: Input data is written directly in the steps.
  4. Reusability: Not reusable for multiple data sets. Separate scenarios are needed for each set of data.
  5. Keyword: Defined using the Scenario keyword.
  6. Examples Table: Does not use an Examples table.
Example 
Scenario: Login with valid credentials
  Given the user is on the login page
  When the user enters "testuser" and "password123"
  Then the user should be redirected to the homepage

Scenario Outline:
  1. Definition: Represents a template that can run the same scenario multiple times with different sets of input data.
  2. Purpose: Used for testing the same functionality with multiple data sets.
  3. Data Handling: Input data is provided through an Examples table.
  4. Reusability: Highly reusable as it iterates through all the rows in the Examples table.
  5. Keyword: Defined using the Scenario Outline keyword.
  6. Examples Table: Uses an Examples table to provide multiple sets of data.
Example 
Scenario Outline: Login with multiple credentials
  Given the user is on the login page
  When the user enters "<username>" and ". <password>"
  Then the user should be redirected to           the  homepage

Examples:
  | username | password |
  | testuser1 | password123 |
  | testuser2 | pass456 |


Comments

Post a Comment

Popular posts from this blog

How to Manage Test Execution Across Different Browsers and Environments (QA, UAT, Staging)

By
In real-time automation projects, test execution is never limited to a single browser or a single environment . Applications must be validated across multiple browsers (Chrome, Firefox, Edge) and multiple environments such as QA, UAT, and Staging before going live. A well-designed Selenium + Java + Cucumber automation framework should allow testers to switch browsers and environments easily without changing test scripts . This blog explains how to manage test execution efficiently across different browsers and environments using best practices followed in real projects. Why Multi-Browser and Multi-Environment Testing Is Important Different users use different browsers QA, UAT, and Staging environments have different configurations Bugs may appear only in specific environments or browsers Same test cases must be validated everywhere before production release Common Challenges Testers Face Hardcoded browser names and URLs Maintaining separate test scripts for each environment Browse...
Read more»

Purpose of the StepData Class in Selenium + Java Cucumber Automation Framework

By
When working with a Selenium + Java + Cucumber automation framework , one of the most common challenges testers face is sharing data between different step definitions within the same scenario. For example, a value created in one step—such as a login token or order ID—often needs to be reused in later steps. This is where the StepData class becomes extremely useful. In this blog, we will cover: What the StepData class is Why it is required in Cucumber frameworks How it is used in real-time automation projects Best practices for using StepData effectively What Is the StepData Class? The StepData class is a simple POJO (Plain Old Java Object) designed to store and share test data across multiple step definition classes within a single Cucumber scenario. It acts as a central data container that holds scenario-specific information during test execution. Why Do We Need StepData in Cucumber? Cucumber follows an object-oriented execution model, which creates certain limitations: Each st...
Read more»

Ensuring Thread Safety in Parallel Test Execution with Selenium, Cucumber, and Java

By
🔒 What Is Thread Safety in Selenium Automation? When multiple threads (tests or scenarios) run simultaneously, they must not interfere with each other’s data or browser sessions. ⚠️ Example: Common Problem Without Thread Safety If your WebDriver is declared as: public static WebDriver driver; and you run tests in parallel, all tests share the same driver object — leading to several issues such as: 1️⃣ Browser windows closing unexpectedly 2️⃣ Wrong data being accessed by other tests 3️⃣ Screenshots captured from the wrong browser 4️⃣ Flaky or inconsistent test results 5️⃣ One test closing the browser while another is still running 6️⃣ Tests opening URLs in the same browser window 7️⃣ Random “Session not found” errors ➡️ Without thread safety, your parallel runs become unstable and unreliable. 💡 How To Achieve Thread Safety We can achieve thread safety using the ThreadLocal class in our automation framework. 🧰 What Is ThreadLocal? ThreadLocal provides each thread with its own copy of ...
Read more»