Programme objective: You design tests from a requirement, write the expected business result first, and build a reusable Playwright framework for the user interface and the application programming interface, with an execution and a report.
Learner path: Fundamentals, test design, AI test design, unit, integration, API, UI automation, end-to-end, the framework, contract testing, testing agents, then CI test integration. The surrounding gates are on Complete AI-Native SDLC Engineering.
Suggested time inside the pathway is 35 hours, within a 16-week professional programme of about 160 to 200 hours. That shape is subject to batch and faculty planning. The cohort and any certificate are confirmed when you enquire. This page does not state fees, batch dates, faculty names, or placement rates.
Module 1 — Testing fundamentals
You separate a requirement, a condition, an expected result, and an observation, and you say which of those an assistant is not allowed to decide.
Module 2 — Test design
You design a small set of cases from the requirement, each with a reason, covering the ordinary path, a missing input, and a value outside the allowed range.
Module 3 — AI test design
You may ask an assistant for candidate cases, then you keep, drop, or rewrite each one against the expected result you wrote first.
Module 4 — Unit testing
You write unit tests in pytest, Jest, JUnit, NUnit, or xUnit for the behaviour you own, and you can point each assertion at the requirement.
Module 5 — Integration testing
You check two parts that meet, record what you sent between them, and refuse a pass that only shows one part in isolation.
Module 6 — API testing
You exercise the application programming interface with Postman, Newman, or REST Assured, including status, body, and a token the exercise already allows.
Module 7 — UI automation
You automate a screen journey and keep the expected business result stable. Self-healing automation must not change the expected business result just to make a test pass.
Module 8 — End-to-end testing
You run a journey a person would recognise, from the first step to the outcome the requirement names, and you record what a person must still judge.
Module 9 — Automation framework
You build a reusable Playwright framework for UI and API, with execution and a report a classmate can open without your machine.
Module 10 — Contract testing
You check that the consumer and the provider still agree on the contract, and you fail the check when the response drifts from that agreement.
Module 11 — AI testing agents
You let an agent propose a case or a locator, then you accept it only when the expected business result is unchanged and you can explain the step.
Module 12 — CI test integration
You run the framework in continuous integration, publish the report, and treat a failed mandatory test as a stop until a person has seen it.
Playwright laboratory
In words, the laboratory covers Chromium, Firefox, and WebKit; locators; login, registration, CRUD, and transaction journeys; screenshot, video, and trace viewer; cross-browser and responsive checks; API request context; token handling; UI plus API flows; parallel runs and retries; reports and CI/CD. You also meet Selenium, Jira, TestRail, JaCoCo, Coverage.py, and Allure as named tools in the same programme.
The code you own is AI-Native Software Engineering and Development. Load, stress, and a controlled failure are AI-Driven Performance and Chaos Engineering. Authorised defensive testing is AI-Powered Application, API and LLM Security Testing.
