Testing of Cross-Platform SDK for Healthcare Developers
Industry
Country
Type of Service
Cooperation Type
Project Type
Test Coverage
Overview
Kenkou has created a custom software development kit that companies can use for various purposes: to enhance telemedicine, prevent and treat chronic diseases, run remote clinical trials, and more.
In particular, this cross-platform SDK enables applications to measure pulse through a smartphone’s camera, control a person’s pulse through breathing, and detect stress. Other development teams can implement this functionality into their applications.
Challenge
Kenkou’s team needed a specialist to set up the QA process, test the application on iOS and Android platforms, describe its specifications, and control system compliance with medical certification standards.
The company requested:
- Testing for the already-developed functionality
- Ongoing quality assurance support
The functionality of the platform is constantly evolving and extending. Along with the features mentioned above, the company keeps working on new capabilities and exploring ways to use smartphone hardware – particularly the camera and accelerometer.
There are three modes for Kenkou’s partners to implement the platform’s functionality. These options differ in difficulty, the scope of ready elements, and terms of certification. Therefore, each mode must be checked as a separate piece of software.
Solution
After the onboarding, the QA specialist started figuring out how the SDK worked and prepared a testing strategy.
Testing activities
Functional and UI testing made up the majority of the QA activities. It is a typical situation for software products under development. In addition to this, the QA expert:
- Covered security testing (superficially), stability, and reliability testing. These activities are essential for healthcare software in terms of both the product’s correct work and legal requirements.
- Ran configuration testing. The application actively uses the device’s camera, and every manufacturer tends to have its specifics regarding the built-in features.
- Performed volume testing. Mobile platforms interpret C++ algorithms using Kotlin for Android and Swift for iOS. As a result, bugs that are difficult to reproduce often appear.
- Used ad-hoc testing. The product documentation wasn’t exhaustive, so the QA expert ran some checks relying on his previous experience with healthcare software.
- Wrote detailed test documentation. Kenkou didn’t have a software requirements specification, so this part was covered by our specialist.
Work scope
- New tasks in Linear; tickets in the backlog, retesting old bugs, and regression.
- Daily online meetings with the dev team to discuss the development process.
- Requirements specification writing – documenting changes and new features, test cases for new features, etc.
- Full retesting before the development team prepares to release a new build.
Results
Our QA expert worked full-time and participated in all dev, refinement, and SCRUM meetings, analyzing and explaining software particularities from user experience and compliance perspectives. Every time new features were announced or introduced, the QA engineer found critical questions that sometimes changed the approach to the development.
The development team was highly competent, so defects that break the intended feature flow were rare. Finding edge cases, however, is quite a frequent story. Such defects popped up on the border between different features and were quickly fixed. As a result, the platform was becoming more and more stable with every update.
Let’s Start a New Project Together
QA Madness helps tech companies strengthen their in-house teams by staffing dedicated manual and automated testing experts.
Relevant Case Studies
Ready to speed up the testing process?