playwright-automation

Import test and expect from @playwright/test, then define a test that uses the page object to navigate and assert. For example, call page.goto('/') and use expect(page.getByRole('heading')).toBeVisible() to verify page content.

Use Playwright to navigate to the login page, fill credential fields with page.fill or locator-based actions, submit the form, and assert the post-login state. You can also reuse authenticated storage state across tests to skip repeated logins.

Yes, Playwright supports Chromium, Firefox, and WebKit (the Safari engine) with a single API. You configure target browsers in the Playwright config and run the same test suite across all of them.

Yes, Playwright can capture full-page or element screenshots during test runs. These screenshots can be compared against baseline images to detect unintended visual changes across releases.

Playwright is designed for browser-based end-to-end testing, so it is not suited for unit testing isolated functions or load testing at scale. For those cases, use a unit test runner or a dedicated load testing tool instead.