How Care Solutions uses visual, AI-powered test automation to safeguard complex Progress OpenEdge applications—without programming, without invasive access to the core system and with significantly less manual testing effort.
Care Solutions GmbH develops digital solutions for the healthcare sector. Its portfolio includes applications for nursing documentation, medical documentation and intensive care documentation.
These solutions support business-critical workflows in hospitals and healthcare facilities. Reliability, quality and stable releases are therefore essential.
Care Solutions GmbH has its headquarters in St. Veit an der Glan, with development based in Klagenfurt. The company was founded in 2010 and operates across a broad range of business areas, including development, qualification, support & documentation, product management, consulting, regulatory affairs, quality management, and marketing. Its core products are nursing documentation (NCaSol), medical documentation (MedCaSol), and intensive care documentation (CCaSol). Following the acquisition of its predecessor company in 2014, Care Solutions GmbH has held full responsibility for development ever since.
Care Solutions works with a historically evolved and highly configurable software landscape. Its applications are based on Progress OpenEdge—a dynamic technology that can make conventional object-based test automation difficult.
In addition, the underlying core system is operated by a partner company, which severely limits direct technical intervention. At the same time, releases must be validated reliably across a code base of approximately 5.9 million lines of code, around 80% of which is not suitable for conventional unit testing.
Key requirements
Less manual testing effort
Before major releases, comprehensive manual test cycles were required—sometimes lasting around one month and involving test cases with up to 400 individual steps.
Low-maintenance regression testing
Tests needed to remain reliable even when user interfaces, layouts or technical IDs changed.
No dependency on object IDs
A previously evaluated object-based approach could not reliably handle the application’s dynamic and highly configurable nature.
Test automation without coding
The quality assurance team needed to create, maintain and execute test cases independently—without programming skills.
Automated test execution outside working hours
Recurring smoke tests, regression tests and stability checks needed to run reliably and unattended.
Care Solutions has been using Drvless since 2023. The decisive advantage was its visual, AI-powered approach: Drvless recognises applications through visible screen content and interacts with them using mouse, keyboard and touch input—just as a human user would.
This makes test automation less dependent on technical object IDs, internal system structures or invasive integrations. Drvless interacts with the system under automation visually and can be used without plug-ins, system-specific libraries or installation on the system being tested.
Visual UI recognition
Drvless recognises and operates elements based on their visible appearance. If technical IDs, layouts or control styles change, automation can remain stable.
No-code test creation
Test cases can be created using Capture & Abstract and transferred directly to Drvless for execution – without programming knowledge.
Execution Lists and scheduling
Smoke tests, regression tests and stability checks are grouped into defined test packages and launched automatically at scheduled times.
Integration into existing processes
At Care Solutions, test runs are triggered via Jenkins. Results are monitored and analysed through a Jira-integrated Xray dashboard, configured to the team’s specific requirements.
Non-invasive test automation
Drvless does not require installation on the system under automation. This makes it suitable for environments in which security requirements or technical limitations make conventional integrations difficult.
With Drvless, more than 50% of our tests will run automatically in the future, enabling us to save significant time and gain greater transparency.
At Care Solutions, Drvless automates more than individual test steps. It supports the complete workflow, from preparing the test environment to analysing failures.
Typical workflow
1. Prepare the test environment
Drvless supports the automated preparation of the test environment, including setup downloads, setup deployment and backup creation.
2. Assemble test packages
Recurring smoke tests, regression tests and stability checks are organised into structured Execution Lists.
3. Execute tests automatically
Test runs are launched on a schedule via Jenkins and run fully unattended between 8:00 p.m. and 4:00 a.m.
4. Analyse failures transparently
Every test step is logged. If a test fails, screenshots and the failed instruction are available for targeted analysis.
You are currently viewing a placeholder content from YouTube. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More Information| RESULT | IMPACT |
|---|---|
| Up to 75% automation potential | A significant share of previously manual tests can be automated in the future. |
| Less maintenance effort | Visual recognition reduces dependency on technical IDs and UI details. |
| Greater release stability | Nightly smoke tests, weekly regression tests and stability checks run automatically. |
| Reduced workload for the QA team | Less repetitive testing creates capacity for complex testing and further development. |
| Improved defect detection | Drvless identified configuration issues that were not visible in the previous manual test setup. |
| Greater transparency | Screenshots and step-by-step logs simplify the analysis of failed test runs. |
Care Solutions demonstrates that even complex, dynamic and difficult-to-access legacy applications can be tested successfully with automation.
Instead of relying on technical object IDs and fragile integrations, Drvless focuses on the visible behaviour of the application. This enables tests to remain robust despite UI changes, configuration variants and technological developments.
The result is less manual effort, more transparency and sustainable quality assurance for business-critical healthcare software.
You are currently viewing a placeholder content from Vimeo. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from YouTube. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More Information