Closing browser (close vs quit) in Selenium Java - Automation Approaches Compared

Verify browser closing behavior using close() and quit() methods

Preconditions (3)

Step 1: Launch the browser using WebDriver

Step 2: Navigate to https://example.com

Step 3: Call driver.close() to close the current browser window

Step 4: Verify that the browser window is closed but WebDriver session may still exist

Step 5: Launch the browser again using WebDriver

Step 6: Navigate to https://example.com

Step 7: Call driver.quit() to close all browser windows and end the WebDriver session

Step 8: Verify that all browser windows are closed and WebDriver session is terminated

✅ Expected Result: After driver.close(), the current browser window closes but WebDriver session may remain active if multiple windows were open. After driver.quit(), all browser windows close and WebDriver session ends.

Automation Requirements - Selenium WebDriver with Java

Assertions Needed:

Verify browser window is closed after driver.close()

Verify WebDriver session is still alive or throws exception after driver.close()

Verify all browser windows are closed after driver.quit()

Verify WebDriver session is terminated after driver.quit()

Best Practices:

Use explicit waits if needed to ensure page loads before closing

Handle exceptions when checking WebDriver session state

Use try-finally to ensure driver.quit() is called to avoid orphan processes

Use descriptive method names and comments

Automated Solution

Selenium Java

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.NoSuchSessionException;

public class BrowserCloseVsQuitTest {
    public static void main(String[] args) {
        System.setProperty("webdriver.chrome.driver", "path/to/chromedriver");

        // Test driver.close()
        WebDriver driver = new ChromeDriver();
        try {
            driver.get("https://example.com");
            // Close current window
            driver.close();

            // After close(), try to get current URL to check if session is alive
            try {
                String url = driver.getCurrentUrl();
                System.out.println("Session alive after close(), current URL: " + url);
            } catch (NoSuchSessionException e) {
                System.out.println("Session ended after close(): " + e.getMessage());
            }
        } catch (Exception e) {
            e.printStackTrace();
        } finally {
            // Quit driver to clean up if session still alive
            try {
                driver.quit();
            } catch (Exception ignored) {}
        }

        // Test driver.quit()
        WebDriver driver2 = new ChromeDriver();
        try {
            driver2.get("https://example.com");
            // Quit closes all windows and ends session
            driver2.quit();

            // After quit(), try to get current URL to verify session ended
            try {
                String url = driver2.getCurrentUrl();
                System.out.println("Session alive after quit(), current URL: " + url);
            } catch (NoSuchSessionException e) {
                System.out.println("Session ended after quit(): " + e.getMessage());
            }
        } catch (Exception e) {
            e.printStackTrace();
        }
    }
}

This code demonstrates the difference between driver.close() and driver.quit() in Selenium WebDriver using Java.

First, it opens a browser and navigates to example.com, then calls driver.close() which closes the current browser window. We then try to get the current URL to check if the WebDriver session is still alive. Usually, if only one window was open, the session may still be alive but the window is closed.

Next, it opens a new browser session and navigates to example.com again, then calls driver.quit() which closes all browser windows and ends the WebDriver session. Trying to get the current URL after quit throws a NoSuchSessionException, confirming the session ended.

Using try-finally blocks ensures the driver quits properly to avoid leftover browser processes. Catching exceptions helps verify session state after close and quit.

Common Mistakes - 3 Pitfalls

Using driver.close() expecting all browser windows to close

Not handling exceptions after calling driver.close() or driver.quit()

Not calling driver.quit() in finally block

Bonus Challenge

Now add data-driven testing to open multiple URLs and test close vs quit behavior for each.

Show Hint

Practice

1. What does the close() method do in Selenium WebDriver?

easy

A. Closes the current browser window or tab only

B. Closes all browser windows and ends the WebDriver session

C. Keeps the browser open but clears cookies

D. Minimizes the browser window

Solution

1. Step 1: Understand the purpose of close()

   The close() method is designed to close only the current browser window or tab that the WebDriver is controlling.

2. Step 2: Differentiate from quit()

   Unlike quit(), which closes all windows and ends the session, close() affects only one window or tab.

3. Final Answer:

   Closes the current browser window or tab only -> Option A

4. Quick Check:

   close() closes one window [OK]

Hint: Close closes one window; quit closes all [OK]

Common Mistakes:

• Confusing close() with quit()
• Thinking close() ends the WebDriver session
• Assuming close() clears cookies

2. Which of the following is the correct syntax to close all browser windows and end the WebDriver session in Java Selenium?

easy

A. driver.close();

B. driver.quit();

C. driver.exit();

D. driver.shutdown();

Solution

1. Step 1: Recall the method to end WebDriver session

   The method quit() is used to close all browser windows and end the WebDriver session.

2. Step 2: Check syntax correctness

   The correct syntax in Java Selenium is driver.quit();. Other options like exit() or shutdown() do not exist in WebDriver API.

3. Final Answer:

   driver.quit(); -> Option B

4. Quick Check:

   Use quit() to close all windows [OK]

Hint: Use quit() to close all windows and end session [OK]

Common Mistakes:

• Using close() instead of quit() to end session
• Using non-existent methods like exit() or shutdown()
• Missing parentheses in method call

3. Consider the following Java Selenium code snippet:

WebDriver driver = new ChromeDriver();
driver.get("https://example.com");
driver.close();
driver.get("https://google.com");

What will happen when this code runs?

medium

A. The browser opens example.com and google.com in the same tab without closing

B. The browser opens example.com, closes the tab, then opens google.com in a new window

C. The browser opens example.com and google.com in two tabs without closing any

D. The browser opens example.com, closes the tab, then throws an exception on the next get() call

Solution

1. Step 1: Analyze the effect of driver.close()

   The close() method closes the current browser window or tab but does not end the WebDriver session. However, if it is the only window, the session becomes invalid.

2. Step 2: Understand the next get() call after close()

   After closing the only window, calling driver.get() will cause a NoSuchWindowException or similar because there is no open window to navigate.

3. Final Answer:

   The browser opens example.com, closes the tab, then throws an exception on the next get() call -> Option D

4. Quick Check:

   close() closes window; next get() fails if no window [OK]

Hint: Close closes tab; next commands fail if no window open [OK]

Common Mistakes:

• Assuming get() opens new window after close()
• Thinking close() ends session like quit()
• Ignoring exceptions after closing last window

4. You have this Java Selenium code:

driver.close();
driver.quit();

What is the problem with this code?

medium

A. No problem; calling close() before quit() works without throwing exceptions

B. close() and quit() do the same thing, so one is redundant

C. Calling quit() before close() is required to avoid errors

D. Calling close() before quit() may cause quit() to throw an exception if no windows remain

Solution

1. Step 1: Understand the effect of close()

   Calling close() closes the current window. If it is the last window, no windows remain open, but the WebDriver session remains active.

2. Step 2: Analyze quit() after close()

   Calling quit() after close() safely terminates the session even with no windows left; no exception is thrown.

3. Final Answer:

   No problem; calling close() before quit() works without throwing exceptions -> Option A

4. Quick Check:

   close() then quit() succeeds [OK]

Hint: close() followed by quit() is safe; no exceptions [OK]

Common Mistakes:

• Thinking close() before quit() throws exception
• Confusing close() and quit() effects
• Believing quit() must precede close()

5. You want to close only the current tab but keep the WebDriver session active to open a new tab later. Which method should you use and why?

hard

A. Use driver.quit() because it closes all tabs and ends session cleanly

B. Use driver.quit() and then create a new WebDriver instance

C. Use driver.close() because it closes only the current tab and keeps session alive

D. Use driver.close() and then call driver.quit() immediately

Solution

1. Step 1: Identify the requirement to keep session alive

   To keep the WebDriver session active, you must not call quit() because it ends the session and closes all windows.

2. Step 2: Choose method that closes only current tab

   The close() method closes only the current tab or window but keeps the WebDriver session alive, allowing further commands like opening new tabs.

3. Final Answer:

   Use driver.close() because it closes only the current tab and keeps session alive -> Option C

4. Quick Check:

   close() closes tab; quit() ends session [OK]

Hint: Close closes tab; quit ends session completely [OK]

Common Mistakes:

• Using quit() and losing session
• Calling quit() then expecting to open new tabs
• Confusing close() with quit() effects