CASE STUDY
TECHNOLOGY
Technologies – Selenium Automation, Hybrid Test Framework, Java
PROBLEM
Challenges faced in testing and releasing the Billing component, a crucial part of their flagship product. The existing automation framework lacked robustness, and the billing end-to-end (E2E) flows interfaced with multiple systems, posing validation difficulties. Additionally, the flows varied based on regions and deployed on unstable test environments.
OVERVIEW
The project aimed to enhance the automation framework’s robustness and efficiency while designing, developing, and maintaining scripts for billing components across different regions. This involved automating approximately 400 E2E billing test cases, integrating services and UI automation seamlessly, and supporting daily Sanity and Priority test case execution.
SCOPE
The scope included analyzing workflows, designing use cases, and automating E2E billing test cases across regions. The framework needed to integrate with services and UI automation seamlessly, perform daily Sanity tests, and support monthly releases.
CHALLENGES
- Limitations in Existing Framework: The current automation framework lacked robustness.
- Integration with Multiple Systems: Billing E2E flows interfaced with multiple systems, making it challenging to validate system-specific flows for downstream systems.
- Regional Variations: Flows differed based on regions and were deployed on unstable test environments.
APPROACH TO CHALLENGES
- Framework Refactoring: The framework was refactored to accommodate page objects and common libraries for reusability.
- Flow Analysis: Internally analyzed the flows and designed/redesigned test cases to ensure comprehensive coverage.
- Modularization: Framework redesigned to accommodate multiple systems with minimal impact on development effort. System-specific flows were modularized for easy extension.
Data analytics and automation
KEY BENEFITS
Robust Automation Framework: Implementation of a robust and stable automation framework with seamless integration between services and UI automation.
Regression Cycle Improvement: The automation regression suite helped the QA team achieve a 5-day monthly regression SLA.
Execution Time Reduction: Reduced regression cycle execution time from 80 to 14 hours, representing an 80% reduction.
Outcome-Based Ownership: The project was delivered under an outcome-based ownership model, with Prakat managing the project end-to-end, ensuring accountability and quality delivery.
