Test Report
Introduction
The scope of testing is to verify fitment to the specification from the perspective of
Functionality
Deployability
Configurability
Overview and Scope
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 is also assessed. This ensures 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
The 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
Combination
UI Automation
API automation
Upgrade Testing
Test Organization
This part lists the team members involved in the testing process and their responsibilities. It clarifies who is accountable for which roles.
Ragini Krishna
Manager
Defining test strategy, managing QA activities, and ensuring overall product quality.
N. Chandra Sekhar, Chaitanya Kesiraju, Maheswara Sarma and Mohanachandran S
Leads
Leading the test team, planning and executing tests, and ensuring timely delivery of quality results.
Likhitha, Swetha N, Aswin, Damodar Guru, Santosh, and Jayesh
Test engineers
Developing and executing test cases, logging defects, and verifying software quality through functional and automation.
Test Planning
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. 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, End-To-End flows across multiple languages and configurations. The testing cycle included simulation of multiple identity schema and respective UI schema configurations.
The Test Planning section outlines the strategy and activities planned for executing the testing process to ensure comprehensive coverage.
Test Environment
This section details the specific environments used for testing. It lists the different platforms, and the versions of the images used.
Environment
Details
qaga.mosip.net
For Platform 1.2.1.0 testing
qa11.mosip.net
For Upgrade 1.2.0.1 to 1.2.1.0 testing
Test Execution Report
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. 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, End-To-End flows across multiple languages and configurations. The testing cycle included simulation of multiple identity schema and respective UI schema configurations.
API Based Testing (with mock ABIS & MV -v1.2.0.2)
Master Data (Eng.)
945
933
0
0
0
0
Master Data (Ara.)
945
930
0
0
15
0
Master Data (Fra.)
945
930
0
0
15
0
PreReg
288
282
0
0
2
4
IDRepo
414
336
0
0
78
0
IDA
612
598
0
0
5
9
PMS
509
497
0
0
0
12
Resident
1142
1142
0
0
0
0
DSL - End to end scenarios results (with mock ABIS & MV -v1.2.0.2):
Module
Total
Passed
Failed
Skipped
Ignored
Known Issues
DSL
209
172
2
0
12
23
API Based Testing (with mock ABIS & MV -v1.3.x):
Module
Total
Passed
Failed
Skipped
Ignored
Known Issues
Master Data (Eng.)
945
933
0
0
0
0
Master Data (Ara.)
945
930
0
0
15
0
Master Data (Fra.)
945
930
0
0
15
0
PreReg
288
282
1
0
2
3
IDRepo
414
336
0
0
78
0
IDA
612
598
0
0
5
9
PMS
509
497
0
0
0
12
Resident
1142
1142
0
0
0
0
Note: PreReg 1 failure has been moved to Known Issues, and the PreReg API test rig was run with mock version 1.2.0.2. There were no failures reported in PreReg.
DSL - End to end scenarios results (with mock ABIS & MV -v1.3.x):
Module
Total
Passed
Failed
Skipped
Ignored
Known Issues
DSL
209
172
2
0
12
23
UI Based Testing:
Module
Total
Passed
Failed
Skipped
Admin UI
16
16
0
0
Reg. Client UI
33
32
1
0
Note: Reg-client UI Automation 1 failure is only observed in automation, manually it is working, raised a Jira for Automation.
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 the failed test cases. (Number of failed tests / Total number of test cases executed) x 100
API Test rig reports were generated by below sha id for mosipqa/automationtests:1.3.x image:
PreReg: sha256:9335f015b1170d7d2a082f6c8c86ffcb5cba2caf04ff7d690bd5093faf1af23d
MasterData: sha256:7b746e83193a1f0a04e66cd08e243d6df3e45371f48051517272b26b55b69013
IDRepo: sha256:610572e6f1a69e8c1e04fd7ad990379d83048c7802ebf8eacb71eab52f8376ed
IDA: sha256:9b1d874bd96f485d6e7ecfc4923a3630fb227692de1a7740672f61650ab7973b
Resident: sha256:927c2803d9a7a605142f2b64842882c83d04d5cf843822d2d381118c64c4788c
Sonar Report
mosip-config
release-1.3.x
v1.3.0
commons
release-1.3.x
v1.3.0
82.8
1
0
0
5.3
mosip-data
release-1.3.x
v1.3.0
bio-utils
release-1.3.x
v1.3.0
19.1
0
0
0
8.7
converters
release-1.3.x
v1.3.0
99.4
0
0
0
0
mosip-openid-bridge
release-1.3.x
v1.3.0
80.8
0
0
0
13.5
biosdk-client
release-1.3.x
v1.3.0
83
0
0
0
1.4
khazana
release-1.3.x
v1.3.0
2.1
4
0
0
0
demosdk
release-1.3.x (ask Jana)
v1.3.0
97.3
0
0
0
0
keymanager
release-1.3.x
v1.3.0
81.1
0
0
0
3.6
packet-manager
release-1.3.x
v1.3.0
biosdk-services
release-1.3.x
v1.3.0
96.5
0
0
0
0
id-repository
release-1.3.x
v1.3.0
82.8
0
0
0
3.2
registration
release-1.3.x
v1.3.0
83.5
1
0
0
8.4
id-authentication
release-1.3.x
v1.3.0
67.4
18
0
0
2.6
admin-services
release-1.3.x
v1.3.0
71.7
1
0
0
3.5
admin-ui
release-1.3.x
v1.3.0
0
69
0
0
9
captcha
release-0.1.x
v0.1.0
46.5
0
0
0
0
mosip-ref-impl
release-1.3.x
v1.3.0
durian
release-1.3.x
v1.3.0
82.7
0
0
0
0
otp manager
release-1.3.x
v1.3.0
48.1
0
0
0
0
release-1.3.x
v1.3.0
73.2
4
0
0
1.9
resident-services
release-1.3.x
v1.3.0
80.4
0
0
0
1.9
websub
release-1.3.x
v1.3.0
audit-manager
release-1.3.x
v1.3.0
70.4
0
0
0
0
image-compressor (release but no announcement)
release-0.1.x
v0.1.0
81.6
0
0
0
11.8
imagedecoder (release but no announcement)
release-0.10.x
v0.10.0
30.9
0
0
0
7.4
mosip-mock-services
release-1.3.x
v1.3.0
nfiq (ask Jana)
release-0.1.x
v0.1.0
76
3
0
0
7.1
mosip-onboarding
release-1.3.x
v1.3.0
N/A
N/A
N/A
N/A
N/A
pre-registration
release-1.3.x
v1.3.0
82.6
0
5
0
2.8
pre-registration-ui
release-1.3.x
v1.3.0
0
0
0
0
2.3
digital-card-service
release-1.3.x
v1.3.0
69
0
0
0
0
artifactory-ref-impl
release-1.3.x
v1.3.0
Observations:
Meta data is missing in the Minio during backup and restore (MOSIP-44059)
Template DB Scripts are missing for update statements in the DB upgrade scripts rely on auto-generated IDs (MOSIP-44100)
Out of Sope:
Roll back scripts were not verified from QA Side.
Partner Management System and Registration Client
Deployment and Docker compose Testing.
Real BIO-SDK and ABIS
Conclusion
Basic functionality of all the Modules in Java 21 env is the same as the functionality in Java 11 env.
QA Approved build release.
QA Approval
Build has met the defined exit criteria and is recommended for release.
Test Case Execution Completion
Defect Status Closure
Automation reports -API, DSL and UI
Documentation Sign-off
Test Environment Stability
Report signed off details
Ragini Krishna
Manager
Defining test strategy, managing QA activities, and ensuring overall product quality.
Chandra Sekhar
Lead
Leading the test team, planning and executing tests, and ensuring timely delivery of quality results.
Chaitanya Kesiraju
Lead
Leading the test team, planning and executing tests, and ensuring timely delivery of quality results.
Appendix
This includes additional reference information for the report. It contains a history of document versions and a list of acronyms and their meanings.
Appendix A: Versions
Version
Date
Author
Reviewers
V1.0
19/12/2025
N. Chandra Sekhar
Ragini Krishna
Appendix B: Acronyms
Reg.Client
PreReg
IDA
ABIS
MV
Registration Client
Pre-Registration
ID Authentication
Automated Biometric Identification System
Manual Verification
Document History
It outlines the strategy used to ensure a comprehensive evaluation.
V1.0
N. Chandra Sekhar
18/12/2025
Ragini Krishna
For all of it and details on reports refer to the link here.
Last updated
Was this helpful?