Are you an automation lead or manager writing the same boilerplate code for all your projects, or do you have an automation project so large that it takes more time to find the proper method than it takes to write the test? In this session, you will learn to move away from a siloed or monolithic automation project and focus on reusability of code across multiple modular projects. In the last decade or more, there has been a significant architectural change to how developers design applications. They are using a more modular approach through the use of RESTful services and UI modules. It is time that automation projects move to this design as well. This approach is not only creating siloed testing projects, but using the methods and classes created to test these projects in other projects, so we don’t keep rewriting the same code over again. We will focus on breaking down the siloed test projects and creating an architecture of reusability. After showing how to bring together the functionality of multiple projects it will be time to tackle the monolithic project and develop strategies that will help break it up in a way that makes sense for testing. * understand the characteristics of a siloed and monolithic automation project. * basic architecture of the modular strategy * where to start the journey * integrating the siloed pieces * breaking down a monolithic project into testable chunks

October 11 @ 14:00
14:00 — 14:45 (45′)

Mark Bensch