Course Category: Software Testing
Course Duration: 4 Days
Hours: 28 Contact Hours

Select your country

Select your country to access the registration page


Register Now

Duration: 4 Day
Timing: 9 AM to 5 PM Malaysia Time


Register Now

Duration: 4 Day
Timing: 9 AM to 5 PM Philippine Time


Register Now

Duration: 4 Day
Timing: 9 AM to 5 PM Singapore Time


Register Now

Duration: 4 Day
Timing: 11 AM to 7 PM AEST

All Other Locations

Register Now

Duration: 4 Day
Timing: 9 AM to 5 PM Philippines/Singapore/Hong Kong Time

Course Overview

Playwright is a widely used browser automation toolset developed by Microsoft. Playwright provides the ability to automate browser tasks in Chromium, Firefox and WebKit with a single API.

This four-day hands-on workshop shall coach the participants to automate end-to-end web testing using Playwright. The course shall explain key concepts and move to functionalities with the emphasis on usage of the tool for test automation for web applications.

The course covers testing of static and dynamic website with html, http, ajax and more.

Playwright api shall be covered in detail including tools like Codegen, Inspector, Trace viewer, Third party tools, and introduction to distributed testing. Several demos are included in addition to hands-on learning.


Participants must be software developers or software testers who aspire to use Playwright.


Participant must be able to code (beginner level) in core Java or C#/Python/Javascript/Typescript/any other OO language with corresponding standard library.


• Software Requirements
Visual Studio Code
Node with npm and yarn
Modern browser(s) like Chrome, Edge, Firefox

• Hardware Requirements
Laptop capable to run MS Office

• Internet Requirements
Good unrestricted internet connection is required.


  • Web and HTTP
  • Browsers and Servers
  • HTML, CSS and JavaScript
  • Browser Developer Tools
  • Cookies, Cache, Headers
  • DOM Tree and Web flow
  • Ajax Vs Non-ajax
  • Brush up on language
    • Key Classes and/or Methods for language
    • Asynchronous code
  • Debugging
  • Manual Testing
  • Coded Tests and Benefits
  • Usage of Unit Testing Framework
  • AAAC structure
  • Annotations
  • Assertions
  • Command Line


  • Architecture
  • Tool set and extensions
  • Configuration
  • Emulation
  • Fixtures
  • API by Examples
  • First project and anatomy
  • First test
  • Running test
    • Headless and with UI
    • Specific or all browser(s)
    • Specific or all test(s)
    • Parallel
  • Locating Elements
    • Role, label, placeholder, text, alt text, title, various id
    • CSS, XPath, React, Vue
    • Filtering
    • Operators
    • Handling lists
  • Verifying page elements
  • Getting state of DOM
    • Text, attributes, subtree
  • Manipulating Elements
  • Handling mouse, keyboard


  • Debugging
    • Tracing
    • Using dev tools
    • Using debugger
    • Using inspector
  • Reporting
  • Matching Text using RegEx
  • Waiting
  • Forms and Tables
  • File upload and download
  • Handing alerts
  • Windows, Frames, Dialogs
  • Browser Window
  • Viewports
  • Hooks
  • Events
  • Parameterization
  • Data Driven Tests
    • Hard-coded
    • Csv
    • Other
  • Keyword (Table) Driven Tests
  • Guidelines for Skeleton framework
  • Page Objects
  • Test Cases Guidelines
  • Custom assertions
  • Record and playback
  • More configuration
  • Geolocation
  • Localization
  • Retries
  • Sharding
  • Timeout
  • Handling server
  • Authentication
  • Handling Cookies
  • Session and local storage
  • Injecting javascript
  • Taking screenshots
  • Taking partial screenshots
  • Isolation
  • Mocking
  • Visual testing
  • Accessibility testing
  • Continuous integration
  • Api testing
  • Best practices
  • Extending Playwright
  • Intro to Cucumber and Gherkin