Execute Playwright Script on Chrome Browser

When you execute a Playwright script on the Chrome browser, you are telling Playwright to launch tests on the real Chrome browser rather than the bundled Chromium. By default, Playwright uses Chromium, which is an open-source browser engine used by Chrome and Edge. However, if you specifically want to run on Google Chrome, Playwright allows you to configure it.

(1) Chromium vs Chrome

• Chromium is the base project that Chrome is built on. Playwright ships with its own bundled version of Chromium.
• Chrome is the actual browser installed on your system (with additional features, branding, and sometimes slight differences).

(2) How Playwright Handles Browsers

• Playwright has built-in support for Chromium, Firefox, and WebKit.
• For Chromium-based browsers, you can point Playwright to use either the bundled Chromium or your installed Chrome browser.
• This is done by specifying the executable path of Chrome.

(3) Why Run Tests on Chrome?

• Some projects or organizations require running automation scripts on the same browser version that end users use (i.e., Chrome instead of Playwright’s default Chromium).
• This ensures compatibility testing with the actual Chrome build.
• Running on Chrome may also be needed when browser policies, extensions, or enterprise configurations are involved.

(4) Process of Running on Chrome

• Playwright launches Chrome using its Playwright API, but instead of the bundled Chromium, it points to the Chrome executable available on your machine.
• Once launched, the script runs in the same way—navigating pages, finding locators, clicking elements, etc.—but all actions are now happening in the Google Chrome browser.

(5) Key Points

• Execution on Chrome is nearly identical to execution on Chromium in terms of Playwright commands.
• The main difference lies in specifying which browser binary to use.
• After that, all locators, assertions, and interactions remain the same.

To execute a Playwright script in the Chrome browser using Java, you need to launch the browser in "Chrome" mode instead of the default "Chromium" (Playwright uses Chromium by default).

Steps to Run Playwright in Chrome (Java):

• Install Chrome on your system (Playwright will launch the installed Chrome browser).
• Set the executable path of Chrome.
• Use launchPersistentContext with Chrome executable path to launch Chrome.
• Write and run your Playwright Java test.

Maven Dependency

<dependency>
  <groupId>com.microsoft.playwright</groupId>
  <artifactId>playwright</artifactId>
  <version>1.43.0</version> <!-- or latest -->
</dependency>

Java Code Example: Launch in Chrome

import com.microsoft.playwright.*;

import java.nio.file.Paths;

public class PlaywrightChromeExample {
  public static void main(String[] args) {
    try (Playwright playwright = Playwright.create()) {

      // Path to the installed Chrome browser executable
      String chromePath = "C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe"; // Adjust this path

      BrowserType.LaunchOptions options = new BrowserType.LaunchOptions()
        .setExecutablePath(Paths.get(chromePath))
        .setHeadless(false); // Show the browser window

      Browser browser = playwright.chromium().launch(options);
      Page page = browser.newPage();
      page.navigate("https://example.com");

      System.out.println("Page title: " + page.title());

      browser.close();
    }
  }
}

Code explanation:

(a) Create Playwright object

(b) Create Browser object

(c) Then, create Page object

(d) Navigate to webpage by page.navigate()

(e) Print page title on console

Suggested Posts:

1. Automate GET API in Playwright
2. Automate POST API in Playwright
3. Automate PUT API in Playwright
4. Test Token Based Authentication in Playwright
5. Basic Authentication in Playwright

Overview of Playwright Framework

What Is Playwright? A Complete Beginner-to-Advanced Guide to Playwright Automation Framework

In today’s fast-paced software development world, delivering high-quality web applications quickly is more important than ever. Automation testing has become a critical part of modern DevOps and CI/CD pipelines. Among the many automation tools available, Playwright has rapidly gained popularity for its speed, reliability, and modern web capabilities.

If you are a QA engineer, automation tester, developer, or DevOps professional looking to understand what Playwright is and why it is becoming the preferred automation framework, this detailed guide will help you.

In this comprehensive article, you will learn:

• What Playwright is

• Key features of Playwright

• Supported browsers and platforms

• Advanced capabilities

• Playwright vs Selenium comparison

• Real-world use cases

• Why Playwright is ideal for modern automation

• CI/CD integration

• Official resources and next steps

This guide is fully SEO optimized, AdSense-friendly, and written in a natural, human-like tone.

What Is Playwright?

Playwright is an open-source end-to-end (E2E) automation testing framework developed by Microsoft. It is designed to automate modern web applications across multiple browsers using a single API and codebase.

Playwright allows developers and testers to:

• Automate browser interactions

• Perform UI testing

• Execute API testing

• Capture screenshots and videos

• Run cross-browser testing

• Simulate mobile devices

• Mock network conditions

It supports automation for:

• Chromium-based browsers (Chrome, Edge)

• Firefox

• WebKit (Safari engine)

One of the most powerful aspects of Playwright is that it was built for modern web applications from the ground up, making it highly reliable for SPAs (Single Page Applications) like React, Angular, and Vue apps.

Why Playwright Is Gaining Massive Popularity

Over the last few years, automation needs have evolved. Modern applications use:

• Dynamic content loading

• Asynchronous requests

• Shadow DOM

• Complex JavaScript frameworks

Traditional automation tools sometimes struggle with these dynamic behaviors. Playwright was built to handle these modern challenges efficiently.

Because of its:

• Built-in auto-waiting

• Faster execution

• Multi-browser support

• Advanced debugging tools

Playwright has become a preferred automation tool for startups and enterprises alike.

Key Features of Playwright

Let’s explore the major features that make Playwright stand out.

1. Cross-Browser Testing

Playwright supports:

• Chromium (Google Chrome, Microsoft Edge)

• Firefox

• WebKit (Safari engine)

• 
  

The biggest advantage?
You can run the same test script across all supported browsers without changing your code.

Unlike other frameworks, Playwright bundles these browsers automatically. There is no need to download or configure drivers manually.

2. Cross-Platform Support

Playwright runs seamlessly on:

• Windows

• Linux

• macOS

This makes it perfect for development environments and CI/CD pipelines.

3. Built-In Auto-Wait

One of the most loved features of Playwright is its automatic waiting mechanism.

Traditional tools often require manual waits such as:

• Explicit waits

• Implicit waits

• Thread.sleep()

Playwright automatically waits for:

• Elements to be visible

• Elements to be clickable

• Network calls to complete

• Page navigation to finish

This drastically reduces flaky tests.

4. Headless and Headful Modes

Playwright supports:

• Headless mode – Runs tests in the background without opening the browser UI

• Headful mode – Opens the browser visibly for debugging

Headless mode is especially useful in CI/CD pipelines where performance matters.

5. Multiple Language Support

Playwright officially supports:

• JavaScript / TypeScript

• Python

• Java

• .NET

This flexibility allows teams to adopt Playwright without changing their technology stack.

For Java developers, the official documentation is available at:

https://playwright.dev/java/

6. Built-In Test Runner

Playwright includes its own powerful test runner called Playwright Test (primarily for JS/TS users).

Features include:

• Parallel execution

• Retry mechanism

• HTML reports

• Screenshots on failure

• Video recording

• Trace viewer

For Java users, Playwright integrates smoothly with:

• JUnit

• TestNG

7. Browser Contexts (Multi-User Simulation)

Playwright introduces a powerful concept called Browser Contexts.

A browser context is like an isolated browser profile inside the same browser instance.

This allows you to:

• Simulate multiple users

• Test role-based authentication

• Run tests faster without launching multiple browsers

This feature significantly improves performance and scalability.

8. Network and Geolocation Mocking

Playwright allows you to:

• Intercept network requests

• Modify API responses

• Block specific URLs

• Simulate slow networks

• Mock geolocation

This is extremely helpful for:

• Testing offline behavior

• Validating API failure scenarios

• Location-based application testing

9. Visual Comparisons

Playwright supports:

• Screenshot capture

• Full-page screenshots

• Video recording

• Visual regression testing

This helps teams catch UI changes early and maintain consistent user interfaces.

Supported Browsers

Playwright supports three major browser engines:

1. Chromium

Includes: Google Chrome, Microsoft Edge

2. Firefox

3. WebKit

Used by: Safari

All these browsers are bundled automatically when Playwright is installed. No need to manage WebDriver binaries manually.

Advanced Features of Playwright

Playwright is not just a UI automation tool. It includes several advanced capabilities.

1. API Testing

Playwright includes built-in API testing capabilities.

You can:

• Send HTTP requests

• Validate responses

• Authenticate APIs

• Test backend services

This eliminates the need for external tools in many cases.

2. Mobile Emulation

Playwright can emulate mobile devices like:

• iPhone

• Pixel

• Galaxy devices

You can test responsive designs and mobile UI without physical devices.

3. Component Testing

Playwright supports component testing for modern frameworks such as:

• React

• Angular

• Vue

This allows you to test individual UI components without launching the entire application.

4. CI/CD Integration

Playwright integrates seamlessly with CI/CD tools such as:

• Jenkins

• GitHub Actions

• GitLab

• Azure DevOps

This makes it easy to automate tests in build pipelines.

Playwright vs Selenium

One of the most common questions is how Playwright compares with Selenium.

Here’s a clear comparison:

Feature	Playwright	Selenium
Modern Web Support	Excellent	Limited
Speed	Faster	Slower
Auto-Wait	Built-in	Mostly manual
Browser Support	Chromium, Firefox, WebKit	All major browsers
API Testing	Built-in	Requires external tools
Built-in Test Runner	Yes	No
Parallel Execution	Native	Requires setup

While Selenium still supports more legacy browsers, Playwright is often preferred for modern web applications.

Real-World Use Cases of Playwright

Playwright is widely used for:

1. Cross-Browser UI Testing

Ensure consistent behavior across Chrome, Firefox, and Safari.

2. Visual Regression Testing

Detect UI changes automatically.

3. API Testing

Validate backend services.

4. CI/CD Automation

Run tests automatically after every deployment.

5. Mobile Testing

Validate responsive design.

6. Network Simulation

Test slow internet scenarios.

Why Playwright Is Ideal for Modern Applications

Modern applications use:

• AJAX calls

• Dynamic rendering

• Single Page Applications

• Shadow DOM

Playwright handles these efficiently because:

• It uses modern browser engines.

• It communicates directly via browser protocols.

• It eliminates WebDriver dependency.

• It supports real user interaction simulation.

This results in:

• Fewer flaky tests

• Faster execution

• Better debugging

Is Playwright Good for Beginners?

Yes.

Playwright has:

• Clean API design

• Clear documentation

• Good community support

• Simple installation process

Even beginners can start writing automation scripts within hours.

Installation Overview (Java Example)

To use Playwright with Java, add the Maven dependency:

<dependency>
  <groupId>com.microsoft.playwright</groupId>
  <artifactId>playwright</artifactId>
  <version>1.44.0</version>
</dependency>

Then install browsers:

mvn exec:java -e -D exec.mainClass=com.microsoft.playwright.CLI -D exec.args="install"

That’s it — no WebDriver setup required.

Advantages of Using Playwright

• Modern architecture

• Reliable execution

• Automatic waiting

• Fast parallel runs

• Built-in debugging tools

• Screenshots and videos

• API testing support

• Easy CI/CD integration

Limitations of Playwright

While powerful, Playwright has some considerations:

• Smaller community compared to Selenium (though growing fast)

• Does not support legacy browsers like Internet Explorer

• Slight learning curve for advanced features

However, for modern applications, it is often the better choice.

Future of Playwright

With backing from Microsoft and rapid adoption by tech companies worldwide, Playwright continues to evolve quickly.

Frequent updates introduce:

• Performance improvements

• New browser capabilities

• Better debugging tools

• Enhanced reporting

Playwright is widely considered the future of browser automation.

Official Website

For complete documentation and examples, visit:

https://playwright.dev/java/

Conclusion

Playwright is a modern, powerful, and reliable end-to-end automation framework designed for today’s dynamic web applications.

With features like:

• Cross-browser support

• Built-in auto-wait

• API testing

• Mobile emulation

• CI/CD integration

• Browser contexts

Playwright simplifies automation while improving reliability and speed.

Whether you are a beginner starting automation or an experienced QA engineer looking to modernize your framework, Playwright is a strong choice for scalable and future-ready test automation.

Suggested Posts:

1. Handle Alerts in Playwright
2. Automate POST API in Playwright
3. Automate PUT API in Playwright
4. Test Token Based Authentication in Playwright
5. Basic Authentication in Playwright

How to Test Cookie based Authentication in API by Playwright

Cookie-Based Authentication in Playwright Java – Complete Guide with Example

Authentication is one of the most important aspects of web application testing. Almost every modern web application requires users to log in before accessing protected features. In real-world automation projects, handling authentication properly is critical for building stable, scalable, and efficient test suites.

In this comprehensive guide, you will learn:

• What cookies are

• What cookie-based authentication is

• How cookie authentication works internally

• Why it is important in automation

• How to handle cookie-based authentication in Playwright Java

• A complete working Java example using Playwright

• Best practices for managing cookies in automation

This guide is fully beginner-friendly, SEO optimized, and written in a human-like, easy-to-understand format.

What Are Cookies?

Cookies are small pieces of data stored by a web browser on the client side. They are typically sent by the server through HTTP response headers and then stored by the browser. On subsequent requests to the same domain, the browser automatically attaches these cookies back to the server.

In simple words, cookies help websites “remember” users.

Why Are Cookies Used?

Cookies serve multiple purposes in modern web applications:

• Session Management

  • Login sessions

  • User preferences

  • Shopping carts

• Personalization

  • Themes

  • Language settings

  • Recommendations

• Tracking and Analytics

  • User behavior tracking

  • Advertising

  • Performance monitoring

Without cookies, users would have to log in again every time they navigate to a new page.

What Is Cookie-Based Authentication?

Cookie-based authentication is a mechanism where the server authenticates a user and creates a session. Instead of sending credentials repeatedly, the server generates a unique session ID and stores it on the server side. This session ID is then sent to the client as a cookie.

The browser automatically sends this cookie with every subsequent request, allowing the server to recognize the authenticated user.

How Cookie-Based Authentication Works

Let’s break it down step by step:

1. User provides login credentials
   The user enters username and password.

2. Server verifies credentials
   If credentials are correct, the server creates a session.

3. Server generates a session ID
   This session ID is stored in server memory or database.

4. Server sends Set-Cookie header
   The session ID is sent back to the browser.

5. Browser stores the cookie
   The browser saves it automatically.

6. Browser sends cookie in future requests
   The server checks the session ID and allows access.

This method is widely used in traditional web applications.

Why Cookie-Based Authentication Is Important in Automation

In automation testing, logging in repeatedly for every test case is inefficient and unstable. UI login flows can slow down your test suite and introduce unnecessary failures.

Handling cookies correctly provides:

1. Efficiency

You can log in once and reuse the authenticated session.

2. Stability

Avoid flaky login UI interactions.

3. Scalability

Multiple tests can reuse the same authenticated state.

4. Faster Execution

Skipping login reduces overall test runtime significantly.

This is especially useful in enterprise applications where login includes CAPTCHA, MFA, or complex flows.

Handling Cookie-Based Authentication in Playwright (Java)

Playwright provides powerful capabilities to handle authentication. In Java, cookie-based authentication can be handled in two primary ways.

Method 1: Manual Login Once and Reuse Cookies

This is the most commonly used approach in automation frameworks.

Steps:

1. Automate login using UI.

2. Extract cookies from the browser context.

3. Save cookies into a JSON file.

4. Reuse cookies in future test sessions.

This approach is ideal for regression test suites.

Method 2: Programmatic Cookie Injection

If you already have valid cookies, you can:

• Directly inject cookies into the browser context.

• Skip the login page entirely.

• Navigate directly to protected resources.

This method is faster and preferred in CI/CD environments.

Practical Example: Cookie-Based Authentication Using Playwright Java

For demonstration, we will use:

SauceDemo

Website URL:
https://www.saucedemo.com/

It is a simple demo e-commerce site that sets authentication cookies after login.

Test Credentials:

• Username: standard_user

• Password: secret_sauce

Maven Dependency for Playwright

Add this dependency to your pom.xml:

<dependency>
  <groupId>com.microsoft.playwright</groupId>
  <artifactId>playwright</artifactId>
  <version>1.44.0</version>
</dependency>

Complete Java Code: Cookie-Based Authentication in Playwright

import com.microsoft.playwright.*;
import java.nio.file.Paths;
import java.util.List;

public class CookieAuthTest {
    public static void main(String[] args) {
        String storageStatePath = "auth.json";

        try (Playwright playwright = Playwright.create()) {

            Browser browser = playwright.chromium()
                    .launch(new BrowserType.LaunchOptions().setHeadless(false));

            BrowserContext context = browser.newContext();
            Page page = context.newPage();

            // Step 1: Navigate to login page
            page.navigate("https://www.saucedemo.com/");

            // Step 2: Perform login
            page.locator("[name='user-name']").fill("standard_user");
            page.locator("[name='password']").fill("secret_sauce");
            page.locator("[name='login-button']").click();

            // Step 3: Wait for successful login
            page.waitForURL("**/inventory.html");

            // Step 4: Save storage state (cookies + localStorage)
            context.storageState(
                new BrowserContext.StorageStateOptions()
                    .setPath(Paths.get(storageStatePath))
            );

            // Step 5: Extract cookies
            List<BrowserContext.Cookie> cookies = context.cookies();
            System.out.println("Extracted Cookies:");
            for (BrowserContext.Cookie cookie : cookies) {
                System.out.println(cookie.name + " = " + cookie.value);
            }

            // Step 6: Create new context with saved cookies
            BrowserContext authContext = browser.newContext(
                new Browser.NewContextOptions()
                    .setStorageStatePath(Paths.get(storageStatePath))
            );

            Page authPage = authContext.newPage();
            authPage.navigate("https://www.saucedemo.com/inventory.html");

            // Step 7: Validate access to protected page
            if (authPage.locator(".header_label").isVisible()) {
                System.out.println("Authentication successful using cookie!");
            } else {
                System.out.println("Authentication failed.");
            }

            browser.close();
        }
    }
}

Step-by-Step Code Explanation

(a) Create Playwright Instance

Playwright playwright = Playwright.create();

Initializes Playwright engine.

(b) Launch Browser

browser = playwright.chromium().launch(...)

Launches Chromium browser.

(c) Create Browser Context

A BrowserContext acts as an isolated browser session.

(d) Perform Login

Using:

page.locator().fill()

Simulates real user interaction.

(e) Wait for Navigation

page.waitForURL("**/inventory.html");

Confirms successful login.

(f) Save Storage State

context.storageState()

Stores:

• Cookies

• LocalStorage

• SessionStorage

(g) Create New Authenticated Context

setStorageStatePath(Paths.get(storageStatePath))

Reuses saved session.

(h) Validate Authentication

Checks if protected element is visible.

Why Use storageState Instead of Only Cookies?

Playwright allows saving:

• Cookies

• LocalStorage

• SessionStorage

Modern applications often store tokens in localStorage instead of cookies. Saving the entire storage state ensures complete authentication.

Best Practices for Cookie-Based Authentication in Playwright

1. Save Authentication State Once

Generate auth file in a setup test.

2. Reuse Auth State in All Tests

Load storage state for test execution.

3. Avoid Hardcoding Credentials

Use environment variables.

4. Handle Expired Sessions

Regenerate auth file if session expires.

5. Use Headless Mode in CI/CD

Set:

.setHeadless(true)

Common Issues and Solutions

Issue: Session Expires Frequently

Solution:

• Regenerate authentication before suite execution.

Issue: Cookies Not Working in New Context

Solution:

• Ensure correct domain.

• Confirm secure/HTTP-only flags.

Issue: Login Redirect Loop

Solution:

• Verify storage state is correctly loaded.

Cookie-Based Authentication vs Token-Based Authentication

Both methods are widely used in web applications.

Advantages of Using Cookie Authentication in Playwright

• Simple implementation

• Realistic browser simulation

• Reduced login flakiness

• Faster test execution

• Easy session reuse

For enterprise automation frameworks, cookie reuse is a must-have optimization strategy.

When Should You Use Cookie-Based Authentication?

Use it when:

• Testing web UI applications

• Running regression suites

• Working with session-based apps

• You want faster automation runs

• Login flow is complex or unstable

Conclusion

Cookie-based authentication is one of the most common and reliable authentication mechanisms used in web applications. Understanding how cookies work and how to handle them in automation is essential for building robust Playwright Java test frameworks.

With Playwright, managing authentication becomes straightforward using:

• BrowserContext

• Cookies extraction

• storageState reuse

• Programmatic injection

By implementing cookie-based authentication properly, you can:

• Improve test stability

• Speed up execution

• Reduce flaky login failures

• Scale automation efficiently

If you are building a professional test automation framework in Java, mastering cookie handling in Playwright is a critical skill.

Suggested Posts:

1. Automate GET API in Playwright
2. Automate POST API in Playwright
3. Automate PUT API in Playwright
4. Test Token Based Authentication in Playwright
5. Basic Authentication in Playwright