Test Automation Engineering roles are becoming more common but there’s no great definition for what an Automation Engineer does. In this presentation, Chris will share his experiences on how he became one, what that the first few years have looked like: the good, bad and the ok. He’ll also share the time he spends automating vs exploring, why writing test automation doesn’t mean just focusing on the UI and where he thinks the skills and role will go in the future.
- Slides
- References
- Email: chris@kenst.com
- Twitter: @ckenst
- LinkedIn: /in/ckenst
- GitHub: (you are already here)
- Website: Kenst.com
- Participating in Code Reviews as a Tester
- Cordny Nederkoorn experience report on becoming an Automation Engineer
- Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations
- The Selenium GuideBook by Dave Haeffner
- Head First Object-Oriented Analysis and Design
- TestAutomationU course on JS UI
- TestAutomationU course on Automating in the browser
- TestAutomationU course on Unit Testing