In a team which is developing mobile apps for multiple platforms, it becomes extremely difficult to maintain multiple Automation codebases and frameworks to test the app. This becomes a bigger problem when the same team is churning out multiple flavours of the same app.
What this session will showcase is how we have built an automation framework that tests 2 different flavours of an app along with using the same framework to test these apps across 3 different platforms.
The session will also include the challenges we faced while moving from a purely Functional approach to writing code to an Object-oriented approach to structure our automation code.
This will help other testing practitioners attending this session in building a robust automation framework with a very reliable and scalable codebase that can be extended beyond just one application/platform.
Although building this sort of a framework comes with a lot of advantages, I would like to talk about our initial challenges and learnings while rewriting the framework that was entirely functional in nature and how we moved to an object-oriented approach in a matter of a few months.
Building the Automation framework with the right architecture using Page-Object pattern which will help with scaling, organizing & readability of the automation codebase.
How to build an automation framework that is so modularized that makes it easy for us to switch the drivers that we are using. For example, when the current driver (in our case calabash for mobile apps) is no longer the best tool for us, we can easily switch to something else. So it is more of a Plug and Play sort of a framework.