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

Test Report

Introduction

The eSignet testing scope includes the validation of authentication, authorization, identity verification, consent management, token generation, OpenID Connect (OIDC) flows, partner integration, and user onboarding workflows across supported authentication methods and external identity systems. eSignet is a modular and standards-based digital identity authentication solution that supports secure and configurable login journeys using OTP, biometrics, wallet-based authentication, and trusted identity providers.

Overview and Scope

The scope of testing defines the boundaries, functionalities, and features that will be tested for the eSignet platform. This ensures comprehensive validation of critical authentication, authorization, consent, and identity verification workflows while clearly identifying what is included and excluded from testing.

Functional Features: Signup Portal with Mock Plugin, MOSIP ID – QABASE, and MOSIP ID – CRE, Login with OTP using Phone Number, UIN/VID, and Email, Login with Password Authentication, Forgot Password Functionality, Login with Biometrics Authentication, Login with KBI (Knowledge-Based Identification), Identity Verification Process for L1 and L2 Flows, Sunbird Plugin Integration, DPoP (Demonstration of Proof-of-Possession) Validation, PAR (Pushed Authorization Request) Validation, Dynamic Signup Schema Validation, Deployment Testing for eSignet and Signup Modules, FAPI 2.0 Compliance Validation, Docker Compose Compatibility Testing across Windows, macOS, and Linux Operating Systems, OIDC Authorization Flow with PKCE, Token Generation & Validation, Consent Management, Claims Management, User info API Validation, Session Management, API Security Validation, Logout Flow, Audit Logging, Verified Claims Support, and Multi-factor Authentication workflows.

Cross-Platform Support

  • Multilingual: eSignet with 6 languages (English/Khmer/Hindi/Kannada/Arabic/Tamil)

  • Multilingual: Signup with 2 languages (English/Khmer)

  • Multi-Browser: Edge, Firefox, Chrome

  • Devices: Windows, Mac, Tablet, Mobile

  • Testing Types: Sanity, Regression Testing and Integration Testing

  • Cross-browser and cross-device compatibility testing

Test Approach

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

  • Functionality

  • Combination

  • UI Automation

  • API Automation

  • Library verification

Test Organization

Table: Test Organization

Name
Functional Role
Responsibilities

Ragini Krishnamurthy

Manager

Defining test strategy, managing QA activities, and ensuring overall product quality.

Chandra Sekhar

Lead

Leading the test team, planning and executing tests, and ensuring timely delivery of quality results.

Prathmesh Jadhav Rohith Goud

Test engineers

Designing and executing test cases, performing functional and regression testing, validating eSignet authentication and signup workflows, verifying login and identity verification functionalities, logging and tracking defects, validating fixes, and ensuring overall application quality, security, and compliance standards.

Test Planning

This Test Plan outlines the testing approach, scope, resources, and schedule for the eSignet platform and Signup modules. The objective is to ensure that all functional, integration, security, and non-functional requirements are validated with high quality before release.

  • Validate end-to-end functionality of eSignet authentication, authorization, and signup workflows.

  • Ensure system stability across supported browsers, operating systems, plugins, and environments.

  • Verify integrations with dependent systems, identity providers, and authentication services.

  • Validate OIDC, DPoP, PAR, and FAPI 2.0 compliance workflows.

  • Identify and mitigate risks early through functional, regression, integration, and deployment testing.

  • Ensure compatibility of Docker Compose setup across Windows, macOS, and Linux operating systems.

  • Validate identity verification workflows for L1 and L2 authentication flows.

  • Verify secure login mechanisms including OTP, Password, Biometrics, and KBI authentication methods.

Sanity Scenarios Verified

Sanity testing will be performed to ensure basic application stability before detailed test execution. The following high-level sanity scenarios will be verified:

  • Application accessibility and successful login across supported authentication methods and environments.

  • Signup portal accessibility and successful user registration using Mock plugin and MOSIP ID integrations.

  • Login validation using OTP (Phone Number, UIN/VID, and Email).

  • Login validation using Password authentication.

  • Forgot Password workflow validation.

  • Basic biometric authentication validation using Mock ID and MOSIP ID.

  • KBI (Knowledge-Based Identification) login validation.

  • Identity verification workflow validation for L1 and L2 flows.

Only upon successful completion of sanity testing will the build be accepted for full regression and integration testing.

Test Environment

Table: Test Environment -images

Tested with Components on esqa2 env

docker.io/mosipqa/apitest-esignet-signup:1.4.x

docker.io/mosipqa/apitest-esignet:1.8.x

docker.io/mosipqa/esignet-with-plugins:1.8.x

docker.io/mosipqa/mock-identity-system:0.13.x

docker.io/mosipqa/mock-relying-party-service:0.13.x

docker.io/mosipid/captcha-validation-service:0.1.0-beta.1

docker.io/mosipid/config-server:1.1.2

docker.io/mosipid/kafka:3.2.1-debian-11-r9

docker.io/mosipid/keycloak-init:1.2.0.2

docker.io/mosipid/kibana:7.17.2-debian-10-r0

docker.io/mosipid/minio-client-util

docker.io/mosipid/minio-client-util:latest

docker.io/mosipid/minio:2022.2.7-debian-10-r0

docker.io/mosipid/mock-smtp:1.0.0

docker.io/mosipid/mosip-artemis-keycloak:1.2.0.1

docker.io/mosipid/os-shell:12-debian-12-r46

docker.io/mosipid/partner-management-service:1.2.2.3

docker.io/mosipid/policy-management-service:1.2.2.3

docker.io/mosipid/postgres-init:1.2.0.1

docker.io/mosipid/postgresql:14.2.0-debian-10-r70

docker.io/mosipid/redis:7.0.5-debian-11-r25

docker.io/mosipid/softhsm:v2

docker.io/mosipid/zookeeper:3.8.0-debian-11-r30

docker.io/mosipint/elasticsearch:7.17.2-debian-10-r4

docker.io/mosipqa/mock-relying-party-ui:0.13.x

docker.io/mosipqa/oidc-ui:1.8.x

docker.io/mosipqa/partner-onboarder:1.3.x-beta.2

docker.io/mosipqa/postgres-init:develop

docker.io/mosipqa/signup-ui:1.4.x

docker.io/mosipqa/signup-with-plugins:1.4.x

docker.io/mosipqa/uitest-signup:1.4.x

docker.io/mosipqa/uitest-signup:release-1.4.x

mosipid/config-server:1.1.2

mosipid/keycloak-init:1.2.0.2

mosipid/postgres-init:1.2.0.1

mosipid/softhsm:v2

mosipqa/apitest-esignet-signup:1.4.x

mosipqa/apitest-esignet:1.8.x

mosipqa/postgres-init:develop

Test Execution Report

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 languages and configurations.

Test case execution summary

The Test Case Execution Summary section provides a detailed overview of the total test cases executed across platforms, including pass, fail, and skip counts. It includes a table summarizing results and observations on execution pass rates.

Table: Test Case - UI based verification

Total
Passed
Failed
Skipped (N/A)

1341

1320

21

0

Test Rate: 100% with Pass Rate: 98.43%

Table: Test Case – API based verification (API):

Total
Passed
Failed
Skipped (N/A)

2215

2140

18

57

Test Rate: 97.43% with Pass Rate: 99.17%

Note: NA - 57 Test Cases which are descoped scenarios/not developed feature

Automation Results

This section provides a summary of the automated test execution. It shows the pass, fail, and known issues from the automated test suite.

Table: Automation Execution Result -API Testrig – mockid environment

Module
Total
Passed
Failed
Skipped (N/A)
Ignored

eSignet

1339

791

0

0

548

0

Signup

670

640

0

0

30

0

Test Rate: 100% with Pass Rate: 100%

Note: 548 test cases in esignet and 30 test cases in signup related to the MOSIP ID plug-in are currently being ignored.

Table: Automation Execution Result -API Testrig – mosipid-qabase environment

Module
Total
Passed
Failed
Skipped (N/A)
Ignored

eSignet

1339

1098

0

0

171

21

Signup

670

653

0

0

17

0

Test Rate: 100% with Pass Rate: 100%

Note: 171 test cases in esignet and 17 test cases in signup related to the mock plug-in are currently being ignored.

Table: Automation Execution Result -API Testrig – mosipid-CRE environment

Module
Total
Passed
Failed
Skipped (N/A)
Ignored

eSignet

1339

1098

32

10

171

21

Signup

670

398

60

195

17

0

Test Rate: 89.80% with Pass Rate: 94.2%

Note: Failures in esignet and signup are due to L2 flow is not supported in esignet and signup and some test cases are failing due to credential movement is taking longer time.

Note- API flow is tested through automation for both positive and negative scenarios, while test cases that are not automated are tested manually.

Table: Automation Execution Result - UI Automation

Total
Passed
Failed
Skipped (N/A)
Ignored
Known issues

17

9

0

0

0

8

Test Rate: 100% with Pass Rate: 100%

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 failed test cases. (Number of failed tests / Total number of test cases executed) x 100

Test Execution Report

Verification is performed on various configurations as mentioned below

  • Default configuration with verified configuration for 3 Lang (English/Arabic/French)

Browser compatibility evaluations

Table: Browser versions tested on desktop/laptop

Sl.No
Browser
Versions

1

Chrome

Version 147.0.7727.138

2

Firefox

Version 150.0.2 (64-bit)

3

Edge

Version 147.0.3912.72

4

Safari

Version 18.6 (20621.3.11.11.3

Feature Health

Known Issues Metrics

This section focuses on a separate category of issues that are known but not addressed in the current release. It provides a count and severity distribution for these defects across releases.

Table: Defect Metrics for the known issues

Blocker: 2 deployment bugs to be tested in v1.8.1 deployment (v1.8.0 testing is already completed).

Critical: 1 critical bug will be coming up as story in 1.8.1 release.

Sonar Report

  • esignet:

  • esignet-signup:

  • esignet-mock-service:

  • esignet-plugins(mock):

  • esignet-plugins(mosipid):

  • esignet-plugins(sunbird):

Conclusion

The eSignet application has been successfully validated in the esqa2 environment, with all critical functionalities performing as expected.

Sanity, regression, and integration testing were completed within the defined scope.

  • Based on the successful test execution and results, QA approves the build for release.

QA Approval

The build has met all the defined exit criteria and is recommended for release based on the following:

  • Test Case Execution: All planned test cases have been executed successfully.

  • Story and Defect Closure: All user stories are completed, and no critical or high-severity defects remain open.

  • Automation Reports: API-Testrig and UI automation execution reports have been reviewed and approved.

  • Documentation Sign-off: All required test and release documentation has been reviewed and signed off.

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

Table: Report is signed off details

Name
Functional Role
Responsibilities

Ragini Krishna

Manager

Defining test strategy, managing QA activities, and ensuring overall product quality.

Chandra Sekhar N

Lead

Leading the test team, planning and executing tests, and ensuring timely delivery of quality results.

Appendix

This includes additional reference information for the report. It contains a history of document versions.

Appendix A: Versions

Version
Date
Author
Reviewers

V1.0

07/05/2026

Prathmesh Jadhav

Ragini Krishna

Document History

It outlines the strategy used to ensure a comprehensive evaluation.

Version
Author
Date
Review
Affected Sections

V1.0

Prathmesh Jadhav

07/05/2026

Ragini Krishnamurthy

Refer here to get more details on reports.

Last updated

Was this helpful?