Course

SDET — Playwright, JS & TS with AI

Event-loop races, closures & memory leaks, generics & discriminated unions, ARIA snapshots, the Clock API, shadow DOM, multi-origin flows, sharding, component testing, and Playwright's official MCP server — verified against Playwright v1.62 and TypeScript 6.0/7.0 RC documentation. Weekday (1 hr/day) or Weekend (2 hrs/day) tracks, same enriched curriculum either way.

⏱ 11 Weeks 🖥 Online 💻 1 projects ★ 4.9
🎓 Book Free Demo 📞 +91 75502 51906
INCLUDED AT NO COST

Everything below is included at no extra cost

🚀 FREE!
Live Project(s)
💼 FREE!
Job Reference(s)
🎓 FREE!
Career Guidance
♾️ FREE!
Life Time Support
PACKAGES

We Offer Responsive Packages With An Unexplored Syllabus

ACCELERATOR
⏱ 9 Weeks
★ 4.8/5

Package 1 — Automation + AI Accelerator

Skip manual testing, go straight to automation + AI.
  • JS, TS & Playwright core
  • Visual/Mobile + CI/CD
  • GenAI + Agentic AI/MCP
  • Capstone + Job Prep
PlaywrightTypeScriptGenAIMCP
View Curriculum →
FAST-TRACK
⏱ 6 Weeks
★ 4.7/5

Package 2 — Playwright Core Fast-Track

Core automation skills and a job-ready project, fastest.
  • JS & TS essentials
  • Playwright Core + API
  • Capstone + Job Prep
PlaywrightTypeScriptPostman
View Curriculum →
MOST POPULAR
⏱ 11 Weeks
★ 4.9/5

Package 3 — Complete Beginner to Automation Tester

True zero-to-hero — no coding background needed.
  • Manual Testing Foundations
  • JS, TS & Playwright
  • Capstone + Job Prep
Manual QAJIRAPlaywright
View Curriculum →
FLAGSHIP
⏱ 15 Weeks
★ 4.9/5

Package 4 — Complete Fourcup Flagship Program

Everything — manual, automation, and AI/Agentic testing.
  • Manual + JS/TS + Playwright
  • Visual/Mobile + CI/CD
  • GenAI + Agentic AI/MCP
  • Capstone + Job Prep
Full CurriculumMCPCI/CD
View Curriculum →
CUSTOM
⏱ Variable
★ 4.8/5

Package 5 — Build Your Own (Customized)

Pick exactly the modules you need from the same module bank.
  • Choose your own modules
  • Either track (Weekday or Weekend)
  • Priced and scheduled accordingly
View Curriculum →
LEARNING OUTCOMES

What you will be able to do

Concrete skills, not topic names — each one is something you can show an interviewer.

🎯

Design test cases that find real defects

Boundary values, equivalence classes and edge cases — not just happy-path coverage.

🧪

Automate with a real framework

Page Object Model, reusable helpers and a suite you can actually maintain.

📊

Read a defect report the way a developer will

Reproduction steps, severity and evidence — reports that get fixed, not ignored.

🔧

Build and maintain a test suite

Structure tests so they survive the product changing under them.

🔗

Test APIs, not just interfaces

Postman and REST Assured, including auth flows most courses skip.

📈

Run suites in a CI pipeline

Jenkins and GitHub Actions — tests that run on every commit automatically.

SUCCESS STORIES

Our Students Excelling Worldwide

“
Priya Krishnamurthy P
Priya Krishnamurthy
QA Automation Engineer
🏢 Zoho Corporation
★★★★★

“Fourcup completely changed my career trajectory. I was stuck in manual testing for 3 years with no idea how to get into automation. The Playwright and TypeScript modules were far deeper than I expected — event-loop races and flaky-test root-cause analysis actually came up in my Zoho interview. Landed the role within 3 months of finishing.”

🎓 SDET — Playwright, JS & TS with AI
“
Karthik Raj K
Karthik Raj
Senior SDET
🏢 Freshworks
★★★★★

“I had tried two other institutes before Fourcup. They taught Selenium and stopped there. Fourcup went into Playwright's Trace Viewer, the Clock API, and shadow DOM handling — genuinely production-level content. By week 4 I had a working framework with CI/CD wired up. That project got me through the Freshworks technical round directly.”

🎓 SDET — Playwright, JS & TS with AI
“
Nithya Subramaniam N
Nithya Subramaniam
Test Automation Lead
🏢 Cognizant
★★★★★

“The TypeScript module alone was worth the course — generics, discriminated unions, module augmentation for custom fixtures. Most QA courses barely touch TypeScript beyond basic types. Cognizant specifically asked about how I structured my Page Object base classes with generics. Got the offer in my first attempt.”

🎓 SDET — Playwright, JS & TS with AI
TOOLS & SKILLS

Tools and skills covered

Playwright
TypeScript
GenAI
MCP
Postman
Manual QA
JIRA
Full Curriculum
CI/CD
🏆

Certificate of Completion

Awarded once every module and project is complete — recognised by our hiring partners.

IS THIS FOR YOU?

Who this course is for

If none of these describe you, tell us — we will point you at a better fit rather than sell you this one.

🎓

Freshers from any engineering branch

🔁

Manual testers hitting the automation ceiling

💻

Support engineers moving into QA

WHY IN FOURCUP?

Software Testing Program

Practical exposure to actual work environment

Work on live, under-construction projects with the exposure of an actual work environment, alongside a freelancer.

Dynamic syllabus structure

Built with multiple industry experts, so students become genuinely fluent in the subject rather than exam-ready.

Expert teachers who are active practitioners too

Mentors bring real industry experience and share their ups, downs and delivery skills, not just slides.

GET STARTED

Get Started Today

01
Download our Syllabus and review it thoroughly.
02
Request Call Back / Apply the Enquiry Form.
03
Join Our Free Demo Class.
04
Understand the Opportunity.
05
Join the Training session and become an expert!
CURRICULUM

Module by module

Open any module to see exactly what it covers. Nothing is hidden behind a "download the syllabus" form.

11 Weeks
DURATION
0
MODULES
1
REAL-TIME PROJECTS
5
MOCK INTERVIEWS
ACCELERATOR

Package 1 — Automation + AI Accelerator

⏱ 9 Weeks ★ 4.8
10 modules
FAST-TRACK

Package 2 — Playwright Core Fast-Track

⏱ 6 Weeks ★ 4.7
6 modules
MOST POPULAR

Package 3 — Complete Beginner to Automation Tester

⏱ 11 Weeks ★ 4.9
7 modules
FLAGSHIP

Package 4 — Complete Fourcup Flagship Program

⏱ 15 Weeks ★ 4.9
11 modules
CUSTOM

Package 5 — Build Your Own (Customized)

⏱ Variable ★ 4.8
0 modules
1 JavaScript Fundamentals for Testers Weekday 1.5 wks · Weekend 2.5 wks ▾
TopicWhat You'll Learn
1. Node.js & VS Code Setup Your daily coding environment, installed and configured from scratch.
2. Variables, Data Types & Operators The building blocks JavaScript uses to store and manipulate data.
3. Conditionals & Loops Writing decision logic and repeating actions — the backbone of any test script.
4. Functions Packaging reusable logic for clean, non-repetitive test code.
5. Arrays & Objects Working with lists and structured data, e.g. a list of test users.
6. Asynchronous JS Deep-Dive: Event Loop & Race Conditions The real reason async tests flake, not "the tool is broken."
6.1) Microtasks vs macrotasks
  • Why await ordering surprises people, and how misunderstanding it explains supposedly "random" test-timing bugs.
  • Tracing a real event-loop timeline to predict execution order before running the code.
6.2) Promise.all / allSettled / race
  • Running parallel API calls in test setup without one silent failure hiding the rest.
  • Choosing allSettled over all when partial failure is acceptable in a test fixture.
6.3) Unhandled promise rejections
  • Catching the exact async failure that crashes a CI run with no useful error message.
  • Setting up global rejection handlers so a swallowed error doesn't silently mark a test 'passed'.
7. Closures & Memory in Long-Running Suites A classic source of bugs that only show up after 200+ tests, not in a 5-test demo.
7.1) Closures capturing stale data
  • The var-vs-let loop bug: why a for-loop over test cases can silently run the last case N times.
  • Fixing it correctly with block scoping and understanding why it worked "by accident" before.
7.2) Memory leaks in Node test processes
  • Event listeners and timers that never get removed, slowly degrading a long CI run.
  • Diagnosing a leak with Node's --inspect and Chrome DevTools memory snapshots.
8. Working with Dates & Time Zones (Test Data Edge Cases) One of the most common real-world sources of "works on my machine" test failures.
8.1) UTC vs local time pitfalls
  • Why a date assertion passes in India and fails in the US CI runner.
  • Normalizing all test data to UTC and converting only at the assertion boundary.
8.2) Daylight Saving Time edge cases Testing a booking or scheduling feature across a DST transition date on purpose.
9. Regular Expressions for Dynamic Locators & Data Validation Matching flexible, changing text without hardcoding brittle strings.
9.1) Building resilient patterns Matching partial/dynamic text (e.g. "Order #12345 confirmed") without over-fitting to one value.
9.2) Common regex pitfalls Catastrophic backtracking: a regex that works on 10 rows and hangs on 10,000.
10. JSON Basics Reading/writing the data format used everywhere in test data and API responses.
11. Git & GitHub Basics Version control fundamentals — commit, push, pull, branches.
2 TypeScript Essentials for Real-World Frameworks Weekday 0.5 wk · Weekend 1 wk ▾
TopicWhat You'll Learn
1. Why TypeScript for Testing Why most modern Playwright frameworks are written in TypeScript, not plain JS.
2. Project Setup (tsconfig.json) Configuring strict mode correctly from day one, not bolting it on later.
3. Type Annotations & Inference Catching mistakes before you even run the test.
4. Generics for Reusable Test Frameworks The single most valuable TS skill for building a framework that scales past 50 tests.
4.1) Generic Page Object base classes Writing one BasePage<T> class that every page object extends, instead of copy-pasting boilerplate.
4.2) Generic API response wrappers Typing ApiResponse<T> once and reusing it for every endpoint's response shape.
5. Utility Types for Test Data & Mocking Built-in TypeScript types that remove huge amounts of manual typewriting.
5.1) Partial, Pick & Omit
  • Building flexible test-data fixtures where only some fields are overridden per test.
  • Deriving a 'CreateUserDto' type from a full User type without duplicating fields.
5.2) Record & Mapped Types Generating typed lookup tables for test data, e.g. environment configs per region.
6. Type Guards, Narrowing & Discriminated Unions How to handle real, messy API responses safely instead of unsafe casting.
6.1) Discriminated unions for API state
  • Modeling loading/success/error API states as a union so TypeScript forces you to handle every case.
  • Using switch-based narrowing instead of optional-field guesswork.
6.2) unknown vs any Why parsing an untrusted API or test-data response as unknown, not any, prevents an entire class of runtime bugs.
7. Interfaces & Type Aliases Structuring test data cleanly as your framework grows.
8. Enums & Union Types Handling fixed sets of values cleanly, e.g. test environments.
9. Classes & Objects The foundation for building the Page Object Model.
10. Extending Playwright's Type System Adding your own custom fixtures with full autocomplete and type safety — how real frameworks are built.
10.1) Module augmentation for custom fixtures Extending Playwright's built-in test object so myPage or apiClient is fully typed everywhere.
10.2) Declaration merging edge cases What breaks when two fixture files try to augment the same type, and how to structure files to avoid it.
3 Playwright Fundamentals Weekday 1.5 wks · Weekend 2 wks ▾
TopicWhat You'll Learn
1. Introduction to Playwright What it is, why Microsoft built it, and why it's overtaken Selenium as the fastest-growing framework.
2. Installation & Configuration Setting up your first project with the official Playwright Test Runner.
3. Your First Test Script Writing and running a test across Chromium, Firefox, and WebKit.
4. Locators Deep-Dive Finding elements reliably with Playwright's built-in locators (getByRole, getByText, getByLabel).
5. ARIA Snapshots & Accessibility-First Locators A 2026 shift: asserting against the accessibility tree instead of brittle CSS selectors.
5.1) Why this matters
  • ARIA-tree assertions survive a CSS/class-name redesign that would break every old selector.
  • Doubles as a lightweight accessibility check for free.
6. Auto-Waiting & Synchronization Why Playwright rarely needs manual waits, and when it still does.
7. Actions: Click, Type, Select, Upload Automating every common user interaction.
8. Assertions Validating that your app behaves correctly.
9. Codegen & UI Mode Auto-generating scripts and debugging interactively in real time.
9.1) UI Mode Running npx playwright test --ui to step through a test live, inspect the DOM at each action, and re-run a single step instantly.
10. Playwright Test Agents (Planner / Generator / Healer) Playwright's own official AI-assisted authoring workflow (v1.56+) — generates and repairs tests from a plan.
10.1) How it fits a real workflow
  • Using the planner to turn a plain-English scenario into a draft test.
  • Using the healer to auto-repair a test broken by a small UI change, then reviewing the diff like a PR.
4 Playwright Framework Design & API Testing Weekday 1.5 wks · Weekend 2 wks ▾
TopicWhat You'll Learn
1. Page Object Model (POM) The industry-standard way to structure reusable, maintainable test code.
2. Test Hooks & Fixtures Automatic setup/cleanup logic before and after tests.
3. Flaky Test Root-Cause Analysis The skill that separates a junior automation tester from a senior one — most 'flaky' tests aren't Playwright's fault.
3.1) Animation-timing races vs network races
  • Telling apart a CSS-transition race from a slow-API race using the same symptom (intermittent failure).
  • Fixing each correctly instead of papering over both with a blanket waitForTimeout.
3.2) Using Trace Viewer's network panel Pinpointing the exact slow request that caused a 1-in-20 failure, with timestamps.
4. Handling Shadow DOM & Web Components Playwright auto-pierces shadow DOM, but real design systems (e.g. Salesforce Lightning) still trip people up.
4.1) Where it still needs help
  • Locating elements inside nested custom web components without over-scoping selectors.
  • Handling closed shadow roots that JavaScript itself cannot pierce.
5. iFrames, Pop-ups & New Tabs Automating trickier real-world UI scenarios.
6. Multi-Tab, Multi-Context & Multi-Origin Flows Testing what actually happens in production apps: logins, payments, and SSO rarely stay on one domain.
6.1) Real scenarios
  • Testing an OAuth/SSO redirect that bounces across 2–3 different domains.
  • Handling a payment gateway that opens in a popup and posts a result back to the parent window.
7. Data-Driven Testing Running the same test with multiple data sets without duplicating code.
8. Test Tagging, Grouping & Annotations Organizing large suites to run only smoke or only regression tests on demand.
9. Screenshots, Video & Trace Viewer Capturing evidence on failure and debugging step-by-step.
10. The Clock API Testing Time-Dependent UI — Playwright's page.clock (1.45+): control time itself instead of waiting for it in real time.
10.1) Mocking timers & countdowns deterministically
  • Testing a session-expiry warning that fires in 30 minutes, in under a second of real test time.
  • Freezing a fixed date to test date-aware rendering (invoices, "time ago" labels) reliably.
10.2) Testing polling/scheduled features Fast-forwarding through a dashboard's 10-second polling interval and asserting on each tick.
11. Advanced Network Interception & Failure Simulation Testing what happens when things go wrong, which is most of what happens in production.
11.1) Simulating failures on purpose
  • Forcing a 500 error, a timeout, or a slow 3G connection to verify the app's error and loading states.
  • Modifying a live response mid-flight vs fully replacing it with route.fulfill.
12. Parallel & Headless Execution Running tests faster, and without a visible browser window for CI/CD.
13. Test Isolation, Sharding & Parallelization Pitfalls What breaks when a suite that worked at 20 tests hits 500.
13.1) Shared state & data pollution Diagnosing tests that pass alone but fail in parallel because they share a database record or login session.
13.2) Sharding across CI runners Splitting a large suite across multiple machines and merging the reports back into one.
14. Component Testing (Playwright CT) Testing a single React/Vue component in isolation, without spinning up the whole app.
14.1) When to use it Design-system and shared-component libraries where full E2E is overkill for a button or form field.
15. API Testing with Playwright Sending GET/POST/PUT/DELETE requests and validating responses inside your Playwright project.
16. Postman Basics Manually exploring and testing APIs before automating them.
17. Auth & Session Reuse (storageState) Reusing login sessions/tokens across tests — a major speed technique used at real companies.
17.1) Doing it securely Storing and reusing storageState without leaking real credentials into a shared CI cache.
5 Visual Testing & Mobile Emulation Weekday 0.5 wk · Weekend 1 wk ▾
TopicWhat You'll Learn
1. Visual Regression Testing Automatically catching UI bugs functional tests miss (wrong colors, broken layouts).
2. Dynamic Content Masking for Visual Diffs The real-world visual-testing skill nobody's beginner tutorial covers.
2.1) What has to be masked Ads, timestamps, live counters, and rotating banners that would otherwise fail every single visual test.
3. Cross-OS Font-Rendering Differences Why a visual test can pass on your Mac and fail in a Linux CI container.
3.1) Handling it Tuning diff thresholds and using Docker-based rendering to match CI exactly.
4. Mobile Device Emulation Testing how a site behaves on simulated phones/tablets, no physical device needed.
5. Cross-Browser/Device Strategy Getting good coverage without 10x-ing your test run time.
6. Environment Variables & Config Running the same tests safely against dev, staging, and production.
6 CI/CD, Reporting & Real-World Workflow Weekday 0.5 wk · Weekend 1 wk ▾
TopicWhat You'll Learn
1. Introduction to CI/CD What Continuous Integration means and why every modern QA job expects it.
2. GitHub Actions for Test Automation Automatically running your suite on every code push.
3. Sharding & Merging Reports Across Runners How large real-world suites (500+ tests) stay fast in CI instead of taking an hour.
3.1) Practical setup Splitting a suite across parallel CI jobs and merging the HTML/trace reports into one artifact.
4. Retry Strategies & Flaky-Test Quarantine What real teams do instead of just re-running a red build and hoping.
4.1) The pattern
  • Auto-retrying a genuinely flaky test while it's investigated, without hiding it forever.
  • Maintaining a quarantine list so flaky tests don't block every PR.
5. Docker Basics for Testing Running tests in a consistent, isolated environment — a common enterprise requirement.
6. HTML Test Reports Generating shareable, professional reports with screenshots.
7. Git Branching for QA Teams Pull requests and code review as part of a real dev workflow.
7 Generative AI for Software Testing Weekday 1 wk · Weekend 1.5 wks ▾
TopicWhat You'll Learn
1. Where GenAI Fits in Testing An honest 2026 map: AI-assisted generation, self-healing locators, visual AI, and where humans are still needed.
2. AI-Assisted Script Generation Using ChatGPT/Claude/GitHub Copilot to draft test cases and scripts faster, then reviewing them like a professional.
3. Self-Healing Locators How AI automatically fixes a broken element locator when the UI changes, cutting maintenance dramatically.
4. AI Visual Testing (Applitools-style) Using vision-based AI to catch pixel-level UI bugs automatically.
5. Testing Non-Deterministic AI Outputs The genuinely hard, real-world problem: how do you assert on an answer that's different every time?
5.1) Practical techniques
  • Fuzzy/semantic assertions instead of exact string matching for AI-generated text.
  • Setting acceptable-range checks for AI outputs (tone, structure, banned-content checks) instead of one 'correct' answer.
6. LLM API Integration into Test Code Hands-on: calling an AI API from inside your own Playwright code for smarter, dynamic assertions.
7. AI Test Data Generation Generating realistic, safe synthetic test data at scale.
8. Prompt-Injection Awareness for QA A real security-adjacent edge case as more apps embed AI features.
8.1) What testers should check Whether user input can hijack an AI feature's instructions (e.g. a support chatbot) — a basic but essential check.
9. Evaluating GenAI Testing Tools A practical look at LambdaTest KaneAI, Testim, Katalon, Applitools — the landscape recruiters ask about.
8 Agentic AI Testing & MCP (Bonus/Advanced) Weekday 0.5 wk · Weekend 1 wk ▾
TopicWhat You'll Learn
1. What Is Agentic AI The difference between 'AI generates a script for you' and 'AI plans, acts, and adapts on its own.'
2. Introduction to MCP (Model Context Protocol) The open standard (from Anthropic, now adopted industry-wide) letting AI safely control tools like a browser.
3. Playwright's Official MCP Server Playwright now ships an official MCP server that drives a real browser via accessibility snapshots, not screenshots — a genuine 2026 shift.
3.1) Why accessibility snapshots matter More reliable and far cheaper than vision-model screenshot parsing for an agent to act on.
4. Playwright MCP Server Hands-On — Connecting an AI agent to Playwright so it can browse and test using natural-language instructions.
5. AI Agents for Exploratory Testing & Bug Triage Using an AI agent to explore an unfamiliar app and surface potential issues.
6. Human-in-the-Loop & Safety Guardrails Why every responsible setup keeps human approval and token/tool-call limits.
6.1) Practical limits Setting a maximum tool-call budget so an agent can't loop indefinitely against a real environment.
9 Capstone Project Weekday 1 wk · Weekend 1.5 wks ▾
TopicWhat You'll Learn
1. Project Kickoff Selecting a real demo application to fully test.
2. Building a Complete Framework Combining POM design, data-driven tests, and API+UI hybrid tests and CI/CD.
3. Code Review & Best Practices Mentor review of your framework against real industry standards.
4. GitHub Portfolio Presentation Polishing your project with a clear README, your #1 proof of skill for recruiters.
10 Job Readiness & Interview Prep Weekday 0.5 wk · Weekend 0.5 wk ▾
TopicWhat You'll Learn
1. Resume & LinkedIn Building An ATS-friendly resume and optimized LinkedIn profile built around your capstone project.
2. Common QA/SDET Interview Questions Working through the most frequently asked manual, automation, and AI-testing questions, including flaky-test and edge-case scenarios.
3. Coding & Logical Problem Rounds Practicing the logic questions that trip up most QA candidates.
4. Mock Interviews Live mock interviews with mentor feedback.
5. Job Search Strategy Getting past ATS filters and finding fresher/switcher-friendly QA openings.
1 JavaScript Fundamentals for Testers Weekday 1 wk · Weekend 1.5 wks ▾
TopicWhat You'll Learn
1. Node.js & VS Code Setup Your daily coding environment, installed and configured from scratch.
2. Variables, Data Types & Operators The building blocks JavaScript uses to store and manipulate data.
3. Conditionals & Loops Writing decision logic and repeating actions — the backbone of any test script.
4. Functions Packaging reusable logic for clean, non-repetitive test code.
5. Arrays & Objects Working with lists and structured data, e.g. a list of test users.
6. Asynchronous JS Deep-Dive: Event Loop & Race Conditions The real reason async tests flake, not "the tool is broken."
6.1) Microtasks vs macrotasks
  • Why await ordering surprises people, and how misunderstanding it explains supposedly "random" test-timing bugs.
  • Tracing a real event-loop timeline to predict execution order before running the code.
6.2) Promise.all / allSettled / race
  • Running parallel API calls in test setup without one silent failure hiding the rest.
  • Choosing allSettled over all when partial failure is acceptable in a test fixture.
6.3) Unhandled promise rejections
  • Catching the exact async failure that crashes a CI run with no useful error message.
  • Setting up global rejection handlers so a swallowed error doesn't silently mark a test 'passed'.
7. Closures & Memory in Long-Running Suites A classic source of bugs that only show up after 200+ tests, not in a 5-test demo.
7.1) Closures capturing stale data
  • The var-vs-let loop bug: why a for-loop over test cases can silently run the last case N times.
  • Fixing it correctly with block scoping and understanding why it worked "by accident" before.
7.2) Memory leaks in Node test processes
  • Event listeners and timers that never get removed, slowly degrading a long CI run.
  • Diagnosing a leak with Node's --inspect and Chrome DevTools memory snapshots.
8. Working with Dates & Time Zones (Test Data Edge Cases) One of the most common real-world sources of "works on my machine" test failures.
8.1) UTC vs local time pitfalls
  • Why a date assertion passes in India and fails in the US CI runner.
  • Normalizing all test data to UTC and converting only at the assertion boundary.
8.2) Daylight Saving Time edge cases Testing a booking or scheduling feature across a DST transition date on purpose.
9. Regular Expressions for Dynamic Locators & Data Validation Matching flexible, changing text without hardcoding brittle strings.
9.1) Building resilient patterns Matching partial/dynamic text (e.g. "Order #12345 confirmed") without over-fitting to one value.
9.2) Common regex pitfalls Catastrophic backtracking: a regex that works on 10 rows and hangs on 10,000.
10. JSON Basics Reading/writing the data format used everywhere in test data and API responses.
11. Git & GitHub Basics Version control fundamentals — commit, push, pull, branches.
2 TypeScript Essentials for Real-World Frameworks Weekday 0.5 wk · Weekend 1 wk ▾
TopicWhat You'll Learn
1. Why TypeScript for Testing Why most modern Playwright frameworks are written in TypeScript, not plain JS.
2. Project Setup (tsconfig.json) Configuring strict mode correctly from day one, not bolting it on later.
3. Type Annotations & Inference Catching mistakes before you even run the test.
4. Generics for Reusable Test Frameworks The single most valuable TS skill for building a framework that scales past 50 tests.
4.1) Generic Page Object base classes Writing one BasePage<T> class that every page object extends, instead of copy-pasting boilerplate.
4.2) Generic API response wrappers Typing ApiResponse<T> once and reusing it for every endpoint's response shape.
5. Utility Types for Test Data & Mocking Built-in TypeScript types that remove huge amounts of manual typewriting.
5.1) Partial, Pick & Omit
  • Building flexible test-data fixtures where only some fields are overridden per test.
  • Deriving a 'CreateUserDto' type from a full User type without duplicating fields.
5.2) Record & Mapped Types Generating typed lookup tables for test data, e.g. environment configs per region.
6. Type Guards, Narrowing & Discriminated Unions How to handle real, messy API responses safely instead of unsafe casting.
6.1) Discriminated unions for API state
  • Modeling loading/success/error API states as a union so TypeScript forces you to handle every case.
  • Using switch-based narrowing instead of optional-field guesswork.
6.2) unknown vs any Why parsing an untrusted API or test-data response as unknown, not any, prevents an entire class of runtime bugs.
7. Interfaces & Type Aliases Structuring test data cleanly as your framework grows.
8. Enums & Union Types Handling fixed sets of values cleanly, e.g. test environments.
9. Classes & Objects The foundation for building the Page Object Model.
10. Extending Playwright's Type System Adding your own custom fixtures with full autocomplete and type safety — how real frameworks are built.
10.1) Module augmentation for custom fixtures Extending Playwright's built-in test object so myPage or apiClient is fully typed everywhere.
10.2) Declaration merging edge cases What breaks when two fixture files try to augment the same type, and how to structure files to avoid it.
3 Playwright Fundamentals Weekday 1.5 wks · Weekend 2 wks ▾
TopicWhat You'll Learn
1. Introduction to Playwright What it is, why Microsoft built it, and why it's overtaken Selenium as the fastest-growing framework.
2. Installation & Configuration Setting up your first project with the official Playwright Test Runner.
3. Your First Test Script Writing and running a test across Chromium, Firefox, and WebKit.
4. Locators Deep-Dive Finding elements reliably with Playwright's built-in locators (getByRole, getByText, getByLabel).
5. ARIA Snapshots & Accessibility-First Locators A 2026 shift: asserting against the accessibility tree instead of brittle CSS selectors.
5.1) Why this matters
  • ARIA-tree assertions survive a CSS/class-name redesign that would break every old selector.
  • Doubles as a lightweight accessibility check for free.
6. Auto-Waiting & Synchronization Why Playwright rarely needs manual waits, and when it still does.
7. Actions: Click, Type, Select, Upload Automating every common user interaction.
8. Assertions Validating that your app behaves correctly.
9. Codegen & UI Mode Auto-generating scripts and debugging interactively in real time.
9.1) UI Mode Running npx playwright test --ui to step through a test live, inspect the DOM at each action, and re-run a single step instantly.
10. Playwright Test Agents (Planner / Generator / Healer) Playwright's own official AI-assisted authoring workflow (v1.56+) — generates and repairs tests from a plan.
10.1) How it fits a real workflow
  • Using the planner to turn a plain-English scenario into a draft test.
  • Using the healer to auto-repair a test broken by a small UI change, then reviewing the diff like a PR.
4 Playwright Framework & API Testing (Core + Real-World Essentials) Weekday 1.5 wks · Weekend 2.5 wks ▾
TopicWhat You'll Learn
1. Page Object Model (POM) The core reusable structure every real automation framework is built on.
2. Hooks & Fixtures Setup/cleanup logic that runs automatically around your tests.
3. Flaky Test Root-Cause Analysis (Essentials) Diagnosing the #1 real-world QA complaint — a test that fails intermittently for no obvious reason.
3.1) Core technique Distinguishing a timing race from a genuine bug using Trace Viewer before touching any code.
4. Data-Driven Testing Running one test against many data sets efficiently.
5. Screenshots & Trace Viewer Debugging failed tests with visual evidence.
6. Advanced Network Interception (Essentials) Simulating an API failure (500, timeout) to check the app handles it gracefully — a top interview question.
7. Playwright API Request Context Testing APIs directly, not just through the UI.
8. Postman Basics The industry-standard tool for manual API exploration.
5 Capstone Project Weekday 1 wk · Weekend 1.5 wks ▾
TopicWhat You'll Learn
1. Project Kickoff Selecting a real demo application to fully test.
2. Building a Complete Framework Combining POM design, data-driven tests, and API+UI hybrid tests and CI/CD.
3. Code Review & Best Practices Mentor review of your framework against real industry standards.
4. GitHub Portfolio Presentation Polishing your project with a clear README, your #1 proof of skill for recruiters.
6 Job Readiness & Interview Prep Weekday 0.5 wk · Weekend 0.5 wk ▾
TopicWhat You'll Learn
1. Resume & LinkedIn Building An ATS-friendly resume and optimized LinkedIn profile built around your capstone project.
2. Common QA/SDET Interview Questions Working through the most frequently asked manual, automation, and AI-testing questions, including flaky-test and edge-case scenarios.
3. Coding & Logical Problem Rounds Practicing the logic questions that trip up most QA candidates.
4. Mock Interviews Live mock interviews with mentor feedback.
5. Job Search Strategy Getting past ATS filters and finding fresher/switcher-friendly QA openings.
1 Manual Testing Foundations & QA Mindset Weekday 2 wks · Weekend 3.5 wks ▾
TopicWhat You'll Learn
1. What is Software Testing & QA vs QC Why testers exist even when developers test their own code.
2. SDLC & STLC How software gets built (Waterfall/Agile/V-Model) and the tester's own life cycle within it.
3. Types of Testing Functional, non-functional, smoke, sanity, regression, exploratory, usability, compatibility.
4. Test Case Design Techniques Equivalence partitioning, boundary value analysis, decision tables — structured ways to find real bugs.
4.1) Real-world edge cases
  • Boundary values on real production forms: currency fields, date pickers, file-size limits.
  • Risk-based prioritization: which edge cases actually matter when you can't test everything before a release.
5. Writing & Executing Test Cases Hands-on practice writing professional-format test cases on a live demo app.
6. Defect Life Cycle & Bug Reporting How a bug moves from found to fixed to verified, and how to write a report developers respect.
7. Bug Tracking with JIRA Logging, tracking, and managing defects the way real QA teams do.
8. Agile Testing Basics A tester's day in a Scrum team — sprints, standups, story points, definition of done.
2 JavaScript Fundamentals for Testers Weekday 2 wks · Weekend 3.5 wks ▾
TopicWhat You'll Learn
1. Node.js & VS Code Setup Your daily coding environment, installed and configured from scratch.
2. Variables, Data Types & Operators The building blocks JavaScript uses to store and manipulate data.
3. Conditionals & Loops Writing decision logic and repeating actions — the backbone of any test script.
4. Functions Packaging reusable logic for clean, non-repetitive test code.
5. Arrays & Objects Working with lists and structured data, e.g. a list of test users.
6. Asynchronous JS Deep-Dive: Event Loop & Race Conditions The real reason async tests flake, not "the tool is broken."
6.1) Microtasks vs macrotasks
  • Why await ordering surprises people, and how misunderstanding it explains supposedly "random" test-timing bugs.
  • Tracing a real event-loop timeline to predict execution order before running the code.
6.2) Promise.all / allSettled / race
  • Running parallel API calls in test setup without one silent failure hiding the rest.
  • Choosing allSettled over all when partial failure is acceptable in a test fixture.
6.3) Unhandled promise rejections
  • Catching the exact async failure that crashes a CI run with no useful error message.
  • Setting up global rejection handlers so a swallowed error doesn't silently mark a test 'passed'.
7. Closures & Memory in Long-Running Suites A classic source of bugs that only show up after 200+ tests, not in a 5-test demo.
7.1) Closures capturing stale data
  • The var-vs-let loop bug: why a for-loop over test cases can silently run the last case N times.
  • Fixing it correctly with block scoping and understanding why it worked "by accident" before.
7.2) Memory leaks in Node test processes
  • Event listeners and timers that never get removed, slowly degrading a long CI run.
  • Diagnosing a leak with Node's --inspect and Chrome DevTools memory snapshots.
8. Working with Dates & Time Zones (Test Data Edge Cases) One of the most common real-world sources of "works on my machine" test failures.
8.1) UTC vs local time pitfalls
  • Why a date assertion passes in India and fails in the US CI runner.
  • Normalizing all test data to UTC and converting only at the assertion boundary.
8.2) Daylight Saving Time edge cases Testing a booking or scheduling feature across a DST transition date on purpose.
9. Regular Expressions for Dynamic Locators & Data Validation Matching flexible, changing text without hardcoding brittle strings.
9.1) Building resilient patterns Matching partial/dynamic text (e.g. "Order #12345 confirmed") without over-fitting to one value.
9.2) Common regex pitfalls Catastrophic backtracking: a regex that works on 10 rows and hangs on 10,000.
10. JSON Basics Reading/writing the data format used everywhere in test data and API responses.
11. Git & GitHub Basics Version control fundamentals — commit, push, pull, branches.
3 TypeScript Essentials for Real-World Frameworks Weekday 1 wk · Weekend 1.5 wks ▾
TopicWhat You'll Learn
1. Why TypeScript for Testing Why most modern Playwright frameworks are written in TypeScript, not plain JS.
2. Project Setup (tsconfig.json) Configuring strict mode correctly from day one, not bolting it on later.
3. Type Annotations & Inference Catching mistakes before you even run the test.
4. Generics for Reusable Test Frameworks The single most valuable TS skill for building a framework that scales past 50 tests.
4.1) Generic Page Object base classes Writing one BasePage<T> class that every page object extends, instead of copy-pasting boilerplate.
4.2) Generic API response wrappers Typing ApiResponse<T> once and reusing it for every endpoint's response shape.
5. Utility Types for Test Data & Mocking Built-in TypeScript types that remove huge amounts of manual typewriting.
5.1) Partial, Pick & Omit
  • Building flexible test-data fixtures where only some fields are overridden per test.
  • Deriving a 'CreateUserDto' type from a full User type without duplicating fields.
5.2) Record & Mapped Types Generating typed lookup tables for test data, e.g. environment configs per region.
6. Type Guards, Narrowing & Discriminated Unions How to handle real, messy API responses safely instead of unsafe casting.
6.1) Discriminated unions for API state
  • Modeling loading/success/error API states as a union so TypeScript forces you to handle every case.
  • Using switch-based narrowing instead of optional-field guesswork.
6.2) unknown vs any Why parsing an untrusted API or test-data response as unknown, not any, prevents an entire class of runtime bugs.
7. Interfaces & Type Aliases Structuring test data cleanly as your framework grows.
8. Enums & Union Types Handling fixed sets of values cleanly, e.g. test environments.
9. Classes & Objects The foundation for building the Page Object Model.
10. Extending Playwright's Type System Adding your own custom fixtures with full autocomplete and type safety — how real frameworks are built.
10.1) Module augmentation for custom fixtures Extending Playwright's built-in test object so myPage or apiClient is fully typed everywhere.
10.2) Declaration merging edge cases What breaks when two fixture files try to augment the same type, and how to structure files to avoid it.
4 Playwright Fundamentals Weekday 2 wks · Weekend 3.5 wks ▾
TopicWhat You'll Learn
1. Introduction to Playwright What it is, why Microsoft built it, and why it's overtaken Selenium as the fastest-growing framework.
2. Installation & Configuration Setting up your first project with the official Playwright Test Runner.
3. Your First Test Script Writing and running a test across Chromium, Firefox, and WebKit.
4. Locators Deep-Dive Finding elements reliably with Playwright's built-in locators (getByRole, getByText, getByLabel).
5. ARIA Snapshots & Accessibility-First Locators A 2026 shift: asserting against the accessibility tree instead of brittle CSS selectors.
5.1) Why this matters
  • ARIA-tree assertions survive a CSS/class-name redesign that would break every old selector.
  • Doubles as a lightweight accessibility check for free.
6. Auto-Waiting & Synchronization Why Playwright rarely needs manual waits, and when it still does.
7. Actions: Click, Type, Select, Upload Automating every common user interaction.
8. Assertions Validating that your app behaves correctly.
9. Codegen & UI Mode Auto-generating scripts and debugging interactively in real time.
9.1) UI Mode Running npx playwright test --ui to step through a test live, inspect the DOM at each action, and re-run a single step instantly.
10. Playwright Test Agents (Planner / Generator / Healer) Playwright's own official AI-assisted authoring workflow (v1.56+) — generates and repairs tests from a plan.
10.1) How it fits a real workflow
  • Using the planner to turn a plain-English scenario into a draft test.
  • Using the healer to auto-repair a test broken by a small UI change, then reviewing the diff like a PR.
5 Playwright Framework Design & API Testing Weekday 2 wks · Weekend 3.5 wks ▾
TopicWhat You'll Learn
1. Page Object Model (POM) The industry-standard way to structure reusable, maintainable test code.
2. Test Hooks & Fixtures Automatic setup/cleanup logic before and after tests.
3. Flaky Test Root-Cause Analysis The skill that separates a junior automation tester from a senior one — most 'flaky' tests aren't Playwright's fault.
3.1) Animation-timing races vs network races
  • Telling apart a CSS-transition race from a slow-API race using the same symptom (intermittent failure).
  • Fixing each correctly instead of papering over both with a blanket waitForTimeout.
3.2) Using Trace Viewer's network panel Pinpointing the exact slow request that caused a 1-in-20 failure, with timestamps.
4. Handling Shadow DOM & Web Components Playwright auto-pierces shadow DOM, but real design systems (e.g. Salesforce Lightning) still trip people up.
4.1) Where it still needs help
  • Locating elements inside nested custom web components without over-scoping selectors.
  • Handling closed shadow roots that JavaScript itself cannot pierce.
5. iFrames, Pop-ups & New Tabs Automating trickier real-world UI scenarios.
6. Multi-Tab, Multi-Context & Multi-Origin Flows Testing what actually happens in production apps: logins, payments, and SSO rarely stay on one domain.
6.1) Real scenarios
  • Testing an OAuth/SSO redirect that bounces across 2–3 different domains.
  • Handling a payment gateway that opens in a popup and posts a result back to the parent window.
7. Data-Driven Testing Running the same test with multiple data sets without duplicating code.
8. Test Tagging, Grouping & Annotations Organizing large suites to run only smoke or only regression tests on demand.
9. Screenshots, Video & Trace Viewer Capturing evidence on failure and debugging step-by-step.
10. The Clock API Testing Time-Dependent UI — Playwright's page.clock (1.45+): control time itself instead of waiting for it in real time.
10.1) Mocking timers & countdowns deterministically
  • Testing a session-expiry warning that fires in 30 minutes, in under a second of real test time.
  • Freezing a fixed date to test date-aware rendering (invoices, "time ago" labels) reliably.
10.2) Testing polling/scheduled features Fast-forwarding through a dashboard's 10-second polling interval and asserting on each tick.
11. Advanced Network Interception & Failure Simulation Testing what happens when things go wrong, which is most of what happens in production.
11.1) Simulating failures on purpose
  • Forcing a 500 error, a timeout, or a slow 3G connection to verify the app's error and loading states.
  • Modifying a live response mid-flight vs fully replacing it with route.fulfill.
12. Parallel & Headless Execution Running tests faster, and without a visible browser window for CI/CD.
13. Test Isolation, Sharding & Parallelization Pitfalls What breaks when a suite that worked at 20 tests hits 500.
13.1) Shared state & data pollution Diagnosing tests that pass alone but fail in parallel because they share a database record or login session.
13.2) Sharding across CI runners Splitting a large suite across multiple machines and merging the reports back into one.
14. Component Testing (Playwright CT) Testing a single React/Vue component in isolation, without spinning up the whole app.
14.1) When to use it Design-system and shared-component libraries where full E2E is overkill for a button or form field.
15. API Testing with Playwright Sending GET/POST/PUT/DELETE requests and validating responses inside your Playwright project.
16. Postman Basics Manually exploring and testing APIs before automating them.
17. Auth & Session Reuse (storageState) Reusing login sessions/tokens across tests — a major speed technique used at real companies.
17.1) Doing it securely Storing and reusing storageState without leaking real credentials into a shared CI cache.
6 Capstone Project Weekday 1.5 wks · Weekend 2.5 wks ▾
TopicWhat You'll Learn
1. Project Kickoff Selecting a real demo application to fully test.
2. Building a Complete Framework Combining POM design, data-driven tests, and API+UI hybrid tests and CI/CD.
3. Code Review & Best Practices Mentor review of your framework against real industry standards.
4. GitHub Portfolio Presentation Polishing your project with a clear README, your #1 proof of skill for recruiters.
7 Job Readiness & Interview Prep Weekday 0.5 wk · Weekend 1 wk ▾
TopicWhat You'll Learn
1. Resume & LinkedIn Building An ATS-friendly resume and optimized LinkedIn profile built around your capstone project.
2. Common QA/SDET Interview Questions Working through the most frequently asked manual, automation, and AI-testing questions, including flaky-test and edge-case scenarios.
3. Coding & Logical Problem Rounds Practicing the logic questions that trip up most QA candidates.
4. Mock Interviews Live mock interviews with mentor feedback.
5. Job Search Strategy Getting past ATS filters and finding fresher/switcher-friendly QA openings.
1 Manual Testing Foundations & QA Mindset Weekday 2 wks · Weekend 3.5 wks ▾
TopicWhat You'll Learn
1. What is Software Testing & QA vs QC Why testers exist even when developers test their own code.
2. SDLC & STLC How software gets built (Waterfall/Agile/V-Model) and the tester's own life cycle within it.
3. Types of Testing Functional, non-functional, smoke, sanity, regression, exploratory, usability, compatibility.
4. Test Case Design Techniques Equivalence partitioning, boundary value analysis, decision tables — structured ways to find real bugs.
4.1) Real-world edge cases
  • Boundary values on real production forms: currency fields, date pickers, file-size limits.
  • Risk-based prioritization: which edge cases actually matter when you can't test everything before a release.
5. Writing & Executing Test Cases Hands-on practice writing professional-format test cases on a live demo app.
6. Defect Life Cycle & Bug Reporting How a bug moves from found to fixed to verified, and how to write a report developers respect.
7. Bug Tracking with JIRA Logging, tracking, and managing defects the way real QA teams do.
8. Agile Testing Basics A tester's day in a Scrum team — sprints, standups, story points, definition of done.
2 JavaScript Fundamentals for Testers Weekday 2 wks · Weekend 3.5 wks ▾
TopicWhat You'll Learn
1. Node.js & VS Code Setup Your daily coding environment, installed and configured from scratch.
2. Variables, Data Types & Operators The building blocks JavaScript uses to store and manipulate data.
3. Conditionals & Loops Writing decision logic and repeating actions — the backbone of any test script.
4. Functions Packaging reusable logic for clean, non-repetitive test code.
5. Arrays & Objects Working with lists and structured data, e.g. a list of test users.
6. Asynchronous JS Deep-Dive: Event Loop & Race Conditions The real reason async tests flake, not "the tool is broken."
6.1) Microtasks vs macrotasks
  • Why await ordering surprises people, and how misunderstanding it explains supposedly "random" test-timing bugs.
  • Tracing a real event-loop timeline to predict execution order before running the code.
6.2) Promise.all / allSettled / race
  • Running parallel API calls in test setup without one silent failure hiding the rest.
  • Choosing allSettled over all when partial failure is acceptable in a test fixture.
6.3) Unhandled promise rejections
  • Catching the exact async failure that crashes a CI run with no useful error message.
  • Setting up global rejection handlers so a swallowed error doesn't silently mark a test 'passed'.
7. Closures & Memory in Long-Running Suites A classic source of bugs that only show up after 200+ tests, not in a 5-test demo.
7.1) Closures capturing stale data
  • The var-vs-let loop bug: why a for-loop over test cases can silently run the last case N times.
  • Fixing it correctly with block scoping and understanding why it worked "by accident" before.
7.2) Memory leaks in Node test processes
  • Event listeners and timers that never get removed, slowly degrading a long CI run.
  • Diagnosing a leak with Node's --inspect and Chrome DevTools memory snapshots.
8. Working with Dates & Time Zones (Test Data Edge Cases) One of the most common real-world sources of "works on my machine" test failures.
8.1) UTC vs local time pitfalls
  • Why a date assertion passes in India and fails in the US CI runner.
  • Normalizing all test data to UTC and converting only at the assertion boundary.
8.2) Daylight Saving Time edge cases Testing a booking or scheduling feature across a DST transition date on purpose.
9. Regular Expressions for Dynamic Locators & Data Validation Matching flexible, changing text without hardcoding brittle strings.
9.1) Building resilient patterns Matching partial/dynamic text (e.g. "Order #12345 confirmed") without over-fitting to one value.
9.2) Common regex pitfalls Catastrophic backtracking: a regex that works on 10 rows and hangs on 10,000.
10. JSON Basics Reading/writing the data format used everywhere in test data and API responses.
11. Git & GitHub Basics Version control fundamentals — commit, push, pull, branches.
3 TypeScript Essentials for Real-World Frameworks Weekday 1 wk · Weekend 2 wks ▾
TopicWhat You'll Learn
1. Why TypeScript for Testing Why most modern Playwright frameworks are written in TypeScript, not plain JS.
2. Project Setup (tsconfig.json) Configuring strict mode correctly from day one, not bolting it on later.
3. Type Annotations & Inference Catching mistakes before you even run the test.
4. Generics for Reusable Test Frameworks The single most valuable TS skill for building a framework that scales past 50 tests.
4.1) Generic Page Object base classes Writing one BasePage<T> class that every page object extends, instead of copy-pasting boilerplate.
4.2) Generic API response wrappers Typing ApiResponse<T> once and reusing it for every endpoint's response shape.
5. Utility Types for Test Data & Mocking Built-in TypeScript types that remove huge amounts of manual typewriting.
5.1) Partial, Pick & Omit
  • Building flexible test-data fixtures where only some fields are overridden per test.
  • Deriving a 'CreateUserDto' type from a full User type without duplicating fields.
5.2) Record & Mapped Types Generating typed lookup tables for test data, e.g. environment configs per region.
6. Type Guards, Narrowing & Discriminated Unions How to handle real, messy API responses safely instead of unsafe casting.
6.1) Discriminated unions for API state
  • Modeling loading/success/error API states as a union so TypeScript forces you to handle every case.
  • Using switch-based narrowing instead of optional-field guesswork.
6.2) unknown vs any Why parsing an untrusted API or test-data response as unknown, not any, prevents an entire class of runtime bugs.
7. Interfaces & Type Aliases Structuring test data cleanly as your framework grows.
8. Enums & Union Types Handling fixed sets of values cleanly, e.g. test environments.
9. Classes & Objects The foundation for building the Page Object Model.
10. Extending Playwright's Type System Adding your own custom fixtures with full autocomplete and type safety — how real frameworks are built.
10.1) Module augmentation for custom fixtures Extending Playwright's built-in test object so myPage or apiClient is fully typed everywhere.
10.2) Declaration merging edge cases What breaks when two fixture files try to augment the same type, and how to structure files to avoid it.
4 Playwright Fundamentals Weekday 2 wks · Weekend 3.5 wks ▾
TopicWhat You'll Learn
1. Introduction to Playwright What it is, why Microsoft built it, and why it's overtaken Selenium as the fastest-growing framework.
2. Installation & Configuration Setting up your first project with the official Playwright Test Runner.
3. Your First Test Script Writing and running a test across Chromium, Firefox, and WebKit.
4. Locators Deep-Dive Finding elements reliably with Playwright's built-in locators (getByRole, getByText, getByLabel).
5. ARIA Snapshots & Accessibility-First Locators A 2026 shift: asserting against the accessibility tree instead of brittle CSS selectors.
5.1) Why this matters
  • ARIA-tree assertions survive a CSS/class-name redesign that would break every old selector.
  • Doubles as a lightweight accessibility check for free.
6. Auto-Waiting & Synchronization Why Playwright rarely needs manual waits, and when it still does.
7. Actions: Click, Type, Select, Upload Automating every common user interaction.
8. Assertions Validating that your app behaves correctly.
9. Codegen & UI Mode Auto-generating scripts and debugging interactively in real time.
9.1) UI Mode Running npx playwright test --ui to step through a test live, inspect the DOM at each action, and re-run a single step instantly.
10. Playwright Test Agents (Planner / Generator / Healer) Playwright's own official AI-assisted authoring workflow (v1.56+) — generates and repairs tests from a plan.
10.1) How it fits a real workflow
  • Using the planner to turn a plain-English scenario into a draft test.
  • Using the healer to auto-repair a test broken by a small UI change, then reviewing the diff like a PR.
5 Playwright Framework Design & API Testing Weekday 2 wks · Weekend 3.5 wks ▾
TopicWhat You'll Learn
1. Page Object Model (POM) The industry-standard way to structure reusable, maintainable test code.
2. Test Hooks & Fixtures Automatic setup/cleanup logic before and after tests.
3. Flaky Test Root-Cause Analysis The skill that separates a junior automation tester from a senior one — most 'flaky' tests aren't Playwright's fault.
3.1) Animation-timing races vs network races
  • Telling apart a CSS-transition race from a slow-API race using the same symptom (intermittent failure).
  • Fixing each correctly instead of papering over both with a blanket waitForTimeout.
3.2) Using Trace Viewer's network panel Pinpointing the exact slow request that caused a 1-in-20 failure, with timestamps.
4. Handling Shadow DOM & Web Components Playwright auto-pierces shadow DOM, but real design systems (e.g. Salesforce Lightning) still trip people up.
4.1) Where it still needs help
  • Locating elements inside nested custom web components without over-scoping selectors.
  • Handling closed shadow roots that JavaScript itself cannot pierce.
5. iFrames, Pop-ups & New Tabs Automating trickier real-world UI scenarios.
6. Multi-Tab, Multi-Context & Multi-Origin Flows Testing what actually happens in production apps: logins, payments, and SSO rarely stay on one domain.
6.1) Real scenarios
  • Testing an OAuth/SSO redirect that bounces across 2–3 different domains.
  • Handling a payment gateway that opens in a popup and posts a result back to the parent window.
7. Data-Driven Testing Running the same test with multiple data sets without duplicating code.
8. Test Tagging, Grouping & Annotations Organizing large suites to run only smoke or only regression tests on demand.
9. Screenshots, Video & Trace Viewer Capturing evidence on failure and debugging step-by-step.
10. The Clock API Testing Time-Dependent UI — Playwright's page.clock (1.45+): control time itself instead of waiting for it in real time.
10.1) Mocking timers & countdowns deterministically
  • Testing a session-expiry warning that fires in 30 minutes, in under a second of real test time.
  • Freezing a fixed date to test date-aware rendering (invoices, "time ago" labels) reliably.
10.2) Testing polling/scheduled features Fast-forwarding through a dashboard's 10-second polling interval and asserting on each tick.
11. Advanced Network Interception & Failure Simulation Testing what happens when things go wrong, which is most of what happens in production.
11.1) Simulating failures on purpose
  • Forcing a 500 error, a timeout, or a slow 3G connection to verify the app's error and loading states.
  • Modifying a live response mid-flight vs fully replacing it with route.fulfill.
12. Parallel & Headless Execution Running tests faster, and without a visible browser window for CI/CD.
13. Test Isolation, Sharding & Parallelization Pitfalls What breaks when a suite that worked at 20 tests hits 500.
13.1) Shared state & data pollution Diagnosing tests that pass alone but fail in parallel because they share a database record or login session.
13.2) Sharding across CI runners Splitting a large suite across multiple machines and merging the reports back into one.
14. Component Testing (Playwright CT) Testing a single React/Vue component in isolation, without spinning up the whole app.
14.1) When to use it Design-system and shared-component libraries where full E2E is overkill for a button or form field.
15. API Testing with Playwright Sending GET/POST/PUT/DELETE requests and validating responses inside your Playwright project.
16. Postman Basics Manually exploring and testing APIs before automating them.
17. Auth & Session Reuse (storageState) Reusing login sessions/tokens across tests — a major speed technique used at real companies.
17.1) Doing it securely Storing and reusing storageState without leaking real credentials into a shared CI cache.
6 Visual Testing & Mobile Emulation Weekday 1 wk · Weekend 2 wks ▾
TopicWhat You'll Learn
1. Visual Regression Testing Automatically catching UI bugs functional tests miss (wrong colors, broken layouts).
2. Dynamic Content Masking for Visual Diffs The real-world visual-testing skill nobody's beginner tutorial covers.
2.1) What has to be masked Ads, timestamps, live counters, and rotating banners that would otherwise fail every single visual test.
3. Cross-OS Font-Rendering Differences Why a visual test can pass on your Mac and fail in a Linux CI container.
3.1) Handling it Tuning diff thresholds and using Docker-based rendering to match CI exactly.
4. Mobile Device Emulation Testing how a site behaves on simulated phones/tablets, no physical device needed.
5. Cross-Browser/Device Strategy Getting good coverage without 10x-ing your test run time.
6. Environment Variables & Config Running the same tests safely against dev, staging, and production.
7 CI/CD, Reporting & Real-World Workflow Weekday 1 wk · Weekend 2 wks ▾
TopicWhat You'll Learn
1. Introduction to CI/CD What Continuous Integration means and why every modern QA job expects it.
2. GitHub Actions for Test Automation Automatically running your suite on every code push.
3. Sharding & Merging Reports Across Runners How large real-world suites (500+ tests) stay fast in CI instead of taking an hour.
3.1) Practical setup Splitting a suite across parallel CI jobs and merging the HTML/trace reports into one artifact.
4. Retry Strategies & Flaky-Test Quarantine What real teams do instead of just re-running a red build and hoping.
4.1) The pattern
  • Auto-retrying a genuinely flaky test while it's investigated, without hiding it forever.
  • Maintaining a quarantine list so flaky tests don't block every PR.
5. Docker Basics for Testing Running tests in a consistent, isolated environment — a common enterprise requirement.
6. HTML Test Reports Generating shareable, professional reports with screenshots.
7. Git Branching for QA Teams Pull requests and code review as part of a real dev workflow.
8 Generative AI for Software Testing Weekday 1.5 wks · Weekend 2.5 wks ▾
TopicWhat You'll Learn
1. Where GenAI Fits in Testing An honest 2026 map: AI-assisted generation, self-healing locators, visual AI, and where humans are still needed.
2. AI-Assisted Script Generation Using ChatGPT/Claude/GitHub Copilot to draft test cases and scripts faster, then reviewing them like a professional.
3. Self-Healing Locators How AI automatically fixes a broken element locator when the UI changes, cutting maintenance dramatically.
4. AI Visual Testing (Applitools-style) Using vision-based AI to catch pixel-level UI bugs automatically.
5. Testing Non-Deterministic AI Outputs The genuinely hard, real-world problem: how do you assert on an answer that's different every time?
5.1) Practical techniques
  • Fuzzy/semantic assertions instead of exact string matching for AI-generated text.
  • Setting acceptable-range checks for AI outputs (tone, structure, banned-content checks) instead of one 'correct' answer.
6. LLM API Integration into Test Code Hands-on: calling an AI API from inside your own Playwright code for smarter, dynamic assertions.
7. AI Test Data Generation Generating realistic, safe synthetic test data at scale.
8. Prompt-Injection Awareness for QA A real security-adjacent edge case as more apps embed AI features.
8.1) What testers should check Whether user input can hijack an AI feature's instructions (e.g. a support chatbot) — a basic but essential check.
9. Evaluating GenAI Testing Tools A practical look at LambdaTest KaneAI, Testim, Katalon, Applitools — the landscape recruiters ask about.
9 Agentic AI Testing & MCP (Bonus/Advanced) Weekday 0.5 wk · Weekend 1 wk ▾
TopicWhat You'll Learn
1. What Is Agentic AI The difference between 'AI generates a script for you' and 'AI plans, acts, and adapts on its own.'
2. Introduction to MCP (Model Context Protocol) The open standard (from Anthropic, now adopted industry-wide) letting AI safely control tools like a browser.
3. Playwright's Official MCP Server Playwright now ships an official MCP server that drives a real browser via accessibility snapshots, not screenshots — a genuine 2026 shift.
3.1) Why accessibility snapshots matter More reliable and far cheaper than vision-model screenshot parsing for an agent to act on.
4. Playwright MCP Server Hands-On — Connecting an AI agent to Playwright so it can browse and test using natural-language instructions.
5. AI Agents for Exploratory Testing & Bug Triage Using an AI agent to explore an unfamiliar app and surface potential issues.
6. Human-in-the-Loop & Safety Guardrails Why every responsible setup keeps human approval and token/tool-call limits.
6.1) Practical limits Setting a maximum tool-call budget so an agent can't loop indefinitely against a real environment.
10 Capstone Project Weekday 1.5 wks · Weekend 2.5 wks ▾
TopicWhat You'll Learn
1. Project Kickoff Selecting a real demo application to fully test.
2. Building a Complete Framework Combining POM design, data-driven tests, and API+UI hybrid tests and CI/CD.
3. Code Review & Best Practices Mentor review of your framework against real industry standards.
4. GitHub Portfolio Presentation Polishing your project with a clear README, your #1 proof of skill for recruiters.
11 Job Readiness & Interview Prep Weekday 0.5 wk · Weekend 1 wk ▾
TopicWhat You'll Learn
1. Resume & LinkedIn Building An ATS-friendly resume and optimized LinkedIn profile built around your capstone project.
2. Common QA/SDET Interview Questions Working through the most frequently asked manual, automation, and AI-testing questions, including flaky-test and edge-case scenarios.
3. Coding & Logical Problem Rounds Practicing the logic questions that trip up most QA candidates.
4. Mock Interviews Live mock interviews with mentor feedback.
5. Job Search Strategy Getting past ATS filters and finding fresher/switcher-friendly QA openings.

The curriculum for this package has not been added yet.

WHAT YOU GET

This Course Includes

💻

Online

🎯

11 Weeks Duration (Flexible)

🖥

1 Real Industry Projects

🏆

Certificate on Completion

♾️

Lifetime Access to Recordings

💼

Job References to 50+ Companies

🎯

5 Mock Interview Rounds

🗣

Soft Skills & Communication

📱

WhatsApp Batch Support

📥

Brochure & Syllabus Download

🛠 Tools Covered:
Node.jsVS CodenpmGit & GitHubTypeScriptPlaywright Test RunnerPlaywright InspectorCodegen & UI ModeTrace ViewerPlaywright Test Agents (MCP)PostmanGitHub ActionsDockerPlaywright HTML ReporterChatGPT/ClaudeGitHub CopilotAI visual-testing toolPlaywright MCP ServerJIRA
⬇️ Download Syllabus 💬 Enquire About This Course
SUCCESS STORIES

Our Students Excelling Worldwide

“
Priya Krishnamurthy P
Priya Krishnamurthy
QA Automation Engineer
🏢 Zoho Corporation
★★★★★

“Fourcup completely changed my career trajectory. I was stuck in manual testing for 3 years with no idea how to get into automation. The Playwright and TypeScript modules were far deeper than I expected — event-loop races and flaky-test root-cause analysis actually came up in my Zoho interview. Landed the role within 3 months of finishing.”

🎓 SDET — Playwright, JS & TS with AI
“
Karthik Raj K
Karthik Raj
Senior SDET
🏢 Freshworks
★★★★★

“I had tried two other institutes before Fourcup. They taught Selenium and stopped there. Fourcup went into Playwright's Trace Viewer, the Clock API, and shadow DOM handling — genuinely production-level content. By week 4 I had a working framework with CI/CD wired up. That project got me through the Freshworks technical round directly.”

🎓 SDET — Playwright, JS & TS with AI
“
Nithya Subramaniam N
Nithya Subramaniam
Test Automation Lead
🏢 Cognizant
★★★★★

“The TypeScript module alone was worth the course — generics, discriminated unions, module augmentation for custom fixtures. Most QA courses barely touch TypeScript beyond basic types. Cognizant specifically asked about how I structured my Page Object base classes with generics. Got the offer in my first attempt.”

🎓 SDET — Playwright, JS & TS with AI
YOUR MENTOR

Who teaches this course

Sessions are taught by someone who does this work, not by a full-time trainer reading slides.

👨‍🏫

Fourcup SDET Faculty

Real Industry Trainers, Not Just Instructors

Every Fourcup trainer has a minimum of 9+ years of total IT industry experience and 5+ years of specific, hands-on experience in the exact tool or domain they teach. They are currently working professionals — the frameworks, edge cases, and interview questions taught are what's actually used in live projects today. Mock-interview mentors are the same trainers who conduct real technical interviews at their day jobs.

9+ years experience Active practitioner
SUCCESS STORIES

Our Students Excelling Worldwide

“
Priya Krishnamurthy P
Priya Krishnamurthy
QA Automation Engineer
🏢 Zoho Corporation
★★★★★

“Fourcup completely changed my career trajectory. I was stuck in manual testing for 3 years with no idea how to get into automation. The Playwright and TypeScript modules were far deeper than I expected — event-loop races and flaky-test root-cause analysis actually came up in my Zoho interview. Landed the role within 3 months of finishing.”

🎓 SDET — Playwright, JS & TS with AI
“
Karthik Raj K
Karthik Raj
Senior SDET
🏢 Freshworks
★★★★★

“I had tried two other institutes before Fourcup. They taught Selenium and stopped there. Fourcup went into Playwright's Trace Viewer, the Clock API, and shadow DOM handling — genuinely production-level content. By week 4 I had a working framework with CI/CD wired up. That project got me through the Freshworks technical round directly.”

🎓 SDET — Playwright, JS & TS with AI
“
Nithya Subramaniam N
Nithya Subramaniam
Test Automation Lead
🏢 Cognizant
★★★★★

“The TypeScript module alone was worth the course — generics, discriminated unions, module augmentation for custom fixtures. Most QA courses barely touch TypeScript beyond basic types. Cognizant specifically asked about how I structured my Page Object base classes with generics. Got the offer in my first attempt.”

🎓 SDET — Playwright, JS & TS with AI
BATCHES

When you can start

Weekday, weekend and fast-track options. Seats are limited so sessions stay small enough to ask questions in.

Batch dates for this course have not been added yet.

SUCCESS STORIES

Our Students Excelling Worldwide

“
Priya Krishnamurthy P
Priya Krishnamurthy
QA Automation Engineer
🏢 Zoho Corporation
★★★★★

“Fourcup completely changed my career trajectory. I was stuck in manual testing for 3 years with no idea how to get into automation. The Playwright and TypeScript modules were far deeper than I expected — event-loop races and flaky-test root-cause analysis actually came up in my Zoho interview. Landed the role within 3 months of finishing.”

🎓 SDET — Playwright, JS & TS with AI
“
Karthik Raj K
Karthik Raj
Senior SDET
🏢 Freshworks
★★★★★

“I had tried two other institutes before Fourcup. They taught Selenium and stopped there. Fourcup went into Playwright's Trace Viewer, the Clock API, and shadow DOM handling — genuinely production-level content. By week 4 I had a working framework with CI/CD wired up. That project got me through the Freshworks technical round directly.”

🎓 SDET — Playwright, JS & TS with AI
“
Nithya Subramaniam N
Nithya Subramaniam
Test Automation Lead
🏢 Cognizant
★★★★★

“The TypeScript module alone was worth the course — generics, discriminated unions, module augmentation for custom fixtures. Most QA courses barely touch TypeScript beyond basic types. Cognizant specifically asked about how I structured my Page Object base classes with generics. Got the offer in my first attempt.”

🎓 SDET — Playwright, JS & TS with AI
FAQ

Questions people actually ask

If yours is not here, call us — a working engineer will answer, not a call centre.

No questions have been added for this course yet.

SUCCESS STORIES

Our Students Excelling Worldwide

“
Priya Krishnamurthy P
Priya Krishnamurthy
QA Automation Engineer
🏢 Zoho Corporation
★★★★★

“Fourcup completely changed my career trajectory. I was stuck in manual testing for 3 years with no idea how to get into automation. The Playwright and TypeScript modules were far deeper than I expected — event-loop races and flaky-test root-cause analysis actually came up in my Zoho interview. Landed the role within 3 months of finishing.”

🎓 SDET — Playwright, JS & TS with AI
“
Karthik Raj K
Karthik Raj
Senior SDET
🏢 Freshworks
★★★★★

“I had tried two other institutes before Fourcup. They taught Selenium and stopped there. Fourcup went into Playwright's Trace Viewer, the Clock API, and shadow DOM handling — genuinely production-level content. By week 4 I had a working framework with CI/CD wired up. That project got me through the Freshworks technical round directly.”

🎓 SDET — Playwright, JS & TS with AI
“
Nithya Subramaniam N
Nithya Subramaniam
Test Automation Lead
🏢 Cognizant
★★★★★

“The TypeScript module alone was worth the course — generics, discriminated unions, module augmentation for custom fixtures. Most QA courses barely touch TypeScript beyond basic types. Cognizant specifically asked about how I structured my Page Object base classes with generics. Got the offer in my first attempt.”

🎓 SDET — Playwright, JS & TS with AI
Related Topics
SDET — Playwright, JS & TS with AISoftware Testing Qa Aicourse in ChennaiOnline training11 Weeks course
People Also Ask AI Assistants
best sdet — playwright, js & ts with aiis sdet — playwright, js & ts with ai worth itsdet — playwright, js & ts with ai for beginnerssdet — playwright, js & ts with ai fees