Playwright End-to-End Test Automation is a course in writing automated web tests from scratch, covering assertions, locators, proper waiting, forms and logins, page objects, fixtures, API testing, Trace Viewer and running tests in CI/CD. It suits web developers, QA staff and testers starting test automation, and small teams that want a test suite they can trust.
Testing a web application by hand before every release burns an enormous amount of team time, and the bigger the system gets the less of it actually gets covered. The bugs users hit are usually in the paths nobody re-clicked. Playwright is Microsoft open-source automation tool that drives Chromium, Firefox and WebKit from a single codebase, with built-in auto-waiting that removes most of the mysterious flaky failures older tools were known for. This course takes
learners from zero to a working automated test suite: installation and project structure, writing tests and assertions, choosing locators that survive UI changes, handling forms and file uploads, reusing a saved login state, organizing code with the page object pattern, testing APIs alongside the UI, capturing screenshots, video and traces on failure, and finally running the whole suite automatically in CI/CD on every code change. (2 days, 6 hours per day, 12 hours in total, Beginner to Intermediate level.)
Course Details
A 2-day course, 6 hours per day (12 hours in total), delivered as lectures with hands-on labs in every section. Beginner to Intermediate level. We provide a practice web application with forms, login, file upload and data tables so learners can cover every situation. Learners take home a lab guide, complete sample test code for every lab, and a working CI configuration. Playwright is open source and can be used in the organization at no licensing cost.
Section 1: Test Automation Concepts
Section 2: Installation and Project Structure
Section 3: Writing Tests and Assertions
Section 4: Locators and Selecting Elements
Section 5: Waiting and Flaky Tests
Section 6: Forms, Files and Login
Section 7: Page Objects and Code Organization
Section 8: Testing APIs Alongside the UI
Section 9: Reporting and Debugging
Section 10: Running in CI/CD
Section 11: Capstone and Real-World Use
Locate elements by what users see, such as getByRole with the button name, getByLabel for form fields or getByText, rather than CSS selectors or XPath tied to an HTML structure that changes often. If an element cannot be found by text or role, add a data-testid attribute and use getByTestId, and use filter when picking from repeated items in a list.
The usual cause is timing, such as checking a result before data has loaded, or several tests sharing the same data. Playwright auto-waits for elements to be ready before clicking or typing, and web-first assertions such as toBeVisible retry until they pass or time out, so avoid fixed delays with waitForTimeout. Give each test its own data, and use Trace Viewer to see exactly which step failed.
Create a setup project that logs in once and saves cookies and local storage to a file with storageState. Then, in playwright.config, make the other test projects depend on setup and use that storageState file by default. Every test starts already logged in and the suite runs much faster. Keep the state file out of Git, as it contains login data. This course practises it in the forms and login section.
It suits web developers who want to cut repetitive testing before each release, QA staff and testers starting test automation, teams struggling with tests that fail for no clear reason, and small teams without a full-time tester. You should understand how the web and HTML work, write reasonable JavaScript or TypeScript, as class examples use TypeScript, and install tools from the command line.
You will be able to install Playwright and write tests with assertions that run in every browser, choose locators that survive UI changes, fix flaky tests, test forms, file uploads and logins, organise code with page objects and fixtures, combine API and UI testing, investigate failures with Trace Viewer and run the suite automatically in CI/CD. Participants who complete the training receive a Certificate of Completion with its own number, which can be verified online.
Yes. It can be run in-house for your team, with examples adapted to your own work, such as building tests for the key user journeys of the web application your team looks after. You can request a quotation from this page, or contact us on LINE @itgenius or by phone on 02-570-8449.
Building and changing infrastructure by hand through a web console creates inconsistency, leaves no audit trail and makes it hard to reproduce an environment. Terraform solves this by expressing infrastructure as code that lives in Git, is reviewed through…
When a system fails or slows down, the first question is how you find out and how fast. Many organizations still learn about problems from customer calls rather than from their own monitoring. Prometheus and Grafana are the open-source standard that DevOps…
