Absolute Path

QA engineer with Playwright

Test web apps with code, and find bugs before your users do.

A QA engineer finds problems in software before people use it. In this path you learn to write programs that test a web app for you. They click, type, and check the result, as often as you want. You start with how pages are built, then learn JavaScript, test design, and Playwright.

  • Building now
  • 4 of 8 courses ready
  • About 26 hours in total
  • Free

Not started

Start the path

Your path, step by step

Some courses are ready. The others are being written now. A step with no link is a course that is planned. Its time is an estimate.

  1. HTML and CSS

    Up next

    Build web pages and make them look good.

    • Beginner
    • 10 lessons
    • 1 h 39 min

    Not started

    Why this step: Playwright finds things on a page by their role, label, and text. You must know how a page is built.

  2. JavaScript

    Not started

    Give web pages and programs a brain.

    • Beginner
    • 11 lessons
    • 1 h 59 min

    Not started

    Why this step: Playwright tests are programs. You need variables, functions, arrays, and objects.

  3. TypeScript basics

    Coming soon

    Add types to JavaScript, so that the editor finds mistakes before your code runs.

    • About 4 h

    Why this step: Most Playwright projects use TypeScript. Types help the editor find mistakes in your test code.

  4. Testing basics

    Coming soon

    Design test cases, check results, and write a bug report that other people can follow.

    • About 3 h

    Why this step: A good test starts with a good test case. This course teaches you how to find the cases that matter.

  5. Playwright

    Not started

    Write browser tests that click, type, and check the page.

    • Beginner
    • 17 lessons
    • 6 h 8 min

    Not started

    Why this step: This is the main tool of the path. You write tests that open a page, act on it, and check the result.

  6. API testing

    Coming soon

    Send requests to a service, and check the status code, the data, and the errors.

    • About 4 h

    Why this step: Many bugs are easier to find below the screen. You test the service that the page talks to.

  7. SQL

    Not started

    Ask questions of a database and get answers.

    • Beginner
    • 10 lessons
    • 1 h 59 min

    Not started

    Why this step: Testers use SQL to check that the screen and the database show the same data.

  8. CI pipelines

    Coming soon

    Run checks and tests on every code change with GitHub Actions, and read the results.

    • About 3 h

    Why this step: A test that nobody runs finds no bugs. You run your tests on every code change.