Since we received the tasks after the new functionality was developed, work by estimate suited this scenario best. Before preparing the checklist, the team studied the product and did a small research on how questionnaires and psychological tests featured in the application work in general, online and offline.
Using checklists was more effective at the initial stage than test cases, as the functionality was under development. Checklists enable more flexibility in updating documentation and become a good background for knowledge maintenance in the future.
Manual Testing
Functional and UI testing make a default minimum QA package for every new application. When working with healthcare software, it is also crucial to check for compatibility and accessibility.
QA engineers checked various flows and features to see what works as planned and what requires fixes. The team also checked the input fields, forms, buttons, links, etc., for functionality and performance.
Regarding compatibility testing, engineers used real Android and iOS devices to get accurate results on the app’s behavior on different screens and hardware. Since the app relates to the healthcare niche, we also provided an accessibility test and checked the app’s Web Content Accessibility Guidelines and ADA Accessibility Standards.
One more important aspect was change-related testing. Ensuring stable functionality and performance is critical for new products, with functionalities developed from scratch and evolving through time. After each interaction, the QA team ran the following checks:
- Smoke testing – inspection of the most crucial functionality of the application, such as registration, logging in, and the main functions.
- Regression testing – verification of the stable functionality after code iteration; it is necessary to confirm that unchanged functions haven’t been affected accidentally.
- Retesting – examination of the functionality after bug fixes to confirm that the defects are gone, and everything works as expected.
Automated Testing
Two years into our cooperation, the client requested to set up automated testing. Given the workload, we agreed on assigning an expert in both manual and automated testing to work with the project full-time.
The manual testing covered the whole functionality of the app, and regression was automated. To set up the process, the QA engineer:
- Wrote test cases to cover the maximum of the app’s functionality. These tests were executed after every build because each iteration came with many code changes.
- Selected test cases for regression to use as the basis for automated scripts. It also involved further review and maintenance of the test suite.
When the development was at the active stage, the team released new builds once every two to four weeks. After every release, the regression was run manually first. When the application became more stable, the majority of the regression tests were automated, with just a few left for manual inspection.
Our healthcare software testing services include specialized QA for mental health platforms with strict accessibility and data privacy requirements.