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
Home Page
Upload Feature
Scan Feature
VP Verification
OVP Flow
SVG Support
Multi Language
Same Device and Cross Device flow
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
Santosh
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.
Ragini Krishna
Senior QA Manager
High-level governance and executive reviews of reports and execution.
Test Organization
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
iPhone 7
iOS 15.8 BLE 4.2
iPhone 11
iOS 26.1 BLE 5.0
iPhone 13
iOS 18.6.2 BLE 5.0
iPhone 14
iOS 26.2 BLE 5.3
SS Galaxy A03 core
Android 11 BLE 4.2
Vivo Y73
Android 13 BLE 5.0
Redmi 6A
Android 9 BLE 4.2
Techno POVA 6 NEO
Android 14 BLE 5.0
OPPO A59 5G
Android 13 BLE 5.3
ONE PLUS 12R
Android 15 BLE 5.3
Infinix NOTE 50X 5G
Android 15 BLE 5.4
Redmi 7A
Android 10 BLE 4.2
iTel
Android 14 BLE 5.0
Xiaomi Redmi NOTE 13 Pro
Android 15 BLE 5.2
Test Devices
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
mosipqa/inji-verify-service:0.16.x
mosipqa/inji-verify-ui:0.16.x
mosipqa/inji-certify-with-plugins:0.13.x
mosipid/apitest-mimoto:0.20.0
mosipqa/mimoto:develop
mosipqa/inji-web:develop
Test Environment
mosipid/mimoto:0.20.0
mosipid/apitest-mimoto:0.20.0
mosipid/inji-verify-service:0.15.2
mosipid/inji-verify-ui:0.15.2
mosipid/inji-certify-with-plugins:0.13.1
mosipid/inji-web:0.15.0
mosipid/esignet-with-plugins:1.6.2
mosipid/authentication-service:1.2.1.0
mosipid/authentication-internal-service:1.2.1.0
mosipid/authentication-otp-service:1.2.1.0
mosipid/kernel-notification-service:1.2.0.1
mosipid/registration-processor-stage-group-1:1.2.1.1
Test Environment
Test Execution Report
Test case execution summary
INJI Verify
953
857
96
0
Test Rate: 100% With Pass Rate: 90%
Test Execution Summary
Combination Testing with device components
This section details Combination Testing results for Inji-verify on Windows, Android and iOS, specifically validating workflows like sharing Verifiable Credentials (VCs) across devices. These tests confirm the application's stability when orchestrating multiple components such as Bluetooth, camera, and biometrics during these cross-platform interactions.
220
197
23
0
Test Rate: 100% With Pass Rate: 89.54%
Combination Result
Automation INJI Verify UI
23
23
0
0
0
Test Rate: 100% With Pass Rate: 100%
UI Automation
Automation INJI Verify API
35
35
0
0
0
Test Rate: 100% With Pass Rate: 100%
API Automation Result
Defect Metrics
Defect Metrics for the Release 0.16.0
The following table depicts only the bugs which are found and not addressed in the current release.
0
0
8
5
13
Defect Metrics for the Release
Known Issues Metrics
This section focuses on a separate category of issues that are known but not addressed in the current release. It provides a count and severity distribution for these defects across releases.
0
0
47
13
60
Defect Metrics for the known issues
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 016.0 has been successfully completed. The testing cycle achieved a 100% execution rate with a 90% pass rate across a total of 953 test cases. Additionally, API automation achieved a 100% pass rate.
While there are 13 open defects (0 Critical, 8 Major, 5 Minor) and 60 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.
Chaitanya K
QA Manager
Ragini Krishna
Senior QA Manager
Report is signed off details
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
V1.0
10/12/2025
Santosh
Chaitanya K
Ragini Krishna
Document History
It outlines the strategy used to ensure a comprehensive evaluation.
V1.0
Santhosh
17/12/2025
Chaitanya Kesiraju
Ragini Krishna
New Document
Last updated
Was this helpful?