Description:

About a decade ago people with advanced knowledge built test automation frameworks with essentially two separate layers: Test Scripts and Test Libraries. The problem with this Bi-Layer architecture is the challenges of reusability in other applications, specifically, the size and complexity of test libraries along with the application-dependent solutions being intertwined made it very difficult, sometimes impossible to reuse them.

That's how the idea of the Tri-Layer Testing Architecture was born: why not add a 3rd layer, for all the libraries that can be easily reused anywhere?

In this presentation, Peter will talk about the main differences between the Bi-Layer and the Tri-Layer architectures. The three layers are Test (runnable test scripts), Business (all the application-specific libraries), and Core (independent, reusable libraries). Peter will provide examples from his experience at big fintech and other companies, where he successfully implemented the Tri-Layer Testing Architecture and dramatically lowered the test automation costs for these big companies.

Key Takeaways:

• Attendees will be able to identify signs of a smelly architecture

• Designing a test automation architecture is way easier than you would first think

• Reusable components and properly designed layers are the heart of a great test automation framework.