Posts

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
Read more»

Popular posts from this blog

Naming convention for different types of web elements to use in automation or coding

By
Image
Introduction defining a naming convention for different types of web elements to use in automation or coding, where the prefix helps quickly identify the element type. This is a good practice to maintain readability and clarity in your code.  Here's a clean list of the prefixes and their examples: Conclusion consistent naming convention for locators is vital for maintainable test automation scripts. Clear naming improves code readability and helps team members quickly understand each locator's purpose. This practice facilitates collaboration and simplifies debugging, allowing for faster updates as applications evolve. Ultimately, adopting standardized naming conventions enhances the quality of your automation framework and leads to more reliable and efficient tests, strengthening your overall testing strategy.
Read more»

Using Properties Files in Selenium for Test Automation

By
Image
Introduction In software testing, managing configuration settings is vital for reliable and maintainable automation scripts. Properties files offer a simple way to store key-value pairs of configuration data separately from the code, enhancing flexibility and ease of management in test automation. Using properties files in test automation offers several benefits: Decoupling Configuration from Code: Properties files allow easy updates to configuration data without changing the test code, minimizing errors. Ease of Maintenance: Testers can quickly modify the properties file for updates, saving time compared to changing multiple scripts. Enhanced Reusability: A single properties file can be reused across different test scripts, promoting cleaner code and easier testing. In this tutorial, we will cover the following topics: How to create a properties file and add key-value pairs for configuration settings. How to read data from the properties file using Java’s built-in Properties clas...
Read more»

How To Handle An Authentication Pop-up Using Selenium WebDriver

By
Image
Introduction As the IT sector continues to evolve, securing applications becomes increasingly important. Many organizations implement specific proxy settings that necessitate user credentials when accessing their servers in a browser. Consequently, Selenium must be equipped to handle these authentication prompts before server access.   Below are several methods for handling such authentication pop-ups, especially in a corporate environment where proxy settings may be in place. 1. Via the URL  you can include the username and password directly in the URL. This method is straightforward but may not work in all scenarios, especially if the authentication pop-up is more complex. Syntax: http://username:password@URL username=xyz password =abc @xyz String URL = “http: //” + xyz+ ”:” + abc@xyz+ “@” +www.AutomationEnigma.com; driver. get ( URL ); Alert alert = driver.switchTo().alert(); alert. accept (); Example Selenium Code // Launch browser and navigate to the URL driver. get...
Read more»

Controlling Execution Order by Naming Feature Files Alphabetically in Cucumber Framework

By
Image
Introduction In the Cucumber framework, you can control the order of execution of your feature files by naming them in the sequence you want them to be executed. Cucumber executes feature files in alphabetical order by default. So, you can prefix your feature files with numbers or letters to control their execution order. Consider the following three features in a basic application: Login , HomePage , and Registration . Here’s how your feature files may look initially: Login.feature HomePage.feature Registration.feature By default, Cucumber might execute these in an unpredictable order. To control the execution sequence, you need to rename them alphabetically or numerically. Rename Feature Files Alphabetically For example, you can rename your feature files like this: 1_Login.feature 2_HomePage.feature 3_Registration.feature And, add the same tag ( @Sanity ) in each feature file: In the TestNG runner class, you specify the tag @Sanity  to run the tests. Execution Flow When you run ...
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»

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...
Read more»

How do you handle dynamic web elements in Selenium

By
Introduction Dynamic elements are those whose attributes (such as IDs, names, or classes) change every time the page loads or during interactions. To handle them, you can use techniques like: Using regular expressions in locators Using XPath functions like contains, starts-with, ends-with Using CSS selectors 1. XPath and CSS Selectors : Use relative XPath or CSS selectors that do not depend on specific attribute values. 2. Explicit Waits : Employ WebDriverWait to wait for the element to become visible or clickable before interacting with it. You can use conditions like ExpectedConditions.visibilityOfElementLocated. 3. Partial Text Matching : When the attribute value changes partially, you can use XPath or CSS to match a substring of the attribute value Conclusion Handling dynamic web elements in Selenium requires a combination of techniques, such as explicit waits, fluent waits, flexible locators, and JavaScript execution. By implementing these strategies, you can create robust test ...
Read more»

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»

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»

How to Configure the @CucumberOptions Annotation in Your Automation Framework

By
Introduction  in Cucumber, the @CucumberOptions annotation helps configure important settings for your tests, such as where to find feature files, step definitions, and how to generate reports. It also lets you filter scenarios and control the test execution flow. When using Cucumber with TestNG, the test runner class usually extends AbstractTestNGCucumberTests . This class allows Cucumber tests to run as TestNG tests, giving you access to TestNG features like parallel execution, flexible configuration, and detailed reports. Together, @CucumberOptions and the TestNG runner class that extends AbstractTestNGCucumberTests create a strong testing setup. This combination makes it easier to run and manage your tests while taking advantage of both Cucumber and TestNG features. Steps to Define Configuration for Running Cucumber Tests Step 1: Set Up the Runner Class import org.junit.runner. RunWith ; import io.cucumber.junit.Cucumber; import io.cucumber.junit. CucumberOptions ; @RunWith ...
Read more»