Challenge

Every update to a production app carries a risk that is rarely visible until it's too late: functionalities that worked can silently stop working. In a sales force app like LinkedBy's SFA, where field teams log orders, manage routes, and access customer information in real time, an undetected regression has a direct impact on operations.

LinkedBy's SFA is an app in active evolution. New features, adjustments to business rules, integrations with ERP and logistics modules: the development cycle never stops. And with each new deployment, there's a possibility that something that worked in the previous version has broken in the new one.

Without automation, verifying this requires manually running the app's critical flows after each update. For an app the size of LinkedBy's SFA, this coverage took about 3 to 4 hours per cycle, hours that the QA team had to repeat with each release, before any other activity.

The risk was twofold: either the team performed the regression tests rigorously (slowly) or they abbreviated them to gain speed (risky).

Transformation_

LinkedBy brought Evo Systems on board with a clear objective: to structure the automation of SFA regression tests using Orange Testing, a no-code platform partnered with Evo Systems that specializes in mobile app automation.

Evo's differentiating factor in this model isn't access to the tool: it's the curation of the test plan, the mapping of critical business journeys, and the knowledge transfer methodology that transforms the platform into internal client capability. A consultancy that leaves the tool installed without this process delivers software. Evo Systems delivers autonomy.

From the outset, it was decided that the project would not end with the delivery of the tests: Evo Systems would conduct the process alongside the LinkedBy QA team so that the team could start operating independently.

The QA team began by fully mapping the SFA: all functionalities, all critical flows, and all scenario variations relevant to LinkedBy's business. Based on this mapping, over 120 automated tests were created covering the app's main flows, including entire order flows with various variations. The tests run automatically with each development update, verifying that essential functionalities continue to operate as expected.

The choice of Orange Testing was both technical and strategic. The platform is no-code and 100% cloud-based, allowing QA analysts without development backgrounds to operate it autonomously. Its visual recognition mechanism is especially effective for mobile apps with dynamic interfaces, such as SFA. And its integration with CI/CD pipelines ensures that testing is part of the development cycle, not an external manual step.

The technical delivery, the 120 tests, is one part of what was built in this project. The other part was the knowledge transfer process. In several working sessions, the Evo Systems team went through all the platform's functionalities with the LinkedBy QA team. Not in a theoretical training format, but side-by-side, during the actual construction of the tests.

The result of this process became evident in one specific detail: by mastering the tool, the LinkedBy team went beyond the initial plan and supplemented the coverage with test cases for more complex business rules, logics that only they knew in sufficient depth to test. Evo Systems came in as a facilitator for the LinkedBy team, which then led the process.

Benefits_

• Regression coverage: Automatic with each deployment, where previously it was manual and partial per cycle.
• Tests in the plan: Over 90 active tests, where previously none were automated.
• Time by countdown cycle: Automatic, without costing staff time, replacing approximately 3 to 4 manual hours per cycle.
• Bugs detected post go-live: Two regressions were captured before impacting production, which were previously unmonitored.
• QA team autonomy: Trained and autonomous on the Orange Testing platform, previously dependent on external support for automation.

The two bugs caught after the go-live came to the team's attention before impacting the field salespeople, exactly the scenario that automation was designed to prevent. And the clearest sign that knowledge transfer worked wasn't the team operating what was delivered: it was the team going further and expanding coverage on their own.

Tools used_

• Orange Testing

The cycle that LinkedBy ended—3 to 4 hours of manual regression testing for each deployment, with increasing risk as the app grows—is the standard cycle for teams that haven't yet automated. Now, the LinkedBy QA team no longer depends on anyone to keep coverage running.

If your development team is accelerating while your QA team is scrambling to keep up, it's worth discussing what can be automated.