Our client is a leading point-of-sale payment platform for retailers and consumers across the North-America region. With a strong market presence, the client facilitates seamless transactions and enhances the overall payment experience.They support millions of transactions daily, ensuring speed, reliability, and security at every touchpoint.Their platform is continuously evolving to integrate emerging technologies like contactless payments and mobile wallets.
.png)
The client faced several challenges in their testing practices, including the reliance on manual testing, lack of reusable code, and limited automation capabilities. Manual testers struggled to adopt automation due to the absence of standardized templates and tools. Additionally, the existing frameworks had multiple dependencies, leading to inefficiencies and maintenance difficulties.
The main purpose of building and bringing reusable test automation frameworks is for:
- Opportunities for Manual Testers to adopt automation easily with re-usable templates.
- One Stop Solution for Test Automation (UI, API) and even performance, this grows with addressing multi-stack technologies.
- Possibilities of bringing reusable code across the project. For e.g., could be technology stack like API or UI Automation, could be App Specific for e.g., origination, customer information, data generation etc.
- Ideas of bringing Manual and Automation tester instead of Silos.
- Possible to bring up In-Sprint Automation which can be started first with API followed by UI.
We developed Codvo.ai Core Library - UI Core, API Core, Mobile App Core, Product Core, Performance Core, and Security Core for the client and removed single existing framework dependency
.png)
The tech stack used: Java, Jenkins, Selenium, Rest Assured, Sauce Labs, BrowserStack, BlazeMeter, Apache JMeter, Grafana, InfluxDB.
-20 to 30% reduction in effort to due to the reusable framework.
-Allow testers to focus on what to automate NOT spending time on how to automate.
-All the projects can simultaneously access the code from a single pull library, or a common server thus reducing the efforts.
-Improved collaboration and consistency across QA teams by standardizing automation practices.
-Accelerated onboarding for new projects with plug-and-play components readily available in the shared framework.
