In this talk, Aaron Evans, an independent consultant with over 20 years of testing experience, breaks a test automation framework into pieces: tests, automation code, execution, reporting and communication. He covers criteria for evaluating a framework, missing pieces such as flakiness, what sits outside it, and how to find the right fit.
- The main pieces of a test framework
- Criteria for evaluating a framework
- Missing pieces: flakiness, traceability, reproducibility, communication, timeliness
- What lives outside the framework
- Finding the right fit and steps to build or improve it
Speech bullet points:
1) The main pieces of a test framework: tests, automation code, execution, reporting, communication
2) Criteria for evaluating a test framework: maintainability, reliability, speed, complexity, coverage
3) Identifying the missing pieces: flakiness, traceability, reproducibility, communication, timeliness
4) What is outside the framework: tools, processes, skills, environments, data
5) Finding the right fit for your project: language & libraries, types of tests, execution strategy
6) Solving the puzzle: steps for building or improving your framework
About the speaker:
I’ve been testing software for over 20 years. I’m an independent consultant and have worked with over 100 companies building (or fixing) test automation code and frameworks. I have seen a lot of good and bad code and met a lot of cool people. Currently, a test automation architect for Massachusettes Medical Society, publishers of the New England Journal of Medicine.
This is part of the speech from the online Test Automation Meetup – August 16