Test Automation for the Public Sector

Greater stability in business processes, less manual regression: With Drvless, government agencies and public IT service providers automate UI-based end-to-end processes—even in heterogeneous system landscapes and under strict security requirements. Drvless is GUI-based (“visible = controllable”), is more resilient to ongoing UI changes, and requires no access to backend code.

Challenges in the public sector

Digital services must function reliably – for citizens, businesses, and internal departments. At the same time, long lifecycles, parallel operation (legacy and new portals), and changing requirements affect numerous stakeholders and require formal approvals. This makes repeatable end-to-end regression crucial to prevent releases and rollouts from failing during approvals or in operation.

Heterogeneous specialist processes & surfaces

Portals, desktop applications, and legacy UIs run in parallel. End-to-end tests across system boundaries are difficult to manually validate – especially when individual steps can only be performed via the user interface.

Safety and operational restrictions

In many government environments, installations on target systems or direct code access are not permitted.

Many stakeholders, clear evidence

Acceptance testing, documentation, and repeatable automation are crucial – especially during rollouts across multiple organizational units, where identical tests must be consistently repeated.

Our solution

Drvless controls everything visible directly via the GUI. This allows you to automate real-world business processes and portal workflows – without invasive integrations and without access to backend code.

Tool for non-experts

Drvless is designed so that even non-programmers can automate: Test cases can be created via drag-and-drop or described in natural language and then converted. This allows business departments, QA, and IT to build automation together.

Technology and platform independent

Drvless is independent of the technology of the system being tested and runs on MS Windows, macOS, Unix, etc. Furthermore, desktop, mobile, and tablet applications are covered by the same automation scenario.

No installation required on the target system

Drvless does not need to be installed on the Under Automation system. You can, for example, connect a CCDevice or run CCSoftware – suitable for restrictive environments with strict approval processes.

Start earlier, get feedback faster

Drvless supports test automation before or in parallel with software development and requirements analysis – helpful when projects have long runtimes and many dependencies.

Drvless allows us to automate complex test cases with a high repetition rate. This saves time, reduces errors, and increases the reliability of our releases.

Sabine Ringhofer
CIO | Cineplexx

Typical Use Cases

With Drvless you can, among other things:

Mann schaut grübelnd und konzentriert auf einen Laptop. Vor ihm ist ein Notizbuch aufgeschlagen und er hat einen Stift in der Hand.
Nahaufnahme von Hand die auf einem Tablet tippt. Darüber schweben transparente Icons: Haken, Dokumente, Pfeile.

Driveless offers, among other things, the following advantages:

Ensure quality and save time, with Driveless Automation