DevOps! Let's Change QA!
summary
Covers how QA and testing must change in a DevOps/Agile world, naming DevOps explicitly and contrasting old practices with new ones. Discusses which QA practices to keep or discard, whether manual testers are still needed, how to adopt new skills and processes, and includes examples and pitfalls from consulting engagements with large banks such as ING and Rabobank.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 1:42Building a small moon
- 3:17Who are you
- 5:05Testing
- 5:43Quality Assurance
- 6:58Testing Definition
- 9:36Engineering
- 9:46Quality Engineering
- 10:52Quality Engineers
- 16:08Quality Assistant
- 17:25Quality from the start
- 18:00User stories
- 18:43Story value
- 20:42Where are the dolphins
- 21:08What are we building
- 22:32Understanding the big picture
- 24:50Examples
- 25:41TDD Example
- 27:47Automate
- 28:22Current Features
- 29:09Good Development Practice
- 29:32Why Automate
- 30:15Test Automation Pyramid
- 33:35Testing vs Automation
- 35:55No Gnomes
- 37:11Explore It
- 37:40Automate It
- 38:38Explore
- 39:58Summary
related talks
06mDoes QA have a place in DevOps? Heck yeah!
42mOPENING KEYNOTE: Quality Engineering in DevOps
47mHow Testing is Evolving in DevOps
45mIs there a place for QA in modern agile autonomous fast-flow teams?
09mQA in an Agile environment
30mHow a Tester Can Survive in an Agile Environment
51mQuality Assurance vs. Testing
37mThe Role of Testing in Devops