What’s the definition of “best practices” for writing automation frameworks? .. for your API test strategy? .. for your GUI tests? What does it mean to write a scalable or clean library/application? The core to ensuring that you, as an automation engineer, or software engineer, are creating a well-designed program, e.g. framework, tests, utilities, is to understand the importance and benefits of software design patterns and their application to a problem. Are you an automation engineer that leverages those “best practices” touted by other automation engineers? Perhaps, you’re an automation engineer that leverages a pre-existing framework or design and now realize that you need a better solution? Or, perhaps you’re fed up with depending on other resources that fall short of your automation needs? … or, are you a passionate engineer ready to learn what it takes to roll your own.
Perhaps, you and your team are ready to invest in a “proven” test strategy? Wouldn’t you want to hear an experienced software design engineer (not an automation engineer that has been using the same approach that was developed back in 2007) show you they would do it? Do you really believe that leveraging all the pillars of Object Oriented Programming is a “best practice”? Do you know the difference between inheritance and composition? Do you want to free yourself from writing repetitive and sequential “designs” with a clean, simple, and scalable one?
This workshop will dive into specific software design patterns that will help you understand and write better test frameworks, tests, and provide insight on breaking down and solving programming challenges that you will and others have faced for the past decade. See how design patterns can be leveraged to create a scalable test framework that is simple and fast. The software problems and challenges that you face (or will eventually face) has been solved already, … let’s see how they can be utilized to make you more knowledgeable and successful.