Healthcare App Testing under Changing Requirements

The app* determines a user’s risk of getting COVID-2019 and makes it easier to contact a doctor. It features a questionnaire, after filling which a person learns the probability of getting ill, receives recommendations, and views the contacts of appropriate hospitals if needed. The app keeps users anonymous and does not collect personal data.

* We recognize the importance of protecting our clients’ privacy and follow the policies to maintain their confidentiality and security. That is why the company name will not be disclosed.

The highlight of this app is an anonymous questionnaire that features several types of queries. Some require one or multiple answers, some don’t require a mandatory answer, and some are displayed only after a user selects a specific option. The user gets a summary based on the provided answers.

• The questionnaire is available in several languages, so it was necessary to ensure the appropriate localization of each question and summary option.
• Due to the tight deadlines, the client frequently modified the questionnaire and summaries and added new information blocks.
• The application is intended for a large number of users with different devices, IT backgrounds, and skills. To achieve broad coverage, we needed to make sure the app was user-friendly and supported by popular mobile and desktop devices.
• The client also needed to integrate the application with other products, and some degree of security testing was essential to ensure user privacy and data safety.

The client company developed the application from scratch. The cooperation started in the early stages of development.

The project team consisted of a Product Owner, Development Team, Designer, Technical Writer, Test Manager, and QA Engineers. Representatives of the medical institution were also involved. They provided and approved the wording and app logic.

The workflow was divided into sprints, but the team didn’t stick to the sprint timing strictly due to the tight deadlines. The working process featured the following stages:

Our QA team received the task.

The Product Owner outlined the work phases and set smaller tech tasks.

We wrote test cases, identified errors in logic and other aspects available at this stage.

The developers finished the code and submitted the complete functionality for testing.

The Product Owner made decisions on further actions based on the testing results.

QA is essential when it comes to the frequently changing requirements. Every time the client modified the app content, our QA engineers performed testing to identify logical, functional, interface, and localization defects.

To ensure the fit for diverse user types, the team performed cross-browser, cross-platform, and usability testing. A vast scope of mobile devices QA Madness has in hand is a must for such applications.

We also tested some security-related aspects. For example, the QA specialists checked if the data was imported correctly after integration with another application and whether the questionnaire started over after a new user logged with the same device.