For the complete documentation index, see llms.txt. This page is also available as Markdown.

Test Report

Coming Soon !

Introduction

The scope of testing is to verify fitment to the specification from the perspective of Functionality, Configurability, and Customizability. Verification is performed not only from the end-user perspective but also from the System Integrator (SI) point of view. Hence, the Configurability and Extensibility of the software are also assessed.

Overview and Scope

Authentication & Security

  • Biometric unlock: Verify app access using device-registered biometrics (fingerprint/face) and the fallback to passcode if biometric disabled.

  • Passcodes unlock: Validate the setup, verification of a numeric PIN for securing app access.

  • Key Management: Validate the rotation of keys within the device with drag and drop options from the application.

  • Wallet binding: Validate that the wallet binding (VC activation) and its credentials are securely bound to the specific device.

  • Logout: Verify that logging out clears the active session and requires re-authentication to re-enter the application.

Credential Management (Download & Storage)

  • VC download via MOSIP: Test fetching credentials using a UIN or VID with OTP authentication against the MOSIP backend.

  • VC downloads via Sunbird: Test the successful download and rendering of credentials from Sunbird RC-based registries.

  • Credential Offer: Test the end-to-end flow of receiving a credential offer via QR and initiating the issuance process.

  • SD JWT VC download: Verify the download and selective disclosure capabilities of credentials in SD-JWT format.

  • SVG VC download: Check the download and correct visual rendering of credentials using dynamic SVG templates defined by the issuer.

  • Credential registry: Verify the wallet's ability to fetch and display trusted issuers and their metadata from the central registry.

  • Backup and restore: Test the backup of credentials to cloud storage and their successful restoration on a new device.

  • Deleting VC: Validate the permanent removal of a credential from the wallet and UI.

Credential Usage & Sharing

  • BLE (offline) VC sharing: Share VCs offline using Bluetooth Low Energy with face auth and fingerprint biometric authentication.

  • Pinning a VC: Verify the functionality to pin frequently used credentials to the top of the home screen for quick access.

  • OpenID4VP: Test the online presentation and sharing of credentials to a verifier using the standard OpenID for Verifiable Presentations flow.

  • QR code Login: Verify using the wallet to scan a QR code and authenticate user login for third-party Relying Parties.

User Experience & Navigation

  • Multi-language support: Check UI rendering, label translations, and layout stability across all supported languages (Kannada, Hindi, Tamil, Arabic, Filipino, and English).

  • Deep link navigation (same device flow): Verify that external links (e.g., inji://) correctly open the app and navigate to specific screens.

Test Approach

The Functional verification of the Inji Mobile Wallet application is performed on Android and iOS platforms to ensure alignment with product specifications and business requirements. Analyzed with respect to functional stability, data integrity, and UI consistency.

  • Functionality

  • Configurability

Test Organization

Table: Test Organization

Name
Functional Role
Responsibilities

Nitin Hegde

QA Lead

Verify the functionality, stability of the application, and report preparation.

Chaitanya K

QA Manager

Reviewing the test execution and review of the report.

Test Planning

  • Data Readiness: Validate the availability of all services along with configured identity schemas (UIN/VID) to support biometric and authentication flows.

  • Data Strategy: Refresh test data for every cycle by generating new QR codes for credential offers and preparing specific datasets for Sunbird/e-Signet integrations.

Test Devices

Table: Test Devices

Device Model
OS and BLE version

iPhone 13

iOS 26.6 BLE 5.0

Realme GT NEO 3T

Android BLE 5.2

Test Environment

Table: Test Environment

Images (qainji env)

injistackqa/inji-verify-service:1.0.x

injistackqa/inji-verify-ui:1.0.x

injistackqa/inji-certify-with-plugins:1.0.x

injistackqa/mimoto:1.0.x

injistackqa/inji-web:1.0.x

Images (released env)

injistack/inji-verify-service:0.18.2

injistack/inji-verify-ui:0.18.2

injistack/inji-certify-with-plugins:0.14.0

injistack/mimoto:0.22.0

injistack/inji-web:0.17.0

injistack/inji-certify-with-plugins:0.14.0

mosipid/authentication-service:1.3.0

mosipid/authentication-internal-service:1.3.0

mosipid/authentication-otp-service:1.3.0

mosipid/kernel-notification-service:1.3.0

mosipid/pre-registration-application-service:1.3.0

Test Execution Report

Test case execution summary

Smoke testing and feature health verification were successfully completed across both Android and iOS platforms. No critical or blocker issues were identified during execution, confirming the overall stability of the build for further testing.

Defect Metrics

Known Issues

This section focuses on the known issues list for the alpha release

Known issue Link - 1.0.0-alpha.1 Known issues Inji wallet

Conclusion

Smoke testing and feature health verification for Inji Mobile Wallet v1.0.0-alpha.1 were successfully completed across both Android and iOS platforms. The verification covered the core application functionalities, and no critical or blocker defects were identified during execution. The build demonstrated stable behavior across the validated features.

Based on the smoke testing and feature health verification results, the Inji Mobile Wallet v1.0.0-alpha.1 build is considered stable and is recommended for release. The remaining known issues will continue to be tracked and addressed as part of the planned release of roadmap and future iterations.

QA Approval

The build has successfully met the defined exit criteria and is recommended for release. The approval is based on the following conditions:

  • Test Case Execution Completion: 100% of planned scenarios executed.

  • Defect Status: No Blocker defects remain open.

  • Documentation Sign-off: All test artifacts and reports are finalized.

  • Test Environment Stability: The test environment remained stable throughout the execution cycle.

Table: Report is signed off details

Name
Functional Role
Responsibilities

Chaitanya K

QA Manager

Reviewing the test execution and review of the report.

Appendix

This includes additional reference information for the report. It contains a history of document versions and a list of acronyms and their meanings.

Appendix A: Versions

Version
Date
Author
Reviewers

V2.0

04/08/2026

Nitin Hegde

Chaitanya K

Appendix B: Acronyms

Acronym
Literal Translation

MOSIP

Modular Open Source Identity Platform

UIN

Unique Identification Number

VID

Virtual Identification

SVG

Scalable Vector Graphics

SD-JWT

Selective Disclosure - JSON Web Token

VC

Verifiable Credentials

OpenID4VP

OpenID for Verifiable Presentations

PDI

Presentation During Issuance

Document History

It outlines the strategy used to ensure a comprehensive evaluation.

Version
Author
Date
Review
Affected Sections

V2.0

Nitin

04/08/2026

Chaitanya Kesiraju

Updated for release 1.0.0-alpha.1

Last updated

Was this helpful?