How Testers Add Value to the Organization But also, to ourselves
summary
Argues that testers do far more than log bugs: they join grooming and architecture meetings to shape requirements and add testability hooks (like accessible element IDs for mobile), write test cases that become the de facto requirements, and prevent bugs with UI plus backend validation. Recommends reliable automated suites run in Jenkins CI, adding automated security, performance and accessibility scanner checks, reviewing commits to check commits for story IDs before release, coordinating release notes, and using customer feedback and metrics to prioritize fixes.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 1:23Welcome
- 2:25Image
- 4:30Success
- 6:28Job Description
- 8:10Your Role
- 9:36Requirements
- 15:56Test Cases
- 17:25Test Requirements
- 18:59Bug Prevention
- 21:51Our Role
- 22:22Automation
- 24:55Reliable Tests
- 25:47Security Testing
- 27:22Performance Testing
- 29:17Accessibility Testing
- 30:55Release Coordination
- 36:45Customer Feedback
- 38:23Development
- 39:46Presentation
- 40:27Achievements
- 40:57Dont get stuck
- 42:38Conclusion
- 42:53QA Session
- 43:10QA QA QA
- 45:38Strategy when requirements are not properly documented
- 47:06Asking testers to do an acceptance criteria test
- 48:45How to prepare for a code review
related talks
34mHelping Testers Add Value to Agile Projects
01h 08mTesting Is Your Brand: Sell It!
15mThe Tester I Was and the Tester I Could Be
41mMartijn Goossens: Be a Better Test Friend to Your Team
55mShifting the Testing Role Pendulum
09m"The Tester’s Role: Balancing Technical Acumen and User Advocacy"
21mHow to thrive as a non-technical testing professional
48mOwning Our Narrative