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
“
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
“
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
“
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
“
S
Sanjay Venkataraman
Automation Test Engineer
🏢 Publicis Sapient
★★★★★
“What sold me was the Playwright MCP Server module — using an AI agent to draft the first pass of a test suite and then reviewing it like an editor, not accepting it blindly. Codegen and UI Mode also made debugging locators far less painful than the XPath guesswork I was used to. My interviewer at Publicis Sapient had never even heard of half of this.”
🎓 SDET — Playwright, JS & TS with AI
“
M
Meera Ramachandran
QA Automation Lead
🏢 Virtusa
★★★★★
“Solid, thorough course — the CI/CD module wiring Playwright into GitHub Actions with Docker containers is exactly what I run day to day now at Virtusa. Only reason it is not a full five stars is I wish the AI visual-testing module had gone a bit deeper, but everything else more than made up for it.”
🎓 SDET — Playwright, JS & TS with AI
TOOLS & SKILLS
Tools and skills covered
Java
Selenium
TestNG
Postman
Git
Jenkins
JMeter
SQL
🏆
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.
AI, ML & Soft Skills — Complete Career Accelerator
A complete AI/ML Engineer flagship program covering Python and statistical foundations, classical machine learning with scikit-learn, XGBoost and LightGBM, deep learning with PyTorch, the full LLM/GenAI engineering stack (Hugging Face, LangChain, LlamaIndex, fine-tuning, end-to-end RAG pipeline design), vector databases (Pinecone, Weaviate, Chroma, Milvus), MLOps (FastAPI, Docker, Kubernetes, MLflow, Airflow, ONNX), AI agent frameworks (LangGraph, AutoGen, CrewAI, MCP) and responsible AI — folded together with professional communication, behavioral interview mastery and resume/portfolio building, so technical depth and interview readiness are built in one program instead of two.
PythonNumPypandasscikit-learnXGBoost+19 more
15% OFF Flagship AI/ML program
AI, ML & Soft Skills
Soft Skills & Interview Readiness Add-On
A focused Soft Skills & Interview Readiness program covering professional communication for technical roles, group discussion and aptitude fundamentals, the STAR method for behavioral interviews, body language and virtual-interview presence, salary negotiation and offer evaluation, workplace professionalism, and resume/LinkedIn optimization — anchored by a mock interview tailored to your own track (developer, tester or cloud/DevOps), not a generic HR-round rehearsal. Designed to work equally well as a standalone short course or as an add-on graduates of other Fourcup tracks bolt onto their main course.
Zoom/Google MeetSlackLinkedInResume templates
22% OFF Standalone or add-on
AI, ML & Soft Skills
AI & GenAI Add-On — Practical AI Skills for Tech Professionals
Works two ways: as a standalone short course in practical AI/GenAI literacy, or as an add-on for graduates of Fourcup's testing, development or cloud/DevOps tracks who want to layer AI skills onto their main course. Covers what LLMs are and aren't, prompt engineering, evaluating AI output critically, using AI coding/testing/ops assistants day to day, RAG (embeddings, vector databases), calling LLM APIs with streaming and tool-calling, a beginner-level intro to AI agents (LangGraph, AutoGen, CrewAI, MCP), and responsible AI use — scoped for practical fluency, not full ML engineering depth.
ChatGPTClaudeGeminiGitHub CopilotClaude Code+10 more
20% OFF Add-on ready
CURRICULUM
Module by module
Open any module to see exactly what it covers. Nothing is hidden behind a "download the syllabus" form.
9.5 Weeks
DURATION
11
MODULES
1
REAL-TIME PROJECTS
5
MOCK INTERVIEWS
➜
ACCELERATOR
Package 1 — Automation + AI Accelerator
⏱ 9.5 Weeks★ 4.8
11 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
⏱ 16 Weeks★ 4.9
12 modules
➜
CUSTOM
Package 5 — Build Your Own (Customized)
⏱ Variable★ 4.8
0 modules
➜
1JavaScript Fundamentals for TestersWeekday 1.5 wks · Weekend 2.5 wks▾
Topic
What 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.
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.
Topic
What 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.
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.
Topic
What 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.
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.
Topic
What 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.
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.
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.
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.
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.
Topic
What 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.
7Generative AI for Software TestingWeekday 1 wk · Weekend 1.5 wks▾
Topic
What 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.
Topic
What 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.
A 2026 shift: testers are expected to verify resilience under deliberate failure, not just correctness under normal conditions.
2.Chaos Engineering Tools
Gremlin, Chaos Monkey, LitmusChaos, Chaos Mesh, and AWS Fault Injection Simulator — what each is built for and when a team reaches for it.
3.Designing a Chaos Experiment
Forming a hypothesis, picking a blast radius, and running a controlled failure-injection test against a staging environment.
3.1)Real-world scenario
Killing a pod mid-checkout with Chaos Mesh and asserting the UI degrades gracefully instead of hanging or corrupting an order. • Using AWS Fault Injection Simulator to simulate an AZ outage and verifying failover behavior end-to-end.
4.OpenTelemetry for Testers
Reading distributed traces and spans to debug a test failure that has no useful error message on its own.
4.1)Why this module exists
When a Playwright test fails against a microservices backend, the real cause is often three services away from the assertion that failed; trace data finds it in minutes instead of hours.
4.2)Tracing a flaky test to its root service
Correlating a failed assertion's timestamp with an OpenTelemetry trace to find the actual slow or failing downstream call.
5.Accessibility Testing at Scale
Integrating axe-core into a Playwright suite so WCAG conformance is checked automatically on every run, not manually before a release.
5.1)Building on ARIA Snapshots
Combining axe-core's automated ruleset with the ARIA-tree assertions from Playwright Fundamentals for a genuinely layered accessibility check.
Topic
What You'll Learn
1.Why Chaos Engineering Now Matters for QA
A 2026 shift: testers are expected to verify resilience under deliberate failure, not just correctness under normal conditions.
2.Chaos Engineering Tools
Gremlin, Chaos Monkey, LitmusChaos, Chaos Mesh, and AWS Fault Injection Simulator — what each is built for and when a team reaches for it.
3.Designing a Chaos Experiment
Forming a hypothesis, picking a blast radius, and running a controlled failure-injection test against a staging environment.
3.1)Real-world scenario
Killing a pod mid-checkout with Chaos Mesh and asserting the UI degrades gracefully instead of hanging or corrupting an order.
Using AWS Fault Injection Simulator to simulate an AZ outage and verifying failover behavior end-to-end.
4.OpenTelemetry for Testers
Reading distributed traces and spans to debug a test failure that has no useful error message on its own.
4.1)Why this module exists
When a Playwright test fails against a microservices backend, the real cause is often three services away from the assertion that failed; trace data finds it in minutes instead of hours.
4.2)Tracing a flaky test to its root service
Correlating a failed assertion's timestamp with an OpenTelemetry trace to find the actual slow or failing downstream call.
5.Accessibility Testing at Scale
Integrating axe-core into a Playwright suite so WCAG conformance is checked automatically on every run, not manually before a release.
5.1)Building on ARIA Snapshots
Combining axe-core's automated ruleset with the ARIA-tree assertions from Playwright Fundamentals for a genuinely layered accessibility check.
10Capstone ProjectWeekday 1 wk · Weekend 1.5 wks▾
Topic
What 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.
Topic
What 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.
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.
Topic
What 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.
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.
Topic
What 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.
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.
Topic
What 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.
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.
Topic
What 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.
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.
Topic
What 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.
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.
Topic
What 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.
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.
Topic
What 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.
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.
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.
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.
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.
Topic
What 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.
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.
Topic
What 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.
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.
Topic
What 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.
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.
Topic
What 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.
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.
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.
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.
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.
Topic
What 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.
8Generative AI for Software TestingWeekday 1.5 wks · Weekend 2.5 wks▾
Topic
What 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.
Topic
What 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.
A 2026 shift: testers are expected to verify resilience under deliberate failure, not just correctness under normal conditions.
2.Chaos Engineering Tools
Gremlin, Chaos Monkey, LitmusChaos, Chaos Mesh, and AWS Fault Injection Simulator — what each is built for and when a team reaches for it.
3.Designing a Chaos Experiment
Forming a hypothesis, picking a blast radius, and running a controlled failure-injection test against a staging environment.
3.1)Real-world scenario
Killing a pod mid-checkout with Chaos Mesh and asserting the UI degrades gracefully instead of hanging or corrupting an order. • Using AWS Fault Injection Simulator to simulate an AZ outage and verifying failover behavior end-to-end.
4.OpenTelemetry for Testers
Reading distributed traces and spans to debug a test failure that has no useful error message on its own.
4.1)Why this module exists
When a Playwright test fails against a microservices backend, the real cause is often three services away from the assertion that failed; trace data finds it in minutes instead of hours.
4.2)Tracing a flaky test to its root service
Correlating a failed assertion's timestamp with an OpenTelemetry trace to find the actual slow or failing downstream call.
5.Accessibility Testing at Scale
Integrating axe-core into a Playwright suite so WCAG conformance is checked automatically on every run, not manually before a release.
5.1)Building on ARIA Snapshots
Combining axe-core's automated ruleset with the ARIA-tree assertions from Playwright Fundamentals for a genuinely layered accessibility check.
Topic
What You'll Learn
1.Why Chaos Engineering Now Matters for QA
A 2026 shift: testers are expected to verify resilience under deliberate failure, not just correctness under normal conditions.
2.Chaos Engineering Tools
Gremlin, Chaos Monkey, LitmusChaos, Chaos Mesh, and AWS Fault Injection Simulator — what each is built for and when a team reaches for it.
3.Designing a Chaos Experiment
Forming a hypothesis, picking a blast radius, and running a controlled failure-injection test against a staging environment.
3.1)Real-world scenario
Killing a pod mid-checkout with Chaos Mesh and asserting the UI degrades gracefully instead of hanging or corrupting an order.
Using AWS Fault Injection Simulator to simulate an AZ outage and verifying failover behavior end-to-end.
4.OpenTelemetry for Testers
Reading distributed traces and spans to debug a test failure that has no useful error message on its own.
4.1)Why this module exists
When a Playwright test fails against a microservices backend, the real cause is often three services away from the assertion that failed; trace data finds it in minutes instead of hours.
4.2)Tracing a flaky test to its root service
Correlating a failed assertion's timestamp with an OpenTelemetry trace to find the actual slow or failing downstream call.
5.Accessibility Testing at Scale
Integrating axe-core into a Playwright suite so WCAG conformance is checked automatically on every run, not manually before a release.
5.1)Building on ARIA Snapshots
Combining axe-core's automated ruleset with the ARIA-tree assertions from Playwright Fundamentals for a genuinely layered accessibility check.
“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
“
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
“
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
“
S
Sanjay Venkataraman
Automation Test Engineer
🏢 Publicis Sapient
★★★★★
“What sold me was the Playwright MCP Server module — using an AI agent to draft the first pass of a test suite and then reviewing it like an editor, not accepting it blindly. Codegen and UI Mode also made debugging locators far less painful than the XPath guesswork I was used to. My interviewer at Publicis Sapient had never even heard of half of this.”
🎓 SDET — Playwright, JS & TS with AI
“
M
Meera Ramachandran
QA Automation Lead
🏢 Virtusa
★★★★★
“Solid, thorough course — the CI/CD module wiring Playwright into GitHub Actions with Docker containers is exactly what I run day to day now at Virtusa. Only reason it is not a full five stars is I wish the AI visual-testing module had gone a bit deeper, but everything else more than made up for it.”
AI, ML & Soft Skills — Complete Career Accelerator
A complete AI/ML Engineer flagship program covering Python and statistical foundations, classical machine learning with scikit-learn, XGBoost and LightGBM, deep learning with PyTorch, the full LLM/GenAI engineering stack (Hugging Face, LangChain, LlamaIndex, fine-tuning, end-to-end RAG pipeline design), vector databases (Pinecone, Weaviate, Chroma, Milvus), MLOps (FastAPI, Docker, Kubernetes, MLflow, Airflow, ONNX), AI agent frameworks (LangGraph, AutoGen, CrewAI, MCP) and responsible AI — folded together with professional communication, behavioral interview mastery and resume/portfolio building, so technical depth and interview readiness are built in one program instead of two.
PythonNumPypandasscikit-learnXGBoost+19 more
15% OFF Flagship AI/ML program
AI, ML & Soft Skills
Soft Skills & Interview Readiness Add-On
A focused Soft Skills & Interview Readiness program covering professional communication for technical roles, group discussion and aptitude fundamentals, the STAR method for behavioral interviews, body language and virtual-interview presence, salary negotiation and offer evaluation, workplace professionalism, and resume/LinkedIn optimization — anchored by a mock interview tailored to your own track (developer, tester or cloud/DevOps), not a generic HR-round rehearsal. Designed to work equally well as a standalone short course or as an add-on graduates of other Fourcup tracks bolt onto their main course.
Zoom/Google MeetSlackLinkedInResume templates
22% OFF Standalone or add-on
AI, ML & Soft Skills
AI & GenAI Add-On — Practical AI Skills for Tech Professionals
Works two ways: as a standalone short course in practical AI/GenAI literacy, or as an add-on for graduates of Fourcup's testing, development or cloud/DevOps tracks who want to layer AI skills onto their main course. Covers what LLMs are and aren't, prompt engineering, evaluating AI output critically, using AI coding/testing/ops assistants day to day, RAG (embeddings, vector databases), calling LLM APIs with streaming and tool-calling, a beginner-level intro to AI agents (LangGraph, AutoGen, CrewAI, MCP), and responsible AI use — scoped for practical fluency, not full ML engineering depth.
ChatGPTClaudeGeminiGitHub CopilotClaude Code+10 more
20% OFF Add-on ready
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 experienceActive practitioner
SUCCESS STORIES
Our Students Excelling Worldwide
“
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
“
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
“
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
“
S
Sanjay Venkataraman
Automation Test Engineer
🏢 Publicis Sapient
★★★★★
“What sold me was the Playwright MCP Server module — using an AI agent to draft the first pass of a test suite and then reviewing it like an editor, not accepting it blindly. Codegen and UI Mode also made debugging locators far less painful than the XPath guesswork I was used to. My interviewer at Publicis Sapient had never even heard of half of this.”
🎓 SDET — Playwright, JS & TS with AI
“
M
Meera Ramachandran
QA Automation Lead
🏢 Virtusa
★★★★★
“Solid, thorough course — the CI/CD module wiring Playwright into GitHub Actions with Docker containers is exactly what I run day to day now at Virtusa. Only reason it is not a full five stars is I wish the AI visual-testing module had gone a bit deeper, but everything else more than made up for it.”
AI, ML & Soft Skills — Complete Career Accelerator
A complete AI/ML Engineer flagship program covering Python and statistical foundations, classical machine learning with scikit-learn, XGBoost and LightGBM, deep learning with PyTorch, the full LLM/GenAI engineering stack (Hugging Face, LangChain, LlamaIndex, fine-tuning, end-to-end RAG pipeline design), vector databases (Pinecone, Weaviate, Chroma, Milvus), MLOps (FastAPI, Docker, Kubernetes, MLflow, Airflow, ONNX), AI agent frameworks (LangGraph, AutoGen, CrewAI, MCP) and responsible AI — folded together with professional communication, behavioral interview mastery and resume/portfolio building, so technical depth and interview readiness are built in one program instead of two.
PythonNumPypandasscikit-learnXGBoost+19 more
15% OFF Flagship AI/ML program
AI, ML & Soft Skills
Soft Skills & Interview Readiness Add-On
A focused Soft Skills & Interview Readiness program covering professional communication for technical roles, group discussion and aptitude fundamentals, the STAR method for behavioral interviews, body language and virtual-interview presence, salary negotiation and offer evaluation, workplace professionalism, and resume/LinkedIn optimization — anchored by a mock interview tailored to your own track (developer, tester or cloud/DevOps), not a generic HR-round rehearsal. Designed to work equally well as a standalone short course or as an add-on graduates of other Fourcup tracks bolt onto their main course.
Zoom/Google MeetSlackLinkedInResume templates
22% OFF Standalone or add-on
AI, ML & Soft Skills
AI & GenAI Add-On — Practical AI Skills for Tech Professionals
Works two ways: as a standalone short course in practical AI/GenAI literacy, or as an add-on for graduates of Fourcup's testing, development or cloud/DevOps tracks who want to layer AI skills onto their main course. Covers what LLMs are and aren't, prompt engineering, evaluating AI output critically, using AI coding/testing/ops assistants day to day, RAG (embeddings, vector databases), calling LLM APIs with streaming and tool-calling, a beginner-level intro to AI agents (LangGraph, AutoGen, CrewAI, MCP), and responsible AI use — scoped for practical fluency, not full ML engineering depth.
ChatGPTClaudeGeminiGitHub CopilotClaude Code+10 more
20% OFF Add-on ready
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
“
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
“
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
“
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
“
S
Sanjay Venkataraman
Automation Test Engineer
🏢 Publicis Sapient
★★★★★
“What sold me was the Playwright MCP Server module — using an AI agent to draft the first pass of a test suite and then reviewing it like an editor, not accepting it blindly. Codegen and UI Mode also made debugging locators far less painful than the XPath guesswork I was used to. My interviewer at Publicis Sapient had never even heard of half of this.”
🎓 SDET — Playwright, JS & TS with AI
“
M
Meera Ramachandran
QA Automation Lead
🏢 Virtusa
★★★★★
“Solid, thorough course — the CI/CD module wiring Playwright into GitHub Actions with Docker containers is exactly what I run day to day now at Virtusa. Only reason it is not a full five stars is I wish the AI visual-testing module had gone a bit deeper, but everything else more than made up for it.”
AI, ML & Soft Skills — Complete Career Accelerator
A complete AI/ML Engineer flagship program covering Python and statistical foundations, classical machine learning with scikit-learn, XGBoost and LightGBM, deep learning with PyTorch, the full LLM/GenAI engineering stack (Hugging Face, LangChain, LlamaIndex, fine-tuning, end-to-end RAG pipeline design), vector databases (Pinecone, Weaviate, Chroma, Milvus), MLOps (FastAPI, Docker, Kubernetes, MLflow, Airflow, ONNX), AI agent frameworks (LangGraph, AutoGen, CrewAI, MCP) and responsible AI — folded together with professional communication, behavioral interview mastery and resume/portfolio building, so technical depth and interview readiness are built in one program instead of two.
PythonNumPypandasscikit-learnXGBoost+19 more
15% OFF Flagship AI/ML program
AI, ML & Soft Skills
Soft Skills & Interview Readiness Add-On
A focused Soft Skills & Interview Readiness program covering professional communication for technical roles, group discussion and aptitude fundamentals, the STAR method for behavioral interviews, body language and virtual-interview presence, salary negotiation and offer evaluation, workplace professionalism, and resume/LinkedIn optimization — anchored by a mock interview tailored to your own track (developer, tester or cloud/DevOps), not a generic HR-round rehearsal. Designed to work equally well as a standalone short course or as an add-on graduates of other Fourcup tracks bolt onto their main course.
Zoom/Google MeetSlackLinkedInResume templates
22% OFF Standalone or add-on
AI, ML & Soft Skills
AI & GenAI Add-On — Practical AI Skills for Tech Professionals
Works two ways: as a standalone short course in practical AI/GenAI literacy, or as an add-on for graduates of Fourcup's testing, development or cloud/DevOps tracks who want to layer AI skills onto their main course. Covers what LLMs are and aren't, prompt engineering, evaluating AI output critically, using AI coding/testing/ops assistants day to day, RAG (embeddings, vector databases), calling LLM APIs with streaming and tool-calling, a beginner-level intro to AI agents (LangGraph, AutoGen, CrewAI, MCP), and responsible AI use — scoped for practical fluency, not full ML engineering depth.
ChatGPTClaudeGeminiGitHub CopilotClaude Code+10 more
20% OFF Add-on ready
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
“
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
“
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
“
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
“
S
Sanjay Venkataraman
Automation Test Engineer
🏢 Publicis Sapient
★★★★★
“What sold me was the Playwright MCP Server module — using an AI agent to draft the first pass of a test suite and then reviewing it like an editor, not accepting it blindly. Codegen and UI Mode also made debugging locators far less painful than the XPath guesswork I was used to. My interviewer at Publicis Sapient had never even heard of half of this.”
🎓 SDET — Playwright, JS & TS with AI
“
M
Meera Ramachandran
QA Automation Lead
🏢 Virtusa
★★★★★
“Solid, thorough course — the CI/CD module wiring Playwright into GitHub Actions with Docker containers is exactly what I run day to day now at Virtusa. Only reason it is not a full five stars is I wish the AI visual-testing module had gone a bit deeper, but everything else more than made up for it.”
AI, ML & Soft Skills — Complete Career Accelerator
A complete AI/ML Engineer flagship program covering Python and statistical foundations, classical machine learning with scikit-learn, XGBoost and LightGBM, deep learning with PyTorch, the full LLM/GenAI engineering stack (Hugging Face, LangChain, LlamaIndex, fine-tuning, end-to-end RAG pipeline design), vector databases (Pinecone, Weaviate, Chroma, Milvus), MLOps (FastAPI, Docker, Kubernetes, MLflow, Airflow, ONNX), AI agent frameworks (LangGraph, AutoGen, CrewAI, MCP) and responsible AI — folded together with professional communication, behavioral interview mastery and resume/portfolio building, so technical depth and interview readiness are built in one program instead of two.
PythonNumPypandasscikit-learnXGBoost+19 more
15% OFF Flagship AI/ML program
AI, ML & Soft Skills
Soft Skills & Interview Readiness Add-On
A focused Soft Skills & Interview Readiness program covering professional communication for technical roles, group discussion and aptitude fundamentals, the STAR method for behavioral interviews, body language and virtual-interview presence, salary negotiation and offer evaluation, workplace professionalism, and resume/LinkedIn optimization — anchored by a mock interview tailored to your own track (developer, tester or cloud/DevOps), not a generic HR-round rehearsal. Designed to work equally well as a standalone short course or as an add-on graduates of other Fourcup tracks bolt onto their main course.
Zoom/Google MeetSlackLinkedInResume templates
22% OFF Standalone or add-on
AI, ML & Soft Skills
AI & GenAI Add-On — Practical AI Skills for Tech Professionals
Works two ways: as a standalone short course in practical AI/GenAI literacy, or as an add-on for graduates of Fourcup's testing, development or cloud/DevOps tracks who want to layer AI skills onto their main course. Covers what LLMs are and aren't, prompt engineering, evaluating AI output critically, using AI coding/testing/ops assistants day to day, RAG (embeddings, vector databases), calling LLM APIs with streaming and tool-calling, a beginner-level intro to AI agents (LangGraph, AutoGen, CrewAI, MCP), and responsible AI use — scoped for practical fluency, not full ML engineering depth.
ChatGPTClaudeGeminiGitHub CopilotClaude Code+10 more
20% OFF Add-on ready
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
🎓
Fourcup Schools
💚 Typically replies in minutes
Fill in your details and we'll start a WhatsApp chat for you
We use cookies to run this site and, with your permission, for analytics and marketing. You can change your choice anytime from the footer. Cookie Policy
