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

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 cannot find an element on the page that it is trying to interact with.

6. NoSuchFrameException is thrown when it cannot find the frame that it is trying to switch to. 

7. NoSuchWindowException is thrown when it cannot find the window that it is trying to switch to. 

8. NoAlertPresentException is thrown when trying to switch to an alert that is not present.

9. ElementClickInterceptedException is thrown when an element that a program is trying to click is blocked from being clicked. This can happen if another element on the page is covering the element that the program is trying to click on, or if the element is obscured by a modal dialog or pop-up window.

10. InvalidElementStateException is thrown when an operation is attempted on an element that is not in a valid state for the operation. For example, if you try to click a button on a webpage using Selenium, but the button is not visible or is disabled.

11. SessionNotFoundException Occurs when WebDriver tries to perform an action after the browser session has ended or is invalid.

12. ElementNotInteractableException Thrown when an element is present and visible in the DOM but cannot be interacted with (e.g., a disabled button or an input field).

13. ElementNotVisibleException occurs when an element is present in the DOM but not visible on the page, so Selenium cannot interact with it.

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»