> For the complete documentation index, see [llms.txt](https://docs.inji.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inji.io/inji-wallet/inji-mobile/versions/version-0.17.0/test-report.md). # Test Report ## Testing Scope The scope of testing is to verify fitment to the specification from the perspective of * Functionality * Deployability * Configurability * Customizability Verification is performed not only from the end user perspective but also from the System Integrator (SI) point of view. Hence Configurability and Extensibility of the software is also assessed. This ensures the readiness of software for use in multiple countries. The Inji testing scope revolves around the following flows: * Biometric unlock * Passcodes unlock * VC download via MOSIP * VC download via e-signet * VC downloads via Sunbird * Pinning a VC * Normal VC sharing with VID * Deleting VC * Face Auth on Resident's phone with VID * Multi language support * Credential registry * Backup and restore * Wallet binding * Deep link navigation * OpenID4VP * QR code Login * Key Management * Logout ## Test Approach Persona based approach has been adopted to perform the IV\&V, by simulating test scenarios that resemble real-time implementation. A Persona is a fictional character/user profile created to represent a user type that might use a product/or a service in a similar way. Persona based testing is a software testing technique that puts software testers in the customer's shoes, assesses their needs from the software and thereby determines use cases/scenarios that the customers will execute. The persona needs may be addressed through any of the following. * Functionality * Deployability * Configurability * Customizability The verification methods may differ based on how the need was addressed. ## Verified configuration Verification is performed on various configurations as mentioned below * Default configuration - with 1 Lang\\ ## Feature Health

## Test execution statistics ### Functional test results by modules Below are the test metrics by performing functional testing using mock MDS and mock ABIS. The process followed was black box testing which based its test cases on the specifications of the software component under test. The functional test was performed in combination with individual module testing as well as integration testing. Test data were prepared in line with the user stories. Expected results were monitored by examining the user interface. The coverage includes GUI testing, System testing, End-To-End flows across multiple languages and configurations. The testing cycle included simulation of multiple identity schema and respective UI schema configurations.

Total	Passed	Failed	Skipped (N/A)
3718	3359	359	0
Test Rate: 100% With Pass Rate: 90%

\*\* Here is the detailed breakdown of metrics for each module\*\*:

	Test cases

On Android Device	Total	1946
Passed	1768
Failed	178
Skipped (N/A)	0
On iOS Device	Total	1772
Passed	1591
Failed	181
Skipped (N/A)	0

Testing with various device combinations **Below are the test metrics by performing VC Sharing functionality on various device combinations**

Total	Passed	Failed	Skipped
192	179	13	0
Test Rate: 100% With Pass Rate: 93.22%

### Device and Component Details: ### Tested Components #### QA Environment (`qa-inji1`) * `mosipqa/inji-verify-service:0.13.x` * `mosipqa/inji-verify-ui:0.13.x` * `mosipqa/inji-certify-with-plugins:develop` * `mosipid/apitest-mimoto:0.17.1` * `mosipqa/mimoto:develop` * `mosipqa/inji-web:0.13.x` #### Released Environment * `mosipid/apitest-mimoto:0.17.1` * `mosipid/apitest-mimoto:0.17.1` * `mosipid/inji-verify-service:0.12.3` * `mosipid/inji-verify-ui:0.12.3` * `mosipid/inji-certify-with-plugins:0.11.0` * `mosipid/inji-web:0.12.0` * `mosipid/esignet-with-plugins:1.5.1` * `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` ### Devices Used for Testing | Device | OS Version | BLE Version | | ------------------------- | ---------- | ----------- | | *Vivo Y73* | Android 13 | 5.0 | | *Samsung Galaxy A03 Core* | Android 11 | 4.2 | | *iPhone 11* | iOS 18.3.2 | 5.0 | | *iPhone 8* | iOS 16.7 | 5.0 | | *iPhone 7* | iOS 15.8 | 4.2 | | *Redmi 7A* | Android 10 | 4.2 | | Redmi Note 10 Lite | Android 13 | 5.0 | | Redmi K20 Pro | Android 13 | 5.0 | | *Redmi 6A* | Android 9 | 4.2 | *Italicized device names indicate devices used for specific compatibility or regression testing.* ### Detailed Test Metrics Below are the detailed test metrics by performing manual testing. The project metrics are derived from Defect density, Test coverage, Test execution coverage, test tracking and efficiency. The various metrics that assist in test tracking and efficiency are as follows: * Passed Test Cases Coverage: It measures the percentage of passed test cases. (Number of tests passed / Total number of tests executed) x 100 * Failed Test Case Coverage: It measures the percentage of all failed test cases. (Number of failed tests / Total number of test cases executed) x 100 ### Execution Test Summary * Well known and wallet metadata story verification was performed against the qa-inji1 env. Other story verification performed against released env. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.inji.io/inji-wallet/inji-mobile/versions/version-0.17.0/test-report.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.