Two fixtures, same file, opposite lifetimes. One built once per worker, one rebuilt every test. Here's why, and what happens if you swap them.

One shared login collided with itself the moment I added a second worker. Here's the architecture that fixed it, three classes, each with exactly one job.

Everything runs on Phase 2's framework, but you'll need your own qa-cart.com login and a few environment variables — here's exactly how to get it running before we start breaking it.

Scaling a Playwright Framework From One Worker to Enterprise Ready If you've followed my Playwright course through Phase 1 and Phase 2, you already have a working test automation framework - Page Object Model, custom fixtures, API testing, CI/CD, AI-assisted review, the whole build, tested against qa-cart.com, my test demo store. It runs cleanly. It passes. It looks done. Then I tried to scale it. I pointed the framework at four concurrent workers, sharded it across CI jobs,

Playwright is a modern end-to-end test automation framework designed for reliable, cross-browser testing using a single unified API. It supports Chromium, Firefox, and WebKit, and comes with a powerful built-in test runner, automatic waiting mechanisms, parallel execution, and rich HTML reporting. In this Playwright tutorial for beginners, we will go beyond basic installation and understand how Playwright fits into a modern TypeScript-based automation workflow. This guide wal

Let's say we are building automation tests for our Demo Store . During testing, we often repeat the same steps again and again: • search for products • login user • calculate total price • validate order success message • format product text • verify product category • process API responses If we write the same code repeatedly, our script becomes: • repetitive • harder to maintain • difficult to scale • error-prone For example, if the login logic changes, we would need to upd

In the previous post , we covered the core basics of TypeScript , including variables, data types, arrays, objects, operators, and conditional statements. These concepts form the foundation of TypeScript and are essential before writing any real-world code. In this post, we continue building on that foundation by focusing on two very important topics: loops and string methods . Loops help us repeat actions efficiently, while string methods allow us to work with and manipulat

In the previous part-1 post , we set up the complete TypeScript development environment required for learning modern automation tools like Playwright . This included installing Node.js , configuring Visual Studio Code , and creating a clean TypeScript project structure with src, dist, and a minimal tsconfig.json. At this stage, we focused only on preparing a solid TypeScript learning setup , without installing Playwright itself. With the environment now ready, the next im

TypeScript Environment with Node.js and VSCode Before starting with Playwright test automation, it is important to understand the language and development environment on which Playwright is built. Playwright tests are written using JavaScript or TypeScript , and both run on top of Node.js . In this guide, we will not install Playwright yet . The focus here is on setting up a clean TypeScript development environment from scratch and understanding how TypeScript works behind