Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Name: Inji Wallet 0.14.0
Date: Coming Soon
Type: Developer
Release Notes
Name: Inji Wallet 0.13.1 Patch release
Date: 10th Sep, 2024
Type: Developer
Name: Inji Wallet 0.13.0
Date: 2nd Aug, 2024
Name: Inji 0.12.0
Date: 31st May, 2024
Name: Inji 0.11.0-Inji
Date: 29th March, 2024
Name: Inji 0.11.0
Date: 23rd February, 2024
Name: Inji DP2
Date: 22nd January, 2024
Name: Inji 0.10.0
Date: 19th December, 2023
Name: Inji DP1 (Beta)
Date: 28th September, 2023
Name: Inji 0.9.1 (Beta)
Date: 25th July, 2023
Name: Inji 0.9.0 (Beta)
Date: 14th April, 2023
Name: Inji 0.8.0 (Alpha)
Date: 20th October, 2022
Release Name: Inji Wallet 0.14.0
Release Type: Developer
Release Date: Coming Soon
We are excited to announce the release of Inji Wallet Version 0.14.0! This update introduces major enhancements and new features, particularly in credential issuance. Here are the key highlights of this release:
PixelPass Enhancements: Support for CBOR encoding/decoding is available, making PixelPass more versatile and efficient in handling data.
Integration with Inji Certify: We've integrated eSignet for authentication and Certify for streamlined credential issuance, providing a seamless experience.
Compliance with Draft 13 of the OpenID4VCI Spec: Inji Wallet now fully supports the latest Draft 13 changes of the OpenID4VCI specification, ensuring compatibility with the evolving standards in the industry.
Java upgrade in mimoto: A significant tech upgrade for mimoto to move from java11 to java21.
PixelPass enhancements - Support CBOR encoding/decoding
Given JSON data, it does the CBOR encode/decode.
Given a JSON and a Mapper(similar to claim 169) are given, it maps the JSON with Mapper and then does the CBOR encode/decode.
Integrate eSignet for Auth and Certify for credential issuance
Authorisation partner: eSignet
KBI plugin: eSignet
Credential Issuance: Certify
Draft 13 changes of OpenID4VCI spec - Compatibility of the credential issuance as per the latest draft of OpenID4VCI specification.
The following table outlines the tested and certified compatibility of Inji Wallet 0.14.0 with other modules.
Below is the list of known issues. To read in detail and view all the issues related to Inji Verify please click here.
Note: Redmi devices are not supported in this release.
Below is the list of fixes as part of the 0.14.0 release:
QA Report
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
Passcode unlock
VC download via MOSIP
VC download via esignet
VC download via Sunbird
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
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.
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 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.
Here is the detailed breakdown of metrics for each module:
The 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.
The 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: 58e77d26fc1b98884c11638bba70c128d27994e3
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 tests passed / 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
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:
To simplify the deployment process for Mimoto in local environment, a Docker Compose file is now available. Click here to know more.
The Inji repo is renamed to inji-wallet
Steps to update local github configuration:
The following table outlines the tested and certified compatibility of Inji Wallet 0.13.0 with other modules.
Redmi devices are not supported in this release. To know more, refer here.
Mentioned below is the list of other known issues.
The 0.13.0 release includes the following bug fixes:
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 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 Wallet
testing scope revolves around the following flows:
Biometric unlock
Passcode unlock
VC download via MOSIP
VC download via eSignet
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(Independent Verification and Validation) by simulating the 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 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 Languages
Virtual countries
1 language configuration
2 language configuration
3 language configuration
Below are the test metrics for Inji Wallet by performing functional testing using mockMDS
and mockABIS
. 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 inline 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.
Test Rate: 97.60% with Pass Rate: 88.31%
Here is the detailed breakdown of metrics:
Total Test cases: 950
Passed: 810
Failed: 114
Skipped (N/A): 26
Total Test cases: 873
Passed: 800
Failed: 55
Skipped: 18
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 endpoint is tested with the test data and expectations of each test data are mapped to assert the test case.
Test Rate: 99.09% with Pass Rate: 94.22%
Here is the detailed breakdown of metrics:
Below section provides details on UI Automation by executing MOSIP functional automation Framework.
Test Rate: 100% with Pass Rate: 87.50%
Here is the detailed breakdown of metrics
Functional and test rig code base branch which is used for the above metrics is:
Hash Tag: sha256 : f010aee8b1e7f25cfb2284b20779cb5b8b6bd2efdd8a22b1e3c6d3a20194411a
Below are the test metrics by performing VC Sharing functionality on various device combinations.
Test Rate: 100% with Pass Rate: 72.8%
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
Link for the detailed test report
Release Name: Inji 0.12.0
Support: Developer Release
Release Date: 31st May, 2024
We are delighted to announce the release of Inji Wallet Version 0.12.0 . This release is compatible with v0.12.0 Mimoto release. As part of 0.12.0, Inji Wallet introduces below mentioned key features:
1. Features added to the Download Functionality:
Credential Type Selection
VC Verification
QR Code Generation for VC
2. Library:
QR Code Generation: PixelPass
3. UI/UX Enhancements:
Card View UI Changes
VC Share Optimization
Activity Log Enhancements
GenderMag Fixes
4. Data Backup Enhancements
Inji Wallet app addresses gender / inclusivity bias in software through GenderMag analysis. In this release, we have incorporated GenderMag fixes for UI / UX in inclusivity space.
To know more about the GenderMag UI/UI changes in the Inji Wallet application, please refer here.
Please find below the details for the Inji Version 0.12.0 release:
Inji Wallet now allows users to select the type of credential they need, giving them the option to choose from a list of Credential Types issued by the ID provider. This enables users to download Verifiable Credentials that match their selection.
Inji Wallet provides the functionality to verify Verifiable Credentials using the Digital Bazaar library. The issuer's signature is verified based on the proof type provided by the issuer. Currently, we support the RSA signature type, and we will soon add support for the Ed25519 proof type.
To prevent failures during download caused by verification of Verifiable Credentials with any other signature type, this step needs to be bypassed. Learn more about the steps here.
PixelPass, part of the Inji Credentialing stack, generates QR codes for Verifiable Credentials within the Inji Wallet. It's specifically designed for smaller data sets when the ID provider doesn't send a QR code along with the Verifiable Credential. Users can view and use this QR code for verification purposes by the relying party or service provider.
To know more about QR code verification, read about Inji Verify here.
QR Code Generation: PixelPass
To read more about PixelPass library refer here.
Inji Wallet version 0.12.0 introduces enhanced UI to deliver a seamless user experience with an intuitive design. The UI modifications included in this release are:
Card View UI Changes:
Users can now view the card in two ways:
A mini view on the Home Page with a quick access menu.
A detailed view.
Additionally, the Settings menu has been moved to the NavBar for easier access.
VC Share Optimization:
With the quick access menu in the mini view of the card:
Users can quickly initiate a Share or Share with Selfie action from the card to be shared.
Activity Log enhancements:
The audit logs have been enhanced to elevate the user experience. Now, they include the card type, along with the card number and the action performed, for better readability.
GenderMag P2 items:
Enhanced text to clarify the next steps and reasons for permission requests.
Improved user experience by providing clear notifications for success or failure, including a success screen or error banner with the reason for failure during VC sharing and face verification.
As part of the 0.12.0 release, the following enhancements have been made to the Data Backup feature:
Cloud as the Primary Source:
The backup file stored in the cloud will be the primary source of truth.
Once the backup file is downloaded and restored, it is automatically removed from the local app storage to ensure that the latest backup file is always restored.
iCloud Section Visibility:
The iCloud Section is now visible in the Backup & Restore settings screen, allowing users to easily manage their backup.
User Notification:
When the user initiates a Backup or Restore process, a banner will be displayed to inform users about the ongoing process.
Redmi devices are not supported in this release. To know more, refer here.
Mentioned below is the list of other known issues.
Below are the list of fixes as part of 0.12.0 release:
Release Name: Inji 0.11.0-Inji
Support: Developer Release
Release Date: 29th March, 2024
We are excited to announce the release of Inji Version 0.11.0 . This release is compatible with v0.11.0 Mimoto release. As part of 0.11.0, Inji introduces below mentioned key features:
VC download using KBI
Data backup and restore
Improved UI / UX
In the recent past, Inji Wallet app had undergone GenderMag analysis which addresses gender / inclusivity bias in software. In this release, we have incorporated GenderMag features for UI / UX in inclusivity space.
To know more about the GenderMag UI/UX changes in the application, please refer here.
Please find below the details for the Inji Version 0.11.0 release:
Inji Wallet has proven capability to integrate with any credential issuer supporting OpenID protocol and issues Verifiable Credentials (VCs) based on OpenID4VCI standards. To demonstrate the implementation of VC download using KBI (Knowledge Based Identification), Inji Wallet when integrated with eSignet 1.4.0, can connect with any issuer preferring KBI-based identification.
To know more about, KBI, refer here.
Inji Wallet currently offers data backup and restore functionality using Google Drive for Android and iCloud for iOS to safely store residents' Verifiable Credentials(VCs) on resident's preferred cloud platform. This ensures security and accessibility. Resident can also easily restore backed up information as required, and thereby enabling seamless user experience whether the resident uses Android or iOS.
The GenderMag Method is a process and also a set of materials helpful in investigating gender biases during resident's problem-solving experiences with software. Gendermag adheres to Human Computer Interaction (HCI) principles and thereby factor in gender differences interaction with software. As part of GenderMag walkthrough, we have identified inclusivity bugs with respect to UI / UX in Inji Wallet. Version 0.11.0 includes UI / UX changes for P1 items.
Redmi devices are not supported in this release. To know more, refer here.
Mentioned below is the list of other known issues.
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 - 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 the 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 Lang
Virtual countries
1 Lang configuration
2 Lang configuration
3 Lang configuration
On Android 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 the simulation of multiple identity schema and respective UI schema configurations.
Test Rate: 98% With Pass Rate: 89.74%
Here is the detailed breakdown of metrics for each module:
The below section provides details on API test metrics by executing the MOSIP functional automation Framework. All external API test executions were performed at module level isolation. Each endpoint is tested with the test data and expectations of each test data are mapped to assert the test case.
Test Rate: 90.6% With Pass Rate: 9.4%
Here is the detailed breakdown of metrics:
The below section provides details on Ui Automation by executing the MOSIP functional automation Framework.
Test Rate: 100% With Pass Rate: 96.72%
Here is the detailed breakdown of metrics:
Functional and test rig code base branch which is used for the above metrics is:
SHA: sha256: b477f64889c7340a1d1ca6b17601473c30d206de8de9c8a69e8879be38e1dbb5
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.
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 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.
In this release, the testing scope has been focused around the hotfixes for Inji Wallet along with the addition of the below new features:
Moving away from Google Nearby API definitions
Optimization of Save VC flow
Persona based approach has been adopted to perform the IV&V(Independent Verification and Validation) by simulating the 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.
Verification is performed on various configurations as mentioned below:
Default configuration (with 6 languages)
Below are the test metrics by performing functional testing using mockMDS and mockABIS. 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.
Test Rate: 95% with Pass Rate : 89%
Here is the detailed breakdown of metrics for each module:
Total Test cases: 206
Passed: 185
Failed: 17
Skipped: 4
Total Test cases: 190
Passed: 152
Failed: 23
Skipped: 15
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.
Test Rate: 100% with Pass Rate : 96%
Below are the test metrics by performing VC Sharing functionality on various device combinations:
Test Rate: 100% with Pass Rate : 100%
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
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 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 Wallet
testing scope revolves around the following flows:
Biometric unlock
Passcode unlock
VC download via MOSIP
VC download via eSignet
Retrieving UIN/VID via AID
Pinning a VC
Normal VC sharing with VID
Deleting VC
Face Auth on Resident's phone with VID
Multi language support
Wallet binding
QR code Login
Logout
Persona based approach has been adopted to perform the IV&V(Independent Verification and Validation) by simulating the 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 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 languages
Virtual countries
1 Lang configuration
2 Lang configuration
3 Lang configuration
Below are the test metrics for Inji Wallet by performing functional testing using mockMDS
and mockABIS
. 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 inline 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.
Test Rate: 96% with Pass Rate: 86%
Here is the detailed breakdown of metrics:
Total Test cases: 733
Passed: 625
Failed: 76
Skipped: 32
Total Test cases: 661
Passed: 541
Failed: 100
Skipped: 20
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 endpoint is tested with the test data and expectations of each test data are mapped to assert the test case.
Test Rate: 100% with Pass Rate: 98.34%
Here is the detailed breakdown of metrics:
Note:
Functional and test rig code base branch which is used for the above metrics is:
Commit Sha: 6641489c9ea2129daaf6989c7e6d73bae528a4c0
Below section provides details on UI test metrics by executing MOSIP UI Automation Framework. 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 are the test metrics by performing VC Sharing functionality on various device combinations.
Test Rate: 100% with Pass Rate: 100%
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
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
Release Name: Inji 0.10.0
Upgrade From: Inji 0.9.0
Support: Developer Release
Release Date: 19th December, 2023
We are pleased to announce the release of Inji Version 0.10.0. This release builds upon Inji 0.9.1, introducing key features and improvements.
OpenID Support for Verifiable Credentials: Inji 0.10.0 introduces support for OpenID, facilitating the issuance of verifiable credentials.
Enhanced Security for Personally Identifiable Information (PII) Data: A significant focus has been placed on reinforcing security measures related to Personally Identifiable Information (PII) data.
Facial Recognition for Transaction Authorization: This version introduces advanced facial recognition capabilities to elevate the security of transaction authorization processes.
Improved UI/UX: User Interface (UI) and User Experience (UX) have undergone refinement to provide users with an intuitive and aesthetically pleasing interaction.
Application ID (AID): Inji 0.10.0 now includes an Application ID, contributing to streamlined identification and tracking.
Below is the detailed summary of the release.
A redesigned interface promises improved usability and a more intuitive experience.
Navigation buttons have been updated to prominently display primary functionalities.
Secondary functionalities, such as viewing received Verifiable Credentials (VC) and displaying QR codes, have been relocated under the settings menu for a streamlined experience.
The introduction of new and detailed error messages, along with app warnings, aims to enhance transparency and overall usability.
Securely stored encryption of private keys using the Android hardware keystore for heightened security.
Implemented hash algorithms for verifying the integrity of downloaded and received Verifiable Credentials (VCs).
Enhanced password security with the implementation of password hashing algorithms.
App now proactively responds to security breaches by initiating a self-reset or eliminating tampered Verifiable Credentials (VCs).
Inji now seamlessly integrates with OpenID, expanding support for Verifiable Credentials (VC).
The app is now equipped to onboard Identity Providers (IdP), offering users a choice when interacting with issuers.
Introduces new screens allowing users to select issuers before downloading Verifiable Credentials (VC).
eSignet and MOSIP have been successfully onboarded as Identity Providers within Inji.
Inji now employs advanced facial recognition libraries for secure and seamless authorization of Verifiable Credential (VC) transfers.
A unique application ID is now associated with each unique installation of Inji. It is made accessible to the users.
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 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 Wallet
testing scope revolves around the following flows:
Biometric unlock
Passcode unlock
VC download via MOSIP
VC download via eSignet
Retrieving UIN/VID via AID
Pinning a VC
Normal VC sharing with VID
Deleting VC
Face Auth on Resident's phone with VID
Multi language support
Wallet binding
QR code Login
Logout
Persona based approach has been adopted to perform the IV&V(Independent Verification and Validation) by simulating the 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 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.
Below are the test metrics for Inji Wallet by performing functional testing using mockMDS
and mockABIS
. 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 inline 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.
Test Rate: 95% with Pass Rate : 82%
Here is the detailed breakdown of metrics:
Total Test cases: 602
Passed: 476
Failed: 99
Skipped: 27
Total Test cases: 485
Passed: 387
Failed: 78
Skipped: 20
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 endpoint is tested with the test data and expectations of each test data are mapped to assert the test case.
Test Rate: 100% with Pass Rate: 99.52%
Here is the detailed breakdown of metrics:
Note:
Functional and test rig code base branch which is used for the above metrics is:
Commit Id is: 103e0606
Hash Tag: afedb56a2977844286bc4cbfedb8263507efa823a3d7d5a7b3cbd601ac22d120
Below are the test metrics by performing VC Sharing functionality on various device combinations.
Test Rate: 100% with Pass Rate : 100%
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
Release Name: Inji vDP2
Upgrade From: Inji 0.10.0
Support: Developer Preview Release2
Release Date: 22nd January, 2024
The Developer Preview Version 2 release is an additional release on top of Inji 0.10.0. This release primarily emphasizes:
UI enhancements
Internal enhancements
Security fixes
Bug fixes
Below is the detailed summary of the release.
As a part of the VC sharing feature or listing of VCs for QR login, the Pinned VC will now appear on top of the VC list.
User can now provide one time consent for a selected VC while sharing the claims during QR code login.
Additionally, a search bar has been added to the Add new card
screen to improve user experience by allowing users to search for issuers based on the title.
Furthermore, any rendering issues in the user interface have been resolved.
Secure KeyStore and Tuvali have been integrated as independent NPM modules within the INJI framework. For further information, please refer to the provided documentation.
Additionally, all image assets have been converted from png
to svg
format. This transition ensures the presence of a single asset set, and the color of the icons will now be dynamically rendered based on the application's theme.
The critical vulnerabilities identified by OWASP dependency check have been addressed:
The expo-app-loading package has been replaced with expo-splash-screen for the purpose of app loading.
In order to enhance security for devices without hardware backed keystore, the crypto-js
package has been substituted with node-forge for encryption, decryption, and HMAC generation.
Release Name: Inji vDP1
Upgrade From: Inji 0.9.1 (Patch)
Support: Developer Preview Release1
Release Date: 28th September, 2023
The developer preview version of Inji Wallet is the release on top of Inji 0.9.1. Key highlights of the release are:
Enhanced UI
Additional functional flows in Inji
Internal enhancements
Bug fixes
Below is the detailed summary of the release.
New UI for Inji Wallet:
This redesign promises an enriched user experience.
Introduction sliders have been introduced.
Helpful FAQ screens are provided.
VC pinning is now available.
Currently, the pinning feature supports a single VC.
Easy VC removal from Inji Wallet.
Improved audit log filtering based on VC.
Branding the App as Inji Wallet
:
We've rebranded the application, transitioning from Resident App
to the more streamlined and recognisable Inji Wallet
.
Ability to Choose Language During App Setup:
Inji Wallet app users can configure the application in six distinct languages:
English
Filipino
Arabic
Hindi
Kannada
Tamil
Warning When Device Storage is Beyond the Threshold:
Inji Wallet now offers customisable storage limits:
For VC downloads, the threshold is set to 5MB. When the device's remaining storage space falls below this limit, Inji Wallet displays a warning message. However, users can still continue to verify and share VCs.
For Inji Wallet audit logs, the threshold is set to 1MB. Once the device reaches this limit, Inji users will be restricted to viewing VCs, unable to perform additional actions.
Traceability with Unique ID for Customer Support:
We've implemented a unique identification called as an Application ID for customer support interactions. Each support request is now assigned a traceable and distinct ID, allowing our support teams to efficiently track, manage, and resolve customer issues.
Improved Bluetooth State and Permission Handling:
We have refined the management of Bluetooth states and permissions.
Removed Google Nearby
Implementation:
Encrypted VC’s Metadata:
We now calculate and securely store an encrypted HASH (HMAC SHA256) of the VC's metadata key in the database, bolstering data security.
Release Name: Inji 0.9.1 (Patch)
Upgrade From: Inji 0.9.0 (Beta)
Support: Developer Release
Release Date: 25th July, 2023
The 0.9.1 version of Inji Wallet is the first patch release on top of Inji 0.9.0. This release has bug fixes for features like Downloading and sharing the VC, Wallet binding, face authentication on resident’s phone, etc.
Below is a summary of some of the important bug fixes made in this version.
Added capabilitities to transfer the VC to more number of devices with an increase in device compatibility.
Introduction of error codes in case the transfer of VC fails.
Based on the android devices, Inji Wallet now asks for only the required Bluetooth permissions.
Migrated to MMKV storage from Async storage. With this, the devices can now store more number of VCs.
Renew auth token after expiry in Mimoto.
Added support for Filipino language (Philippines language).
Added support for languages whose semantics are Right-to-Left.
Added feature to restrict the downloading of ID card when the download of the card via UIN is blocked.
Updated VC thumbprints when the same VC is downloaded multiple times on the same device and is activated.
The 0.9.1 version of Inji Wallet mainly focuses on bug fixes along with some internal improvements like:
Ability to build on Windows
Abilty to build and push iOS builds to TestFlight without any human intervention
The older version of Inji Wallet app (0.9.0) will not be compatible with the newer version of Inji, due to the following reasons:
The storage has been changed from Async Storage to mmkv storage, which are two different storage mechanisms.
The VC sharing might break as Tuvali has updated the type of data shared across devices, hence it can cause array index out of bounds exception.
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 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
Passcode unlock
VC download via MOSIP
VC download via esignet
VC download via Sunbird
Retriving 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
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.
Verification is performed on various configurations as mentioned below
Default configuration - with 3 Lang
Virtual countries
1 Lang configuration
2 Lang configuration
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. 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.
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:c2a71c11f19a6585e6cfd3ae8ab70130babb2077e27714f5fc225b986e7c14d0
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
Release Name: Inji Wallet 0.13.1 Patch release
Release Version: 0.13.1
Release Type: Developer
Release Date: 10th Sep, 2024
We are excited to announce the release of Inji Wallet Version 0.13.1! This patch release aims on critical fixes and improvements to ensure smoother integration of libraries and enhanced performance. Key updates include the bundling of dependencies with Android Archive (AAR) and JAR files, which simplifies the integration process and resolves issues related to library dependencies for the below mentioned libraries:
tuvali
inji-vci-client
pixelpass
secure-keystore
Library Updates:
Updated libraries to bundle dependencies with Android Archive (AAR) and JAR formats. This ensures that all required dependencies are included within the package, reducing the need for external dependency management and minimizing conflicts during app integration.
These changes enhance compatibility with various Android development environments and improve the overall stability of the wallet.
The following table outlines the tested and certified compatibility of Inji Wallet 0.13.1 with other modules.
None
Redmi devices are not supported in this release. To know more, refer here.
Mentioned below is the list of other known issues.
Jira issue | Issue description |
---|---|
Module | Version |
---|---|
Jira Issue | Issue Description | Severity |
---|---|---|
Jira issue | Issue description |
---|---|
Jira issue | Severity | Issue description |
---|---|---|
Jira issue | Issue description |
---|---|
Jira issue | Severity | Issue description |
---|---|---|
Total | Passed | Failed | Skipped(N/A) |
---|
Total Test Cases | Passed | Failed | Skipped(N/A) |
---|
Total Test Cases | Passed | Failed | Skipped(N/A) |
---|
Total Test Cases | Passed | Failed | Skipped(N/A) |
---|
Total Test Cases | Passed | Failed | Skipped(N/A) |
---|
Total Test Cases | Passed | Failed | Skipped(N/A) |
---|
Tested with Components |
---|
Tested with MOSIP Components |
---|
Devices Used For Testing |
---|
Link for the .
Link for the .
Git hub link for the xls file is .
Redmi devices are not supported for this release. To know more, refer to .
The user will now be redirected to the MOSIP page successfully from the About INJI
screen. Earlier the link was crashing the app. #
The user will be able to login into eSignet portal via QR code, using the VC activated on Home screen via. ellipsis menu. #
App will prompt and remove tampered VC. #
The user will be asked for language preference only at new installation. #
Previously used UIN/VID will not be suggested in the AID field for VC download. #
The user will be able to see the detailed view of Received
VC. #
The user will be redirected to an intermittent downloading screen, when download is triggered from OpenID supported issuer. #
Link for the .
Efforts have been made to improve the security of data in the default file located in the mmkv
folder under the task.
To know more about Inji, watch the !
We've transitioned to using for Bluetooth Low Energy (BLE) communication, enhancing the connectivity experience.
Bug fix: Reduced the app size for Android #
Bug fix: Resolved connectivity issue when sharing VC #
Bug fix: Fixed QR/ Esignet login using INJI app #,
Bug fix: Resolved BLE issues #,
To know more about Inji Wallet, watch the !
Bug fix: All the binded VCs will be shown and every binded VC can be used for online login irrespective of the timeframe of binding. #
Bug fix: Tuvali now has the capability to specify an error code to let Inji know where the error has occurred during VC sharing instead of displaying the default error message. #
Bug fix: Added capability to build APKs on Windows. # #
Bug fix: In iOS, when the user tries to go back from the OTP screen while generating VID from AID, Inji was crashing. As a fix, it was made sure that the models (overlays) are not overlapping. #
Bug fix: Inji now has the capability to render the resident's demographic information in the language chosen by the Residents. #
Bug fix: Inji now has the capability to identify when the App is low on storage and notify the same to the Residents. #
Bug fix: During wallet binding when the auth token is expired, the first call made for wallet binding will be used for refreshing the auth token, which then makes the current call to fail and subsequent calls to succeed. As a fix, the wallet binding call will refresh the token and complete the binding process. #
Bug fix: Inji Wallet had a restriction to the overall storage size, in that, we were not able to download more than 29 VCs. As a fix, we migrated from Async storage to MMKV which does not have any upper limit on the storage size. #
Bug fix: In the Home Screen, the tab indicators were not properly working in RTL. After the fix, RTL is being rendered properly. #
Bug fix: The VCs that are added were getting stored in the app memory rather than user data. As a fix, MMKV storage was introduced (as opposed to async storage) to solve this by moving the VC data to user data instead of App memory. #
Bug fix: A few texts were not being rendered in Arabic. The Arabic translations were added to make sure when the resident has chosen Arabic language, all the data is being rendered in Arabic. #
Bug fix: Inji Wallet application was not consistent in different locales, and some literals were not properly translated in the native languages. As a fix, all the missed out translations were added. # #
Bug fix: The error popup shown during the BLE transfer is updated, the popup will now contain few error codes which depicts different stages where the failure has happened in the BLE layer. #
Bug fix: There was a delay in reading and writing the VC from the device, so the storage mechanism has been changed from Async Storage to MMKV Storage, which ensures faster reading and writing. #
Bug fix: Few devices failed to establish the connection while sharing of VCs were initiated (Vivo Y73 & Redmi K20 Pro). To resolve this, setting preferred PHY was removed and missing BLE permissions for Android 12 and above were added. #
Bug fix: The VC transfers from iOS device always failed when Android 13 was the Verifier. As a fix, Bluetooth negotiation was updated to support Google Pixel (Android 13). #
To know more about Inji Wallet, watch the !
Github link for the xls file is .
Repositories
Tags Released
Inji-wallet
v0.14.0
Module
Version
Mimoto
v0.14.0
Inji-config
v0.3.0
eSignet
v1.4.1
Inji Verify
v0.10.0
tuvali
tuvali-ios-swift
secure-Keystore
pixelpass
pixelpass-ios-swift
Inji-vci-client
Inji-vci-client-ios-swift
Inji Wallet- After clicking the + icon, the screen flickers before landing on the 'Add New Card' screen
The search box close button is not working unless invoked on a specific point
Inji Wallet- Android - History timings could be more precise
IOS- The Wallet app session should expire if the app is opened for a longer time and the user tries to log in again with the PIN to generate VC by using UIN/VID.
Inji Wallet- The error message of QR code login without an internet attempt should be revised
Inji Wallet- On the face verification page the capture button overlaps with the text
Inji Wallet- During face authentication, the camera view is not opening in all IOS device
Inji Wallet - IOS - "Share QR Code" is not working on iPhone 8.
Inji Wallet - Backup is not triggering automatically when VC is removed.
Inji Wallet- the logo of Inji Wallet stretched while booting the app
IOS -For specific devices, the User cannot see the iCloud ID in the iCloud setting section of the backup and restore page.
Inji Wallet - An error message is not proper when an invalid QR is scanned after changing the language to something other than English.
Inji Wallet- Backup & restore Name Is Different In Settings And Backup & restore Page
Backup and Restore heading Alignment is not proper on the Backup& restore page
Inji Wallet- Sometimes VC activate the button and the back button responses are very slow
Inji Wallet- ID Repo UINs are failing in VC verification
Inji Wallet- Backup doesn't append the new data but replaces the data
Upon changing the finger authentication in the device, the application does not display the error pop-up for biometrics change
Jira issue
Issue description
Inji Wallet: When the camera access is disabled, the user clicks on the close icon error screen it redirects to the sharing screen
Inji Wallet - Unable to go back from the detailed view page
Inji Wallet- VC verification is passing for missing attribute VC
Inji Wallet- During face authentication, the camera view is wider than the face.
Inji Wallet - IOS - The "Share QR Code" feature saves both the QR Code and a text file to files.
Inji Wallet- Users are unable to upload the VC QR code shared via email and WhatsApp, or stored locally
Inji Wallet- In Android when the user clicks the + icon from the home page issuer page is not loaded
Inji Wallet - Unable to see the issuer of the credentials
Inji Wallet- Sunbird issuer is not loading and is redirecting to the 'Add New Card' screen. Trying to click any other issuer is also not working
Inji Wallet- The Intermittent share with selfie option is not getting for the National Identity department
Activation successful banner is not showing up
Inji Wallet- We are unable to download the VC Stay Protected insurance credential
Inji Wallet- When the Certify well-known is replaced with fall back well-known url in the Inji configuration The user is not redirected to the default well-known issuer
Inji Wallet- The user is not getting any error if the fallback is not working
Inji Wallet-Mock identity is not loading and is redirecting to the 'Add New Card' screen. Trying to click any other issuer is also not working
Activated option in quick access menu for VCs which doesn't have biometrics
Inji Wallet- In the mock VC, there is no profile photo, but the share option is still visible
When display properties are removed at mosip certify the user is blocked with a white screen and not able to use the app.
Update mimoto local properties file to run mimoto locally without docker-compose
Background colour not showing up in VC as per configuration in well-known
Total
Passed
Failed
Skipped (N/A)
2461
2203
214
44
Test Rate: 98.21% With Pass Rate: 91.14%
Test cases
On Android Device
Total
1315
Passed
1169
Failed
117
Skipped (N/A)
29
On iOS Device
Total
1146
Passed
1034
Failed
97
Skipped (N/A)
15
Total
Passed
Failed
Skipped
141
134
4
3
Test Rate: 97.97% With Pass Rate: 97.10%
Total
Passed
Failed
Skipped
108
106
2
0
Test Rate: 100% With Pass Rate: 98.14%
Test cases
Android
Total
60
Passed
58
Failed
2
Skipped
0
iOS
Total
48
Passed
48
Failed
0
Skipped
0
Total
Passed
Failed
Skipped
192
192
0
0
Test Rate: 100% With Pass Rate: 100%
Tested with Components
mosipid/esignet:1.4.1
mosipqa/mimoto:develop
Tuvali Version - 0.5.1
Tested with MOSIP Components
mosipid/admin-service:1.2.0.1-B1
mosipid/admin-ui:1.2.0.1-B1
mosipid/artifactory-server:1.4.1-ES
mosipid/authentication-internal-service:1.2.0.1
mosipid/authentication-otp-service:1.2.0.1
mosipid/authentication-service:1.2.0.1
mosipid/biosdk-server:1.2.0.1
mosipid/commons-packet-service:1.2.0.1-B1
mosipid/config-server:1.1.2
mosipid/consolidator-websub-service:1.2.0.1-B1
mosipid/credential-request-generator:1.2.0.1
mosipid/credential-service:1.2.0.1
mosipid/data-share-service:1.2.0.1-B2
mosipid/hotlist-service:1.2.0.1-B1
mosipid/id-repository-identity-service:1.2.0.1
mosipid/id-repository-salt-generator:1.2.0.1
mosipid/id-repository-vid-service:1.2.0.1
mosipid/kernel-auth-service:1.2.0.1-B2
mosipid/kernel-idgenerator-service:1.2.0.1-B1
mosipid/kernel-keymanager-service:1.2.0.1
mosipid/kernel-notification-service:1.2.0.1-B1
mosipid/kernel-otpmanager-service:1.2.0.1-B1
mosipid/kernel-pridgenerator-service:1.2.0.1-B1
mosipid/kernel-ridgenerator-service:1.2.0.1-B1
mosipid/kernel-salt-generator:1.2.0.1-B2
mosipid/kernel-syncdata-service:1.2.0.1-B1
mosipid/keycloak-init:1.2.0.1
mosipid/keycloak-init:1.2.0.1-B2
mosipid/keycloak-init:1.2.0.1-B3
mosipid/keys-generator:1.2.0.1-B3
mosipid/masterdata-loader:1.2.0.1-B4
mosipid/mock-abis:1.2.0.1-B2
mosipid/mock-mv:1.2.0.1-B2
mosipid/mock-relying-party-service:0.9.1
mosipid/mock-relying-party-service:0.9.2
mosipid/mock-relying-party-ui:0.9.1
mosipid/mock-relying-party-ui:0.9.2
mosipid/oidc-ui:1.4.1
mosipid/partner-management-service:1.2.0.1-B3
mosipid/partner-onboarder:1.2.0.1-B4
mosipid/pmp-ui:1.2.0.1-B1
mosipid/policy-management-service:1.2.0.1-B3
mosipid/postgres-init:1.2.0.1-B4
mosipid/pre-registration-application-service:1.2.0.1-B1
mosipid/pre-registration-batchjob:1.2.0.1-B1
mosipid/pre-registration-booking-service:1.2.0.1-B1
mosipid/pre-registration-captcha-service:1.2.0.1-B1
mosipid/pre-registration-datasync-service:1.2.0.1-B1
mosipid/pre-registration-ui:1.2.0.1-B1
mosipid/print:1.2.0.1-B1
mosipid/registration-client:1.2.0.1-B1
mosipid/registration-processor-common-camel-bridge:1.2.0.1-B1
mosipid/registration-processor-dmz-packet-server:1.2.0.1-B1
mosipid/registration-processor-notification-service:1.2.0.1-B1
mosipid/registration-processor-registration-status-service:1.2.0.1-B1
mosipid/registration-processor-registration-transaction-service:1.2.0.1-B1
mosipid/registration-processor-reprocessor:1.2.0.1-B1
mosipid/registration-processor-stage-group-1:1.2.0.1-B1
mosipid/registration-processor-stage-group-2:1.2.0.1-B1
mosipid/registration-processor-stage-group-3:1.2.0.1-B2
mosipid/registration-processor-stage-group-4:1.2.0.1-B1
mosipid/registration-processor-stage-group-5:1.2.0.1-B1
mosipid/registration-processor-stage-group-6:1.2.0.1-B1
mosipid/registration-processor-workflow-manager-service:1.2.0.1-B1
mosipid/signup-service:1.0.0
mosipid/signup-ui:1.0.0
mosipid/softhsm:v2
mosipid/websub-service:1.2.0.1-B1
mosipint/digital-card-service:release-1.2.0.1-DP
mosipint/kernel-masterdata-service:develop-DP
mosipint/registration-processor-stage-group-7:develop-DP
mosipint/resident-service:develop-DP
mosipint/resident-ui:develop-DP
mosipqa/artifactory-server:0.9.0-INJI
mosipqa/artifactory-server:1.4.1-ES
mosipqa/authentication-demo-service:develop
mosipqa/automationtests:develop
mosipqa/dsl-orchestrator:develop
mosipqa/dsl-packetcreator:develop
mosipqa/inji-certify:0.9.x
mosipqa/inji-web:develop
mosipqa/kernel-auditmanager-service:1.2.0.1
mosipqa/keycloak-init:develop
mosipqa/mock-identity-system:0.9.3
mosipqa/mock-relying-party-service:0.9.x
mosipqa/mock-relying-party-ui:0.9.x
mosipqa/mock-smtp:0.0.2
mosipqa/mosip-artemis-keycloak:develop
mosipqa/mosip-file-server:develop
mosipqa/postgres-init:develop
mosipqa/softhsm:v2
Devices Used For Testing
Vivo Y73 with Android 12 BLE 5.0
SS Galaxy A03 core with Android 11 BLE 4.2
iPhone 11 with i-OS 15 BLE 5.0
iPhone 8 with i-OS 16 BLE 5.0
iPhone 7 with i-OS 15.6 BLE 4.2
Redmi 7A Android 10 BLE 4.2
Redmi note 10 lite Android 10 BLE 5.0
redmi K20 pro Android 11 BLE 5.0
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
Repositories
Tags Released
tuvali
secure-keystore
pixelpass
inji-vci-client
Inji Wallet
Module
Version
Mimoto
inji-config
Jira issue
Issue description
In the INJI 0.12x version, issues with downloading their UIN cards.
INJIMOBILE- After clicking the + icon, the screen flickers before landing on the 'Add New Card' screen
Search box close button is not working unless invoked on a specific point
INJIMOB- Android - History timings could be more precise
IOS- Mobile app session should get expired, if the app is opened for a longer time and user tries to login again with the PIN to generate VC by using UIN/VID.
INJI - error message of QR code login without internet attempt should be revised
INJIMOB- In the face verification page the capture button overlaps with text
INJIMOB- During face authentication, the camera view is not opening in all IOS device
INJIMOB - IOS - "Share QR Code" is not working on iPhone 8.
INJIMOB - Backup is not triggering automatically when VC is removed.
INJI - logo of inji mobile stretched while booting the app
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- Sometimes VC activate the button and back button responses is very slow
INJI - Iderpo UINs are failing in VC verification
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
Total
Passed
Failed
Skipped
1823
1610
169
44
Total
Passed
Failed
Skipped
1436
1353
68
13
Total
Passed
Failed
Skipped
157
143
14
0
Total
Passed
Failed
Skipped
1279
1210
54
13
Total
Passed
Failed
Skipped
128
112
16
0
Total
Passed
Failed
Skipped
72
64
8
0
Total
Passed
Failed
Skipped
56
48
8
0
Total
Passed
Failed
Skipped
213
155
61
0
Repositories
Tags Released
Inji
mimoto
mosip-config
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 - onboarding of new issuer is affecting the existing issuers
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
Blocker
inji - we are observing a download error message
Critical
Inji-Downloading error is observed when we were trying to restore VCs in a new device.
Critical
INJI- after deleting the backed up data it is not reflecting in the app
Critical
INJI - we are able to restore when there is no data to restore
Critical
IOS - app is not responsive in few senarios
Critical
INJI - once we delete a restored VC, we are not able to delete or pin other restore VC
Critical
IOS - device specific data is backuped if the Icloud is shared in multiple device
Critical
IOS - in specific device we are not able to restore VC
Critical
IOS- While deleting a single VC all downloaded VCs are getting deleted
Critical
INJI- The Backup button and restore button both are clickable at the same time
Critical
INJI - face auth is not working in room brightness on all devices
Critical
Getting tampered error pop up without tampering any vc in Vivo Y73.-- update: all devices
Critical
Inji- The Inji application is not stable sometimes we are not able to activate the VC
Major
INJIUI :- share button text is not translating to another language for ios
Major
Backup and restore screen the back button's response is slow.
Major
INJI- sunbird Vc is not rendering properly for a few second in sharing card page and received card page
Major
VC Select screen appears in a flash when the user clicks on Share from NavBar after navigating to Home page from the ID Transfer successful screen.
Major
android - receive card header is fully in caps
Major
INJI - few elements are not changing when the app converted to rtl
Major
Inji- We are missing the face validating popup and the Face match successfully popup.
Major
"Id details" section of downloaded card through e-signet don't have green tick mark in status.
Minor
Inji-In the intro sliders, the heading on the backup data page mentions "Data Backup."
Minor
INJI - The date format for downloaded and received are different for the same VC.
Minor
Inji- In download id screen enter the random 10 digits number it was showing UIN/VID/AID is invalid.
Minor
IOS- After downloading the sunbird Vc Unwanted space in between tick icon and valid
Minor
INJI-There was a glitch on previous connected screen for a second.
Repositories
Tags Released
Inji
mimoto
tuvali
mosip-config
Secure-Keystore
mosip-onboarder
Android- Occasionally, unable to activate the restored VC
Inji-Unable to download when user attempted to restore VCs in a new device
INJI- Unable to download the card with a new UIN
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
Android- Specific device, Redmi 7A- During face authentication, app crashes
Redmi 6A device is not compatible with Inji's Tuwali version
Upon changing the finger authentication in the device, application does not display the error pop up for biometrics change
Android - All downloaded VC's are deleted in specific device
Inji- Even upon Wallet failure, the verifier receives success message on the specific devices
Android - Couldn't share VCs between Two specific android devices
Android - Unable to share VC for specific combination
Android - VC transfer fails intermittently for specific device
Inji- The Inji application is not stable. Occasionally, unable to activate the VC
Verifier app crashes upon face authentication
Inji - Unable to save received VC error. Displays as Identity proofs are tampered
Unable able to retrieve VID / UIN from the AID which is raised through pre-registration process
Android - Couldn't share VC between two specific android devices as device crashes
Ios - Redmi 6A doesn't connect with any IOS devices
Android - Redmi 6A idoesn't connect with any android devices
Error message for Invalid OTP is not correctly displayed during VC activation
Critical
Inji - App crashes during click of OTP re-send button of download through AID
Critical
Android - Received VC's are deleted
Critical
Android - App crashes during the first launch
Critical
Inji- Occasionally, user is unable to share immediately
Major
Inji-During activation, VC in ID details page displays the green color toaster message on home screen
Major
Inji- MOSIP logo changes according to the issuer
Major
Inji - Deleted VC's HMAC data is not deleted
Major
Inji-Paragraph border is displayed in color, orange for purple theme selection
Major
Loading time for VC is longer than expected time
Major
Inji- VC sharing is failing intermittently using selfie with share feature
Major
App closes upon re-send code during VC activation through kebab popup
1236 | 1085 | 124 | 27 |
1236 | 1085 | 124 | 27 |
64 | 58 | 6 | 0 |
64 | 58 | 6 | 0 |
61 | 59 | 2 | 0 |
61 | 59 | 2 | 0 |
mosipid/esignet:1.4.0 |
mosipqa/mimoto:develop |
Tuvali Version - 0.5.1 |
mosipid/admin-service:1.2.0.1-B1 |
mosipid/admin-ui:1.2.0.1-B1 |
mosipid/artifactory-server:1.4.0-ES |
mosipid/authentication-internal-service:1.2.0.1 |
mosipid/authentication-otp-service:1.2.0.1 |
mosipid/authentication-service:1.2.0.1 |
mosipid/biosdk-server:1.2.0.1 |
mosipid/commons-packet-service:1.2.0.1-B1 |
mosipid/config-server:1.1.2 |
mosipid/consolidator-websub-service:1.2.0.1-B1 |
mosipid/credential-request-generator:1.2.0.1 |
mosipid/credential-service:1.2.0.1 |
mosipid/data-share-service:1.2.0.1-B2 |
mosipid/hotlist-service:1.2.0.1-B1 |
mosipid/id-repository-identity-service:1.2.0.1 |
mosipid/id-repository-salt-generator:1.2.0.1 |
mosipid/id-repository-vid-service:1.2.0.1 |
mosipid/kernel-auth-service:1.2.0.1-B2 |
mosipid/kernel-idgenerator-service:1.2.0.1-B1 |
mosipid/kernel-keymanager-service:1.2.0.1 |
mosipid/kernel-notification-service:1.2.0.1-B1 |
mosipid/kernel-otpmanager-service:1.2.0.1-B1 |
mosipid/kernel-pridgenerator-service:1.2.0.1-B1 |
mosipid/kernel-ridgenerator-service:1.2.0.1-B1 |
mosipid/kernel-salt-generator:1.2.0.1-B2 |
mosipid/kernel-syncdata-service:1.2.0.1-B1 |
mosipid/keycloak-init:1.2.0.1 |
mosipid/keycloak-init:1.2.0.1-B2 |
mosipid/keycloak-init:1.2.0.1-B3 |
mosipid/keys-generator:1.2.0.1-B3 |
mosipid/masterdata-loader:1.2.0.1-B4 |
mosipid/mock-abis:1.2.0.1-B2 |
mosipid/mock-mv:1.2.0.1-B2 |
mosipid/mock-relying-party-service:0.9.1 |
mosipid/mock-relying-party-service:0.9.2 |
mosipid/mock-relying-party-ui:0.9.1 |
mosipid/mock-relying-party-ui:0.9.2 |
mosipid/oidc-ui:1.4.0 |
mosipid/partner-management-service:1.2.0.1-B3 |
mosipid/partner-onboarder:1.2.0.1-B4 |
mosipid/pmp-ui:1.2.0.1-B1 |
mosipid/policy-management-service:1.2.0.1-B3 |
mosipid/postgres-init:1.2.0.1-B4 |
mosipid/pre-registration-application-service:1.2.0.1-B1 |
mosipid/pre-registration-batchjob:1.2.0.1-B1 |
mosipid/pre-registration-booking-service:1.2.0.1-B1 |
mosipid/pre-registration-captcha-service:1.2.0.1-B1 |
mosipid/pre-registration-datasync-service:1.2.0.1-B1 |
mosipid/pre-registration-ui:1.2.0.1-B1 |
mosipid/print:1.2.0.1-B1 |
mosipid/registration-client:1.2.0.1-B1 |
mosipid/registration-processor-common-camel-bridge:1.2.0.1-B1 |
mosipid/registration-processor-dmz-packet-server:1.2.0.1-B1 |
mosipid/registration-processor-notification-service:1.2.0.1-B1 |
mosipid/registration-processor-registration-status-service:1.2.0.1-B1 |
mosipid/registration-processor-registration-transaction-service:1.2.0.1-B1
|
mosipid/registration-processor-reprocessor:1.2.0.1-B1 |
mosipid/registration-processor-stage-group-1:1.2.0.1-B1 |
mosipid/registration-processor-stage-group-2:1.2.0.1-B1 |
mosipid/registration-processor-stage-group-3:1.2.0.1-B2 |
mosipid/registration-processor-stage-group-4:1.2.0.1-B1 |
mosipid/registration-processor-stage-group-5:1.2.0.1-B1 |
mosipid/registration-processor-stage-group-6:1.2.0.1-B1 |
mosipid/registration-processor-workflow-manager-service:1.2.0.1-B1 |
mosipid/signup-service:1.0.0 |
mosipid/signup-ui:1.0.0 |
mosipid/softhsm:v2 |
mosipid/websub-service:1.2.0.1-B1 |
mosipint/digital-card-service:release-1.2.0.1-DP |
mosipint/kernel-masterdata-service:develop-DP |
mosipint/registration-processor-stage-group-7:develop-DP |
mosipint/resident-service:develop-DP |
mosipint/resident-ui:develop-DP |
mosipqa/artifactory-server:0.9.0-INJI |
mosipqa/artifactory-server:1.4.1-ES |
mosipqa/authentication-demo-service:develop |
mosipqa/automationtests:develop |
mosipqa/dsl-orchestrator:develop |
mosipqa/dsl-packetcreator:develop |
mosipqa/inji-certify:0.9.x |
mosipqa/inji-web:develop |
mosipqa/kernel-auditmanager-service:1.2.0.1 |
mosipqa/keycloak-init:develop |
mosipqa/mock-identity-system:0.9.0 |
mosipqa/mock-relying-party-service:0.9.x |
mosipqa/mock-relying-party-ui:0.9.x |
mosipqa/mock-smtp:0.0.2 |
mosipqa/mosip-artemis-keycloak:develop |
mosipqa/mosip-file-server:develop |
mosipqa/postgres-init:develop |
mosipqa/softhsm:v2 |
Vivo Y73 with Android 12 BLE 5.0 |
SS Galaxy A03 core with Android 11 BLE 4.2 |
iPhone 11 with i-OS 15 BLE 5.0 |
iPhone 8 with i-OS 16 BLE 5.0 |
iPhone 7 with i-OS 15.6 BLE 4.2 |
Redmi 7A Android 10 BLE 4.2 |
Redmi note 10 lite Android 10 BLE 5.0 |
redmi K20 pro Android 11 BLE 5.0 |
Total | Passed | Failed | Skipped |
396 | 337 | 40 | 19 |
Total | Passed | Failed | Skipped |
154 | 149 | 5 | 0 |
Total | Passed | Failed | Skipped |
192 | 192 | 0 | 0 |
Total | Passed | Failed | Skipped |
1394 | 1166 | 176 | 52 |
Total | Passed | Failed | Skipped |
1268 | 1247 | 17 | 4 |
Total | Passed | Failed | Skipped |
154 | 152 | 2 | 0 |
Total | Passed | Failed | Skipped |
1114 | 1095 | 15 | 4 |
Total | Passed | Failed | Skipped |
102 | 61 | 41 | 0 |
Total | Passed | Failed | Skipped |
52 | 36 | 16 | 0 |
Total | Passed | Failed | Skipped |
50 | 25 | 25 | 0 |
Total | Passed | Failed | Skipped |
152 | 152 | 0 | 0 |
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% |
Total | Passed | Failed | Skipped |
1087 | 863 | 177 | 47 |
Total | Passed | Failed | Skipped |
1268 | 1262 | 6 | 0 |
Total | Passed | Failed | Skipped |
154 | 152 | 2 | 0 |
Total | Passed | Failed | Skipped |
1114 | 1110 | 4 | 0 |
Total | Passed | Failed | Skipped |
40 | 40 | 0 | 0 |
Total | Passed | Failed | Skipped (N/A) |
2118 | 1975 | 103 | 40 |
Test Rate: 98% With Pass Rate : 95% |
| Test cases |
On Android Device | Total | 1112 |
Passed | 1005 |
Failed | 81 |
Skipped (N/A) | 26 |
On iOS Device
| Total | 1006 |
Passed | 970 |
Failed | 22 |
Skipped (N/A) | 14 |
Total | Passed | Failed | Skipped |
1436 | 1426 | 6 | 4 |
Test Rate: 99.72% With Pass Rate: 99.30% |
| Test cases |
Mobile ID
| Total | 157 |
Passed | 157 |
Failed | 0 |
Skipped | 0 |
eSignet
| Total | 1279 |
Passed | 1269 |
Failed | 6 |
Skipped | 4 |
Total | Passed | Failed | Skipped |
162 | 146 | 16 | 0 |
Test Rate: 100% With Pass Rate: 90.12% |
| Test cases |
Android
| Total | 82 |
Passed | 75 |
Failed | 7 |
Skipped | 0 |
iOS
| Total | 80 |
Passed | 71 |
Failed | 9 |
Skipped | 0 |
Total | Passed | Failed | Skipped |
213 | 155 | 61 | 0 |
Test Rate: 100% With Pass Rate: 72.8% |
Release Name: Inji 0.9.0 (Beta)
Release Date: 14th April, 2023
The 0.9.0 version of Inji Wallet is the beta release which covers essential features such as Downloading and sharing the VC, Wallet binding, face authentication on resident' phone, etc.
The basic features such as,
Biometric Unlock
Passcode Unlock
VC download with VID
Renaming VC / Edit tag for VID
Normal VC sharing with VID
Online and Offine mode sharing
Face Auth on Resident's phone with VID
Multi-language support
Wallet binding
QR code Login
Logout
are available as part of this release.
Repositories | Tags Released |
mimoto |
inji |
tuvali |
mosip-config |
secure-keystore |
mosip-onboarder |
Issue ID | Description |
Unable to get error message when download retry count is updated to 10. |
iOS - app data erased when we logout in offline. |
We are not able to scan the e-signet QR code In iOS device. |
App resets on re-launch after VC activation in iOS. |
Logout not working in iOS version of Inji. |
iOS - language preference is again asked when we logged out of the app. |
UIN of previously downloaded VC is wrongly pre-filled in AID screen. |
VC sharing is failing intermittently on Android. |
Pinned VC's audit logs are missing. |
Issue ID | Description |
Android - app crashing while saving VC from eSignet, if the hardware keystore is rejected by user. |
Android- The Inji app is crashing intermediately. |
Issue ID | Description |
Android - specific verifier is not connecting with wallet. |
Cross-platform - App couldn't recognize if the Bluetooth is turned off while in connection state. |
Android - We are able to receive VC even if we turned off Bluetooth in specific devices. |
Handle timeout during VC share via BLE. |
Issue ID | Description |
The app couldn't recognize resident face when there are changes. |
Issue ID | Description |
iOS- once we share VC through share with selfie, we are not getting successful screen in the wallet. |
iOS - Loading Screen is missing after Face Auth. |
Button name in "Status" page is not matching as per the requirement provided. |
The navigation button to go back from the ID details page is missing, not matching the wireframe provided. |
While logging out for the first time the language selection and tour guide show up. |
There is no popup to cancel the download card. |
The back button is not working on few places of the app. |
While sharing the VC, if we click on scan icon, application displays the camera. |
Issue ID | Description |
UI - text search field in Add new card screen does not match wireframe. |
Not getting "setting up" message under loading screen (intermittent screen). |
'+' icon used for downloading VC is occupying three dots ellipses of last VC. |
The face authentication button is not as per the theme color. |
A page from wireframe is missing in the application. |
On 'Received Card' screen expanded view of VC is not working. |
The successful QR code login audit is not matching the wireframe. |
There are few elements still in color, orange in the purple theme. |
The app is not aligned properly with the smaller display phone. |
Share button is not aligned properly in iOS and Android. |
"It is necessary" text in consent screen is getting overlapped with page slider in smaller devices. |
Try again button is not aligned properly upon change language to Tamil (when no internet connection). |
Intermittent: Getting double toaster message on home screen. |
Capture button text is not getting displayed completely. |
In the connecting page user is getting some orange color box. |
The error pop-up is not user friendly and not matching the UI. |
The Download pop-up should stay longer. |
Time stamp should be removed in OTP screen once it is expired. |
Repositories | Tags Released |
Inji |
config |
Repositories | Tags Released |
Inji |
Mimoto |
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 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 Wallet
testing scope revolves around the following flows:
Biometric Unlock
Passcode Unlock
VC download with VID
Renaming VC / Edit tag for VID
Normal VC sharing with VID
Online and Offine mode sharing
Face Auth on Resident's phone with VID
Multi language support
Wallet binding
QR code Login
Persona based approach has been adopted to perform the IV&V(Independent Verification and Validation) by simulating the 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 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.
Below are the test metrics for Inji Wallet by performing functional testing using mockMDS
and mockABIS
. 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 inline 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.
Test Rate: 100% with Pass Rate : 88%
Here is the detailed breakdown of metrics:
Total Test cases: 185
Passed: 177
Failed: 8
Skipped: 0
Total Test cases: 174
Passed: 142
Failed: 32
Skipped: 0
Below section provides details on API test metrics by executing MOSIP functional automation Framework. The 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.
Test Rate: 100% with Pass Rate : 97%
End-to-end flows are a set of stateful test cases that expects the results across multiple modules. The test does not cover the intermediary stages, rather concentrates on the end result for a given data. The test covers both negative scenarios and positive scenarios with real world scenarios. Below are the end-to-end scenarios test metrics by executing MOSIP Automation Framework.
Test Rate: 100% with Pass Rate: 75%
Below are the test metrics by performing VC Sharing functionality on various device combinations.
Test Rate: 100% with Pass Rate : 83%
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
Link for the detailed test report.
Release Name: Inji 0.11.0
Upgrade From: Inji 0.10.0
Support: Support Release
Release Date: 23rd February, 2024
We are excited to announce the first independent release of Mimoto, officially named version 0.11.0. This release is built upon Inji 0.10.0 and primarily focuses on the following:
Onboarding a new VC Issuer
Mimoto-Issuer onfiguration changes
Please find below the details for the 0.11.0 release:
Onboarding a new VC Issuer: For each new VC Issuer, Mimoto must be onboarded as an OIDC client to . To know more, refer .
Mimoto-Issuer configuration changes: Changes to authentication and well-known configuration details will be included in the mimoto-issuers configuration. To know more, refer .
Total
Passed
Failed
Skipped
359
319
40
0
Total
Passed
Failed
Skipped
37
36
1
0
Total
Passed
Failed
Skipped
84
63
21
0
Total
Passed
Failed
Skipped
192
160
32
0
Repositories | Tags Released |
mimoto |
mosip-config |