From Manual Testing to Automated Excellence: Zucchetti’s Success with AskUI

May 20, 2025
linkedin icontwitter icon

Discover how Zucchetti, a leading provider of business software solutions, leveraged AskUI to transform their mobile application testing and automation processes. In this customer interview, Kevin Schneider from Zucchetti shares his team's journey, the challenges they faced, and the tangible benefits they've realized with AskUI's AI-powered automation platform. Hear firsthand how strong collaboration with Customer Support/Success and innovative product features have driven efficiency and quality in their workflows.

Tangible Results

Aspect Before AskUI After AskUI
Manual Regression Testing Required, time-consuming No longer required; process automated
Test Process Structure Traditional, manual, less structured Restructured, automated, more efficient
Customer Stability Lower, more frequent critical issues Significantly improved, fewer critical issues
Reporting Limited reporting More reports generated (e.g., Xray reports in Azure DevOps)
Automated Tests 25–30 smoke tests (critical functions only) 130 tests currently; planning 150 regression tests
Functional Validations Not specified 250–300 (e.g., payments, bookings, inventory)
Code Base Not specified ~6,000 lines (AskUI commands + TypeScript)

1. Why did you choose AskUI?

The decision to go with AskUI had already been made before I joined Zucchetti and the project where the Automation should be used. The main reason was that our software is a mobile application and runs on a .NET canvas element, traditional solutions with an id-based object recognition like Selenium simply dinʼt work in this context. Another important factor was that AskUI is a German company, which means short communication paths and easier collaboration for us.

2. What problem were you hoping to solve with AskUI?

We wanted to automate billing processes and test them on multiple parallel mobile devices all connected per P2P and working together. On that basis, it was important that communication between different controllers was possible, including transferring data from one to another. Previously, everything was tested manually and always under time pressure. Releases were often rushed, and we shortened regression testing due to lack of time – only new features and critical areas were tested. Now, with AskUI, we are faster in testing, have significantly better test coverage, and benefit from AI-powered features.

3. Were there any concerns or fears before buying?

Yes – at that time, AskUI was a young company with a new product. We asked ourselves whether it could really cover everything as well as established providers with 15 to 20 years of experience. Initially, the object recognition didn’t quite work as expected. We had to create a lot of screenshots and use custom elements. But after about two to three months, the OCR retraining feature was introduced, and since then it has worked much better. One improvement we would have wished for back in the day: was better documentation and concrete examples during onboarding. We have now been working together for one and a half years.

4. What do you like most about our product?

The support is fantastic – especially working with Customer Support. When an issue arises, a meeting is quickly set up, and together we can find a solution in a very short time. Also, new feature ideas are heard and taken seriously. Compared to other SaaS products, where you must open tickets and wait forever, this is a huge advantage. Stability is extremely important to us – and AskUI is quite stable. If there’s a bug, it’s either on our side or in our third-party software. One downside: writing code in certain scenarios can be a bit tricky, especially for people without TypeScript experience. We are excited about the upcoming agent and recorder features of AskUi. I have worked with a lot of other automation tools that have a recorder or mapping function as well as a coding base. Having both options – code, and low-code – is ideal.

5. What has changed the most since introducing AskUI?

Kevin: For me personally, a lot has changed. I no longer do manual regression testing – our entire test process has slowly been restructured. Stability for our customers has significantly improved. Critical issues occur less frequently. We now generate more reports – for example, we can use AskUI's Xray reports to input them in tools like Azure DevOps and generate Test reportsfor our client from there. Currently, we are running 130 tests in AskUI, along with 250 to 300 functional validations (e.g., different payments, booking items, and managing inventories). Altogether, the setup includes around 6,000 lines of code – a mix of AskUI commands and TypeScript. We are planning to automate around 150 regression tests – before, we had just 25 to 30 smoke tests focused on the most critical functions. Improvement suggestion: The annotate feature currently takes about two seconds per AskUI command. That adds up to about 5.5 to 6 hours of total run time. If the GUI hasn’t changed much, it would be helpful to disable the annotate function – or at least speed it up.

6. How would you describe what AskUI does?

For techies: AI-driven test automation software. For non-techies, AI-assisted software that can fully automate tasks in an application — it takes over user interactions that would otherwise need to be done manually

Summary

Zucchetti adopted AskUI to automate and improve the testing of their mobile application, which previously relied on manual, time-consuming processes. The main motivation was AskUI's unique ability to handle .NET canvas-based mobile apps—something traditional solutions struggled with. Since implementation, Zucchetti has seen faster test cycles, better coverage, and more stable releases. Customer Support/Success played a pivotal role in their positive experience, offering responsive and effective assistance. Today, Zucchetti runs hundreds of automated tests and has significantly restructured its quality assurance processes, leading to greater reliability and efficiency.

Ron van Cann
·
May 20, 2025
On this page