Select your language

Select your language

Test Automation

Every new version of your software can break what was still working yesterday. Testing this completely by hand is hardly possible any more: the intervals between releases are getting shorter, the software keeps growing, and bugs only come to light at the customer's site. Automated tests check every version equally thoroughly and reveal bugs while the cause is still fresh. We help you in three ways: we create your test automation, we take over an existing one, and we hand it over so that your team can work with it independently.

Create

We build the test automation for your software – from unit tests to user interface tests.

Take Over and Maintain

We take over existing test automation, get it running again and keep it up to date.

Hand Over

We hand over the tests with documentation and an introduction, so that your team can run and extend them itself.

Creating Test Automation

The starting point is the question of which processes are critical for you and your customers. We then align the tests accordingly:

  • Unit tests check individual classes and functions, for example with MSTest, NUnit, xUnit or Google Test.
  • Integration tests check the interaction with databases, files, devices or interfaces.
  • User interface and system tests operate your application the way a user would and check the result.

For desktop applications with WPF, WinForms, MFC or QML, as well as for CAD applications, we use our own product TesteriX. It records user actions and plays them back without any test code having to be written. It controls the AutoCAD and BricsCAD drawing area via CAD commands and also checks what is in the drawing. If you already work with other test tools, we build on them.

Taking Over and Maintaining Existing Test Automation

Many test automation efforts got off to a good start and were then left to languish: tests fail permanently, give inconsistent results, or nobody knows any more what they actually check. Then the results are ignored – and the tests are worthless.

We review what is there, stabilise unreliable tests, adapt them to new versions of your software and close gaps in important processes. After that, we maintain the tests on an ongoing basis and, within the agreed scope, ensure that they keep running and deliver meaningful results, for example through a support and maintenance contract.

Introduction at a laptop: a team working together on a test run

Handing Over to Your Team

Would you like to use the tests yourself? We set them up to fit your workflow:

  • Run manually: Developers or testers start individual tests or entire test runs at their own workstation.
  • Trigger on demand: for example before a delivery or after a bug fix, at the push of a button or from the command line, and if you wish only for the affected areas.
  • Fully automated, scheduled: The tests run at night or at the weekend on a test computer or a virtual machine. The report is ready in the morning.
  • In the build process (CI/CD): The tests run with every build, for example in Azure DevOps, GitHub Actions or Jenkins. If a test fails, you see it before the version is passed on.

The handover includes documentation of the test cases and the test environment, an introduction for the people who work with the tests, and a transition period during which we remain available for questions. If your team would like to go deeper, we offer suitable training courses.

What You Gain

  • Every version is tested equally thoroughly, not only when there is time for it.
  • Bugs are noticed while the change is still fresh, not only at the customer's site.
  • Reports and logs make bugs traceable, for support and specialist departments too.
  • Your team gains time for new features instead of repeated manual testing.
  • Automated tests are also a building block when you need to demonstrate security and quality, for example under the Cyber Resilience Act.

From Our Projects

For a measuring instrument manufacturer, we analysed LabVIEW software that had grown over many years and built automatically executed unit tests. This revealed risk areas and pinpointed memory leaks, enabling the customer to safeguard the continuous operation of its measurements: Software analysis and unit tests for LabVIEW. In a research project on digital PCR, we safeguarded the requirements as user stories with automated tests – find out more in our case studies.

Would you like your test coverage assessed first? That is part of our quality audit. You can find all our services in the Quality and Security overview.

Your Next Step

Tell us which software you would like to test and how you test it today. We will suggest where you can achieve the most.

Arrange an initial consultation

CONTACT

Select your language

First meetingarrange nowFirst meetingarrange now