top of page

When a Small App Update Creates Bigger Problems: QA Challenges in Digital Health

Writer: Seema K Nair
Seema K Nair
7 days ago
5 min read

A new feature is ready. The interface has been improved, a few existing functions have been updated, and the development team is preparing for release.

Everything seems to be working as expected. But has the team checked what else might have been affected?

In digital health applications, features are often closely connected. A change to session tracking could affect progress updates. An adjustment to notifications might change how users return to an ongoing activity. Even a minor interface improvement could make an existing feature harder to access on certain mobile devices.

These issues can be easy to miss when testing focuses only on the latest changes.

For HealthTech product teams, the challenge is not just checking whether a new feature works. It's understanding how an update affects the rest of the application.

Here are a few areas worth looking at before the next release.

1. A change to one feature can affect the entire user journey


Consider a digital health application that offers guided activities, tracks completed sessions, and displays progress through a dashboard.

The team decides to improve the session timer. The updated timer works correctly, but does the application still record completed sessions? Does the dashboard show the right progress? What happens if a user pauses an activity and resumes it later?

These are connected parts of the same user journey, and testing the timer alone may not reveal problems elsewhere. What should teams check before release?

  • Whether users can complete important tasks from beginning to end.

  • Whether information passes correctly between connected features.

  • Whether existing functionality still works after an update.

  • How the application handles interrupted or partially completed activities


Looking at the complete journey helps teams catch issues that individual feature checks can miss.

2. Are integrations still communicating correctly?


Digital health applications often rely on APIs, notification services, authentication providers and other external platforms.

A change to one component can affect how information moves between these systems.

For example, an application might save a user's activity successfully but fail to update the connected dashboard. A notification might arrive but take the user to the wrong screen.

The individual components may appear to work, but the interaction between them tells a different story.

What should teams check before release?

  • Whether API requests and responses contain the expected information.

  • Whether connected services handle successful and failed requests correctly.

  • Whether authentication and user sessions continue to work.

  • Whether notifications trigger the right actions.

  • How the application responds when a connected service is slow or unavailable.

Integration testing helps identify problems that may not be visible when each component is tested separately.


3. Small changes can lead to data inconsistencies


Think about an application that records completed activities, tracks progress and allows users to revisit previous sessions.

If an update changes how activity records are saved, the team needs to check more than whether the information is stored successfully.

Does the latest activity appear correctly? Does the progress dashboard reflect the same information? What happens when a user updates an existing record or repeats an activity?

A problem with data handling can affect several parts of the application, even when the individual screens appear to work normally.

What should teams check before release?

  • Whether information is saved and retrieved correctly.

  • Whether updated records appear consistently across relevant screens.

  • How duplicate or incomplete entries are handled.

  • Whether information remains consistent when users move between features.

  • Whether access restrictions work correctly for different user roles.

These checks are particularly important when users rely on accurate records and progress information.


4. Has the update affected accessibility?

A redesigned interface might look better, but has it become harder for some users to navigate?

A button could lose its visible keyboard focus. A colour change might make important status information difficult to distinguish. A popup could open correctly but prevent keyboard users from navigating the rest of the screen.

These are the kinds of issues that can go unnoticed when testing focuses mainly on visual appearance.

What should teams check before release?

  • Whether important actions can be accessed using a keyboard.

  • Whether focus moves correctly when menus, dialogues, and popups open or close.

  • Whether text, controls and status indicators have sufficient contrast.

  • Whether form fields and buttons have meaningful labels.

  • Whether content works with assistive technologies.

Accessibility checks are worth revisiting whenever teams make changes to navigation, layouts or interactive elements. Previously tested features can also develop new accessibility issues after an update.

5. Does the application work consistently across mobile devices?


A feature that works perfectly on one device might behave differently on another.

Consider someone completing an activity on their phone. They receive a call, switch to another application or temporarily lose their internet connection.

When they return, does the activity resume correctly? Is their progress still there? Does the screen display as expected?

These everyday situations deserve attention during mobile application testing.

What should teams check before release?

  • Navigation and functionality across supported devices and operating systems.

  • Layouts, buttons and interactive elements across different screen sizes.

  • Application behaviour when internet connectivity is interrupted.

  • What happens when users switch applications or lock their screens.

  • Whether progress is retained after interruptions.

  • Whether performance remains acceptable during normal use.

Testing across devices and real-world usage scenarios helps teams find issues that might not appear during development or on a single test device.


6. Regression testing: Are previously working features still working?


When a new feature is introduced or existing functionality is modified, other parts of the application can be affected too.

For example, an update to a dashboard might interfere with navigation. A change to authentication could affect existing user sessions. An improvement to an activity workflow might alter how completed sessions are recorded.

This is where regression testing becomes important. Rather than focusing only on the new functionality, QA teams revisit existing features to check whether they still behave as expected.

What should teams check before release?

  • Critical user journeys that worked before the update.

  • Features connected to the modified functionality.

  • Existing integrations and important API interactions.

  • Previously reported defects to check that they have not returned.

  • Automated test cases covering frequently used functionality.

Regression testing doesn't mean repeating every test after every change. The focus should be on identifying what could have been affected and prioritising those areas based on the scope of the update.

Building a better QA approach for digital health applications


Testing doesn't have to become a lengthy exercise before every release. What matters is knowing where to focus.

Before an update goes live, product teams should have a clear understanding of what has changed, which areas could be affected and what needs to be checked.

A practical QA approach involves:

  • Reviewing the scope and potential impact of each update.

  • Identifying important user journeys and business-critical functionality.

  • Prioritising tests around areas affected by the changes.

  • Combining functional, integration, accessibility and regression testing.

  • Checking application behaviour across supported mobile devices.

  • Reviewing test results and addressing critical issues before release.

Automation can make repeatable checks easier to run across development cycles. However, manual testing remains valuable when exploring unexpected behaviour, assessing usability and investigating scenarios that require human judgement.

The right balance depends on the application's functionality, release frequency and testing requirements.


Conclusion:


A new feature working correctly is a good start. But product teams also need to know that existing functionality, connected systems and important user journeys haven't been affected.

Making these checks part of the release process helps teams identify potential issues earlier and make more informed release decisions.

At CalibreCode, we work with product teams to assess application functionality, user journeys, integrations, accessibility and regression requirements through independent software testing.

Whether you're introducing new features, improving an existing platform or reviewing your current QA approach, it's worth looking beyond the latest change.


The question isn't just whether the update works. It's whether everything around it still does.

Explore our HealthTech QA services to learn more about our approach to software testing for digital health applications.


Comments


bottom of page