Release version: v0.9.1
Release Date: Coming soon!
This is a v0.9.1 release of Resident Services, offering valuable insights into the range of features and functionality. Resident Services is designed to run on the 1.2.0.1 version of the MOSIP platform. Resident Services are the self-services that the residents themselves use via a portal. Resident Portal is a web-based UI application that provides residents of a country with services related to their Unique Identification Number (UIN). The residents can perform various operations related to their UIN/ VID and can also raise concerns if any through the portal.
The key features provided on the Resident portal are:
Avail UIN services using UIN/ VID (through eSignet):
View My History
Manage My VID
Secure My ID
Track My Requests
Get Personalised Card
Share My Data
Update My Data
Login and Logout
Get Information
Get the list of Registration Centres
Get the list of Supporting Documents
Get My UIN (using UIN/ VID/ AID)
Verify Email ID and/ or phone number
Book an appointment for new enrolment (via the pre-registration portal)
Ancillary features
Multi-lingual support
Get Notifications (email and bell notifications)
View profile details of the logged in user (name, photo, and last login details)
Responsive UI support
For a quick overview of the design principles and to understand the relationship of Resident Services with other services, please refer to the Resident Services Overview section.
(To be updated soon)
resident-services
resident-ui
mosip-config
mosip-data
admin-services
postgres-init
(To be updated soon)
For a detailed description of Resident services, the code, and the design, refer to the resident services repo.
MOSIP provides a reference implementation of the resident portal that can be customized to the country’s needs. The sample implementation is available here.
To get the complete list of known bugs please refer here (link to be updated soon)
Update my data feature is not working as expected for a few UINs. The issue is intermittent.
Video policy transactions allowed are not working as per policy.
The following table outlines the tested and certified compatibility of v0.9.1 with other modules.
mosipid/authentication-service
1.2.1.0
mosipid/authentication-internal-service
1.2.1.0
mosipid/authentication-otp-service
1.2.1.0
mosipid/credential-service
1.2.1.0
mosipid/credential-request-generator
1.2.1.0
mosipid/id-repository-identity-service
1.2.1.0
mosipid/id-repository-vid-service
1.2.1.0
mosipid/partner-management-service
1.2.1.0
mosipid/policy-management-service
1.2.1.0
mosipid/kernel-notification-service
1.2.0.1
mosipid/kernel-keymanager-service
1.2.0.1
mosipid/registration-processor-stage-group-7
1.2.0.1
mosipid/registration-processor-common-camel-bridge
1.2.0.1
mosipid/registration-processor-stage-group-1
1.2.0.1
mosipid/registration-processor-stage-group-2
1.2.0.1
mosipid/registration-processor-stage-group-3
1.2.0.1
mosipid/registration-processor-stage-group-4
1.2.0.1
mosipid/registration-processor-stage-group-5
1.2.0.1
mosipid/registration-processor-stage-group-6
1.2.0.1
mosipid/registration-processor-stage-group-7
1.2.0.1
mosipid/registration-processor-notification-service
1.2.0.1
mosipid/registration-processor-dmz-packet-server
1.2.0.1
mosipid/registration-processor-reprocessor
1.2.0.1
mosipid/registration-processor-registration-status-service
1.2.0.1
mosipid/registration-processor-registration-transaction-service
1.2.0.1
mosipid/registration-processor-workflow-manager-service
1.2.0.1
mosipid/kernel-auditmanager-service
1.2.0.1
mosipid/kernel-masterdata-service
1.2.1.0
mosipid/admin-service
1.2.1.0
mosipid/hotlist-service
1.2.1.0
mosipid/kernel-syncdata-service
1.2.1.0
mosipid/digital-card-service
1.2.0.1
mosipid/print
1.2.0.1
mosipid/commons-packet-service
1.2.0.1
mosipid/mosip-artemis-keycloak
1.2.0.1
mosipid/websub-service
1.2.0.1
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. Since MOSIP is an “API First” product platform, the Verification scope required comprehensive automation testing for all the MOSIP APIs. An automation Test Rig is created for the same.
The Resident Revamp testing scope revolves around the following flows:
● Get Information
● Pre-registration Booking
● Verify phone/email
● View My history
● Track services
● Manage My VID
● Secure MY ID
● Get a personalized Card
● Share credentials with partner
● Multilingual (English/Arabic/French)
● Resident UI End to End testing
● Regression Testing
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.
For regression check, “MOSIP Test Rig” - an automation testing suite - 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 the creation of a packet in the registration center, processing the packet through the registration processor, generating UIN, and authenticating identity using IDA through various permutations and combinations of cases being covered. MOSIP Test Rig will be an open source artifact that 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.
Verification is performed on various configurations as mentioned below
● Default configuration - with 3 Languages (English/Arabic/French)
Below are the test metrics by performing functional testing using mock MDS 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 test was performed in combination with 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 the simulation of multiple identity schema and respective UI schema configurations.
Test Rate: 99% With Pass Rate: 98%
Note: NA - 12 Test Cases which are descoped scenarios/not developed feature
The section below provides details on API test metrics, executing the MOSIP functional automation Framework. All external API test executions were performed at module-level isolation. The test data is used to test each endpoint, and the expectations of each test data set are mapped to assert the test case.
Test Rate: 100% With Pass Rate: 99.2%
The below section provides details on UI Automation by executing the MOSIP functional automation Framework.
Test Rate: 100% With Pass Rate: 100%
The functional and test rig codebase branch used for the above metrics is:
Hash Tag:
mosipqa/resident-ui@sha256:69e0edb4a61c724d1fca36178984382bfd87f58f6df54520704bac0da06c55f1
Below are the detailed test metrics for manual and 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
Please refer to the GitHub link for the XLS file given here(To be updated)
2502
2461
29
12
1126
1117
9
0
25
25
0
0