Alert accept and dismiss in Selenium Java - Framework Patterns

Framework Mode - Alert accept and dismiss

Folder Structure

src/
└── test/
    └── java/
        └── com/
            └── example/
                ├── pages/
                │   └── AlertPage.java
                ├── tests/
                │   └── AlertTests.java
                ├── utils/
                │   └── WebDriverFactory.java
                └── config/
                    └── ConfigReader.java
    

Test Framework Layers

• Driver Layer: Manages WebDriver setup and teardown (e.g., WebDriverFactory.java).
• Page Objects: Encapsulate page elements and alert handling methods (e.g., AlertPage.java with methods to accept and dismiss alerts).
• Tests: Test classes that use page objects to perform alert accept and dismiss actions (e.g., AlertTests.java).
• Utilities: Helper classes for common tasks like waits or reading configurations.
• Configuration: Manage environment variables, browser settings, and credentials (e.g., ConfigReader.java).

Configuration Patterns

Use property files or environment variables to manage:

• Browser type (Chrome, Firefox, etc.)
• Base URL of the application
• Timeouts for waits
• Credentials if needed

Load these settings in ConfigReader.java and use them in WebDriverFactory.java and tests.

Test Reporting and CI/CD Integration

• Use TestNG or JUnit reports to show pass/fail status of alert tests.
• Integrate with CI tools like Jenkins or GitHub Actions to run tests on code changes.
• Generate HTML or XML reports for easy review.
• Include screenshots on failure for alert handling issues.

Best Practices

• Use explicit waits to wait for alerts before accepting or dismissing.
• Encapsulate alert handling in page object methods for reuse and clarity.
• Keep test methods focused: one test for accept, one for dismiss.
• Handle unexpected alerts gracefully to avoid test failures.
• Use descriptive method names like acceptAlert() and dismissAlert().

Self Check

Where in this folder structure would you add a new method to handle alert text retrieval?

Key Result

Organize Selenium Java tests with clear layers: driver setup, page objects for alert handling, tests, utilities, and config for maintainable alert accept and dismiss automation.

Practice

1. What does the accept() method do when called on a JavaScript alert in Selenium?

easy

A. Clicks the OK button on the alert

B. Clicks the Cancel button on the alert

C. Closes the browser window

D. Throws an exception without interacting

Solution

1. Step 1: Understand alert interaction methods

   The accept() method is used to click the OK button on an alert popup.

2. Step 2: Differentiate from dismiss()

   The dismiss() method clicks Cancel, so accept() must click OK.

3. Final Answer:

   Clicks the OK button on the alert -> Option A

4. Quick Check:

   accept() = OK click [OK]

Hint: accept() clicks OK, dismiss() clicks Cancel [OK]

Common Mistakes:

• Confusing accept() with dismiss()
• Thinking accept() closes the browser
• Assuming accept() throws an exception

2. Which of the following is the correct syntax to switch to an alert and dismiss it in Selenium Java?

easy

A. driver.switchTo().alert().dismiss();

B. driver.switchTo().alert().cancel();

C. driver.switchTo().alert().close();

D. driver.switchTo().alert().accept();

Solution

1. Step 1: Identify the method to dismiss alert

   The method to click Cancel on an alert is dismiss().

2. Step 2: Confirm correct syntax for switching and dismissing

   The correct chain is driver.switchTo().alert().dismiss(); to dismiss the alert.

3. Final Answer:

   driver.switchTo().alert().dismiss(); -> Option A

4. Quick Check:

   dismiss() = Cancel click [OK]

Hint: Use dismiss() to cancel alerts, accept() to confirm [OK]

Common Mistakes:

• Using accept() instead of dismiss() to cancel
• Using non-existent methods like close() or cancel()
• Missing switchTo().alert() before calling dismiss()

3. Given the following code snippet, what will be printed if the alert is accepted?

driver.switchTo().alert().accept();
System.out.println("Alert handled successfully");

medium

A. UnhandledAlertException

B. Alert handled successfully

C. No output

D. Alert not found error

Solution

1. Step 1: Understand alert acceptance effect

   Calling accept() closes the alert, allowing the next line to execute.

2. Step 2: Check output after alert handling

   Since alert is accepted, System.out.println runs and prints the message.

3. Final Answer:

   Alert handled successfully -> Option B

4. Quick Check:

   accept() closes alert, next line prints [OK]

Hint: accept() lets code continue, so print runs [OK]

Common Mistakes:

• Expecting exception after accept()
• Thinking alert blocks print statement
• Confusing accept() with dismiss() effect

4. Identify the error in this Selenium Java code snippet that tries to dismiss an alert:

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

medium

A. alert.dismiss() should be alert.cancel()

B. Calling accept() before dismiss() causes an exception

C. Missing driver.switchTo() before alert()

D. Cannot call dismiss() after accept() on the same alert instance

Solution

1. Step 1: Understand alert lifecycle after accept()

   Once accept() is called, the alert is closed and no longer available.

2. Step 2: Calling dismiss() after accept() is invalid

   Trying to dismiss the same alert after accepting it causes an error because alert is gone.

3. Final Answer:

   Cannot call dismiss() after accept() on the same alert instance -> Option D

4. Quick Check:

   accept() closes alert, no dismiss() after [OK]

Hint: Alert closes after accept(), can't dismiss same alert [OK]

Common Mistakes:

• Calling dismiss() after accept() on same alert
• Assuming alert stays open after accept()
• Using non-existent cancel() method

5. You want to write a Selenium Java test that clicks Cancel on a confirmation alert only if the alert text contains the word "Delete". Which code snippet correctly implements this?

hard

A. Alert alert = driver.switchTo().alert();
if (alert.getText() == "Delete") {
alert.accept();
} else {
alert.dismiss();
}

B. Alert alert = driver.switchTo().alert();
alert.dismiss();
if (alert.getText().contains("Delete")) {
alert.accept();
}

C. Alert alert = driver.switchTo().alert();
if (alert.getText().contains("Delete")) {
alert.dismiss();
} else {
alert.accept();
}

D. Alert alert = driver.switchTo().alert();
alert.accept();
alert.dismiss();

Solution

1. Step 1: Check alert text for "Delete" substring

   Use alert.getText().contains("Delete") to detect if alert text includes "Delete".

2. Step 2: Dismiss alert if condition true, else accept

   If text contains "Delete", call dismiss() to click Cancel; otherwise, call accept().

3. Final Answer:

   Alert alert = driver.switchTo().alert(); if (alert.getText().contains("Delete")) { alert.dismiss(); } else { alert.accept(); } -> Option C

4. Quick Check:

   Use contains() and dismiss() for conditional cancel [OK]

Hint: Use getText().contains() before dismiss() or accept() [OK]

Common Mistakes:

• Using == instead of contains() for string check
• Calling dismiss() before checking alert text
• Calling accept() and dismiss() both without condition