Testing Scope

The scope of testing is to verify fitment to the specification from the perspective of

• Functionality

• Deployability

• Configurability

• Customizability

Verification is performed not only from the end user perspective but also from the System Integrator (SI) point of view. Hence Configurability and Extensibility of the software are also assessed. This ensures the readiness of software for use in multiple countries. Since MOSIP is an “API First” product platform.

Testing scope has been focused on the below features:

• Inji certify Docker compose testing(VCI segregations)

• Docker compose testing for Insurance and Mock ID use case

• Inji certify - Insurance use case using namespace

• Inji certify - Mock IDA use case using namespace

• Inji certify - MOSIP ID use case using namespace(verified using idrepo UIN/VIDs only)

• Integration with INJI Web

Swaggers links

https://injicertify-mosipid.qa-inji.mosip.net/v1/certify/swagger-ui/index.html#/

https://injicertify-mock.qa-inji.mosip.net/v1/certify/swagger-ui/index.html#/

https://injicertify-insurance.qa-inji.mosip.net/v1/certify/swagger-ui/index.html#/

Test Approach

Persona based approach has been adopted to perform the IV&V, by simulating test scenarios that resemble a real-time implementation.

A Persona is a fictional character/user profile created to represent a user type that might use a product/or a service in a similar way. Persona based testing is a software testing technique that puts software testers in the customer's shoes, assesses their needs from the software, and thereby determines use cases/scenarios that the customers will execute. The persona's needs may be addressed through any of the following.

• Functionality

• Deployability

• Configurability

• Customizability

The verification methods may differ based on how the need was addressed.

Verified configuration

Verification is performed on configurations as mentioned below

• Default configuration

  • English

Feature Health

Test execution statistics

Functional test results

Below are the test metrics by performing functional testing. 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 configurations. The testing cycle included the simulation of multiple identity schema and respective UI schema configurations.

Detailed Test metrics

Below are the detailed test metrics by performing manual/automation testing. The project metrics are derived from Defect density, Test coverage, Test execution coverage, test tracking, and efficiency.

The various metrics that assist in test tracking and efficiency are as follows:

• Passed Test Cases Coverage: It measures the percentage of passed test cases. (Number of passed tests / Total number of tests executed) x 100

• Failed Test Case Coverage: It measures the percentage of all the failed test cases. (Number of failed tests / Total number of test cases executed) x 100

Stories Tested

API + Docker compose testing

Tested with Components

Browser Versions Used For Testing

The Github link for the xls file is here.

Release Name: Inji Certify 0.9.0

Support: Developer Release

Release Date: 22nd August, 2024

Overview

Inji Certify continues to innovate in the realm of verifiable credentials (VCs) with the release of version 0.9.0. This update introduces significant enhancements, improving the platform's flexibility, scalability, and ease of use. Designed to empower organizations to issue and manage VCs securely, Inji Certify 0.9.0 further strengthens its integration capabilities. With these new features, users can expect a more streamlined experience in credential issuance and management, ensuring compliance with industry standards while offering robust data control. Support for various plugins and microservices, allowing organizations to tailor the platform to their specific needs and existing systems.

New Features in Version 0.9.0:

1. Enhanced Verifiable Credential Issuance:

   • National Identity Plugin: Integration with MOSIP for identity verification, enabling secure and reliable credential issuance.

   • Insurance Plugin: Seamless integration with Sunbird services to facilitate the issuance and management of VCs.

   • Mock IDA Plugin: Introduced for testing and development purposes, providing a controlled environment to simulate credential issuance.

2. Segregation of eSignet VCI Component:

   • The eSignet VCI component is now separated from eSignet services and migrated to the core Inji Certify system, optimizing functionality and scalability, and allowing for more modular deployments.

3. Support for VC Formats:

   • JSON-LD Compliance: Ensures adherence to W3C VC v1.1 standards promoting interoperability and industry compliance.

   • Credential Schema Configuration: Issuers can now configure custom credential schemas for various types of certificates, enhancing flexibility in credential design and issuance.

4. Ease of Installation and Deployment:

   • Docker-compose Support: Quick and easy deployment using Docker-compose, allowing for rapid local setup and scaling. Click to learn more!

5. Inji-config Repository:

   • Configuration Management: Introduction of the inji-config repository to maintain all configurations related to the Inji Certify, streamlining configuration management and consistency across deployments.

6. Support for Mock and Insurance Credential Use Cases:

   • Mock Credential Use Case: Provides a predefined setup for mock credentials, useful for testing and development.

   • Insurance Credential Use Case: A specialized setup for issuing insurance-related credentials, offering a targeted solution for the insurance sector.

Testing and Integration Note:

1. Setup: Configure InjiWeb and Mimoto in your local environment.

2. Issuer Configuration: Add an issuer in Mimoto with the authorization_endpoint, credential_endpoint and .well-known properties pointing to the installed eSignet and Certify services.

3. Private Key Addition: Insert the private key from the OIDC client created in eSignet into the .p12 file in Mimoto.

4. Verification: The configured issuer should now appear on the InjiWeb homepage, allowing you to download the credential.

5. Plugin Compatibility: For this release, ensure that the eSignet image version in Docker Compose (currently 1.4.0) is consistent with the Mock plugin dependencies in Artifactory. This alignment is crucial due to shared Redis cache dependencies resolving serialization issues.

Repositories: Released/Dependent

Compatible Modules:

The following table outlines the tested and certified compatibility of Inji Certify 0.9.0 with other modules.

Known Issues

Bug Fixes

Below is the list of fixes as part of the 0.9.0 release:

Conclusion:

Inji Certify 0.9.0 represents a significant milestone in the evolution of the module offering users enhanced capabilities for issuing, managing, and integrating verifiable credentials. With a focus on scalability, interoperability, and ease of use, this release empowers organizations to leverage the full potential of VCs securely and efficiently.

Documentation