- Home /
- Case studies /
- Catalyst
QA for solution for BCBA therapist
DeviQA provided QA for Catalyst, a web and mobile platform that helps Board Certified Behavior Analysts (BCBAs) collect, review, and report behavioral data.
Technologies and tools
Azure DevOps
Jenkins
Linux
BrowserStack
Android Studio
AWS Device Farm
Jira
TestRail
Confluence
Postman
Swagger UI
Team
2 manual QA engineers
Project length
5 years
~1k
150
25%
45%
About project
Owned by Therapy Brands, Catalyst is a web application for Board Certified Behavior Analysts and other behavioral therapy professionals. The web application collects, organizes, and processes behavioral data and provides reports, visual charts, and document-printing functionality. Configurable widgets, reports, and email updates help therapists review patient data and monitor progress.
The Catalyst mobile application allows patients to submit data directly to the web platform. Assigned therapists can then analyze the information and use it to inform therapy decisions.
Before DeviQA
Insufficient QA process
No detailed specifications
Lack of QA documentation
Releases were slow and sometimes delayed
Minimal involvement of QA engineers in the development process
With DeviQA
Created and fully stabilized the testing process
Supported all popular browsers and mobile devices
Created detailed specifications with clear acceptance criteria; 150 Confluence pages and 60 user stories were created
Created and maintained flexible and comprehensive regression and smoke test checklists
Created ≈ 1000 test cases in Azure DevOps
With proper QA documentation in place, we optimized bug detection—25% of the bugs found were critical, while 45% were major
Ensured timely releases of all versions
Assisted with the release process on the App Store/Google Play
The first release was completed 3 months after we started working on the project
Initiated brief team meetings to keep all team members on the same page
Helped with QA interviews and onboarded new QA engineers
Our engagement
DeviQA’s QA engineers learned the product and began improving the testing process to support the planned release schedule.
Working with the project manager, the QA team prepared detailed specifications and acceptance criteria to clarify requirements before development. The resulting project documentation included 150 Confluence pages and 60 detailed user stories.
Daily 15-minute meetings helped the team review progress, resolve open questions, and track work against the delivery schedule.
The QA engineers created a testing checklist and updated it whenever new functionality was introduced. They later designed the complete test suite from scratch. The suite included approximately 1,000 test cases that documented the expected behavior of the product and supported the onboarding of new QA engineers. New team members could use the documented test cases to understand the product and testing scope.
The team completed its work within the planned schedule. The first product version was ready one week ahead of its scheduled release. The remaining time was used to prepare the product demonstration and support the project manager with release procedures for Google Play and the Apple App Store.
Following positive feedback from the investor and beta users, the engagement continued through subsequent releases. The team refined the QA process for ongoing web and mobile releases. Checklist-based smoke tests were executed for each new web portal and mobile application build. Critical defects accounted for 25% of all reported bugs and were identified during feature development.
Detailed product knowledge helped the QA engineers investigate defects and identify potential issues during feature development.
Using the company’s device fleet, the team tested the mobile application across supported iOS and Android versions, including beta releases, and the required tablet and smartphone configurations. The web portal was tested across the required browsers and screen resolutions.
All product versions covered by the engagement were released on schedule.
Services provided
Services
Web testing
Web testing focused on new features and functionality before their release to production. Smoke tests ran against every new build to identify blocker defects and server errors early in the release process. Backward compatibility testing checked that new changes did not disrupt existing functionality. Synchronization testing verified data exchange between the web portal and mobile applications. The team updated the smoke test suite as new functionality was introduced.
Services
Web testing
Web testing focused on new features and functionality before their release to production. Smoke tests ran against every new build to identify blocker defects and server errors early in the release process. Backward compatibility testing checked that new changes did not disrupt existing functionality. Synchronization testing verified data exchange between the web portal and mobile applications. The team updated the smoke test suite as new functionality was introduced.
Facing similar challenges to Catalyst?
Schedule a call to see how we can help you