Acceptance Test Driven Development has become an industry buzz word, and that buzz has reached your automation doorstep. With all of the promises of conversational language test cases, increased communication, and productivity, this paradigm almost seems too good to be true.
When your team starts the process of implementing ATDD, there is a healthy amount of knowledge to consume and execute on. There are the methodology and the practices needed to hold the process together. There are tools to help support the process. Along the path of implementation, some myths and traps can start to remove the shine of the value that ATDD can provide. If you can identify the warning signs of these traps, you have a higher likelihood of correcting your paths before it is too late.
In this session, Jason will talk about his experiences working on ATDD projects and some of the myths and traps that he corrected along the way.
- Defining ATDD and what value it can potentially add to your team.
- Reduce some of the maintenance headaches by aligning tools across your team.
- Identifying automation warning signs in ATDD and implementing corrections.
- Managing the expectations of the value that ATDD can provide a team.
Jason Edstrom – Senior Quality Engineer, Magenic Technologies
Jason Edstrom is an Automation Architect at Magenic Technologies whom aides organizations in their digital transformation by focusing on automation strategies and implementations. He has a passion for new technology and exploring unconventional methods to solve problems.