Course hub · Draft
Software Testing with AI Automation
Learn to write clear cases and automate them with Playwright. Volume 1 ends at page objects; AI chapters follow.
Who this is for
Freshers aiming for QA/SDET roles in India, and developers who want to test their own features without jargon overload.
What you will build
A small Playwright project with login-style flows, solid locators, and a LoginPage object. AI test-gen comes after this preview.
How to use this path
Read in order. Practise on apps you own or public demos. Do not attack third-party sites. Enquire for live batches — no fees listed here.
Chapters
- Chapter 01
What Is Software Testing (Manual vs Automation)
Testing is checking that software does what users need — and fails safely when it should.
- Chapter 02
Test Cases and Bug Reports in Plain English
A good test case is a recipe. A good bug report is a story someone can replay.
- Chapter 03
Black Box vs White Box (Simple)
Black box = you cannot see the code. White box = you can. Most UI testing starts black box.
- Chapter 04
First Automation with Playwright
Playwright is the primary tool on this path: one install, Chromium, and clear docs.
- Chapter 05
Locators, Assertions and Waits
Flaky tests usually mean weak locators or missing waits — not “Playwright is bad”.
- Chapter 06
Page Object Idea for Beginners
Page objects keep selectors in one place so a UI change does not break twenty files.
FAQ
Playwright or Selenium?
This path uses Playwright as primary. Selenium skills still transfer; we may add a bridge chapter later.
Do I need coding?
Basic JavaScript/TypeScript helps. Chapter 4 starts from install with copy-friendly examples.
When does AI enter?
After Volume 1 — generating cases and reviewing AI tests safely. Humans still own quality.