Release Name: Inji Verify 0.8.0

Support: Developer Release

Release Date: 8th May, 2024

Overview

We are excited to announce the release of Inji Verify version 0.8.0! This release introduces several new features like scanning QR code, uploading QR code, and error handling aimed at improving the user experience and functionality of the verification portal. Below are the key highlights of this release:

New Features:

1. QR Code Scanning: Users can now scan QR codes directly from their device cameras using the built-in scanning feature. This allows for quick and seamless verification of Verifiable Credentials without the need for manual data entry.

2. QR Code Upload: In addition to QR code scanning, users have the option to upload QR code files from their devices for verification. This provides flexibility for users who may have QR codes saved as digital files.

3. Error Handling: Error messages and prompts have been added to provide clearer guidance to users in case of issues such as unsupported QR code formats, unreadable QR codes, or scan session timeouts.

Scan Feature QR Code Compatibility:

• QR code versions supported for the scan feature range from v22 and below.

Camera Resolution Requirement:

• The device's front or web camera resolution must exceed 8 megapixels.

• Cameras should be used in well-lit environments without filters, ensuring proper alignment for optimal scanning.

Upload Feature QR Code Compatibility:

• QR code versions supported for the upload feature range from v32 and below.

Repositories: Released/Dependent

Known Issues

Documentation

• Feature Documentation

• User Guide

• QA Report

Testing Scope

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

● 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.

Testing scope has been focused around the below features:

● Inji Verify Home page

● Verify Scan Feature

● Verify Upload Feature

Below are the combinations that QA verified and Certified Inji Verify:

Upload feature Verification:

1. Windows using Edge, Firefox and Chrome browsers.

2. MAC using Safari browser.

Scan functionality Verification:

1. MAC (Laptop) with a front camera of 2 megapixel and Safari browser.

2. Mobile phone Android with front camera 16 megapixel using browsers Chrome.

3. Mobile phone Android with front camera 8 megapixel using browsers Chrome.

4. iPhone with 12 megapixel front camera using Safari browser.

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 needs may be addressed through any of the following functions.

● Functionality

● Deployability

● Configurability

● Customizability

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

Verified configuration

Verification is performed on various configurations as mentioned below

● Default configuration - with 1 language which is 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.

Here is the detailed breakdown of metrics for each module:

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.

Inji-Verify 0.8.0 - Verification - Report