> 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/release-notes-1.2.0.1-beta/functional-test-report-b1.md).

# Functional Test Report

## Scope and Objective

Verifying the LTS bug fixes and performing regression for the same.

## Testing tools

* Manual testing for bug validation.
* DSL automation/ API test rig: Java, Selenium

## Test deliverables

* Test report with results
* Feature health report

## Verified Configuration

* Tested in environments supporting 2 languages: Eng, Ara
* Features tested on V2 as well as V3 console

## Functional test results by modules

Below are the test metrics by performing functional tests:

| Total | Passed | Failed | Skipped |
| ----- | ------ | ------ | ------- |
| 690   | 632    | 50     | 8       |

### Tests execution for bugs verification and sanity testing

| Module     | Total | Passed | Failed | Skipped |
| ---------- | ----- | ------ | ------ | ------- |
| Pre-Reg    | 70    | 63     | 6      | 1       |
| Reg Client | 107   | 99     | 8      | 0       |
| Reg proc   | 143   | 138    | 5      | 0       |
| Resident   | 85    | 77     | 8      | 0       |
| Admin      | 114   | 90     | 17     | 7       |
| IDA        | 122   | 117    | 5      | 0       |
| PMS        | 49    | 48     | 1      | 0       |

### API Test Automation Metrics

| Module   | Total | Passed | Failed | Skipped |
| -------- | ----- | ------ | ------ | ------- |
| Pre-Reg  | 212   | 205    | 7      | 0       |
| Resident | 306   | 279    | 27     | 0       |
| Admin    | 903   | 897    | 6      | 0       |
| IDA      | 358   | 354    | 4      | 0       |
| PMS      | 457   | 456    | 1      | 0       |

*Note*: The number of failed test cases is cumulative of issues in released software as well the issues in the test automation scripts.


---

# 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/release-notes-1.2.0.1-beta/functional-test-report-b1.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.