EUDI Wallet Test Report
Home > Tag > US RAPDCAPISD
Application version
Version 2026.05.37-Demo
Report generated 20-05-2026 17:01:27

Tag: US RAPDCAPISD

22 tests |

Overview

Test Outcomes

Test Performance

Functional Coverage Overview

Features

Key Statistics

Number of Scenarios 20
Total Number of Test Cases 22
Number of Manual Test Cases 22
Tests Started May 20, 2026 11:33:54
Tests Finished May 20, 2026 12:00:45
Total Duration 26m 50s
Fastest Test 16s
Slowest Test 44s
Average Execution Time 26s
Total Execution Time 9m 53s

Functional Coverage Details

Features

Feature Scenarios StepsText Test Cases % Pass Result Coverage
Android > digital credential API attestation presentation 57 > remote attestation presentation with digital credentials API on android same device 235 > Present Digital Attestations via Browser using EUDI Wallet on Same Device 13 Given the user is on the Relying Party service page When the user initiates the wallet verification flow Then a presentation request is initiated by the Relying Party Given a presentation request has been initiated When the browser processes the Digital Credentials API invocation Then the user is prompted to grant permission Given the browser displays a permission prompt When the user grants permission Then the Operating System starts searching for suitable attestations Given the Operating System searches installed Wallet Units When suitable attestations matching the request exist Then the browser displays a selector interface with the matching attestations Given the Operating System searches installed Wallet Units When no suitable attestations match the request Then the user is notified and the process is terminated Given matching attestations are displayed in the selector interface When the user views the attestation list Then each attestation displays credential type, and wallet name Given multiple Wallet Units contain suitable attestations When the selector interface is displayed Then each attestation indicates which Wallet Unit holds it Given the selector interface displays suitable attestations When the user selects one attestation Then the corresponding Wallet Unit is automatically invoked Given the Wallet Unit is opened after attestation selection When the presentation request screen is shown Then the requested attestations and related attributes are displayed Given the presentation request screen is displayed in the Wallet When the user provides consent to share selected attributes Then the Wallet requests PIN authentication Given the Wallet requests PIN authentication When the user enters a valid six-digit PIN Then the attestation is presented successfully Given the attestation has been presented to the Relying Party When the Relying Party validates the attestation successfully Then a verification confirmation is displayed in the browser Given the attestation has been presented to the Relying Party When the Relying Party fails to validate the attestation Then an error message is displayed and retry is allowed 13 100%
Ios > digital credential API attestation presentation 57 > remote attestation presentation with digital credentials API same device 322 > Present Digital Attestations via Browser using EUDI Wallet on Same Device 9 Given the user is on the Relying Party service page When the user initiates the wallet verification flow Then a presentation request flow is initiated Given a presentation request flow has been initiated When the Desktop browser invokes the Digital Credentials API Then the user is not prompted to grant permission Given the mobile device has received a presentation request When no installed Wallet Unit contains suitable attestations Then the user is notified and the process is terminated Given the mobile device has received a presentation request When the system identifies one or more suitable attestations Then the user sees an extension of the Wallet open automatically Given the extension of the Wallet is open When the presentation request screen is shown Then the requesting Relying Party and the requested attestations and related attributes are displayed Given the presentation request screen is displayed in the Wallet When the user consents to share attributes and enters a valid six-digit PIN Then the attestation is presented successfully Given the Wallet requests PIN authentication When the user enters an incorrect six-digit PIN Then an authentication error is displayed Given the attestation has been presented to the Relying Party When the Relying Party validates the attestation successfully Then a verification confirmation is displayed in the browser Given the attestation has been presented to the Relying Party When the Relying Party fails to validate the attestation Then an error message is displayed and retry is allowed 9 100%

Key Statistics

Number of Scenarios 20 Total Duration 26m 50s
Total Number of Test Cases 22 Fastest Test 16s
Number of Manual Test Cases 22 Slowest Test 44s
Tests Started May 20, 2026 11:33:54 Average Execution Time 26s
Tests Finished May 20, 2026 12:00:45 Total Execution Time 9m 53s

Automated Scenarios

No automated tests were executed

Manual Tests

## Scenario Context Steps StepsText Result
Present Digital Attestations via Browser using EUDI Wallet on Same Device User initiates verification from browser 3 Given the user is on the Relying Party service page When the user initiates the wallet verification flow Then a presentation request is initiated by the Relying Party SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device Browser requests permission for Digital Credentials API 3 Given a presentation request has been initiated When the browser processes the Digital Credentials API invocation Then the user is prompted to grant permission SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device User grants Digital Credentials API permission 3 Given the browser displays a permission prompt When the user grants permission Then the Operating System starts searching for suitable attestations SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device Matching attestations are found on the device 3 Given the Operating System searches installed Wallet Units When suitable attestations matching the request exist Then the browser displays a selector interface with the matching attestations SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device No matching attestations found 3 Given the Operating System searches installed Wallet Units When no suitable attestations match the request Then the user is notified and the process is terminated SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device Attestation details are displayed in selector 3 Given matching attestations are displayed in the selector interface When the user views the attestation list Then each attestation displays credential type, and wallet name SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device Selector indicates Wallet Unit ownership 3 Given multiple Wallet Units contain suitable attestations When the selector interface is displayed Then each attestation indicates which Wallet Unit holds it SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device User selects an attestation and Wallet opens 3 Given the selector interface displays suitable attestations When the user selects one attestation Then the corresponding Wallet Unit is automatically invoked SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device Wallet verifies Relying Party identity and origin 3 Given the Wallet Unit is opened after attestation selection When the presentation request screen is shown Then the requested attestations and related attributes are displayed SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device User consents and proceeds to authentication 3 Given the presentation request screen is displayed in the Wallet When the user provides consent to share selected attributes Then the Wallet requests PIN authentication SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device Successful authentication and presentation 3 Given the Wallet requests PIN authentication When the user enters a valid six-digit PIN Then the attestation is presented successfully SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device Relying Party verifies attestation successfully 3 Given the attestation has been presented to the Relying Party When the Relying Party validates the attestation successfully Then a verification confirmation is displayed in the browser SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device Relying Party verification fails 3 Given the attestation has been presented to the Relying Party When the Relying Party fails to validate the attestation Then an error message is displayed and retry is allowed SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device User initiates verification from browser on their mobile device 3 Given the user is on the Relying Party service page When the user initiates the wallet verification flow Then a presentation request flow is initiated SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device Browser does not request permission for Digital Credentials API 3 Given a presentation request flow has been initiated When the Desktop browser invokes the Digital Credentials API Then the user is not prompted to grant permission SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device No matching attestations on mobile device 3 Given the mobile device has received a presentation request When no installed Wallet Unit contains suitable attestations Then the user is notified and the process is terminated SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device Attestation identifying information is displayed 3 Given the mobile device has received a presentation request When the system identifies one or more suitable attestations Then the user sees an extension of the Wallet open automatically SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device Wallet displays requested attestations and attributes 3 Given the extension of the Wallet is open When the presentation request screen is shown Then the requesting Relying Party and the requested attestations and related attributes are displayed SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device Successful consent and authentication 3 Given the presentation request screen is displayed in the Wallet When the user consents to share attributes and enters a valid six-digit PIN Then the attestation is presented successfully SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device Invalid PIN during cross-device presentation 3 Given the Wallet requests PIN authentication When the user enters an incorrect six-digit PIN Then an authentication error is displayed SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device Relying Party verifies attestation successfully 3 Given the attestation has been presented to the Relying Party When the Relying Party validates the attestation successfully Then a verification confirmation is displayed in the browser SUCCESS
Present Digital Attestations via Browser using EUDI Wallet on Same Device Relying Party verification fails 3 Given the attestation has been presented to the Relying Party When the Relying Party fails to validate the attestation Then an error message is displayed and retry is allowed SUCCESS
Serenity BDD version 4.2.22