- /
- ... /
- Catalyst
Quality Engineering for a BCBA Therapy Management Platform
A long-term QA engagement focused on setting up and refining quality processes for a rapidly evolving behavioral therapy platform consisting of web and mobile applications.
client
Ensora Health
cooperation
5 years
industry
Healthcare / Mental Health
product
Catalyst – Web & mobile platform for BCBA and their patients
About the platform
Catalyst is an advanced BCBA therapy management platform. Its web app helps therapists collect, analyze, and act on behavioral health data. It centralizes patient information, reporting, and progress tracking, enabling therapists to monitor outcomes and adjust therapy in real time.
The mobile applications complement the web app by allowing patients to securely submit their health data, which is then synchronized with the therapist’s dashboard for ongoing review and decision-making.
Team
2
Senior manual QA engineers
Tech stack
Azure DevOps
Jenkins
Linux
BrowserStack
Android Studio
AWS Device Farm
Jira
TestRail
Confluence
Postman
Swagger UI
Objectives
The client engaged us to:
- Set up a structured QA process from scratch.
- Reduce critical production defects.
- Introduce detailed specifications and acceptance criteria.
- Ensure stable releases across web and mobile platforms.
The goal was to move from reactive QA to controlled, process-driven quality management.
Challenges
- No defined QA process.
- Limited documentation and unclear specifications.
- Minimal QA involvement in the development process.
- Release delays and instability.
- High risk of critical bugs reaching production.
Our approach
Step 1
Specification and documentation as a foundation
Together with a project manager, QA engineers:
- Created 150 Confluence documentation pages.
- Defined 60 detailed user stories with acceptance criteria.
- Standardized requirements to prevent ambiguity.
Clear and detailed documentation strengthened the requirement traceability and minimized defect introduction at the development stage.
Step 2
Test coverage built from zero
- Designed flexible regression and smoke checklists.
- Created ~1,000 detailed test cases in Azure DevOps.
- Prepared comprehensive test cases to speed up onboarding.
This enabled structured testing for every release and reduced ramp-up time for new QA team members.
Step 3
Continuous release validation
- Smoke tests executed for every new build.
- Regression updated as features evolved.
- Web app tested across all major browsers.
- Mobile apps tested across supported iOS and Android versions, including beta builds.
The first major release was completed within 3 months of engagement, ahead of schedule.
Step 4
Mobile & data synchronization validation
- Verified web–mobile data synchronization.
- Prevented merge-related crashes.
- Conducted compatibility testing across devices and resolutions.
- Assisted with App Store and Google Play release procedures.
Step 5
Embedded QA collaboration
- Daily 15-minute sync meetings.
- QA fully embedded in the sprint workflow.
- Assistance with QA hiring and onboarding.
- Improved cross-team clarity and prioritization.
QA engineering outcomes
- ~1,000 structured test cases in Azure DevOps.
- 150 Confluence documentation pages.
- 25% of detected bugs classified as critical.
- 45% of detected bugs classified as major.
- Stable cross-browser and cross-device coverage.
- On-time delivery of every release.
Business outcomes
From unstable releases to predictable delivery
Releases moved from delays and uncertainty to consistent, on-time deployments. The first production version was delivered ahead of schedule, setting a new operational baseline.
Early detection of critical issues
70% of detected defects were major or critical. Catching those defects during development prevented costly production incidents and protected therapist workflows.
Reduced rework and firefighting
Clear acceptance criteria and structured documentation reduced misinterpretation, late-stage bug discovery, and repeated fixes.
Protected patient data integrity
Web–mobile synchronization and backward compatibility testing ensured no behavioral health data was corrupted or lost after releases.
Scalable QA foundation
The documented QA process enabled smooth onboarding of new QA engineers and long-term sustainability of quality practices.
Increased investor and stakeholder confidence
Stable releases and structured quality control supported positive feedback from investors and beta users, enabling continued product expansion.
Client
success
Catalyst evolved from an unstable QA environment to a mature, process-driven quality control. The platform now delivers reliable web and mobile releases while maintaining data integrity and predictable delivery timelines.
This case demonstrates Flyant’s ability to build structured QA systems from scratch for healthcare platforms where documentation, discipline, and early defect detection are critical to long-term stability.
Facing similar challenges to
Ensora Health?
