Test Report

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 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 on the following features:

  • Inji certify Docker compose testing (Data provider CSV plugin, Data provider Postgres plugin)

  • Insurance, MosipId and Mock (Issuance and Data provider (Postgres plugin)), which covered Land registry use case

  • Integration with Inji Web and Inji verify

  • ECCR1 signing of VC request

  • Did:key signing – scope from automation

  • Credential config APIs

  • DB upgrade scripts testing, Backward complatibility - from Docker setup

  • Sd_jwt format (Draft implementation)

  • Revocation feature (Draft implementation)

Test Approach

Persona based approach has been adopted to perform the IV&V, by simulating test scenarios that resemble 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.

Verified configuration

Verification is performed on configurations as mentioned below

  • Default configuration

    • English

Feature Health

Note:

For Esignet compatibility

  • eSignet 1.5.1 from released env

  • Docker compose testing – esignet from collab env by default

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. 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, and End-To-End flows across multiple configurations. The testing cycle included simulation of multiple identity schema and respective UI schema configurations.

Total
Passed

747

723

21

2

Test Rate: 99%, With Pass Rate: 97% and Fail Rate: 3%

Automation Statistics

  • Sunbird use case

Total
Passed
Failed
Ignored
Known issues

442

72

0

336

34

Test Rate: 100%, With Pass Rate: 90% and Fail Rate: 10%

  • Mock Use case

Total

Passed

Failed

Ignored

Known issues

442

50

0

358

34

Test Rate: 100%, With Pass Rate: 94.4% and Fail Rate: 5.6%

- Mock (Data provider) Landregistry Use case

Total

Passed

Failed

Ignored

Known Issues

442

209

0

199

34

Test Rate: 100%, With Pass Rate: 94.6% and Fail Rate: 5.4%

MosipId Use case

Total

Passed

Failed

Ignored

Known Issues

442

64

0

344

34

Test Rate: 100%, With Pass Rate: 85.3% and Fail Rate: 14.7%

Note: Ignored scenarios are not related to particular use cases and 34 scenarios are known issues can be tracked from INJICERT-681, INJICERT-1118, INJICERT-1176

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

Tested with Components

Module/Repo
Image
POM version
Dependent artifactID
Comments

Inji-certify-mosipid

mosipqa/inji-certify-with-plugins:0.12.x

Digital-credential-plugin - 0.5.0

Inji-certify-mock

mosipqa/inji-certify-with-plugins:0.12.x

Digital-credential-plugin - 0.5.0

Inji-certify-Insurance

mosipqa/inji-certify-with-plugins:0.12.x

Digital-credential-plugin - 0.5.0

Inji-certify- landregistry

mosipqa/inji-certify-with-plugins:0.12.x

Digital-credential-plugin - 0.5.0

Mdoc-mdl

mosipqa/inji-certify-with-plugins:0.12.x

Digital-credential-plugin - 0.5.0

Inji-config

Releasing from release-0.10.x branch

Digital-credential-plugin - 0.5.0

eSignet

eSignet-1.5.1

Keymanager

As a library

1.3.0-beta.4(1.3.0-SNAPSHOT)

Getting release with branch name release-1.3.x

Last updated

Was this helpful?