We engaged a1qa to assess our QA and automation, set up automated UI testing, and integrate checks into CI in Azure DevOps using open-source tools. Their experience with Azure DevOps matched our stack.
a1qa built our test automation from the ground up. They added multi-browser and multi-role coverage. They enabled parallel execution. They integrated the suite into our Azure DevOps pipelines.
… We value the partnership and the results delivered by a1qa.
Chief Technology Officer
The client, a US-based risk services provider focused on exceeding profitability targets and providing world-class user support, developed a B2B product for medical and insurance companies. However, a lack of structured QA and test automation led to ad hoc workflows and delivery bottlenecks, extending release cycles to 1.5–2 months.
That’s why the client was looking for an experienced software testing provider who would be able to mitigate their QA pain points with professional services.
Initially, the client contacted a1qa for a short-term consultation to help lead their automation efforts. This led to a focused 1.5-month pilot allowing a1qa to build an automation solution and demonstrate its value.
After the pilot, a1qa expanded its work to formalise the client’s QA processes, build test automation, and train the client’s teams within its existing Scrum workflow. The engagement included the following activities:
The partnership began with QA consulting to address the client’s request for a test automation strategy. The initial assessment found no formal QA process or structured test documentation. a1qa created an implementation plan covering automation and the wider testing life cycle. This work set the direction for the wider engagement.
Following the initial assessment, a1qa’s QA manager found that testing bottlenecks were often linked to broader process challenges, including unclear sprint scope and requirements. Based on these findings, a1qa helped establish clear quality gates, a “Definition of Ready,” a “Definition of Done,” and formal QA sign-offs before releases.
To address specific gaps like limited visibility into test coverage at the start and inconsistent quality in early developer-written tests, a1qa implemented formal tracking by functional area and adjusted the code review process to include a mandatory reviewer from the automation team. These changes helped reduce testing bottlenecks and supported the move to a two-week release cycle.
Additionally, to accelerate the client’s release cycles, a1qa implemented shift-left testing. This brought quality activities into the earliest stages of the development life cycle, helping teams find and prevent defects sooner. a1qa implemented this through three key practices:
a1qa reviewed the client’s processes and team skills, then built a Selenium-based automation framework using Aquality Automation. The team created more than 1,000 automated tests, some covering dozens of document combinations. To achieve this, the team had to engineer solutions to solve several significant technical hurdles:
During a discovery phase, a1qa assessed the product’s current state to identify performance issues and assist in defining performance metrics. The work included setting up a performance environment and executing a full spectrum of preliminary runs, including calibration, stress, load, and client-side tests.
Quality assurance workflows were transformed from the previous ad-hoc approach to a systematic process. This included creating over 3,300 test cases covering full acceptance criteria, integration points, positive/negative scenarios, and comprehensive E2E business scenario checks. QA engineers also conducted testing on Google Chrome, Microsoft Edge, and Mozilla Firefox browsers. The low rate of detected cross-browser defects allowed a1qa to advise the client on optimizing their support strategy, saving future testing effort.
A key part of the strategy was to empower the client’s experts to sustain the new quality standards. a1qa conducted training sessions for developers and QA engineers, enabling the client to independently maintain and extend the established quality processes and automation assets.
