Test Report

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. This ensures the readiness of the software for use in multiple countries and diverse identity ecosystems.

Overview and Scope

Authentication & Security

• Verifier Authentication: Validate login, logout, session management, and re-authentication.
• DID-based Client Authentication: Verify decentralized_identifier client_id and DID validation.
• VP Request Security: Validate server-side VP request expiry, nonce validation, and duplicate VP submission prevention.

Authentication & Security

• Verifier Authentication: Validate login, logout, session management, and re-authentication.
• DID-based Client Authentication: Verify decentralized_identifier client_id and DID validation.
• VP Request Security: Validate server-side VP request expiry, nonce validation, and duplicate VP submission prevention.

Verification Request Management

• Authorization Request: Validate OpenID4VP Authorization Request generation.
• QR Code & Deep Link: Verify QR code and deep link generation for wallet verification.
• VP Session Management: Validate VP session creation, retrieval, and status updates.

Credential Verification

• DCQL Processing: Validate DCQL query processing and credential matching using type_values.
• Credential Formats: Verify SD-JWT VC, LDP VC, and DC+SD-JWT credential verification.
• Holder Binding: Validate cryptographic holder binding and selective disclosure.

OpenID4VP Compliance

• Client Metadata: Validate vp_formats_supported, ldp_vc, and updated OpenID4VP v1.0 client metadata.
• Protocol Compliance: Verify Authorization Request and VP Response compliance with OpenID4VP v1.0.

Verification Results & Error Handling

• Verification Results: Validate verification status, verified claims, and audit logging.
• Error Handling: Verify protocol-compliant error responses for invalid client IDs, expired requests, duplicate submissions, invalid nonce, and malformed VP tokens.

Test Approach

The Functional verification of the Inji verify 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. The validation adopts a persona-based testing strategy, simulating real-world user scenarios across diverse device matrices and multi-language configurations to ensure robustness in both online and offline environments.

• Functionality

Test Organization

Table: Test Organization

Name	Functional Role	Responsibilities
Nitin	QA Lead Engineer	Verifying the functionality, stability of the application,and report preparation. and performing combination testing.
Chaitanya K	QA Manager	Overviewing 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.
• Coverage Distribution: Execute test scenarios across a broad matrix of browsers on Windows, Android, and iOS devices, spanning multiple user personas to ensure end-to-end compatibility coverage.

Test Devices

Table: Test Devices

Device Model	OS and BLE version
iPhone 11	iOS 26.1 BLE 5.0
ONE PLUS 12R	Android 15 BLE 5.3
Xiaomi Redmi NOTE 13 Pro	Android 15 BLE 5.2

Browser Versions

Used the below browser versions in testing INJI Verify

• Chrome: Version 123.0.6312.124
• Firefox: Version 125.0.1
• Edge: Version 124.0.2478.51
• Safari : Version 17

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/inji-web:develop

Images (released env)
injistack/apitest-mimoto:0.22.0
injistack /inji-verify-service:0.18.2
injistack /inji-verify-ui:0.18.2
injistackqa/inji-certify-with-plugins:0.14.0
mosipid/authentication-demo-service:1.2.0.1
mosipid/authentication-internal-service:1.3.0
mosipid /authentication-otp-service:1.3.0

Test Execution Report

Automation INJI Verify API

Table: API Automation Result

Total	Pass	Fail	Known Issues	Ignored
204	204	0	0	0
Test Rate: 100% With Pass Rate: 100%

Defect Metrics

Known Issues Metrics

This section focuses on the known issues list

For a detailed overview and the complete list of issues related to Inji Verify, please click here.

Conclusion

Smoke testing and feature health verification for INJI Verify v1.0.0-alpha.1 were successfully completed. The verification covered the core verifier functionalities, including OpenID4VP authorization request generation, VP session management, credential verification, DCQL processing, client metadata validation, and end-to-end verification flows. No critical or blocker defects were identified during execution, and the build demonstrated stable behavior across the validated features.

Based on the smoke testing and feature health verification results, the INJI Verify v1.0.0-alpha.1 build is considered stable and is recommended for release. Any remaining known issues will continue to be tracked and addressed as part of the planned release 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 satisfied 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
Chaitanya K	QA Manager	Overviewing 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
V1.0	04/08/2026	Nitin	Chaitanya K

Document History

It outlines the strategy used to ensure a comprehensive evaluation.

Version	Author	Date	Review	Affected Sections
V1.0	Nitin Hegde	04/08/2026	Chaitanya Kesiraju	New Document

Github link for more on reports is here.