Cookie management in Selenium Java - Build an Automation Script

Verify cookie management on example.com

Preconditions (3)

Step 1: Open browser and navigate to https://example.com

Step 2: Add a cookie with name 'testCookie' and value 'cookieValue123'

Step 3: Retrieve the cookie named 'testCookie' and verify its value is 'cookieValue123'

Step 4: Delete the cookie named 'testCookie'

Step 5: Verify that the cookie named 'testCookie' no longer exists

✅ Expected Result: The cookie 'testCookie' is added successfully with correct value, then deleted and no longer present

Automation Requirements - Selenium WebDriver with Java

Assertions Needed:

Assert cookie value equals 'cookieValue123' after adding

Assert cookie is null after deletion

Best Practices:

Use WebDriver's manage().getCookies() and manage().addCookie() methods

Use explicit waits if needed before cookie operations

Use meaningful variable names and comments

Close browser after test

Automated Solution

Selenium Java

import org.openqa.selenium.By;
import org.openqa.selenium.Cookie;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.support.ui.WebDriverWait;
import org.openqa.selenium.support.ui.ExpectedConditions;
import java.time.Duration;

public class CookieManagementTest {
    public static void main(String[] args) {
        // Set up ChromeDriver (assumes chromedriver is in system PATH)
        WebDriver driver = new ChromeDriver();
        try {
            // Navigate to example.com
            driver.get("https://example.com");

            // Wait until page title contains 'Example Domain' to ensure page loaded
            new WebDriverWait(driver, Duration.ofSeconds(10))
                .until(ExpectedConditions.titleContains("Example Domain"));

            // Create a cookie named 'testCookie' with value 'cookieValue123'
            Cookie testCookie = new Cookie.Builder("testCookie", "cookieValue123")
                .domain("example.com")
                .path("/")
                .build();

            // Add cookie to browser
            driver.manage().addCookie(testCookie);

            // Retrieve cookie by name
            Cookie retrievedCookie = driver.manage().getCookieNamed("testCookie");

            // Assert cookie value is 'cookieValue123'
            if (retrievedCookie == null) {
                throw new AssertionError("Cookie 'testCookie' was not found after adding.");
            }
            if (!"cookieValue123".equals(retrievedCookie.getValue())) {
                throw new AssertionError("Cookie value mismatch. Expected 'cookieValue123' but got '" + retrievedCookie.getValue() + "'.");
            }

            // Delete the cookie named 'testCookie'
            driver.manage().deleteCookieNamed("testCookie");

            // Verify cookie no longer exists
            Cookie deletedCookie = driver.manage().getCookieNamed("testCookie");
            if (deletedCookie != null) {
                throw new AssertionError("Cookie 'testCookie' still exists after deletion.");
            }

            System.out.println("Test passed: Cookie management works as expected.");

        } finally {
            // Close browser
            driver.quit();
        }
    }
}

This test script uses Selenium WebDriver with Java to automate cookie management on https://example.com.

First, it opens the browser and navigates to the site. It waits until the page title contains 'Example Domain' to ensure the page is fully loaded.

Then, it creates a cookie named 'testCookie' with the value 'cookieValue123' and adds it to the browser.

Next, it retrieves the cookie by name and asserts that the value matches the expected value.

After that, it deletes the cookie and verifies that it no longer exists.

Finally, it prints a success message and closes the browser to clean up.

This approach uses explicit waits, meaningful variable names, and proper assertions to ensure reliability and clarity.

Common Mistakes - 4 Pitfalls

Not specifying the domain when creating a cookie

Using Thread.sleep() instead of explicit waits before cookie operations

Not checking if the cookie exists before accessing its value

Not closing the browser after test execution

Bonus Challenge

Now add data-driven testing to add and verify cookies with 3 different name-value pairs.

Show Hint

Practice

1. What is the primary purpose of managing cookies in Selenium tests?

easy

A. To change the browser's window size

B. To store and manipulate small pieces of data like user sessions

C. To locate elements on a web page

D. To execute JavaScript code on the page

Solution

1. Step 1: Understand what cookies do

   Cookies store small data such as user sessions or preferences to remember users.

2. Step 2: Relate to Selenium's cookie management

   Selenium allows adding, retrieving, and deleting cookies to simulate user sessions during tests.

3. Final Answer:

   To store and manipulate small pieces of data like user sessions -> Option B

4. Quick Check:

   Cookies = user session data [OK]

Hint: Cookies store user info for session tests [OK]

Common Mistakes:

• Confusing cookies with browser window controls
• Thinking cookies locate page elements
• Assuming cookies run JavaScript

2. Which of the following is the correct way to add a cookie in Selenium Java?

easy

A. driver.addCookie(new Cookie("name", "value"));

B. driver.addCookie("name", "value");

C. driver.manage().cookieAdd("name", "value");

D. driver.manage().addCookie(new Cookie("name", "value"));

Solution

1. Step 1: Recall Selenium cookie API

   Cookies are added via driver.manage().addCookie() method with a Cookie object.

2. Step 2: Check syntax correctness

   driver.manage().addCookie(new Cookie("name", "value")); uses correct method and creates a new Cookie object properly.

3. Final Answer:

   driver.manage().addCookie(new Cookie("name", "value")); -> Option D

4. Quick Check:

   Use driver.manage().addCookie(new Cookie()) [OK]

Hint: Use driver.manage().addCookie(new Cookie()) [OK]

Common Mistakes:

• Calling addCookie directly on driver
• Using incorrect method names like cookieAdd
• Passing strings instead of Cookie objects

3. What will be the output of the following code snippet?

Cookie cookie = new Cookie("session", "abc123");
driver.manage().addCookie(cookie);
Cookie retrieved = driver.manage().getCookieNamed("session");
System.out.println(retrieved.getValue());

medium

A. abc123

B. session

C. null

D. Throws NoSuchElementException

Solution

1. Step 1: Add cookie named "session" with value "abc123"

   The code adds a cookie with name "session" and value "abc123" to the browser.

2. Step 2: Retrieve cookie by name and print its value

   driver.manage().getCookieNamed("session") returns the cookie object, and getValue() prints "abc123".

3. Final Answer:

   abc123 -> Option A

4. Quick Check:

   getCookieNamed("session").getValue() = abc123 [OK]

Hint: getCookieNamed returns cookie object; getValue prints value [OK]

Common Mistakes:

• Expecting cookie name instead of value
• Assuming null if cookie not found (but it is added)
• Thinking exception is thrown when cookie exists

4. Identify the error in this Selenium Java code for deleting a cookie:

driver.manage().deleteCookie("session");

medium

A. deleteCookie requires cookie name as a String, so code is correct

B. deleteCookie method does not exist in Selenium

C. deleteCookie method requires a Cookie object, not a String

D. deleteCookie should be called on driver, not driver.manage()

Solution

1. Step 1: Check deleteCookie method signature

   deleteCookie expects a Cookie object, not a String name.

2. Step 2: Correct usage

   To delete by name, use deleteCookieNamed(String name) instead.

3. Final Answer:

   deleteCookie method requires a Cookie object, not a String -> Option C

4. Quick Check:

   deleteCookie(Cookie) vs deleteCookieNamed(String) [OK]

Hint: Use deleteCookieNamed for String name, deleteCookie for Cookie object [OK]

Common Mistakes:

• Passing String to deleteCookie instead of Cookie object
• Confusing deleteCookie and deleteCookieNamed methods
• Calling deleteCookie on wrong object

5. You want to test that after deleting a cookie named "user", it no longer exists. Which code snippet correctly verifies this?

hard

A. driver.manage().deleteCookieNamed("user");
assert driver.manage().getCookieNamed("user") == null;

B. driver.manage().deleteCookie(new Cookie("user", "value"));
assert driver.manage().getCookieNamed("user").getValue().equals("");

C. driver.manage().deleteCookieNamed("user");
assert driver.manage().getCookieNamed("user").getValue() == null;

D. driver.manage().deleteCookie(new Cookie("user", "value"));
assert driver.manage().getCookieNamed("user") != null;

Solution

1. Step 1: Delete cookie by name "user"

   Use deleteCookieNamed("user") to remove the cookie by its name.

2. Step 2: Verify cookie no longer exists

   getCookieNamed("user") returns null if cookie is deleted; assert null confirms deletion.

3. Final Answer:

   driver.manage().deleteCookieNamed("user"); assert driver.manage().getCookieNamed("user") == null; -> Option A

4. Quick Check:

   Deleted cookie returns null [OK]

Hint: Deleted cookie returns null on getCookieNamed [OK]

Common Mistakes:

• Checking getValue() on null cookie causing NullPointerException
• Using deleteCookie with Cookie object without correct value
• Asserting cookie still exists after deletion