How to Automate a Login Page by Playwright Java


When automating a login page with Playwright in Java, the process involves simulating the exact steps a real user would perform when logging into a web application. Here’s the conceptual flow:

1. Test Preparation

  • Launch Browser: Use Playwright to start a browser instance (Chrome, Firefox, WebKit).
  • Create Context and Page: A browser context is like a fresh user session, and a page represents a single browser tab. These are required to isolate the login test.

2. Navigating to the Login Page
  • Direct the browser to the application’s login URL.
  • Ensure the page is fully loaded before proceeding (Playwright automatically waits for the page to be ready, but explicit waits can be used for synchronization).
3. Interacting with Input Fields
  • Locate Username Field: Identify the username/email input box using a selector (ID, name, placeholder, or CSS).
  • Locate Password Field: Similarly, find the password input field.
  • Enter Credentials: Simulate typing the username and password into their respective fields.
4. Clicking the Login Button
  • Identify the login/submit button on the page.
  • Simulate a user click on the button. Playwright ensures the element is ready for interaction before performing the click.
5. Handling Synchronization
  • After clicking login, the application might redirect to another page (like a dashboard).
  • Playwright automatically waits for navigation, but you may also wait for a specific element on the home/dashboard page to confirm successful login.
6. Validation of Login
  • Positive Scenario: Verify that a unique element on the home page (e.g., a profile icon, welcome message, or logout button) is visible, confirming login success.
  • Negative Scenario: Check for error messages (example: “Invalid username or password”) when wrong credentials are entered.
7. Security & Session Handling
  • Playwright allows capturing and storing cookies or session tokens. This can be reused in future tests to avoid repeated logins.
  • Browser Context ensures each test runs in isolation, preventing session overlap.
8. Tear Down
  • After test execution, close the page, context, and browser to free up resources.
  • This ensures test environments remain clean and consistent.



















Website to be automated: 

https://opensource-demo.orangehrmlive.com/web/index.php/auth/login








Add maven dependency in pom.xml:

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

Java Code to Automate Login


import com.microsoft.playwright.*;

public class OrangeHRMLoginTest {
    public static void main(String[] args) {
        // Step 1: Launch Playwright
        try (Playwright playwright = Playwright.create()) {

            // Step 2: Launch a browser (Chromium)
            Browser browser = playwright.chromium().launch(new BrowserType.LaunchOptions().setHeadless(false));

            // Step 3: Create a new browser context
            BrowserContext context = browser.newContext();

            // Step 4: Open a new page
            Page page = context.newPage();

            // Step 5: Navigate to the login page
            page.navigate("https://opensource-demo.orangehrmlive.com/web/index.php/auth/login");

            // Step 6: Wait for username input field to be visible
            page.waitForSelector("input[name='username']");

            // Step 7: Fill in the login credentials
            page.fill("input[name='username']", "Admin");
            page.fill("input[name='password']", "admin123");

            // Step 8: Click the login button
            page.click("button[type='submit']");

            // Step 9: Print login success message
            System.out.println("Login successful!");

            // Optional: Close browser after verification
            browser.close();
        }
    }
}

Code explanation:

Line/BlockExplanation
Playwright.create()Starts Playwright engine
chromium().launch(...)Launches Chromium browser (can be firefox() or webkit() too)
browser.newContext()Creates a new isolated browser context (like incognito)
context.newPage()Opens a new browser tab/page
page.navigate(url)Opens the specified URL
page.fill(selector, value)Enters value into input field (selector is a CSS locator)
page.click(selector)Clicks the element (e.g., login button)
browser.close()Closes the browser at the end

Required Credentials

For this demo:

  • Username: Admin
  • Password: admin123


Points to Consider:
  • This script assumes that the page loads fast enough, but for real-world tests, you should use explicit waits where needed.
  • You can run this from a main method or integrate it into a test framework like JUnit/TestNG for proper test cases.

Integration of Playwright, Cucumber, and TestNG

 

Integrating CucumberPlaywright, and TestNG in Java enables you to write BDD (Behavior Driven Development) style tests using Gherkin (.feature files), automate browser interactions using Playwright, and manage execution using TestNG.


Role of Each Component

Playwright:

A powerful automation framework that interacts with modern browsers (Chromium, Firefox, WebKit). It is mainly responsible for performing browser-based actions like navigating pages, clicking elements, validating results, handling alerts, and more. It provides the engine for execution of test steps.

Cucumber:

A BDD (Behavior-Driven Development) framework that allows writing test scenarios in Gherkin language (Given-When-Then format). Its purpose is to make test cases readable and understandable for both technical and non-technical stakeholders. It provides the structure for test scenarios and bridges the gap between business requirements and automated test scripts.

TestNG:

A test management and execution framework in Java. It provides advanced features like test configuration, grouping, parallel execution, annotations, data-driven testing, and detailed reporting. It manages how and when tests are executed, integrates with build tools (Maven/Gradle), and generates structured results.


How Integration Works

Step 1: Cucumber defines test scenarios

Business or QA teams write scenarios in Gherkin. Example:

  • Given user launches the browser
  • When user logs in with valid credentials
  • Then homepage should be displayed

Step 2: Step Definitions in Java call Playwright

Each step in the feature file is mapped to a step definition (Java method). Inside these step definitions, Playwright APIs are used to perform browser actions like opening a page, entering data, or verifying results.

Step 3: TestNG executes scenarios

TestNG acts as the test runner. It executes Cucumber feature files (via Cucumber runner classes) and manages the lifecycle of the tests. TestNG annotations help configure test execution order, parallel runs, retries, or grouping of test suites.

Step 4: Unified Reporting and Logs

TestNG generates test execution reports (HTML/XML), while Cucumber generates BDD reports. These can also be integrated into advanced reporting dashboards like Allure or Extent Reports. This way, both the technical (developer/QA) and business teams can consume the results in formats they understand.


Benefits of Integration

Readable Scenarios: Cucumber ensures tests are described in plain English, improving collaboration.

Powerful Browser Automation: Playwright provides modern, fast, and cross-browser execution.

Robust Test Management: TestNG handles execution strategies (parallelism, suites, groups).

Scalability: The combination is suited for enterprise-level projects where test readability, execution speed, and configurability are crucial.

Flexible Reporting: Both business-friendly BDD reports and developer-focused TestNG reports are available.



Tools Used:

  • Cucumber for BDD feature files and step definitions

  • Playwright for Java for browser automation

  • TestNG for test execution and reporting

  • Maven for dependency management


Website to be automated: https://example.com













Below are the steps showing integration of Cucumber, Playwright and TestNG



pom.xml:

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>com.example</groupId>
  <artifactId>cucumber-playwright-testng</artifactId>
  <version>1.0</version>

  <dependencies>
    <!-- Cucumber Dependencies -->
    <dependency>
      <groupId>io.cucumber</groupId>
      <artifactId>cucumber-java</artifactId>
      <version>7.14.0</version>
    </dependency>
    <dependency>
      <groupId>io.cucumber</groupId>
      <artifactId>cucumber-testng</artifactId>
      <version>7.14.0</version>
    </dependency>

    <!-- TestNG -->
    <dependency>
      <groupId>org.testng</groupId>
      <artifactId>testng</artifactId>
      <version>7.9.0</version>
      <scope>test</scope>
    </dependency>

    <!-- Playwright Java -->
    <dependency>
      <groupId>com.microsoft.playwright</groupId>
      <artifactId>playwright</artifactId>
      <version>1.44.0</version>
    </dependency>
  </dependencies>

  <build>
    <plugins>
      <!-- Surefire for TestNG -->
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>3.2.5</version>
        <configuration>
          <suiteXmlFiles>
            <suiteXmlFile>testng.xml</suiteXmlFile>
          </suiteXmlFiles>
        </configuration>
      </plugin>
    </plugins>
  </build>
</project>

Title.feature (Gherkin feature file)

Below is the feature file having feature as 'Check title' and Scenario as 'Open login page and check title'. Steps in feature file are implemented by gherkins keywords and expected title of page is 'Example Domain'

Feature: Check title

  Scenario: Open login page and check title
    Given I launch the application
    Then I should see the page title as "Example Domain"


PlaywrightFactory.java

PlaywrightFactory is a utility class which consists of Playwright, Browser and Page objects, it also contain init() to initialize browser and close() to close browser and Playwright object.


package utils;

import com.microsoft.playwright.*;

public class PlaywrightFactory {
    public static Playwright playwright;
    public static Browser browser;
    public static Page page;

    public static void init() {
        playwright = Playwright.create();
        browser = playwright.chromium().launch(new BrowserType.LaunchOptions().setHeadless(false));
        page = browser.newPage();
    }

    public static void close() {
        browser.close();
        playwright.close();
    }
}


LoginSteps.java

LoginSteps is a step definition class, which is implimentation of Title.feature file. In this, all feature file steps are implemented by annotations like @Given, @Then, etc. which are gherkin keywords of respective steps in feature file. @Before and @After is used for initialization and tear down work respectively.


package steps;

import com.microsoft.playwright.Page;
import io.cucumber.java.After;
import io.cucumber.java.Before;
import io.cucumber.java.en.*;
import utils.PlaywrightFactory;

import static org.testng.Assert.assertEquals;

public class LoginSteps {
    Page page;

    @Before
    public void setup() {
        PlaywrightFactory.init();
        page = PlaywrightFactory.page;
    }

    @Given("I launch the application")
    public void i_launch_the_application() {
        page.navigate("https://example.com");
    }

    @Then("I should see the page title as {string}")
    public void i_should_see_the_page_title_as(String expectedTitle) {
        String actualTitle = page.title();
        assertEquals(actualTitle, expectedTitle);
    }

    @After
    public void tearDown() {
        PlaywrightFactory.close();
    }
}


TestRunner.java (Cucumber TestNG runner)

TestRunner class is used to execute tests written in feature files and implemented in step definition files. Here path of feature file is given by 'features' keyword and path of step definition by 'glue' keyword. All these things are implemented under @CucumberOptions annotation. This TestRunner class is implemented by Cucumber and TestNG.


package runners;

import io.cucumber.testng.AbstractTestNGCucumberTests;
import io.cucumber.testng.CucumberOptions;
import org.testng.annotations.DataProvider;

@CucumberOptions(
    features = "src/test/resources/features",
    glue = "steps",
    plugin = {"pretty", "html:target/cucumber-reports.html"},
    monochrome = true
)
public class TestRunner extends AbstractTestNGCucumberTests {
    @Override
    @DataProvider(parallel = true)
    public Object[][] scenarios() {
        return super.scenarios();
    }
}


testng.xml

TestNG.xml is optional file which contains TestRunner class path represented in class tag. We can execute TestRunner class by TestNG.xml also.

<!DOCTYPE suite SYSTEM "https://testng.org/testng-1.0.dtd">
<suite name="Cucumber Playwright TestNG Suite">
  <test name="Cucumber Tests">
    <classes>
      <class name="runners.TestRunner"/>
    </classes>
  </test>
</suite>


Suggested Posts:

1. Playwright with TestNG Integration
2. Automate Login Page in Playwright
3. Comma Selectors in Playwright
4. Handle Alerts in Playwright
5. How to Show Visible Elements in Playwright