For the complete documentation index, see llms.txt. This page is also available as Markdown.

Test Report

Introduction

The scope of testing is to verify fitment to the specification from the perspective of Functionality, Configurability and 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 are also assessed. This ensures the readiness of the software for use in multiple countries and diverse identity ecosystems.

Overview and Scope

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, school and Farmer use case

  • Preauthcode

  • Mdoc mdl format

Test Approach

The Functional verification of Inji Certify is performed to ensure alignment with product specifications, business requirements, and the OpenID for Verifiable Credential Issuance flow. The validation covers credential generation, signing, and issuance of W3C-compliant Verifiable Credentials across supported formats such as JSON-LD and SD-JWT, along with integration of issuer configurations, credential schemas, data provider plugins, and dependent services. The testing adopts a use-case-based strategy, validating issuance workflows for configured certificate types and data sources to ensure functional stability, data integrity, interoperability, configurability, and readiness for deployment in diverse credential ecosystems.

  • Functionality through automation

Test Organization

Table: Test Organization

Name
Functional Role
Responsibilities

Nitin Hegde

QA Lead

Verifying the functionality, Automation scenarios development and report preparation

Chaitanya K

QA Manager

Overviewing the test execution and review of the report.

Test Planning

  • Data Readiness: Validate the availability of all services along with configured identity schemas (UIN/VID) to authentication flows.

Test Environment

Table: Test Environment

Test Environments

Images (qainji env)

injistackqa/inji-certify-with-plugins:1.0.x

injistackqa/inji-web:develop

injistackqa/mimoto:1.0.x

injistackqa/inji-verify-service:1.0.x

injistackqa/inji-verify-ui:1.0.x

Nginx

mosipid/softhsm:v2

mosipid/kernel-config-server:1.3.0

mosipqa/postgres-init:develop

injistackqa/apitest-inji-certify:1.0.x

Images (released env)

mosipid/credential-service:1.3.0

mosipid/data-share-service:1.3.0

mosipid/data-share-service:1.3.0-beta.2 - Injiweb

mosipid/digital-card-service:1.3.0

mosipid/esignet-with-plugins:1.6.2

mosipid/mock-identity-system:0.11.2

sunbird-rc/sunbird-rc-core:v1.0.0

sunbird-rc/sunbird-rc-credential-schema:v2.0.0-rc3

sunbird-rc/sunbird-rc-credentials-service:v2.0.0-rc3

sunbird-rc/sunbird-rc-identity-service:v2.0.0-rc3

Test Execution Report

Test case execution summary

Automation Test Execution was completed in qainji env achieving a 100% execution rate for all planned scenarios. The testing validated core functionalities with a high pass rate, while identified issues on both platforms have been logged for defect resolution.

Automation Result

  • Sunbird use case

Total
Passed
Failed
Ignored
Known issues

515

48

0

447

20

Test Rate: 100%, With Pass Rate: 100% and Fail Rate: 0%

  • Mock Use case

Total
Passed
Failed
Ignored
Known issues

515

21

0

474

20

Test Rate: 100%, With Pass Rate: 100% and Fail Rate: 0%

  • Mock (Data provider) Land registry Use case

Total
Passed
Failed
Ignored
Known issues

515

249

0

246

20

Test Rate: 100%, With Pass Rate: 100% and Fail Rate: 0%

  • MosipId Use case

Total
Passed
Failed
Ignored
Known issues

515

92

0

403

20

Test Rate: 100%, With Pass Rate: 100% and Fail Rate: 0%

  • Preauth code(academic) Use case

Total
Passed
Failed
Ignored
Known issues

515

35

0

460

20

Test Rate: 100%, With Pass Rate: 100% and Fail Rate: 0%

  • Mdoc mdl Use case

Total
Passed
Failed
Ignored
Known issues

515

18

0

477

20

Test Rate: 100%, With Pass Rate: 100% and Fail Rate: 0%

Defect Metrics

Defect Metrics for the Release 1.0.0-alpha.1

The following table depicts only the bugs which are found and not addressed in the current release.

Table: Defect Metrics for the Release

Blocker
Critical
Major
Minor
Total

0

1

0

0

1

Conclusion

This section summarizes the key findings of test execution. It also provides a final QA recommendation on the build's readiness for release. The functional verification for Inji Certify release version 1.0.0-alpha.1 has been successfully completed. The testing cycle achieved a 100% execution rate with a 100% pass rate across a total of 515 automation test cases.

While there are 1 Critical open defects and as known issues, there are zero blocker defects that are open. Testing has demonstrated functional stability and data integrity consistent with product specifications.

QA Approval

The build has successfully met the defined exit criteria and is recommended for release. The approval is based on the following satisfied conditions:

  • Test Case Execution Completion: 100% of planned scenarios executed.

  • Defect Status: No Blocker defects remain open.

  • Documentation Sign-off: Reports are finalized.

  • Test Environment Stability: The test environment remained stable throughout the execution cycle.

Table: Report is signed off details

Name
Functional Role
Responsibilities

Chaitanya K

QA Manager

Appendix

This includes additional reference information for the report. It contains a history of document versions and a list of acronyms and their meanings.

Appendix A: Versions

Version
Date
Author
Reviewers

V1.0

28/07/2026

Nitin Hegde

Chaitanya K

Appendix B: Acronyms

Acronym
Literal Translation

MOSIP

Modular Open-Source Identity Platform

UIN

Unique Identification Number

VID

Virtual Identification

SVG

Scalable Vector Graphics

SD-JWT

Selective Disclosure - JSON Web Token

VC

Verifiable Credentials

OpenID4VC

OpenID for Verifiable Credentials

Refer to the github link for more on reports here.

Last updated

Was this helpful?