> 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.1.0-beta.1-part-4/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 readiness of the software for use in multiple countries.

Since MOSIP is an **“API First”** product platform, the verification scope requires comprehensive automation testing for all MOSIP APIs. An automation Test Rig has been created for this purpose.

### Test Approach

A **persona-based approach** has been adopted to perform the IV\&V, simulating test scenarios that resemble a real-time implementation.

A **persona** is a fictional character or user profile created to represent a user type that might use a product or service in a particular way. Persona-based testing is a software testing technique that puts testers in the customer's shoes, assesses their needs, and determines use cases/scenarios that 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.

For regression checks, the **MOSIP Test Rig**—an automation testing suite designed and developed in-house—supports persona-based testing. It covers end-to-end test execution and reporting.

**Key aspects of MOSIP Test Rig:**

* End-to-end functional test scenarios written from pre-registration to:
  * Creation of packets at registration centers
  * Processing packets through the registration processor
  * Generating UIN
  * Authenticating identity using IDA with various permutations and combinations
* Open-source artifact enabling countries to validate SI deliveries before going live
* Includes both **positive personas** (e.g., genuine citizens) and **negative personas** (e.g., bribed registration officers, malicious insiders)
* The needs of positive personas must be met, while the needs of negative personas must be effectively restricted

### Verified Configuration

Verification was performed on the following configuration:

* **Default configuration** with 3 languages (English, Arabic, French)

**Main features tested:**

* Registration Client
* Master Data
* ID Authentication
* Key Manager

### Test Execution Statistics

**Functional Test Results**

Below are the test metrics from functional testing using mock MDS, mock Auth, and mock ABIS:

| Total | Passed | Failed | Skipped | Ignored |
| ----- | ------ | ------ | ------- | ------- |
| 1967  | 1861   | 1      | 0       | 105     |

**Test Rate: 100%**\
**Pass Rate: 99.95%**

**Detailed Breakdown**

| Module            | Total | Pass | Fail | Skipped | Ignored |
| ----------------- | ----- | ---- | ---- | ------- | ------- |
| Master Data - Eng | 945   | 945  | 0    | 0       | 0       |
| ID Repository     | 410   | 325  | 1    | 0       | 84      |
| ID Authentication | 612   | 591  | 0    | 0       | 21      |
| **Overall**       | 1967  | 1861 | 1    | 0       | 105     |

> **Note:** In API-based testing, some test cases are marked as 'ignored' due to dependencies on other modules.

**DSL – End-to-End Scenarios Results**

| Total | Pass | Fail | Skipped |
| ----- | ---- | ---- | ------- |
| 205   | 165  | 11   | 29      |

### Detailed Test Metrics

The metrics derived from manual and automation testing include:

* **Defect Density**
* **Test Coverage**
* **Test Execution Coverage**
* **Test Tracking & Efficiency**

**Key indicators:**

* **Passed Test Case Coverage:**\
  `(Number of passed tests / Total number of tests executed) × 100`
* **Failed Test Case Coverage:**\
  `(Number of failed tests / Total number of tests executed) × 100`


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mosip.io/1.2.0/roadmap-and-releases/releases/1.2.1.0-beta.1-part-4/test-report.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.