Lesson 1Putting automation first: which tests to automate first (API, critical flows, regression), why, and rules for automation ROIThis part explains how to choose tests for automation, looking at APIs, important user paths, and regression sets, and sets rules for automation value, keeping up, and cutting risk to guide spending choices.
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 blocking and test exit rules linked to acceptance criteria and metricsThis part sets release blocking and test exit rules, showing how to link dem to acceptance criteria, risk, and metrics like defect rates, coverage, and speed so release choices clear and based on proof.
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: linking requirements to tests and reporting coverageThis part covers linking requirements to tests, including making and keeping link tables, joining tests to user stories and risks, and reporting gaps in coverage that help planning and release choices.
Creating a lightweight traceability matrixLinking user stories, risks, and test casesTraceability in agile tools and test managementMeasuring coverage beyond simple countsIdentifying and prioritizing coverage gapsUsing traceability in audits and complianceLesson 4Types of testing needed: functional, regression, smoke/sanity, E2E, performance/load/stress, security, accessibility, cross-browser and responsive, localization and data validationThis part lists needed test types for web apps, including functional, regression, smoke, end to end, performance, security, accessibility, cross browser, responsive, localization, and data checking, with advice on when to use 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 testsLocalization and data validation considerationsLesson 5Manual testing strategy: exploratory, usability, ad-hoc, session-based testing, edge case validationThis part looks at manual testing ways that help automation, including exploratory, usability, ad hoc, and session-based testing, plus ways to find edge cases and write good test notes and plans.
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 virtualization for third-party payments and real-time channelsThis part details how to make and handle web test places, including staging setups, real but hidden data, and service faking for third party payments and real time channels to allow safe, repeatable testing.
Designing staging to mirror production risksStrategies for synthetic and masked test dataManaging environment configuration and driftService virtualization for payment gatewaysSimulating real time channels and webhooksMonitoring environment health and availabilityLesson 7Test automation strategy: choosing frameworks, test pyramid, CI/CD linking, test data and environment handlingThis part sets a lasting automation way for web apps, covering framework choice, the test pyramid, CI/CD linking, and strong ways for test data and place handling that keep sets fast, steady, and easy to keep.
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, anonymizationStabilizing flaky tests and handling async behaviorVersioning tests alongside application codeLesson 8Overview of test strategy parts: scope, levels, types, environments, schedule, rolesThis part breaks down main parts of test strategy, including scope, levels, types, places, timing, and roles, and shows how to write dem clear so teams share same understanding of quality aims.
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 sharing for a beta timelineThis part explains how to time testing work and share people, places, and tools over beta timeline, balancing risk, scope, and limits while keeping stakeholders in the know with real, data-based 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 part explains each testing level for web systems—unit, integration, component, system, and end to end—making clear goals, owners, example outputs, and how levels work together for 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 behaviorEnd-to-end tests for critical user journeysChoosing ownership and tooling per level
