Biometric sensor on mobile devices enable powerful functionality for mobile applications. Just a decennary ago, being able to use fingerprints, vox input and other biometric data sources within applications remained generally a dream. Today, it ’ s commonplace.

With this new functionality comes a challenge for QA teams: Biometric sensors and data must too be tested decently in order to ensure a character mobile covering exploiter experience. If biometric information is not properly addressed by your DevOps team ’ s testing workflow, then performance, security or other trouble stemming from biometric information sources could undercut the benefits of habituate biometric data in the first place.

This article explores some of the challenges for QA teams that biometric data creates within roving coating and identifies scheme for addressing them through software testing.

What Is Biometric Data?

Put simply, biometric information is any type of data that is based on the physical characteristic of a human being. (Some people might say that biometric data could be derived from any character of organism, but since today ’ s mobile devices currently focus on human-generated biometric data, we ’ ll limit the scope of this article to that context.)

Examples of biometric information that can be amass by many peregrine device today include:

• Fingerprints

• Voice input

• Facial images

• Iris scan

SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

Because biometric sensors like fingerprint readers are now so mutual on smartphones, it can be easy to forget only how refreshing the far-flung use of this technology is. Fingerprint readers were introduced to the mainstream smartphone market only in 2013, when Appledebuted the iPhone 5S. And although mobile devices have been capable of employ voice stimulant for some clip, it has solely recently turn common to use vox identification for assay-mark purposes. Facial image credit and flag scanning are even new.

It ’ s deserving noting, too, that we are only at the beginning of the biometric data revolution in nomadic device. Researchers are already working onsensorsthat can analyze profligate, spit and more with the help of a smartphone. Although such sensors presently function as peripheral devices that associate outwardly to the smartphone, it is likely but a matter of time before they become directly integrated into mobile device.

Biometric Data and Mobile Software Testing

The biometric gyration is exciting for mobile software developers. Biometric data creates innovative opportunities for authenticate user, personalizing interaction with software, and lots more.

Yet the integration of biometric data into roving applications also exhibit challenges for QA squad. They include the following.

Collecting Biometric Data for Testing

Obtaining accurate software testing results prior to production requires having accurate real-world datum to help drive pre-production tests. In general, QA teams can acquire non-biometric data for this purpose easily enough by taking sample of data from production environments and feeding it into exam environments.

When you ’ re dealing with biometric data, however, this approach may not act. There may be compliance and morality issues associated with collecting biometric data from real-world users and using the data for testing. In addition, if your biometric data sampling sizing is too small, it may not accurately represent real-world conditions in all of their biological complexness and diversity. It ’ s easier to collect a representative sampling of data about, say, Web traffic for examine purposes than it is to generate a representative collection of vocalisation input.

In some situations, there may not be a pure resolution to this challenge. It simply may not be possible to collect enough reliable biometric data for pre-production testing. In that case, the better solution would be to build a continuous quiz loop that ensures that problems associated with biometric datum or detector can be detected apace in production, even if they are not caught by pre-production tests. Although in an ideal world, problems would ne'er hap at all in production, it ’ s withal better for your QA team to find out about a production problem quickly than to wait until users part complaining before the issue get to light.

Safeguarding Biometric Data

Because biometric datum can often be associated with individuals, it raises major privacy and compliance issues. QA teams must work alongside security engineers, and mayhap also legal consultant, to ensure that mobile applications cover biometric datum responsibly.

Beyond simply complying with regulatory requirements, it may be useful for QA teams to perform a form of usability testing with biometric data to determine which types of information users are comfortable with for collection, and ensure that users are able to opt out of biometric functionality when appropriate. This type of testing may not be the initiative that arrive to mind when you think of usableness, but from the user ’ s perspective, it ’ s crucial for ensuring a plus experience and avoiding complaint about spyware or privacy invasion by a mobile covering.

Handling Biometric Input Failures

As powerful as biometric data stimulant may be, it can fail, like any other form of stimulant. To avert peregrine covering performance and handiness problems, it ’ s important for QA teams to ensure that backup input methods are available when biometric input fails.

In former words, if authentication via vocalisation recognition or fingerprint scanning is not working, users should get another way to log into an application. If a earpiece ’ s camera temporarily stops working, the covering should be able to continue accepting information, even if it normally relies on facial recognition to do so. In this causa, the covering might continue collecting datum, but look until the camera comes rearward online to process it.

Simulating Biometric Data Entry

One substantial practical challenge that arises from biometric data in mobile device is that, in contrast to early types of stimulant, biometric stimulation can be hard to mime when you run tests on simulated or emulated roving device.

This is one reason why having real device usable for testing is so crucial in a biometric-driven world. Failing that, biometric data could still be fed to a peregrine trial environment running inside a simulator or copycat, although at some point prior to the application ’ s freeing, testing on real hardware with real biometric stimulus devices is even advisable, because feeding data into a simulated test environment artificially does not allow you to test all of the variables that are at play when you ’ re dealing with biometric information that is input directly via hardware.

Conclusion

Biometric data is creating exciting new opportunities for mobile developers and user. In order to take advantage of them, however, QA teams want to update examination workflows and scheme in order to ensure that mobile applications use biometric data reliably and securely. This demand will exclusively grow greater as the use of biometric information by wandering applications increases, and as new types of biometric information input become widely available.

Chris Riley (@ HoardingInfo) is a technologist who has spent 12 years help organizations transition from traditional development practices to a modern set of culture, processes and tooling. In addition to be a enquiry analyst, he is an O ’ Reilly generator, regular speaker, and subject subject expert in the country of DevOps scheme and culture. Chris believes the biggest challenges faced in the tech market are not creature, but preferably citizenry and planning.