Customer story · ERP Software

FocusSoft runs its full ERP regression in under 30 minutes

FocusSoft, an enterprise ERP vendor, replaced a Selenium suite that couldn't cope with its dynamic screens. It now runs 260 complex end-to-end cases in under 30 minutes, with more than 8,600 executions logged.

Diagram of a no-code regression suite running across ERP modules
< 30 min
full end-to-end ERP regression
260
complex ERP cases automated (target: 200)
8,600+
executions logged

01About FocusSoft

FocusSoft builds an enterprise ERP with deep business logic and complex screens. Its customers rely on it for finance and trade processes, so every release has to keep those processes working.

The team had tried to automate regression with Selenium. Dynamic screens, drag-and-drop configuration and keyboard shortcuts made the scripts fragile, and feedback on a commit arrived days later.

ERP vendors face a harder version of everyone's regression problem. Each customer runs the product a little differently, so a defect in a core module is multiplied across the installed base. A regression suite that can't keep up with the codebase isn't an inconvenience. It's a release risk.

02Business objectives

  • Automate at least 200 complex end-to-end ERP cases
  • Get regression feedback the same day as the change, not days later
  • Cover the business logic customers depend on, not just screens
  • Retire the fragile Selenium suite

03Testing challenges

Dynamic UIs

ERP screens build fields and grids on the fly, so locator-based Selenium scripts broke with every change.

Unusual interactions

Drag-and-drop configuration and function-key (F-key) shortcuts are hard to script reliably.

Deep business logic

Payment terms, letters of credit, credit limits and inter-company postings each have many rules and edge cases.

Slow feedback

With an unreliable suite, defects were found days after the commit that caused them.

04How they use Robonito

  1. 1

    Process-level tests

    Cases were built as full business processes, step by step, rather than screen-by-screen scripts.

  2. 2

    Complex interactions covered

    Drag-and-drop configuration and keyboard shortcuts are handled as ordinary test steps.

  3. 3

    Business logic, not just screens

    Each case checks the outcome of the process, such as an installment schedule or an order hold, not only that a screen loaded.

  4. 4

    Every run logged

    The full suite runs end to end in under 30 minutes and every execution is logged, so feedback arrives the same day as the change.

05Test scenarios, in plain language

Representative examples in the areas FocusSoft's suite covers. Each one is typed as written; the agent works through the app and saves the steps.

AI Studio · describe what to test
  • Payment termsCreate a sales invoice with 30/60/90 payment terms and confirm three installments are scheduled with the right due dates.
  • Letters of creditOpen a letter of credit against an import order and confirm the order can't ship until the LC is confirmed.
  • Credit limitsRaise an order that takes a customer over their credit limit and confirm it is put on hold for approval.
  • Recurring journalsSet up a monthly recurring journal and confirm the next period's entry is generated with the same lines.
  • Inter-companyPost an inter-company sale and confirm the matching purchase is created in the receiving company.

06Results

260 complex cases automated

Against a target of 200, covering payment terms, letters of credit, credit limits, recurring journals and inter-company flows.

Regression in under 30 minutes

The full end-to-end regression now runs in under 30 minutes.

8,600+ executions logged

Every execution keeps its evidence, so the team can trace any failure back to the run.

Selenium suite retired

The fragile scripts are gone, and so is the maintenance that came with them.

07What other teams can take from this

Automate business processes, not screens

FocusSoft's cases check outcomes such as installment schedules and credit holds. Screen-level checks would pass while the logic underneath broke.

Set a target, then beat it

A concrete goal of 200 cases made progress visible to everyone. The team finished at 260.

Speed changes behavior

When regression runs in under 30 minutes, it runs on every change instead of once before a release, and defects are found while the change is still fresh.

08Frequently asked questions

Why did Selenium struggle with FocusSoft's ERP?

The ERP builds fields and grids on the fly and relies on drag-and-drop configuration and F-key shortcuts. Locator-based Selenium scripts broke with each change, and repairing them took longer than the feedback was worth.

How long does FocusSoft's regression take now?

The full end-to-end regression of 260 complex cases runs in under 30 minutes, with more than 8,600 executions logged.

Which parts of the ERP are covered?

The 260 cases cover payment terms, letters of credit, credit limits, recurring journals and inter-company flows, among other finance and trade processes.

Can Robonito handle drag-and-drop and keyboard shortcuts?

Yes. In FocusSoft's suite they are ordinary test steps. For unusual cases, Robonito also supports low-code extensions alongside its no-code steps.

Is Robonito a good Selenium alternative for ERP testing?

For teams whose Selenium scripts break on dynamic screens, often yes. Tests are no-code or plain language, self-healing adapts to UI changes and logs each fix for review, and Robonito can still export executable code when you need it. Keep Selenium where you need fine-grained control in code.

ERP Software

See these tests run on your own app

Pick one journey from this page. We'll build it with you in Robonito, run it, and show you the evidence: video, traces and root cause.