> 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-web/inji-web/version-0.14.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, the Configurability and Extensibility of the software are also assessed. This ensures the readiness of the software for use in multiple countries. MOSIP is an “API First” product platform.
The testing scope has been focused on the following features:\\
* Inji Home page
* Issuer and Credential selection
* Authenticating with user credentials
* PDF Generation and Auto Download
* Success/Failure notification after downloading the VC PDF
* Retrieve Issuers and Credential list
* Downloading VC
* Multi-language support
* Error Handling
* Theme update
* PDF View
* Issuers support
* Responsive view of the web
* Access violations
* QR Code
* Durian data storage integration
* PDF and CBOR
* Log in with Google
* OpenID4VP Implementation
* Latest draft changes support for OpenID4VCI
* FAQ Support
* UI UX Design updates
* Swagger update
* Secure Time-Bound Storage
* Locale Support
* PDF Template Support
* Authorization endpoint discovery through the auth server's well-known
* SD JWT support
* Passcode Reset
### Test Approach
A personal-based approach has been adopted to perform the IV\&V by simulating test scenarios that resemble a 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's 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 7 Lang
* English
* French
* Arabic
* Hindi
* Tamil
* Kannada
* Portuguese
The UI will render in all the above languages, but the PDF file after download will only be in English language as Certify is currently only supporting English. When any language is selected in UI, as a fallback, the PDF will be in English.
### Feature Health
### Test execution statistics
#### Functional test results
Below are the test metrics for performing functional testing. The process followed was black box testing, which was based on the specifications of the software component under test. Functional test was performed in combination of 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, and End-To-End flows across multiple configurations. The testing cycle included the simulation of multiple identity schemas and respective UI schema configurations.
Total
Passed
Failed
NA
823
745
78
0
**Test Rate:** 100%, **Pass Rate:** 90%
### UI Automation and API Test Rig test results
Below are the test metrics by performing UI Automation and API Test rig:
| Total | Passed | Failed | Skipped/Known Issues |
| ----- | ------ | ------ | -------------------- |
| 344 | 307 | 0 | 37 |
**Test Rate:** 83%, **Pass Rate:** 100%
Here is the detailed breakdown of metrics for each module:\
\
**Inji Web UI Automation**
| Metric | Test cases |
| ------- | ---------- |
| Total | 28 |
| Passed | 28 |
| Failed | 0 |
| Skipped | 0 |
**Inji Web API Test Rig**
| Metric | Test cases |
| --------------- | ---------- |
| Total | 316 |
| Passed | 279 |
| Failed | 0 |
| Skipped/Ignored | 33 |
| Known Issues | 4 |
{% hint style="success" %}
Note: Ignored 33 OTP related test cases which are descoped and not applicable. For the known Issues, we have bugs added in the xls report.
{% endhint %}
The functional and test rig code base branch, which is used for the above metric, is:
* UI Automation: 9adaa889
* API automation: 286b73fc
### Detailed Test Metrics
Below are the detailed test metrics by performing manual/automation 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 the failed test cases. (Number of failed tests / Total number of test cases executed) x 100
{% hint style="success" %}
Github link for the detailed report is [**here**](https://github.com/mosip/test-management/tree/master/inji-web/inji%20web%200.14.0)
{% endhint %}
---
# 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-web/inji-web/version-0.14.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.