Test Report

Introduction

The scope of testing for INJI Verify 0.18.1 is to validate the holder binding enhancements introduced in this patch release and ensure compliance with the relevant OpenID4VP and Verifiable Credential verification specifications. Testing includes positive and negative holder binding scenarios, VP result validation, regression testing of existing verification workflows, and assessment of backward compatibility. The objective is to ensure secure, reliable, and interoperable verification across diverse deployment environments and identity ecosystems.

Overview and Scope

• Home Page

• Upload Feature

• Scan Feature

• VP Verification

• OVP Flow

• SVG Support

• Multi Language

• Same Device and Cross Device flow

• V2 end point for "statusCheckFilters" and “Claims”

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

• Combination

• Configurability

• Customizability

• Library verification (vc-verifier)

Test Organization

Table 1: Test Organization

Name	Functional Role	Responsibilities
Nitin Hegde	Lead QA 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.

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 2: Test Environment

Images (qa-inji1 env)
injistackqa/inji-verify-service:0.18.x
injistackqa/inji-verify-ui:0.18.x
injistackqa/inji-certify-with-plugins:0.14.x
injistackqa/inji-web:develop

Images (released env)
injistack/apitest-mimoto:0.22.0
injistack /inji-verify-service:0.17.0
injistack /inji-verify-ui:0.17.0
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 UI

Table 3: UI Automation

Total	Pass	Fail	Known Issues	Ignored
48	45	0	3	0
Test Rate: 100% With Pass Rate: 100%

Automation INJI Verify API

Table 4: API Automation Result

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

Conclusion

This section summarizes the key findings of test execution. It also provides a final QA recommendation on the build's readiness for release. The functional verification for Inji-verify version 0.18.1 has been successfully completed. The testing cycle achieved a 100% execution rate with a 93% pass rate, API automation achieved a 100% pass rate.

While there are 55 known issues in total, there are zero blocker defects identified. The application has demonstrated functional stability and data integrity consistent with product specifications.

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 5: Report is signed off details

Name	Functional Role	Responsibilities
Chaitanya K	QA Manager

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

	Date	Author	Reviewers
V1.0	3/6/2026	Nitin Hegde	Chaitanya K

For further details on the QA Reports you can refer here.