> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/roadmap-and-releases/releases/1.2.0.2-reg-processor-and-id-repo/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 are also assessed. This ensures the readiness of software for use in multiple countries.

#### **The ARC (Android Reg-Client) testing scope revolves around the following flows:**

● Logging and Logout into ARC

● Adding machine details

● Consent page verification

● Demographic data input

● Document upload

● Biometric data verification

● Preview screen evaluation

● Authentication screen

● Acknowledgement screen review

● Syncing and uploading

● Audit logging

● Dashboard

● Operator Onboarding

● Update Operator biometrics

● Installation from adb

● Export Packet

● Notification

● Pending approvals

● ARC packets processing in Regproc

● New and Updated UIN

● Handles with NRCID/Email Id/Phone Number

#### **Platform modules Coverage:**

● Packet manager verified along with ARC

● IDRepo sanity

● Regproc verified along with ARC

### Test Approach <a href="#id-3znysh7" id="id-3znysh7"></a>

Persona 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 <a href="#id-2et92p0" id="id-2et92p0"></a>

Verification is performed on various configurations as mentioned below

● Default configuration - with 1 Language (English)

### Limitations or Out of Scope <a href="#id-3dy6vkm" id="id-3dy6vkm"></a>

● Update UIN

● Handles feature with Update UIN

● Real biometric device

#### Platform modules tested along with ARC v 0.11.0:

| Module/Repository      | Compatible Version |
| ---------------------- | ------------------ |
| id-repository          | 1.2.2.x            |
| registration-processor | 1.2.0.x            |
| packet-manager         | 1.2.0.x            |

### Feature Health

<div align="left"><figure><img src="/files/om3MMGllz9OSI9mAE2xg" alt=""><figcaption><p>Feature Health</p></figcaption></figure></div>

### Test execution statistics

#### Functional test results by modules <a href="#id-17dp8vu" id="id-17dp8vu"></a>

Below are the test metrics by performing functional testing using mock SBI and mock ABIS.

1. **Test Metrics Overview**:
   * **Functional testing** was performed using mock SBI and mock ABI&#x53;**.**
2. **Testing Approach**:
   * **Black-box testing** was used, focusing on test cases based on the specifications of the software component.
3. **Testing Types**:
   * Functional testing was conducted in combination with:
     1. Individual module testing.
     2. Integration testing.
4. **Test Data Preparation**:
   * Test data were created based on user stories.
   * Expected results were validated by monitoring the user interface.
5. **Scope of Testing**:
   * **GUI testing**.
   * **System testing**.
   * End-to-end flows across multiple languages and configurations.
6. **Simulation Testing**:
   * Simulated multiple identity schema and corresponding UI schema configurations during the testing cycle.

<table data-full-width="true"><thead><tr><th>Total</th><th>Passed</th><th>Failed</th><th>Skipped (N/A)</th></tr></thead><tbody><tr><td>521</td><td>386</td><td>135</td><td>0</td></tr></tbody></table>

**Test Rate:** 100% With **Pass Rate:** 74%

#### UI Automation Reports:

<table data-full-width="true"><thead><tr><th>Total</th><th>Passed</th><th>Failed</th><th>Skipped (N/A)</th></tr></thead><tbody><tr><td>6</td><td>4</td><td>2</td><td>0</td></tr></tbody></table>

**Test Rate:** 100% With **Pass Rate:** 66%

#### IDRepo API Testrig Report:

<table data-full-width="true"><thead><tr><th>Total</th><th>Passed</th><th>Failed</th><th>Skipped (N/A)</th></tr></thead><tbody><tr><td>410</td><td>371</td><td>30</td><td>9</td></tr></tbody></table>

**Test Rate:** 97% With **Pass Rate:** 92%

{% hint style="info" %}
**Note**:

1. As per the schema email and phone number are optional in this env, so the 8 test cases are ignored. One testcase skipped in this env, verified manually. It is working fine.
2. DSL with handles was not implemented, so the verification was done manually and working fine. As implementation was not done, the DSL report was not included in the certification.
   {% endhint %}

**Git Commit ID:** 355ba6d9572da313262a164a869bf6f5b0b2195d

**Client Version:** 1.2.0.1-B1

### 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 passed tests / 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

Please find the Github link for the .xlsx file [here](https://github.com/mosip/test-management/blob/master/ARC/ARC%200.11.0%20Platform%201.2.0.2/ARC_Platform_1.2.0.2_Verification_Report_latest.xlsx).


---

# 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.mosip.io/1.2.0/roadmap-and-releases/releases/1.2.0.2-reg-processor-and-id-repo/test-report.md?ask=<question>&goal=<endgoal>
```

`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.