Frontory

Playwright

Frontory technology map

Testing · 4 stages · 28 units in the full series · 28 published in English

Series goal

Verify user flows in a separate Node test environment and design data isolation, asynchronous waiting, and diagnostic evidence.

Prerequisites

DOM roles and asynchronous behavior, testing basics

Practice approach and scope

Learning units are not calendar days. Read the explanation and tasks, check the completion criteria, then move on. Use each example as a starting point: change variables and observe the results. Built-in examples and tasks requiring a separate environment are identified separately. Opening an example does not complete a unit.

Existing unit IDs and notes are preserved. The original 01, 02, and 03 examples occupy positions 1, 14, and 28 in the expanded sequence, so the number in the address may differ from the learning order.

Only published English units are linked below. The full series has 28 units.

Learning path

Stage 1 · User Flows and Locators

Stage 2 · Persistent Data and File Round Trips

Stage 3 · Asynchrony, Isolation, and Diagnosis

Stage 4 · Visual Regression and Execution Strategy

Capstone project and deliverables

Build a test suite that verifies Frontory navigation, documents, note backup and restoration, preservation on errors, and visual regression on an independent origin.

Keep the implementation, run instructions, baseline and changed conditions, failure cases, and recovery steps together. Do not report unmeasured performance or tests you have not run as results.

Official references