
Manual and Automated Testing for the Mental Health Support Application
Challenge
The client, an online mental health support platform, did not have an in-house QA specialist and needed an experienced expert who could join the development team and establish a reliable testing process. The application connects users with licensed therapists through text-based chat, so stable functionality and a user-friendly experience were essential.
The initial requirement was to perform comprehensive manual testing of the mobile application, including functional, UI, compatibility, and accessibility testing. As the product continued to evolve and new functionality was developed, the volume of repetitive testing tasks also increased. The client therefore needed to introduce automated testing to make regression checks more efficient while maintaining sufficient coverage of the application’s functionality.
The client, an online mental health support platform, did not have an in-house QA specialist and needed an experienced expert who could join the development team and establish a reliable testing process. The application connects users with licensed therapists through text-based chat, so stable functionality and a user-friendly experience were essential.
The initial requirement was to perform comprehensive manual testing of the mobile application, including functional, UI, compatibility, and accessibility testing. As the product continued to evolve and new functionality was developed, the volume of repetitive testing tasks also increased. The client therefore needed to introduce automated testing to make regression checks more efficient while maintaining sufficient coverage of the application’s functionality.
Solution
QA Madness provided a full-time QA engineer experienced in both manual and automated testing. At the initial stage, the team studied the application and researched how the questionnaires and psychological tests used in the product generally work. Because the functionality was still evolving, QA engineers used flexible checklists instead of test cases for the initial testing process.
Manual testing covered functional and UI aspects, as well as compatibility and accessibility. QA engineers tested different application flows, input fields, forms, buttons, and links, and verified the application on real Android and iOS devices. Accessibility testing included checks against Web Content Accessibility Guidelines and ADA Accessibility Standards. Smoke, regression, and retesting were performed after code iterations and bug fixes.
After two years of cooperation, the client requested automated testing. The QA engineer created detailed test cases, selected the most suitable cases for regression automation, and maintained the resulting test suite. Regression was initially performed manually after each release, while the majority of repetitive regression checks were gradually automated as the application became more stable.
QA Madness provided a full-time QA engineer experienced in both manual and automated testing. At the initial stage, the team studied the application and researched how the questionnaires and psychological tests used in the product generally work. Because the functionality was still evolving, QA engineers used flexible checklists instead of test cases for the initial testing process.
Manual testing covered functional and UI aspects, as well as compatibility and accessibility. QA engineers tested different application flows, input fields, forms, buttons, and links, and verified the application on real Android and iOS devices. Accessibility testing included checks against Web Content Accessibility Guidelines and ADA Accessibility Standards. Smoke, regression, and retesting were performed after code iterations and bug fixes.
After two years of cooperation, the client requested automated testing. The QA engineer created detailed test cases, selected the most suitable cases for regression automation, and maintained the resulting test suite. Regression was initially performed manually after each release, while the majority of repetitive regression checks were gradually automated as the application became more stable.
Results
The QA Madness team established a long-term testing partnership with the client and continuously adapted the QA process as the application evolved. More than 500 test cases were executed across six mobile devices, providing coverage of the application’s functionality and behavior across different hardware and platforms.
Approximately 100 critical defects were identified and reported during testing. Addressing these issues improved the application’s stability and contributed to a better user experience. The team also incorporated accessibility and compatibility checks into the testing process, which was particularly important for a healthcare application intended to serve a broad range of users.
The introduction of automated regression testing reduced the amount of repetitive manual work and improved testing accuracy. As the application became more stable, most regression checks were automated, helping shorten testing turnaround times and accelerate the release cycle.
The QA Madness team established a long-term testing partnership with the client and continuously adapted the QA process as the application evolved. More than 500 test cases were executed across six mobile devices, providing coverage of the application’s functionality and behavior across different hardware and platforms.
Approximately 100 critical defects were identified and reported during testing. Addressing these issues improved the application’s stability and contributed to a better user experience. The team also incorporated accessibility and compatibility checks into the testing process, which was particularly important for a healthcare application intended to serve a broad range of users.
The introduction of automated regression testing reduced the amount of repetitive manual work and improved testing accuracy. As the application became more stable, most regression checks were automated, helping shorten testing turnaround times and accelerate the release cycle.