unthinkable
Case study · Qdabra Software, Washington, US · electronic forms and web services

Qdabra's customers get new features sooner, tested and free of production issues.

Qdabra wanted to bring new features to its customers first in a competitive market, without quality slipping as the product grew.

United States

What changed

85%less testing time (as reported)
60%faster time to market (as reported)
30%lower QA costs (as reported)
What stood in the way

What stood in the way.

What stood in the way
  • New features and modules made the application more complex and harder to keep at quality.
  • There was no standard QA process, no test metrics, no SLAs and no review mechanism.
What changed
  • 85%less testing time (as reported)
  • 60%faster time to market (as reported)
  • 30%lower QA costs (as reported)
What we built

What we built.

  • Manual testing of the core products across platforms and devices, alongside test automation of the whole workflow.
  • A test automation infrastructure in CodeceptJS with reports from Mocha, cutting regression effort by 80-85%.
  • Performance testing for enterprise-size networks, central test dashboards and optimised scripts, including a single login that cut a 3-hour run to 30 mins.
  • A coded continuous delivery pipeline joined to Agile and DevOps practice.
  • CodeceptJS
  • Mocha
  • Continuous delivery
  • Performance testing
What it shows

What this work shows about us.

Quality as a process, not a phase

Test processes, metrics and reporting came first, then automation that runs on every release.

Faster releases without new risk

Regression effort fell by 80-85% while the delivery flow kept running as before.

Want test automation like this for your product? Tell us what you want to change. Our AI assistant, Ask Unthinkable, helps you define your requirements, then connects you with the right team.

Start your plan ↗
If we built it today

If we built it today, with AI.

This work came before today's AI. If Qdabra Software asked us now, this is what we would add, step by step.

Testing a release

An agent would write and update test cases from each new feature's specification and run them, for QA engineers to review. Engineers still decide what is ready to release.

Finding the cause

An agent would read a failed test run, group the failures by likely cause and open tickets with the evidence. Developers still fix the code.

Ask Unthinkable

Want this for your business?

Tell us what you run or what you're building. Our AI assistant, Ask Unthinkable, helps you define your requirements, then connects you with a senior AI engineer.

Send us a note instead

Required

Thanks. A senior AI engineer will reply to you.
u
Ask UnthinkableClarity first, then the right team
Your conversation

An AI agent. This prototype uses prepared answers and sends nothing.