Premier Heavy Equipment Rental Marketplace Streamlining Machinery Rental Experience for Everyone

Reduce Time to Delivery by 50%

Download case study

Services

QA Testing

Industry

SaaS

Location

USA

Employees

100 to 1,000 Employees

About Rubbl

Rubbl is a well-established, first-of-its-kind, and cloud-based heavy equipment rental marketplace that offers seamless access to optimal quality contractor-owned equipment. Every rental comprises a host of benefits, including but not limited to preventive maintenance, comprehensive service coverage, managed transportation logistics, and dedicated support for unforeseen circumstances. Using Rubbl’s cutting-edge platform, clients can book dozers, excavators, earth movers, skid steers, water trucks, petrol trucks, cranes, and dumpers for different purposes.

Accelerating Production: Automating Testing to Ensure Seamless Operation

Helped Rubbl Automate Tests to Reduce Production Time

The biggest issue Rubbl was experiencing before coming in touch with Binmile was massive time consumption while testing their web application. Due to this, their production cycle was getting impacted and they were looking to get an immediate solution to it. The situation was such that they were compelled to test the entire application manually even when they had added just a small feature or changed the color of any element. That’s when they shared their concern with Binmile’s representatives and informed them that they wanted to introduce automation and integrate testing activities into their CI/CD pipeline. Since their application was fully developed, neither major changes were required nor they were carried out.

All the executives of Rubbl wanted was that their tests get automated and that whatever minor changes they make get automatically tested and incorporated into their CI/CD pipeline. We did it and this way the time to production was reduced to a great extent and the client was pretty impressed with such an outcome.

Met Rubbl’s Expectations to Integrate API into Existing UI Automation For Faster Response

Rubbl had existing automation that was primarily focused on their user interface. Since it was not that comprehensive, the testing team at Binmile decided to integrate API with UI automation to expedite the process and make it easy to execute. And while doing this, our testers faced several challenges, like sometimes some machines were not available. And when we needed to run a test, we used to check the availability of machines first using the Application Programming Interface. It was mainly done to ensure that the existing automation becomes more robust and dynamic and the cases of False Failure can be reduced. For the uninitiated, failures are of two types. The first one is True Fail, which means there is a bug in the system and it is not functioning as expected. The second one is False Fail, which means there may be no defect in the systems and it is working as expected.

Previously, when the items were in stock, the codes were picking only the items that were targeted. If there was something out of stock, the test used to simply fail. To deal with this issue, our testers used to fetch information about the available items through API and then we used to dynamically pick them through code and perform test automation. By doing this, we were able to make tests dynamic and robust at the same time, resulting in seamless operation down the line.

Assisted Rubbl in Increasing Device Coverage From Desktop Browser to Mobile Browser

The last thing we did for Rubbl was boost the device coverage big time. Initially, the client used to test things on the desktop browser. But when we started working on the project, we automated the tests on the mobile browser too. We also increased the range of the device by integrating it with LambdaTest.

For the unversed, Test coverage refers to the percentage of application code that has been tested and whether the test cases cover the entire code. Take, for instance, if a web application consists of 10,000 lines of code, an ideal test case should be able to test the whole codebase. If only 6000 lines of code are checked out of 10,000, the coverage is 60%.