Action-Based Test Automation significantly reduced the go-to-market time (by one man-month) for a truck leasing company
About Our Customer
A provider of freight brokerage, transportation management, warehousing and supply chain consulting. The company’s multimodal freight services include truckload, less-than-truckload, intermodal, air freight and ocean transportation.
Industry: Logistics & Supply Chain
Country: United States
Company Size: Over 200 employees
The Challenge
For the project, LogiGear was chosen to manage the entire automated testing strategy for the Transportation Management System (TMS). The customer onboarding process, which was crucial for their revenue, had Oracle Transportation Manager (OTM) as the centerpiece interacting with several extended applications.
For QA, the customer onboarding process was translated into a smoke test that must be performed to ensure data integrity across multiple applications. Manual QA teams had to run through the scenarios in multiple environments.
The company also required the automated tests to be extended to the developers who can run quick regression tests on their environments when they develop new features. A prior attempt with a well-established consulting firm using a record and playback automation product had failed.
The Solution
LogiGear’s managed services team automated the smoke test using TestArchitect leveraging Action Based Testing method. This way allowed the automation engineers to automate actions from numerous applications and develop tests implementing those actions.
TestArchitect’s module-based design allowed the engineers to categorize tests based on functionalities and plain UI verification. Tests that had the same functionalities on the web and mobile were designed with the commonalities in mind, and the actions were generated once and re-used on different platforms leveraging TestArchitect’s variation feature.
The Result
LogiGear delivered the TestArchitect to execute automated test scripts in multiple environments, which led to 26 hours per environment time saving compared to manual tests. Moreover, regression test execution time was reduced from 1.5 weeks with 3 manual testers to merely 10 machine hours. Hence, 182 man hours or 22,75 man-days were saved in regression testing activities.