Release Name: Android Registration Client 0.11.0-beta.1
Release version: 0.11.0-beta.1
Support: Beta Release
Release Date: 10th Sept, 2024
The Android Registration Client is a tablet application designed to provide a mobile version of the existing desktop Registration Client. It has been developed to ensure accessibility on all Android devices and to meet the mobility needs of countries implementing MOSIP.
The new features included in this release, along with those from the Android Registration Client DP1, Android Registration Client 0.9.0, and Android Registration Client 0.10.0 releases, are:
Version 0.11.0-beta.1 of the Android Registration Client is the beta release, covering features such as:
Supervisor's Approval: This feature will only be available for users having a “Supervisor” role. This is an additional check by the Supervisor where they will have to go through each application to make sure the details filled are coherent. At this stage, the Supervisor can either Approve the Application or he can Reject it.
Manual Application upload/export: This feature can be used to sync and upload a packet if there is internet connectivity and in case of lack of internet connectivity, the User can also export the packet to their local device storage.
Update UIN: This feature can be used by the Residents when they want to update their demographic data, documents, and biometrics.
Update operator's biometrics: This feature can be used by the operator to update their biometrics.
Logout: Using this feature, the user can logout once they are done with their registration tasks and other activities.
Note: Compatible with MOSIP version 1.2.0
Repositories
Tags Released
android-registration-client
To access the build and read through the deployment instructions, refer to the Developer Guide.
For details related to Android Registration Client configurations, refer to the Configuration Guide.
To learn more about the available features, processes, and user interface, refer Android Registration User Guide for further information.
To view the list of known issues, refer here.
The scope of testing is to verify fitment to the specification from the perspective of the following:
● 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.
The ARC (Android Reg-Cline) testing scope revolves around the following flows:
● Login into ARC
● Adding machine details
● Consent page
● Demographic details
● Document upload
● Biometric data
● Preview screen
● Authentication screen
● Acknowledgement screen
● Multilanguage support
● Sync/upload/Auto upload packet
● Operator Onboarding
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.
Verification is performed on various configurations as mentioned below
● Default configuration - with 1 Language (English)
Below are the test metrics by performing functional testing using mock SBI 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 using individual modules and 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 numerous identity schema and respective UI schema configurations.
511
373
138
0
Test Rate: 100% With Pass Rate: 72%
UI Automation Reports:
6
6
0
0
Test Rate: 100% With Pass Rate: 100%
Git Commit ID: 8eac450ed9e0ba479199cd50f7c21d97c602b508
Client Version: 1.2.0.1-B1
Below are the detailed test metrics by performing manual/automation testing. The project metrics are derived from Defect density, Test coverage, execution coverage, test tracking, and efficiency.
The various metrics that assist in test tracking and efficiency are as follows:
● Passed Test Cases Coverage: This measures the percentage of passed test cases. (Number of passed tests / Total number of tests executed) x 100
● Failed Test Case Coverage: This measures the percentage of all failed test cases. (Number of failed tests / Total number of test cases executed) x 100
The Github link for the xls file can be found here.