How Testers Can Help Paving the Future of Modern Requirements Engineering
summary
Argues testers move left into requirements engineering by turning requirements into executable examples and early tests, claiming faster delivery and fewer late defects when refinements write Gherkin examples and treat test cases as requirements. Shows artifacts used: UML/use‑case descriptions, cucumber scenarios, mocks and service virtualization (mentions puck). Calls out anti‑patterns like test sprints and testing columns, reports real projects where this approach speeds delivery and makes acceptance criteria and edge cases explicit and testable.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 2:35Scrum anti-patterns in testing
- 6:34ISTQB retroactive testing
- 10:13Gatekeeping to holistic quality
- 12:03Use cases as requirements
- 15:38Requirements by example & BDD
- 17:29Refinement as quality engineering
- 20:58Tester as quality ambassador
- 24:10Collaboration over silos
- 24:30Q&A: Three amigos & firefighting
- 26:34Q&A: Risk-based testing strategy
- 28:01Q&A: Trusting devs & performance
- 29:02Q&A: Testing columns on boards
- 30:47Q&A: Frontend waiting backend
- 31:49Q&A: AI’s collaboration impact
- 32:52Q&A: Business vs dev focus
- 33:14Q&A: Refinement session prep
- 34:38Q&A: BDD mandatory?
- 35:41Closing
related talks
42mHow a Tester Can Help Improve the Quality of Requirements
54mExtreme Shift Left / Out with the Requirement Engineer?
45mPanel Discussion | How to deal with bad requirements in testing?
44mExcellent Testing Starts With Excellent End-User Requirement Engineering and Specification
09m"Effective ways of using BDD concept for Testing"
58mTesting Strategy - New Model, Better Outcomes
34mHelping Testers Add Value to Agile Projects
01h 02mAgile Testers and Test Managers: Now What?