# 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 is also assessed. This ensures the readiness of software for use in multiple countries. Since MOSIP is an “API First” product platform, Verification scope required comprehensive automation testing for all the MOSIP APIs. An automation Test Rig is created for the same. ## Test Approach 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 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 check, “MOSIP Test Rig” - an automation testing suite - which is indigenously designed and developed for supporting persona-based testing. MOSIP Test Rig covers the end-to-end test execution and reporting. The end-to-end functional test scenarios are written starting from pre-registration to creation of packet in registration center, processing the packet through the registration processor, generating UIN and authenticating identity using IDA through various permutation and combinations of cases being covered. MOSIP Test Rig will be an open-source artifact which can also be enhanced and used by countries to validate the SI deliveries before going live. Persona classes include both negative and positive personas. Negative persona classes include users like Bribed Registration Office, Malicious Insider etc. The needs of positive persona classes must be met, whereas the needs of negative persona classes must be effectively restricted by the software. ## Verified configuration Verification is performed on various configurations as mentioned below Default configuration - * eSignet with 7 languages (English/Khmer/Hindi/Kannada/Tamil/Arabic/French) * Signup with 2 languages (Khmer/English) Main feature tested: * Signup Portal with mock ID * Login with Password with mock ID * Forgot Password with mock ID * Login with OTP with mock ID * Login with biometrics with mock ID * Login with KBI with mock ID * Identity verification process (L2 flow) with mock ID * Identity verification process (L2 flow) with MOSIP ID * Signup Portal with MOSIP IDA * Login with Password with MOSIP IDA * Forgot Password with MOSIP IDA * Login with OTP with MOSIP IDA * Login with biometrics MOSIP IDA * Sunbird Plugin with MOSIP IDA * Critical and Blocker Bugs verification * Docker Compose testing for esignet, esignet-signup, esignet-mock-services (windows) ## Feature Health

## Test execution statistics ## Functional test results Below are the test metrics by performing functional testing using mock MDS, mock Auth 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 tests were 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, 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
3183	3113	35	35

Test Rate: 98% with Pass rate: 98% {% hint style="info" %} Note: In API-based testing, 35 test cases were marked as skipped because they were not automated and cannot be executed using Postman. {% endhint %} Here is the detailed breakdown:

	Test cases	Total
API Based Testing - eSignet		2017
	Passed	1965
	Failed	17
	Skipped	35
UI Based Testing		1166
	Passed	1148
	Failed	18
	Skipped	0

#### API Testrig results for eSignet and Signup with Mock ID:

	Test cases	Total
API Based Testrig - eSignet		1011
	Passed	514
	Failed	0
	Skipped	0
	Ignored	495
Known issues	2
API Based Testrig - eSignet-signup		661
	Passed	626
	Failed	0
	Skipped	0
	Ignored	30
	Known issues	5

Note: 525 test cases related to the MOSIP ID plug-in are currently being ignored. #### API Testrig results for eSignet and Signup with MOSIP - CRE:

	Test cases	Total
API Based Testrig - eSignet		1011
	Passed	838
	Failed	0
	Skipped	0
	Ignored	169
	Known issues	4
API Based Testrig - eSignet-signup	Total	661
	Passed	400
	Failed	53
	Skipped	186
	Ignored	17
	Known issues	5

{% hint style="info" %} Note: * In the mosipid-cre environment, 186 test cases are being skipped as L2 flow test cases are out of scope. * There is 1 failure in the registration status endpoint; the other 52 failures are related to L2 test cases and can be ignored. * Additionally, 186 test cases are being ignored due to the esignet sunbird report being executed separately. {% endhint %} #### API Testrig results for eSignet and Signup with MOSIP – qa-base:

	Test cases	Total
API Based Testrig - eSignet		1011
	Passed	848
	Failed	0
	Skipped	0
	Ignored	169
Known issues		4
API Based Testrig - eSignet-signup		661
	Passed	643
	Failed	0
	Skipped	0
	Ignored	17
	Known issues	1

Note: 186 test cases related to the mock plug-in are currently being ignored. #### API Testrig results for eSignet and Signup with Sunbird:

	Test cases	Total

API Based Testrig - Sunbird		1011
	Passed	93
	Failed	0
	Skipped	0
	Ignored	918

#### **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 #### **Sonar Report**:

Repo Name	Branch Name	Release Version (POM)	Coverage (>80%)	Duplications (Less than 3%)
eSigent	release-1.6.x	release-1.6.x	86	0%
eSignet Signup	release-1.2.x	release-1.2.x	82.1	0%
esignet-mock-services	release-0.11.x	Release-0.11.x	81.4	0%
esignet-plugins(mock-plugin)	release-1.3.x	release-1.3.x	83	2.9%
esignet-plugins(mosip-identity-plugin)	release-1.3.x	release-1.3.x	68.9	0%
esignet-plugins(sunbird-rc-plugin)	release-1.3.x	release-1.3.x	83	0%

Refer to the github link for more on reports [**here**](https://github.com/mosip/test-management/tree/master/e-signet/1.6.2). --- # Agent Instructions: 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: ``` GET https://docs.esignet.io/roadmap-and-releases/versions/v1.6.2/test-report.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.