Selenium Java: Handling Alerts and Popups

When working with web applications, handling alerts and popups is a common requirement in test automation. These elements often interrupt the flow of interaction and can affect automated scripts if not handled properly. With Selenium WebDriver in Java, you can effectively manage different types of alerts and popups using built-in methods.

In this blog, we’ll explore how to handle JavaScript alerts, confirmation boxes, and browser popups using Selenium Java, with practical examples and best practices.


Types of Alerts and Popups

  • Before diving into the code, it’s important to understand the types of alerts you may encounter:
  • JavaScript Alerts – Simple alerts with an "OK" button.
  • Confirmation Alerts – Alerts with "OK" and "Cancel" buttons.
  • Prompt Alerts – Alerts that take input from the user.
  • Browser Popups/Authentication Windows – Popups triggered by the browser (not part of the DOM).
  • HTML Popups/Modals – Custom dialogs built using HTML, CSS, and JavaScript.


Handling JavaScript Alerts in Selenium

Selenium provides the Alert interface to interact with JavaScript-based browser alerts.


1. Accepting an Alert

java


import org.openqa.selenium.Alert;

import org.openqa.selenium.WebDriver;

import org.openqa.selenium.chrome.ChromeDriver;


WebDriver driver = new ChromeDriver();

driver.get("https://example.com/alert");


Alert alert = driver.switchTo().alert(); // Switch to the alert

System.out.println("Alert message: " + alert.getText());

alert.accept(); // Click OK

2. Dismissing an Alert

java


Alert alert = driver.switchTo().alert();

alert.dismiss(); // Click Cancel

3. Sending Input to a Prompt Alert

java


Alert alert = driver.switchTo().alert();

alert.sendKeys("Test input");

alert.accept();

Handling Authentication Popups

Browser authentication popups usually appear for protected pages and are outside the control of Selenium. One common workaround is to pass credentials in the URL:


java


driver.get("https://username:password@example.com/protected");

Note: This method may not work in all modern browsers due to security policies.


Handling HTML Popups and Modals

Unlike JavaScript alerts, HTML popups are part of the DOM and can be handled like any other web element using standard Selenium commands:


java


driver.findElement(By.id("modalTrigger")).click(); // Trigger popup

WebElement popup = driver.findElement(By.className("modal-content"));

popup.findElement(By.id("closeButton")).click(); // Close modal

Waits and Synchronization

Popups can take time to appear. Using explicit waits ensures your script waits for the alert to be present:


java


WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(10));

wait.until(ExpectedConditions.alertIsPresent());


Alert alert = driver.switchTo().alert();

alert.accept();

This improves script reliability, especially in dynamic applications.


Best Practices

  • Always use ExpectedConditions.alertIsPresent() to avoid NoAlertPresentException.
  • Handle all types of alerts explicitly based on their behavior.
  • For HTML popups, treat them like regular DOM elements.
  • Avoid using hard-coded delays like Thread.sleep()—prefer WebDriverWait.


Conclusion

Handling alerts and popups is a crucial part of test automation with Selenium Java. Whether it’s a simple alert box or a complex modal dialog, Selenium provides the tools you need to manage these interruptions gracefully. Mastering these interactions ensures your tests run smoothly across different scenarios, enhancing the stability and accuracy of your automation suite.

With the techniques outlined above, you can confidently manage all alert and popup situations in your Selenium test scripts. 

Learn Selenium with Java Training

Read More: Working with Radio Buttons and Checkboxes in Selenium Java

Visit Our IHUB Talent Institute Hyderabad
Get Direction 

Comments

Post a Comment

Popular posts from this blog

How to Use Tosca's Test Configuration Parameters

Tosca by Tricentis is a powerful model-based test automation tool widely used in enterprise environments for end-to-end testing. One of its most useful features is Test Configuration Parameters (TCPs), which provide flexibility and control in managing test execution. TCPs enable testers to create reusable test cases by passing dynamic values without hardcoding them. This significantly enhances test maintenance, scalability, and efficiency. In this blog, we’ll explore what Test Configuration Parameters are, how to create and use them, and the best practices to follow when working with TCPs in Tosca. What Are Test Configuration Parameters? Test Configuration Parameters are custom-defined key-value pairs that can be associated with test cases, test case folders, or execution lists in Tosca. They help manage configuration data such as environment URLs, browser types, credentials, or any other variable data that may differ across test runs. By using TCPs, you can avoid duplicating test case...
Read more

Using Hibernate ORM for Fullstack Java Data Management

In the world of fullstack Java development, managing data efficiently and seamlessly across the application is critical. One of the most powerful tools in the Java ecosystem for handling database operations is Hibernate ORM (Object-Relational Mapping). Hibernate simplifies the interaction between Java applications and relational databases, reducing boilerplate code and improving maintainability. This blog explores how Hibernate ORM works, why it’s widely used, and how it fits into the data management strategy of a fullstack Java application. What is Hibernate ORM? Hibernate ORM is an open-source Java framework that provides a powerful and flexible mechanism for mapping Java objects to database tables. It abstracts the low-level JDBC code, allowing developers to work with high-level object-oriented concepts. Instead of writing raw SQL queries, Hibernate allows developers to define database interactions using simple Java classes (also known as POJOs) and annotations or XML configurations...
Read more

Creating a Test Execution Report with Charts in Playwright

Modern test automation isn't just about running tests—it's also about presenting clear, visual feedback on test results. When working with Playwright, one of the most powerful end-to-end testing tools for modern web apps, generating detailed execution reports can help your team track progress, identify issues quickly, and make data-driven decisions. A visual report with charts brings your testing efforts to life. In this blog, we’ll walk through how to create a test execution report with charts using Playwright’s built-in capabilities along with third-party tools for enhanced visualization. Why Visual Reports Matter Plain text logs and console outputs are hard to parse at scale. A good report should answer questions like: How many tests passed or failed? What’s the overall success rate? Which tests are flaky or slow? How have test results changed over time? Visualizing this data with charts—like pie charts, bar graphs, or timelines—helps QA teams and stakeholders better underst...
Read more