1. Why many Automation Frameworks? when ONE can do ALL
Veeramanikandan Velumani – Tech lead
Selvin S Sreekumar – Senior Automation Engineer
Prabakaran Mayakkannan – Automation Engineer
Fiserv
Fiserv

2. Abstract
Todays need for test automation is so that the framework has to handle anything and everything. While many in the industry are using different Automation Frameworks & tools for testing different Application layers, here we go with the working solution of ONE Framework for Automating all layers of application (Web, Mobile, Services, Database) with the capability to plug-in any (&multiple) Functional testing tools.
We have created this framework with the thought "Everyone can automate" to enable manual testers to automate and thereby eliminating the thought that it can be done only by a dedicated Automation team. 

3. One Framework for all layers
Challenges when using different frameworks & tools
Integration of test cases between layers of applications involved lot of manual effort in spite of automating the tests as one tool might not talk to the other with ease.
Major difficulty we faced was when creating different format of input data for different frameworks.
Maintaining different design (input and output) for different framework became tedious.
When there is a new version of tools was released then most of the time was spent accommodating the new changes to make the existing flow work.
Movement of team members between teams became difficult as we had invested lot of time in training the resource in automating the test cases using the specific tool/framework.
Hiring a person with the corresponding skill was again a challenging task
Solution
One Framework for all layers

4. Architecture Test Case File Test Control Logic Driver
Page Methods
Services Template
Test Control Logic
Selenium/ Appium
Action in Applications
Driver
Report Generator
Service API
Screen Shot Generation
Result in CSV File/Mail
Reporting Dashboard
Service Response Validation

5. Tools & API
Selenium WebDriver – API (Web Applications)
Appium / Node js (Mobile Automation)
Phantom js (Head Less)
HTTP Client – API (Services Automation)
REST ASSURED – API (Services Automation)
XML Unit - API (Services Automation)
JSCH – API (Unix Server File downloads)
Mail – API (Mailing the Result)
Image Comparison API (Screenshot comparison)
Mainframe Connectivity API (DB2 Connectivity)
Extent Reports API (Automation Reporting Dashboard)

6. Automated Areas
UI Functionality Automation
Batch File Validation
Soap WS/Rest WS Automation
XML Parsing
Mobile App/Web
Test Library
Head-Less Mode
Schedulers
Browser Compatibility
Result File Reader
Screenshot comparison
Parallel Execution
Flat File Validation
API Automation
Mainframe Database

7. Advantages
Open Source Framework
One framework for all needs(UI, web-Services, RestWS, Mobile App/Web, Screenshot Comparison and Browser Compatibility)
Can support any tool
Customized reporting dashboard
Lightly loaded framework. Manual testers can do all the test. No need for a dedicated automation team
Hassle-free Test preparation and execution
Framework maintenance cost is very low

8. Achievements
Made everyone automate their test cases
Reduced more than 1000 hrs. of Manual effort for every release
Maintaining >80% of In-Sprint Automation for every sprint

9. Manual Vs Automation (Per Release)

10. ROI (per cycle)

11. Author Biography
I’m Veeramanikandan, Tech Lead at Fiserv. Started my career as a .NET developer in a Bangalore based start-up. Moved to Cash-Edge in 2010 for web service development. Very passionate in learning new things and adopting the new technologies. This passion made us to identify a solution for the challenge of having many tools and different automation processes for different layers of application. Working towards to be an “Architect” and “Consultant” for Automation.

12. Thank You!!!
Fiserv