Automators Through Developers' Eyes
summary
Examines why developers often think automation engineers (QA) aren’t needed and why QA code can look “strange” to programmers. Explains how developers view QA and gives concrete guidance on how QA engineers can grow their coding skills to write simpler, better, and more robust automation code.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:46Talk purpose
- 3:30Developers vs testers
- 9:59Tests in separate repo
- 15:57Automation language
- 17:48Stereotypes about roles
- 20:41Coding skills in automation
- 22:11Common test code mistakes
- 25:25JavaScript and Selenium issues
- 27:54Becoming automation pro
- 30:00Product quality and accessibility
- 33:15Accessibility testing
- 37:48Accessibility selectors
- 38:51Committing tests to codebase
- 41:01One team over isolated roles
- 43:10Burger joints vs McDonald's
- 45:42Pipeline development fails
- 47:28Summary
- 47:50Q&A
related talks
30mConfessions of a Serial Automation QA
44mTest Automation as a Development Team
51mQuality Assurance vs. Testing
53mIs having a QA a symptom of a dysfunctional team?
06mDoes QA have a place in DevOps? Heck yeah!
48mTest Automation - A Systems Thinking Approach
45mTOP 5 Modern Stereotypes in QA World
53mTest automation for developers