Lesson 1Prioritisation for automation: which tests to automate first (API, critical flows, regression), why, and criteria for automation ROIThis section explains how to prioritise tests for automation, focusing on APIs, critical user flows, and regression suites, and defines criteria for automation ROI, maintainability, and risk reduction to guide investment decisions wisely.
Identifying high value candidates for automationAutomating API tests before complex UI flowsAutomating critical paths and happy day journeysBuilding a stable regression automation backboneCalculating and tracking automation ROIDeciding when not to automate a testLesson 2Release gating and test exit criteria tied to acceptance criteria and metricsThis section defines release gating and test exit criteria, showing how to tie them to acceptance criteria, risk, and metrics such as defect rates, coverage, and performance so release decisions are transparent and evidence based.
Defining clear entry and exit criteriaLinking exit criteria to acceptance criteriaQuality metrics for go or no-go decisionsDefect severity thresholds and open bug limitsHandling risk-based exceptions and waiversDocumenting release decisions and sign-offsLesson 3Traceability: mapping requirements to tests and reporting coverageThis section covers requirements to test traceability, including building and maintaining traceability matrices, linking tests to user stories and risks, and reporting coverage gaps that inform planning and release decisions accurately.
Creating a lightweight traceability matrixLinking user stories, risks, and test casesTraceability in agile tools and test managementMeasuring coverage beyond simple countsIdentifying and prioritising coverage gapsUsing traceability in audits and complianceLesson 4Types of testing required: functional, regression, smoke/sanity, E2E, performance/load/stress, security, accessibility, cross-browser and responsive, localisation and data validationThis section outlines required test types for web apps, including functional, regression, smoke, end to end, performance, security, accessibility, cross browser, responsive, localisation, and data validation, with guidance on when to apply each.
Functional and regression suites for core flowsSmoke and sanity checks for rapid feedbackPerformance, load, and stress test objectivesSecurity testing for common web vulnerabilitiesAccessibility, cross-browser, and responsive testsLocalisation and data validation considerationsLesson 5Manual testing strategy: exploratory, usability, ad-hoc, session-based testing, edge case validationThis section focuses on manual testing strategies that complement automation, including exploratory, usability, ad hoc, and session-based testing, plus techniques for uncovering edge cases and capturing high quality test notes and charters.
Planning and structuring exploratory test chartersHeuristics and tours for discovering hidden defectsUsability evaluation for web flows and UI patternsSession-based test management and note takingAd hoc testing for quick risk probes and spikesDesigning edge case scenarios and boundary checksLesson 6Test environments, staging setup, data masking, service virtualisation for third-party payments and real-time channelsThis section details how to design and manage web test environments, including staging setups, realistic but masked data, and service virtualisation for third party payments and real time channels to enable safe, repeatable testing.
Designing staging to mirror production risksStrategies for synthetic and masked test dataManaging environment configuration and driftService virtualisation for payment gatewaysSimulating real time channels and webhooksMonitoring environment health and availabilityLesson 7Test automation strategy: selecting frameworks, test pyramid, CI/CD integration, test data and environment managementThis section defines a sustainable automation strategy for web apps, covering framework selection, the test pyramid, CI/CD integration, and robust approaches to test data and environment management that keep suites fast, stable, and maintainable.
Criteria for selecting UI and API automation frameworksDesigning a maintainable test pyramid for web productsIntegrating automated tests into CI/CD pipelinesManaging test data: seeding, factories, anonymisationStabilising flaky tests and handling async behaviourVersioning tests alongside application codeLesson 8Overview of test strategy components: scope, levels, types, environments, schedule, rolesThis section breaks down the core components of a test strategy, including scope, levels, types, environments, schedule, and roles, and shows how to document them clearly so teams share a common understanding of quality goals.
Defining in-scope and out-of-scope featuresSelecting appropriate test levels for each layerChoosing test types based on product risksPlanning environments and required configurationsDocumenting roles, ownership, and RACI chartsMaintaining and versioning the strategy documentLesson 9Test scheduling and resource allocation for a beta timelineThis section explains how to schedule testing activities and allocate people, environments, and tools across a beta timeline, balancing risk, scope, and constraints while keeping stakeholders informed with realistic, data driven plans.
Defining testing phases within a beta timelineEstimating effort using risk and complexityAllocating testers, tools, and environmentsAligning test milestones with release milestonesBuffers, contingencies, and handling slippageCommunicating schedule and changes to stakeholdersLesson 10Testing levels: unit, integration, component, system, end-to-end — goals and example deliverables for eachThis section explains each testing level for web systems—unit, integration, component, system, and end to end—clarifying goals, ownership, example deliverables, and how levels interact to provide layered quality feedback.
Unit tests: scope, isolation, and code contractsIntegration tests for services and data layersComponent tests for UI widgets and modulesSystem tests for full web application behaviourEnd-to-end tests for critical user journeysChoosing ownership and tooling per level
