Test automation

Your process checked after every change

End-to-end testing of business processes

An ERP update can break invoicing. A change in CRM can stop orders. A test robot checks the whole process and reports the error before deployment.

  • Robot Framework
  • Regression
  • RPA

We build test robots that run through business processes the way a user does. We test ERP, CRM, web systems and RPA robots.

01 / Robotic test automation

What we test

Whole processes, from the first click to the document in the system.

  • 01

    End-to-end tests

    A robot runs a process across several systems, e.g. from order to invoice.

  • 02

    Regression tests

    After every change, the robot repeats known scenarios. It finds what has stopped working.

  • 03

    ERP, CRM and web systems

    We test the user interface, the API and the data in the database.

  • 04

    RPA robots

    We check that RPA robots still work after changes to the systems they use.

02 / Robotic test automation

Tools and reports

Tests your team can later maintain on its own.

  • 01

    Robot Framework

    Our tools include Robot Framework. It is an open-source framework for test automation and RPA.

  • 02

    Readable scenarios

    We write scenarios in the language of the process. Analysts and business users can read them.

  • 03

    Test reports

    After every run, you receive a report with steps, screenshots and errors.

  • 04

    CI/CD integration

    Tests run automatically with every deployment.

03 / Robotic test automation

Process

  1. 01

    Choosing processes

    We choose the processes whose failure costs the most.

  2. 02

    Scenarios

    We write down the steps, test data and expected results.

  3. 03

    Building the robots

    We automate the scenarios and connect them to CI/CD.

  4. 04

    Handover and maintenance

    We train the team and update tests after changes to the systems.

04 / Robotic test automation

Use cases

  • Order-to-invoice process in ERP
  • Tests after an ERP system update
  • New customer onboarding in CRM
  • Sign-up and login in a customer portal
  • Regression before every application release
  • Checking RPA robots after an interface change
  • Testing the integration between an online shop and the warehouse
  • Testing the document workflow in a DMS

05 / FAQ

Frequently asked questions

How do automated tests differ from RPA?

A test robot checks that a process works. An RPA robot carries out the process instead of a person. Both use similar tools.

Do we have to use Robot Framework?

No. We choose the tool to fit your systems and team. Robot Framework is a common choice because it is open source.

Who maintains the tests after rollout?

Your team after training, or us under a separate contract.

What data do the tests use?

Test data or anonymised copies. We do not use personal data without your consent.

How many processes should we automate first?

Usually a few of the most important ones. We start with the processes whose failure costs the most. We add more after the first results.

Which process do you still check by hand?

Describe it. We will propose scenarios and the scope of automation.

Book a call