Developing an automated suite of Research and Clinical workflow 500 test cases and 10,000 test steps, monitoring test results and reporting bugs.
The customer is a global medical innovator that uses technology to improve medical discovery and diagnostics, as well as care delivery. The company focuses on developing innovative solutions for cellular studies and genomics and has many partners around the world to address and resolve health issues, collaborating with associates to enhance outcomes for patients.
The customer has developed an embedded solution dedicated to flow cytometry analysis and visualization. The solution automates the business processes of obtaining, analyzing, and visualizing data from flow cytometry experiments.
Itransition won a tender to create and support an automated testing suite for the customer’s embedded solution.
The main project goal was to reduce QA costs and transform manual QA into partially or fully automated QA. To achieve this it was decided to develop automated Research and Clinical workflow test cases and steps, monitoring test results and immediately informing the development team of defects. Automation testing was used to achieve those goals.
Itransition’s team had to ensure that the customer’s embedded solution was compliant with the FDA’s Electronic Records and Electronic Signatures Rule (21 CFR Part 11) as well as specific customer’s requirements. Itransition’s team ran the testing suite both on remote and on-premises machines.
Itransition’s team delivered the planned testing suite on time and on budget, with all required features and functions. Automation included over 15,000 application functions (test steps) mixed into workflows (Verification Procedures) over 2 years. More than 500 test cases were implemented in total.
By automating previously manual QA, QA costs were cut by 3 times. Thanks to running higher coverage, reusable tests 24/7, bugs in the embedded solution were found earlier, reducing the number of long-term problems. As a result, the customer enjoyed higher ROI and faster time to market.
The capped dedicated team consisted of 4 automation leads, an automation engineer, a DevOps lead and a project manager.
The team had to deal with high-pressure day-to-day activities, such as 2 daily meetings, QA case updates, test deployments and runs, as well as weekly sprints. Manageable resource rotation was an ongoing added challenge. Mixing development and QA resources provided an additional benefit, since the development team helped boost code quality and performance, while QA specialists ensured process quality.
The customer’s embedded solution was tested in sprints lasting14 days. At the end of each sprint a testing report was presented to the customer, detailing: