Test Automation as a Development Team
summary
Looks at treating test automation as a development team function: using developer tools and workflows (e.g., code repositories, CI/CD, code review) to build and maintain automated tests, and organizing people and processes so test automation integrates into the software development cycle rather than remaining an isolated QA activity.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:38Optimizer team testing
- 4:52Solo tester problems
- 8:29Testing pyramid decisions
- 9:31Automation business goals
- 12:40Test framework development
- 15:47DoL track methodology
- 24:08Team integration tools
- 28:03Nexus dependency management
- 31:39Single test run and report
- 34:06Test data management
- 35:32Automation as dev team
- 37:24DoL track steps
- 41:49Q&A
related talks
24mTesting Automation
38mDo We Really Need A Test Automation Engineer?
46mSoftware Devs in Test Automation - Dream or Reality in Agile Software Dev?
44mDirections for the Development of Test Automation Systems
11mTechTalk "Automated Testing Inside the Team or as an External Service"
53mTest automation for developers
48mTest Automation - A Systems Thinking Approach
40mDevops and Test Automation: Myths and Tips
