---
title: "Testing the completed Authenticator for Android"
slug: "dpo-authenticator-sdk-for-android-testing-the-completed-authenticator"
updated: 2026-10-27T20:13:21Z
published: 2026-10-27T20:13:21Z
canonical: "docs.onespan.com/dpo-authenticator-sdk-for-android-testing-the-completed-authenticator"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.onespan.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Testing the completed Authenticator for Android

## Using TutorialAppPlus

You can test your ASM implementation with the Android Tutorial App.

For details on building and using Tutorial App, see [Tutorial App for Android](/dpoa/docs/s3suite94-tutorial-app-for-android-1).

For details on using standalone (remote) ASM with Tutorial App, see [Using Remote ASMs with Tutorial App](/dpoa/docs/s3suite94-tutorial-app-for-android-1#using-remote-asms-with-tutorial-app).

For details on configuring the new ASM on the Server, see [Configuring Your UAF Authenticators](/dpoa/docs/s3suite94-step-3-create-fido-policies-1#step-3a-create-a-fido-policy-for-uaf-authenticators).

## Using the FIDO Alliance Conformance Tool

Before your completed authenticator can achieve FIDO certification, you must test it using the conformance testing tool available through the FIDO Alliance website. Authenticator implementers must have a Vendor ID and metadata for each implementation of an authenticator. For more details on FIDO certification and conformance self‐validation testing, see [FIDO Alliance documentation](https://fidoalliance.org/certification/conformance/).

To ensure that your ASM achieves conformance, you need to collect logging information which you input to the conformance self-test tool. Information captured in logcat includes the ASM commands received from the Client, as well as ASM responses sent to the Client. Contact the FIDO Alliance for more details on what logging info to capture.