MODERN TEST AUTOMATION BOOTCAMP
Build production-style test automation using Playwright • TypeScript • APIs • Git • GitHub Actions • AI. Then prove it with three practical projects and a portfolio-ready automation framework.
£199 · Lifetime access
Built for testers ready to move into automation and engineers ready to modernise — and to walk away with evidence, not just a certificate.
Moving into automation and wanting to do it properly from the start.
Levelling up to a modern, maintainable automation toolset.
Modernising onto Playwright, TypeScript and CI-first workflows.
Building portfolio evidence that proves what you can actually do.
Design, build, debug, maintain and integrate a production-style Playwright framework — with TypeScript, APIs, Git, CI/CD and AI.
Sixteen modules that build from an engineering mindset to a complete, production-style automation framework.
What automation is actually for, what to automate and what to leave manual, the real cost of bad automation, and the engineering mindset that separates automators from tutorial-followers.
Just enough TypeScript to write clean, typed Playwright tests: types and interfaces, functions and modules, async/await, and the everyday patterns you will actually use.
Branching, commits, pull requests and code review — how real teams collaborate on a shared test codebase without stepping on each other.
Installing and configuring Playwright, the test runner, locators, actions and web-first assertions, and the config that underpins everything else.
Test design for automation: what a test should assert, meaningful versus weak assertions, and why a green test is not automatically a good test.
Auto-waiting, web-first assertions, the real causes of flakiness, and how to build tests that stay green for the right reasons.
Page objects, fixtures, components and project structure — designing a maintainable framework without over-engineering it.
Logging in once and reusing storage state, handling multiple roles, and creating and cleaning up test data so tests own their own state.
Testing REST APIs with Playwright's request context, asserting status and payloads, and using API calls to set up and verify state for UI tests.
Intercepting, stubbing and mocking network traffic to test edge cases, isolate the UI and control flaky third-party dependencies.
Browser projects, parallel execution and sharding — keeping a large suite fast, trustworthy and cheap to run.
Running the suite automatically on every push: workflows, browsers in CI, artifacts and reports, and using automation as a real quality gate.
Reporters, traces, screenshots and video; debugging failures fast, and keeping a suite healthy and trusted over time.
Using AI coding assistants as an engineering tool — pair-programming, generation, debugging and refactoring — and rigorously reviewing what they produce for hallucinations, weak assertions and security risks.
How automation fits a delivery team: what to automate for a story, code review, shared ownership, and communicating quality and risk to the people who make release decisions.
Independently build a complete, production-style automation repository — UI, API, fixtures, auth, data, CI/CD, reporting and a README — that brings the whole programme together as portfolio evidence.
The exact stack real automation teams use today — learned together, the way they fit together in production.
The modern test runner: locators, web-first assertions, fixtures, tracing and cross-browser projects.
Clean, typed test code — types, interfaces, modules and async/await used the way real frameworks use them.
Playwright's request context for REST APIs: asserting payloads and setting up state without the UI.
Branches, pull requests and code review, then running the suite as a real CI quality gate on every push.
AI coding assistants as an engineering tool — generate, debug and refactor, then rigorously review the output.
You do not just read about automation — you build it three times, each one closer to the real thing.
Project 1
Build a reliable UI automation suite with Playwright and TypeScript: solid locators, meaningful assertions and page objects that stay maintainable.
Project 2
Combine UI and API automation with authentication, test data and network control, then wire it into GitHub Actions so it runs on every push.
Project 3
Independently build a complete, production-style automation repository — UI, API, fixtures, auth, data, CI/CD, reporting and a README — as portfolio evidence.
You finish with a public, portfolio-ready automation framework and a certificate — real evidence you can point an employer to.
Complete the modules, labs and projects to earn your Inside STLC Academy Modern Test Automation Bootcamp Certificate of Completion — with your name, completion date, and a unique certificate ID.
Lifetime access
No prior automation experience is assumed. The bootcamp starts from the fundamentals and includes a dedicated TypeScript module, so you build the coding foundations as you go. Some familiarity with testing helps, but you do not need to be a developer.
No. Playwright is taught from installation and configuration upward, then built on across the whole programme.
No — that is the point. You build real automation through 12 hands-on labs and three practical projects, then prove it with a production-style framework you own.
Yes. You finish with a portfolio-ready automation framework in a public GitHub repository — UI, API, CI/CD, reporting and a README — that you can genuinely link on your CV and talk through in an interview.
As an engineering tool, not a shortcut. You learn to use AI assistants to generate, debug and refactor, and — just as importantly — to review what they produce for hallucinations, weak assertions and security risks.
Lifetime access. Enrol once and revisit the modules, labs and resources whenever you need them.
Yes — the Inside STLC Academy Modern Test Automation Bootcamp Certificate of Completion, awarded when you finish the course activities. It is not an externally accredited qualification.
Join Inside STLC Academy and finish with a production-style Playwright framework you own — and can prove.