Devising a Project Test Approach
summary
Starts at project initiation, scans impact docs, and produces a one‑page A3 test approach within hours then refines over two weeks; chooses tests by risk not completeness — skip heavy performance testing for a 70‑user timesheet app but plan it for a 250,000‑user NHS scale; drafts about 20 UAT checks for simple verification, uses Oracle farm lift and shift as a real example, embeds a senior tester with poor suppliers, requires factory and operational acceptance gates, and documents all assumptions.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:20Testers dont like change
- 2:25The world goes blank
- 2:55When to start planning
- 4:25Typical test plan
- 5:15What is a test approach
- 6:52Corporate test strategy
- 8:19Sweet shop analogy
- 9:37Right test approach
- 12:07Approach
- 15:05Example
- 17:04Talk to the team
- 19:02Other considerations
- 21:49Creating a test plan
- 26:02Documenting the test plan
- 28:31Test planning
- 34:19Top tips
related talks
20mTesting Complex and Time Critical Projects!
55mShifting the Testing Role Pendulum
18mEffective Test Automation Framework Design
48mWhat is UAT and, more importantly, what it isn’t
24mWe have health checks for our bodies–so why not for our testing processes?
42mThe Holy Trinity of UI Testing
51mThe Art of Test Planning – Expect the Unexpected
49mBalancing Release & Sprint Delivery Speed with Thorough Testing