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 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.
The Inji testing scope revolves around the following flows:
Biometric unlock
Passcodes unlock
VC download via MOSIP
VC download via eSignet
VC download via Sunbird
Retrieving UIN/ via AID
Pinning a VC
Normal VC sharing with VID
Deleting VC
Face Auth on Resident's phone with VID
Multi language support
Credential registry
Backup and restore
Wallet binding
QR code Login
Logout
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
Deploy ability
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.
Verification is performed on various configurations as mentioned below
Default configuration - with 3 Lang
Virtual countries
1 Lang configuration
2 Lang configuration
3 Lang configuration
On Android Device:
On iOS Device:
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 simulation of multiple identity schema and respective UI schema configurations.
Here is the detailed breakdown of metrics for each module:
Below section provides details on API test metrics by executing MOSIP functional automation Framework. All external API test executions were performed at module level isolation. Each end point is tested with the test data and expectations of each test data are mapped to assert the test case.
Here is the detailed breakdown of metrics
Below section provides details on Ui Automation by executing MOSIP functional automation Framework.
Here is the detailed breakdown of metrics
Functional and test rig code base branch which is used for the above metrics is:
Hash Tag:
SHA: sha256: b477f64889c7340a1d1ca6b17601473c30d206de8de9c8a69e8879be38e1dbb5
Below are the test metrics by performing VC Sharing functionality on various device combinations
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
Git hub link for the xls file is here.
Release Name: Inji 0.13.0
Support: Developer Release
Release Date: 2nd Aug, 2024
We are delighted to announce the release of Inji Wallet Version 0.13.0. This update includes a significant change: The Inji repository has been renamed to inji-wallet and is now compatible with Mimoto v0.13.1. In this latest version, Inji Wallet introduces the following key features:
Libraries:
Native artefacts (Kotlin & Swift) available for:
Secure Keystore
Pixelpass
VCI client
Tuvali
UUID changes for verifier services in tuvali
Secure-keystore changes (credential request keypair change from RSA-4096 to RSA-2048 bits)
Enhancements:
Issuer’s Well-known as a source of truth
OTP flow disabled for MOSIP VC
Deployment:
Docker compose for mimoto
Please find below the details for the Inji Version 0.13.0 release:
Libraries:
Inji Wallet utilizes the Secure Keystore SDK to store keypairs, ensuring enhanced security. The SDK now includes native artifacts and is fully integrated with Inji Wallet. Additionally, the keypair generation for credential requests has been updated from RSA-4096 to RSA-2048 bits to reduce the size of the VCs.
Tuvali: UUID for all the verifier services is modified to reflect the UUID service definition as per the spec. In addition, Tuvali SDK which enables offline sharing based on BLE, has native artifacts (Kotlin and Swift) now and is integrated with Inji Wallet.
With this release, Java, Kotlin, and Swift artifacts are available for the PixelPass library, and native artifacts are integrated into the Inji Wallet app. Additionally, the Java library facilitates QR code generation on the server side.
The VCI client library handles credential requests from issuance, provided it has the accessToken, proof, and issuer metadata.
Enhancements:
The issuer's well-known URL will serve as the source of truth, providing details on locale settings for fields, credential types, display properties, and order. This URL will be accessible in the [specific location].
With this release, the OTP flow for downloading MOSIP VC, which connects to MOSIP ID Repo, credential service and websub has been disabled. Instead, MOSIP VC can now be downloaded using the OpenID4VCI flow.
Deployment:
Steps to update local github configuration:
The following table outlines the tested and certified compatibility of Inji Wallet 0.13.0 with other modules.
Mentioned below is the list of other known issues.
The 0.13.0 release includes the following bug fixes:
To simplify the deployment process for Mimoto in local environment, a Docker Compose file is now available. Click to know more.
The Inji repo is renamed to
Module | Version |
---|
Redmi devices are not supported in this release. To know more, refer .
Jira Issue | Issue Description | Severity |
---|
Total
Passed
Failed
Skipped (N/A)
2303
2034
226
43
Test Rate: 98% With Pass Rate: 90%
Test cases
On Android Device
Total
1236
Passed
1085
Failed
124
Skipped (N/A)
27
On iOS Device
Total
1067
Passed
949
Failed
102
Skipped (N/A)
16
Total
Passed
Failed
Skipped
1335
1275
32
28
Test Rate: 97.9% With Pass Rate: 97.5%
Test cases
Mobile ID
Total
63
Passed
61
Failed
2
Skipped
0
eSignet
Total
1272
Passed
1214
Failed
30
Skipped
28
Total
Passed
Failed
Skipped
120
107
13
0
Test Rate: 100% With Pass Rate: 89.16%
Test cases
Android
Total
63
Passed
54
Failed
9
Skipped
0
iOS
Total
57
Passed
53
Failed
4
Skipped
0
Total
Passed
Failed
Skipped
192
192
0
0
Test Rate: 100% With Pass Rate: 100%
Repositories | Tags Released |
inji-wallet |
mimoto |
inji-config |
tuvali |
tuvali-ios-swift |
secure-keystore |
pixelpass |
pixelpass-ios-swift |
inji-vci-client |
inji-vci-client-ios-swift |
Mimoto |
eSignet |
Inji Verify |
Jira Issue | Description |
INJIMOB- During face authentication, the camera view is not opening in all IOS device |
INJIMOB- In Android when the user clicks + icon from home page issuer page is not getting loaded |
INJIMOB- Users are unable to upload the VC QR code shared via email and WhatsApp, or stored locally |
INJI - unable to scroll the page add new card page |
INJIMOB - IOS - "Share QR Code" is not working on iPhone 8. |
INJIMOB - IOS - The buttons in the INJI tour guide are not properly aligned. |
INJIMOB - Android - The backup and restore process is failing on Android devices when the size of the backup exceeds 10MB. |
INJIMOB - Backup is not triggering automatically when VC is removed. |
INJI - logo of Inji Wallet stretched while booting the app |
Inji mob- During face authentication, the camera view is wider than the face. |
INJI - VC download failed because of eSignet pod being down doesn't have a proper error message |
IOS -Specific devices the User not able to see the iCloud ID in iCloud setting section of backup and restore page. |
INJI- Error message is not proper when invalid QR is scanned after changing language to other than English. |
INJI - Backup & restore Name Is Different In Settings And in Backup & restore Page |
INJI - Help Icon Language not Changing when we select other language that english |
Backup and Restore heading Alignment is not proper in Backup& restore page |
IOS - Associated app ID is missing in the Backup and restore page. |
Inji- Date format is not proper in the e-signet Vc |
INJI- Sometimes VC activate the button and back button responses is very slow |
INJI - VC getting created without image while generating the UIN with lower and higher iso files. |
Android - Intermediately while doing the face authentication the app is getting crashed |
INJI - Iderpo UINs are failing in VC verification |
Inji - Screen header and back button are overlapping |
Inji- In specific devices, the Pin and Unpin feature is not working. |
Android- Occasionally, unable to activate the restored VC |
IOS - Upon sharing sunbird VC twice and then upon sharing Mosip VC, app crashes |
Android - During face authentication, app crashes on a specific device |
INJI - Backup doesn't append the new data, but replaces the data |
Upon changing the finger authentication in the device, application does not display the error pop up for biometrics change |
INJIVER- The user is unable to upload the VC QR code shared via email and WhatsApp | Critical |
INJIVER-The user is unable to scan the QR code when it is stored locally | Critical |
INJIVER-The user is unable to scan the VC QR code shared via email and WhatsApp | Critical |
INJIMOB - IOS - The "Share with Selfie" is causing the app to crash after face verification. | Critical |
INJI - VC verification is passing for missing atribute VC | Critical |
INJI - VC download failed because of eSignet pod being down doesn't have a proper error message | Major |
Share with selfie flow from card mini view in home page is not showing the Share with Selfie pop-up before face verification. | Major |
INJI - onboarding of new issuer is affecting the existing issuers | Blocker |
Inji- E-Mail OTP channel is not mentioned on the OTP verification page. | Minor |