Test Report
Scope
The scope of testing revolved around verifying the compliance of the product as per the specifications published by MOSIP using the below devices:
The Windows Compliance tool kit was tested with the below specifications:
ABIS (Automated Biometric Identification System) Specifications was tested with Fingerprint, Iris and Face modalities as per MOSIP ABIS API specifications.
Secure Biometric Interface (SBI)
Registration devices for Iris, Face and Fingerprint
Authentication devices for Iris, Face and Fingerprint
Biometric SDK
Quality Check
Match
Extraction
Conversion
The Android Compliance tool kit app v1.2.0 was tested with the below specifications:
Secure Biometric Interface (SBI)
Registration devices for Iris, Face and Fingerprint
Authentication devices for Iris, Face and Fingerprint
Test Execution Statistics
ABIS Testing
MOSIP interfaces with an Automated Biometric Identification System (ABIS) to perform de-duplication of a resident's biometric data. A country may use multiple ABISs for the same biometric data and evaluate the best ABIS based on de-duplication quality. ABIS is used for 1:N de-duplication. For 1:1 authentication, Biometric SDK is used. MOSIP does not recommend using an ABIS for 1:1 authentication.
Test cases have been tested with MOSIP mock ABIS for compliance with the MOSIP specifications across 29 test cases.
Scenarios | Mock ABIS |
Total | 28 |
Passed | 27 |
Pending | 0 |
Failed | 0 |
NA | 1 |
Test Rate (%) | 100% |
Pass Rate (%) | 100% |
Out of scope: Real ABIS testing in CTK 1.2.0
SBI Testing
The Secure Biometric Interface (SBI) is used to interface with the biometric devices. The Compliance tool kit was tested to ensure that the interface built by the device provider is following the specifications and security rules defined in the SBI spec. The device hardware security features are not tested as a part of Compliance tool kit.
For Android Authentication Devices using MOSIP's Android mock SBI
The Android CTK app v1.2.0 with MOSIP Android Mock SBI has been tested for compliance with the specifications across 55 test cases. Test cases specific to quality and user interactions have been tested with MOSIP Android mock SBI.
Scenarios | Finger | Iris | Face |
Total | 19 | 21 | 15 |
Passed | 19 | 19 | 15 |
Pending | 0 | 0 | 0 |
Failed | 0 | 0 | 0 |
Test Rate (%) | 100% | 100% | 100% |
Pass Rate (%) | 100% | 90% | 100% |
For Android Registration Devices using MOSIP's Android mock SBI
The Android CTK app v1.2.0 with MOSIP Android Mock SBI has been tested for compliance with the specifications across 64 test cases. Test cases specific to quality and user interactions have been tested with MOSIP Android mock SBI and real registration face SBI.
Scenarios | Finger | Iris | Face |
Total | 29 | 18 | 17 |
Passed | 29 | 18 | 17 |
Pending | 0 | 0 | 0 |
Failed | 0 | 0 | 0 |
NA | 1 | ||
Test Rate (%) | 100% | 100% | 100% |
Pass Rate (%) | 100% | 100% | 100% |
For Windows Authentication Devices using MOSIP's windows mock SBI
The Windows CTK 1.2.0 with MOSIP windows Mock SBI has been tested for compliance with the specifications across 55 authentication spec test cases.
Scenarios | Finger | Iris | Face |
Total | 19 | 21 | 15 |
Passed | 19 | 21 | 15 |
Pending | 0 | 0 | 0 |
Failed | 0 | 0 | 0 |
Test Rate (%) | 100% | 100% | 100% |
Pass Rate (%) | 100% | 100% | 100% |
For Windows Registration Devices using MOSIP's windows mock SBI
The Windows CTK 1.2.0 with MOSIP windows Mock SBI has been tested for compliance with the specifications across 76 registration spec test cases.
Scenarios | Finger | Iris | Face |
Total | 35 | 21 | 20 |
Passed | 35 | 21 | 20 |
Pending | 0 | 0 | 0 |
Failed | 0 | 0 | 0 |
Test Rate (%) | 100% | 100% | 100% |
Pass Rate (%) | 100% | 100% | 100% |
Out of scope: Real devices testing on Windows and android CTK.
SDK Testing
The SDK implementation has been tested to support quality check, match, extraction, and conversion of biometrics. Test cases have been tested with MOSIP mock SDK.
Scenarios | With Mock SDK |
Total | 65 |
Passed | 65 |
Pending | 0 |
Failed | 1 |
Test Rate (%) | 100% |
Pass Rate (%) | 100% |
Out of scope: Segmentation testing and Real SDK testing.
Known Issues
After login to CTK Android app, the previous browser tab is not killed. Workaround: Once the popup appears, the user can manually close the tabs.
Newly registered user not landing on the CTK android home page (an intermittent issue observed on Samsung A03 mobile device).
In CTK Android app, UI elements are overlapping with each other (issue observed on Samsung A03 and Oneplus nord AC2001 mobiles because of screen size).
Add project/ collection takes empty spaces as name (validation is missing).
In Android CTK -
Encryption Keybutton is not appearing for Auth projects (Workaround: Partners can download theEncryption Keyfrom the web application.With Android mock MDS,
SBI1067andSBI1068testcases for Auth Iris ISO validation failing (issue with Android mock MDS).
Docker version (required for Compliance Tool Kit)
mosipqa/compliance-toolkit-service:1.2.0
mosipqa/compliance-toolkit-ui:1.2.0
mosipqa/postgres-init:1.2.0.1
mosipid/postgres-init:1.2.0.1-B2
mosipid/config-server:1.1.2
mosipid/kernel-auditmanager-service:1.2.0.1-B1
mosipid/kernel-auth-service:1.2.0.1-B2
mosipqa/authentication-service:1.2.0.1
mosipid/kernel-keymanager-service:1.2.0.1-B2
mosipid/keycloak-init:1.2.0.1-B2
mosipqa/partner-management-service:1.2.0.1
mosipqa/partner-onboarder:develop
mosipid/kernel-notification-service:1.2.0.1-B1
mosipid/mosip-keycloak:16.1.1-debian-10-r85
Sonar Report
MOSIP CTK Service
Last updated
