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

Tag: Ios

63 tests |

Overview

Test Outcomes

Test Performance

Functional Coverage Overview

Features

Key Statistics

Number of Scenarios 37
Total Number of Test Cases 63
Number of Manual Test Cases 43
Tests Started May 07, 2026 12:20:01
Tests Finished May 20, 2026 12:07:29
Total Duration 13d 2h 47m 27s
Fastest Test 16s
Slowest Test 7m 10s
Average Execution Time 1m 59s
Total Execution Time 2h 5m 27s

Functional Coverage Details

Features

Feature Scenarios StepsText Test Cases % Pass Result Coverage
Ios > digital credential API attestation presentation 57 > remote attestation presentation with digital credentials API cross device 323 > Cross-Device Presentation of Digital Attestations via EUDI Wallet 12 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 prompted to grant permission Given the browser displays a permission prompt When the user grants permission Then the Relying Party generates a valid presentation request Given a valid presentation request has been created When the browser processes the request Then a QR code is displayed to the user Given a QR code is displayed on the Desktop browser When the user scans the QR code with the mobile device camera Then the presentation request is transferred to the mobile device 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 from the mobile Wallet When the Relying Party validates the attestation successfully Then a verification confirmation is displayed in the Desktop browser Given the attestation has been presented from the mobile Wallet When the Relying Party fails to validate the attestation Then an error message is displayed and retry is allowed 12 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%
Ios > issuing mdoc and sd-jwt PID together at once 236 > issuing mdoc and sd-jwt PID together at once 249 > PID-07 Issuing mdoc and sd-jwt PID together at once 6 Given a wallet user navigates to the Documents section and selects to add from a list When the documents on the list are displayed Then the user can see one PID option without any format indication Given a wallet user requests PID issuance When the PID provider processes the request Then both ISO mdoc and SD-JWT VC formats are generated simultaneously Given both PID formats are generated successfully When the PID is delivered to the user's wallet Then both formats are received in a secure transaction Given both PID formats are delivered to the wallet When they are stored in the wallet Then both formats are accessible And they appear as PID mdoc and PID sd-jwt in the user interface's documents section Given the wallet has both PID formats stored When a service requests PID-based identity verification Then the wallet automatically selects the appropriate format And the user does not need to manually choose the format Given either the mdoc or sd-jwt format fails to generate When the issuance process encounters an error Then the entire PID issuance process fails And no partial PID is stored in the wallet 6 100%
Ios > re issuance of PI ds and attestation before the validity ends 52 > re issue attestation wallet initiated on user request 225 > Attestations 6 Given the user opens the Wallet application When the user authenticates successfully using a six digit PIN Then the Wallet grants access to the user Given the user opens the Wallet application When the user fails to authenticate using the six digit PIN Then the Wallet presents an error message And the user can retry the authentication Given the user is authenticated in the Wallet And an existing PID or attestation is stored in the Wallet When the user selects the re-issuance option from the Issuer details Then the wallet requests re-issuance from the issuer Given the user requested re-issuance for an existing PID or attestation When the wallet sends the re-issuance request Then the request is sent to the same issuer that issued the original PID or attestation And the request is for the same PID or attestation type Given an existing PID or attestation is already stored in the Wallet When the Wallet receives the re-issued PID or attestation of the same type Then the existing PID or attestation is replaced Given the original PID or attestation was issued in batch When the issuer re-issues the PID or attestation Then the PID or attestation is re-issued in batch 6 100%
Ios > regression tests > automated regression Tests > MDL MSO mdoc > Issuance and presentation - mDL 2 1: Successful credential issuance and presentation with selective disclosure - Python Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Python, issuance_method=from list, issue_scenario=same device, verifier=Web verifier, presentation_scenario=same device, selective_disclosure=specific attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Python And the issuance method is from list And the issuance is performed on a same device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares specific attributes And the presentation is performed on a same device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with same device for specific attributes 2: Successful credential issuance and presentation with selective disclosure - Python Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Python, issuance_method=from list, issue_scenario=same device, verifier=Web verifier, presentation_scenario=same device, selective_disclosure=all attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Python And the issuance method is from list And the issuance is performed on a same device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares all attributes And the presentation is performed on a same device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with same device for all attributes 3: Successful credential issuance and presentation with selective disclosure - Python Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Python, issuance_method=from list, issue_scenario=same device, verifier=Web verifier, presentation_scenario=cross device, selective_disclosure=specific attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Python And the issuance method is from list And the issuance is performed on a same device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares specific attributes And the presentation is performed on a cross device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with cross device for specific attributes 4: Successful credential issuance and presentation with selective disclosure - Python Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Python, issuance_method=from list, issue_scenario=same device, verifier=Web verifier, presentation_scenario=cross device, selective_disclosure=all attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Python And the issuance method is from list And the issuance is performed on a same device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares all attributes And the presentation is performed on a cross device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with cross device for all attributes 5: Successful credential issuance and presentation with selective disclosure - Python Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Python, issuance_method=credential offer, issue_scenario=same device, verifier=Web verifier, presentation_scenario=same device, selective_disclosure=specific attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Python And the issuance method is credential offer And the issuance is performed on a same device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares specific attributes And the presentation is performed on a same device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with same device for specific attributes 6: Successful credential issuance and presentation with selective disclosure - Python Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Python, issuance_method=credential offer, issue_scenario=same device, verifier=Web verifier, presentation_scenario=same device, selective_disclosure=all attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Python And the issuance method is credential offer And the issuance is performed on a same device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares all attributes And the presentation is performed on a same device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with same device for all attributes 7: Successful credential issuance and presentation with selective disclosure - Python Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Python, issuance_method=credential offer, issue_scenario=same device, verifier=Web verifier, presentation_scenario=cross device, selective_disclosure=specific attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Python And the issuance method is credential offer And the issuance is performed on a same device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares specific attributes And the presentation is performed on a cross device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with cross device for specific attributes 8: Successful credential issuance and presentation with selective disclosure - Python Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Python, issuance_method=credential offer, issue_scenario=same device, verifier=Web verifier, presentation_scenario=cross device, selective_disclosure=all attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Python And the issuance method is credential offer And the issuance is performed on a same device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares all attributes And the presentation is performed on a cross device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with cross device for all attributes 9: Successful credential issuance and presentation with selective disclosure - Python Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Python, issuance_method=credential offer, issue_scenario=cross device, verifier=Web verifier, presentation_scenario=same device, selective_disclosure=specific attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Python And the issuance method is credential offer And the issuance is performed on a cross device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares specific attributes And the presentation is performed on a same device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with same device for specific attributes 10: Successful credential issuance and presentation with selective disclosure - Python Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Python, issuance_method=credential offer, issue_scenario=cross device, verifier=Web verifier, presentation_scenario=same device, selective_disclosure=all attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Python And the issuance method is credential offer And the issuance is performed on a cross device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares all attributes And the presentation is performed on a same device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with same device for all attributes 11: Successful credential issuance and presentation with selective disclosure - Python Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Python, issuance_method=credential offer, issue_scenario=cross device, verifier=Web verifier, presentation_scenario=cross device, selective_disclosure=all attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Python And the issuance method is credential offer And the issuance is performed on a cross device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares all attributes And the presentation is performed on a cross device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with cross device for all attributes 12: Successful credential issuance and presentation with selective disclosure - Python Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Python, issuance_method=credential offer, issue_scenario=cross device, verifier=Web verifier, presentation_scenario=cross device, selective_disclosure=specific attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Python And the issuance method is credential offer And the issuance is performed on a cross device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares specific attributes And the presentation is performed on a cross device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with cross device for specific attributes 1: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Kotlin, issuance_method=credential offer, issue_scenario=same device, verifier=Web verifier, presentation_scenario=same device, selective_disclosure=specific attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Kotlin And the issuance method is credential offer And the issuance is performed on a same device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares specific attributes And the presentation is performed on a same device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with same device for specific attributes 2: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Kotlin, issuance_method=credential offer, issue_scenario=same device, verifier=Web verifier, presentation_scenario=same device, selective_disclosure=all attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Kotlin And the issuance method is credential offer And the issuance is performed on a same device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares all attributes And the presentation is performed on a same device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with same device for all attributes 3: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Kotlin, issuance_method=credential offer, issue_scenario=same device, verifier=Web verifier, presentation_scenario=cross device, selective_disclosure=specific attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Kotlin And the issuance method is credential offer And the issuance is performed on a same device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares specific attributes And the presentation is performed on a cross device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with cross device for specific attributes 4: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Kotlin, issuance_method=credential offer, issue_scenario=same device, verifier=Web verifier, presentation_scenario=cross device, selective_disclosure=all attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Kotlin And the issuance method is credential offer And the issuance is performed on a same device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares all attributes And the presentation is performed on a cross device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with cross device for all attributes 5: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Kotlin, issuance_method=credential offer, issue_scenario=cross device, verifier=Web verifier, presentation_scenario=same device, selective_disclosure=specific attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Kotlin And the issuance method is credential offer And the issuance is performed on a cross device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares specific attributes And the presentation is performed on a same device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with same device for specific attributes 6: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Kotlin, issuance_method=credential offer, issue_scenario=cross device, verifier=Web verifier, presentation_scenario=same device, selective_disclosure=all attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Kotlin And the issuance method is credential offer And the issuance is performed on a cross device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares all attributes And the presentation is performed on a same device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with same device for all attributes 7: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Kotlin, issuance_method=credential offer, issue_scenario=cross device, verifier=Web verifier, presentation_scenario=cross device, selective_disclosure=all attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Kotlin And the issuance method is credential offer And the issuance is performed on a cross device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares all attributes And the presentation is performed on a cross device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with cross device for all attributes 8: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Kotlin, issuance_method=credential offer, issue_scenario=cross device, verifier=Web verifier, presentation_scenario=cross device, selective_disclosure=specific attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Kotlin And the issuance method is credential offer And the issuance is performed on a cross device for the mDL (MSO Mdoc) When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the Web verifier And the user shares specific attributes And the presentation is performed on a cross device for the mDL (MSO Mdoc) Then the verifier verifies the credential successfully with cross device for specific attributes 20 100%
Ios > regression tests > manual regression tests > Issuance and presentation - Proximity case 2 1: Successful credential issuance and presentation with selective disclosure - Python Issuer ({issuer=Python, issuance_method=from list, issue_scenario=same device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=specific attributes (custom), status=passed}) Given user initiates credential issuance using the Python And issuance method is from list And issuance is performed on a same device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares specific attributes (custom) Then verifier verifies the credential successfully with passed 2: Successful credential issuance and presentation with selective disclosure - Python Issuer ({issuer=Python, issuance_method=from list, issue_scenario=same device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=all attributes (full), status=passed}) Given user initiates credential issuance using the Python And issuance method is from list And issuance is performed on a same device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares all attributes (full) Then verifier verifies the credential successfully with passed 3: Successful credential issuance and presentation with selective disclosure - Python Issuer ({issuer=Python, issuance_method=credential offer, issue_scenario=same device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=specific attributes (custom), status=passed}) Given user initiates credential issuance using the Python And issuance method is credential offer And issuance is performed on a same device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares specific attributes (custom) Then verifier verifies the credential successfully with passed 4: Successful credential issuance and presentation with selective disclosure - Python Issuer ({issuer=Python, issuance_method=credential offer, issue_scenario=same device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=all attributes (full), status=passed}) Given user initiates credential issuance using the Python And issuance method is credential offer And issuance is performed on a same device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares all attributes (full) Then verifier verifies the credential successfully with passed 5: Successful credential issuance and presentation with selective disclosure - Python Issuer ({issuer=Python, issuance_method=credential offer, issue_scenario=cross device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=specific attributes (custom), status=passed}) Given user initiates credential issuance using the Python And issuance method is credential offer And issuance is performed on a cross device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares specific attributes (custom) Then verifier verifies the credential successfully with passed 6: Successful credential issuance and presentation with selective disclosure - Python Issuer ({issuer=Python, issuance_method=credential offer, issue_scenario=cross device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=all attributes (full), status=passed}) Given user initiates credential issuance using the Python And issuance method is credential offer And issuance is performed on a cross device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares all attributes (full) Then verifier verifies the credential successfully with passed 1: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer ({issuer=Kotlin, issuance_method=credential offer, issue_scenario=same device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=specific attributes (custom), status=passed}) Given user initiates credential issuance using the Kotlin And issuance method is credential offer And issuance is performed on a same device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares specific attributes (custom) Then verifier verifies the credential successfully with passed 2: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer ({issuer=Kotlin, issuance_method=credential offer, issue_scenario=same device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=all attributes (full), status=passed}) Given user initiates credential issuance using the Kotlin And issuance method is credential offer And issuance is performed on a same device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares all attributes (full) Then verifier verifies the credential successfully with passed 3: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer ({issuer=Kotlin, issuance_method=credential offer, issue_scenario=cross device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=specific attributes (custom), status=passed}) Given user initiates credential issuance using the Kotlin And issuance method is credential offer And issuance is performed on a cross device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares specific attributes (custom) Then verifier verifies the credential successfully with passed 4: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer ({issuer=Kotlin, issuance_method=credential offer, issue_scenario=cross device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=all attributes (full), status=passed}) Given user initiates credential issuance using the Kotlin And issuance method is credential offer And issuance is performed on a cross device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares all attributes (full) Then verifier verifies the credential successfully with passed 10 100%

Tags

US IMASPTAO TC 06   1 US RAPDCAPISD   9 US IMASPTAO TC 02   1 US RAPDCAPICD TC 12   2 US RIAWIOUR   6 US RAPDCAPICD TC 04   1 Ios   63 US RAPDCAPICD TC 08   2 US RIAWIOUR TC 04   1 US IMASPTAO TC 05   1 US IMASPTAO TC 01   1 Execution   20 US RAPDCAPICD TC 01   2 US RAPDCAPICD   12 US RAPDCAPICD TC 09   2 US RIAWIOUR TC 01   1 US RAPDCAPICD TC 05   1 US RIAWIOUR TC 05   1 US IMASPTAO TC 04   1 Manual   33 US ETESM   10 US RAPDCAPICD TC 02   2 US RAPDCAPICD TC 10   2 US RIAWIOUR TC 02   1 US RAPDCAPICD TC 06   2 US RIAWIOUR TC 06   1 US IMASPTAO TC 03   1 US CIPSDPYMDL   20 Automated   20 Q1 2026   43 US RAPDCAPICD TC 03   1 US RAPDCAPICD TC 11   2 US IMASPTAO   6 US RIAWIOUR TC 03   1 US RAPDCAPICD TC 07   2
Manual

Key Statistics

Number of Scenarios 37 Total Duration 13d 2h 47m 27s
Total Number of Test Cases 63 Fastest Test 16s
Number of Manual Test Cases 43 Slowest Test 7m 10s
Tests Started May 07, 2026 12:20:01 Average Execution Time 1m 59s
Tests Finished May 20, 2026 12:07:29 Total Execution Time 2h 5m 27s

Automated Scenarios

## Scenario Context Steps StepsText Started Total Duration Result
Issuance and presentation - mDL Successful credential issuance and presentation with selective disclosure - Python Issuer - mDL
12 passing test cases
9 Given the user initiates a <credential> issuance using the <issuer> And the issuance method is <issuance_method> And the issuance is performed on a <issue_scenario> for the <credential> When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the <verifier> And the user shares <selective_disclosure> And the presentation is performed on a <presentation_scenario> for the <credential> Then the verifier verifies the credential successfully with <presentation_scenario> for <selective_disclosure> 12:20:01 1h 11m 1s SUCCESS
Issuance and presentation - mDL Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - mDL
8 passing test cases
9 Given the user initiates a <credential> issuance using the <issuer> And the issuance method is <issuance_method> And the issuance is performed on a <issue_scenario> for the <credential> When the issuance flow is completed Then the credential is stored in the Wallet When the user presents the credential to the <verifier> And the user shares <selective_disclosure> And the presentation is performed on a <presentation_scenario> for the <credential> Then the verifier verifies the credential successfully with <presentation_scenario> for <selective_disclosure> 13:31:03 41m 22s SUCCESS

Manual Tests

## Scenario Context Steps StepsText Result
Cross-Device Presentation of Digital Attestations via EUDI Wallet User initiates verification from Desktop browser 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
Cross-Device Presentation of Digital Attestations via EUDI Wallet Desktop browser requests 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 prompted to grant permission SUCCESS
Cross-Device Presentation of Digital Attestations via EUDI Wallet User grants permission on Desktop browser 3 Given the browser displays a permission prompt When the user grants permission Then the Relying Party generates a valid presentation request SUCCESS
Cross-Device Presentation of Digital Attestations via EUDI Wallet QR code is displayed for cross-device flow 3 Given a valid presentation request has been created When the browser processes the request Then a QR code is displayed to the user SUCCESS
Cross-Device Presentation of Digital Attestations via EUDI Wallet User scans QR code using mobile device 3 Given a QR code is displayed on the Desktop browser When the user scans the QR code with the mobile device camera Then the presentation request is transferred to the mobile device SUCCESS
Cross-Device Presentation of Digital Attestations via EUDI Wallet 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
Cross-Device Presentation of Digital Attestations via EUDI Wallet 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
Cross-Device Presentation of Digital Attestations via EUDI Wallet 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
Cross-Device Presentation of Digital Attestations via EUDI Wallet 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
Cross-Device Presentation of Digital Attestations via EUDI Wallet 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
Cross-Device Presentation of Digital Attestations via EUDI Wallet Relying Party verifies attestation successfully on Desktop 3 Given the attestation has been presented from the mobile Wallet When the Relying Party validates the attestation successfully Then a verification confirmation is displayed in the Desktop browser SUCCESS
Cross-Device Presentation of Digital Attestations via EUDI Wallet Relying Party verification fails on Desktop 3 Given the attestation has been presented from the mobile Wallet 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
PID-07 Issuing mdoc and sd-jwt PID together at once PID Request in UI 3 Given a wallet user navigates to the Documents section and selects to add from a list When the documents on the list are displayed Then the user can see one PID option without any format indication SUCCESS
PID-07 Issuing mdoc and sd-jwt PID together at once Successful Dual Format Generation 3 Given a wallet user requests PID issuance When the PID provider processes the request Then both ISO mdoc and SD-JWT VC formats are generated simultaneously SUCCESS
PID-07 Issuing mdoc and sd-jwt PID together at once Secure Delivery of Both Formats 3 Given both PID formats are generated successfully When the PID is delivered to the user's wallet Then both formats are received in a secure transaction SUCCESS
PID-07 Issuing mdoc and sd-jwt PID together at once Wallet Storage and Display 4 Given both PID formats are delivered to the wallet When they are stored in the wallet Then both formats are accessible And they appear as PID mdoc and PID sd-jwt in the user interface's documents section SUCCESS
PID-07 Issuing mdoc and sd-jwt PID together at once Automatic Format Selection by Wallet 4 Given the wallet has both PID formats stored When a service requests PID-based identity verification Then the wallet automatically selects the appropriate format And the user does not need to manually choose the format SUCCESS
PID-07 Issuing mdoc and sd-jwt PID together at once Error Handling for Generation Failure 4 Given either the mdoc or sd-jwt format fails to generate When the issuance process encounters an error Then the entire PID issuance process fails And no partial PID is stored in the wallet SUCCESS
User Authentication and Re-Issuance of PIDs/Attestations Successful authentication 3 Given the user opens the Wallet application When the user authenticates successfully using a six digit PIN Then the Wallet grants access to the user SUCCESS
User Authentication and Re-Issuance of PIDs/Attestations Unsuccessful authentication 4 Given the user opens the Wallet application When the user fails to authenticate using the six digit PIN Then the Wallet presents an error message And the user can retry the authentication SUCCESS
User Authentication and Re-Issuance of PIDs/Attestations User initiates re-issuance from an existing PID or attestation 4 Given the user is authenticated in the Wallet And an existing PID or attestation is stored in the Wallet When the user selects the re-issuance option from the Issuer details Then the wallet requests re-issuance from the issuer SUCCESS
User Authentication and Re-Issuance of PIDs/Attestations Wallet requests re-issuance to the same issuer for same document type 4 Given the user requested re-issuance for an existing PID or attestation When the wallet sends the re-issuance request Then the request is sent to the same issuer that issued the original PID or attestation And the request is for the same PID or attestation type SUCCESS
User Authentication and Re-Issuance of PIDs/Attestations Existing PID or attestation is replaced by the re-issued one 3 Given an existing PID or attestation is already stored in the Wallet When the Wallet receives the re-issued PID or attestation of the same type Then the existing PID or attestation is replaced SUCCESS
User Authentication and Re-Issuance of PIDs/Attestations Re-issuance in batch when the original issuance was in batch 3 Given the original PID or attestation was issued in batch When the issuer re-issues the PID or attestation Then the PID or attestation is re-issued in batch SUCCESS
Issuance and presentation - Proximity case 1: Successful credential issuance and presentation with selective disclosure - Python Issuer
issuer=Python, issuance_method=from list, issue_scenario=same device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=specific attributes (custom), status=passed 		9 Given user initiates credential issuance using the Python And issuance method is from list And issuance is performed on a same device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares specific attributes (custom) Then verifier verifies the credential successfully with passed SUCCESS
Issuance and presentation - Proximity case 2: Successful credential issuance and presentation with selective disclosure - Python Issuer
issuer=Python, issuance_method=from list, issue_scenario=same device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=all attributes (full), status=passed 		9 Given user initiates credential issuance using the Python And issuance method is from list And issuance is performed on a same device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares all attributes (full) Then verifier verifies the credential successfully with passed SUCCESS
Issuance and presentation - Proximity case 3: Successful credential issuance and presentation with selective disclosure - Python Issuer
issuer=Python, issuance_method=credential offer, issue_scenario=same device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=specific attributes (custom), status=passed 		9 Given user initiates credential issuance using the Python And issuance method is credential offer And issuance is performed on a same device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares specific attributes (custom) Then verifier verifies the credential successfully with passed SUCCESS
Issuance and presentation - Proximity case 4: Successful credential issuance and presentation with selective disclosure - Python Issuer
issuer=Python, issuance_method=credential offer, issue_scenario=same device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=all attributes (full), status=passed 		9 Given user initiates credential issuance using the Python And issuance method is credential offer And issuance is performed on a same device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares all attributes (full) Then verifier verifies the credential successfully with passed SUCCESS
Issuance and presentation - Proximity case 5: Successful credential issuance and presentation with selective disclosure - Python Issuer
issuer=Python, issuance_method=credential offer, issue_scenario=cross device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=specific attributes (custom), status=passed 		9 Given user initiates credential issuance using the Python And issuance method is credential offer And issuance is performed on a cross device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares specific attributes (custom) Then verifier verifies the credential successfully with passed SUCCESS
Issuance and presentation - Proximity case 6: Successful credential issuance and presentation with selective disclosure - Python Issuer
issuer=Python, issuance_method=credential offer, issue_scenario=cross device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=all attributes (full), status=passed 		9 Given user initiates credential issuance using the Python And issuance method is credential offer And issuance is performed on a cross device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares all attributes (full) Then verifier verifies the credential successfully with passed SUCCESS
Issuance and presentation - Proximity case 1: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer
issuer=Kotlin, issuance_method=credential offer, issue_scenario=same device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=specific attributes (custom), status=passed 		9 Given user initiates credential issuance using the Kotlin And issuance method is credential offer And issuance is performed on a same device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares specific attributes (custom) Then verifier verifies the credential successfully with passed SUCCESS
Issuance and presentation - Proximity case 2: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer
issuer=Kotlin, issuance_method=credential offer, issue_scenario=same device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=all attributes (full), status=passed 		9 Given user initiates credential issuance using the Kotlin And issuance method is credential offer And issuance is performed on a same device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares all attributes (full) Then verifier verifies the credential successfully with passed SUCCESS
Issuance and presentation - Proximity case 3: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer
issuer=Kotlin, issuance_method=credential offer, issue_scenario=cross device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=specific attributes (custom), status=passed 		9 Given user initiates credential issuance using the Kotlin And issuance method is credential offer And issuance is performed on a cross device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares specific attributes (custom) Then verifier verifies the credential successfully with passed SUCCESS
Issuance and presentation - Proximity case 4: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer
issuer=Kotlin, issuance_method=credential offer, issue_scenario=cross device, verifier=Proximity Verifier App, presentation_scenario=proximity case, selective_disclosure=all attributes (full), status=passed 		9 Given user initiates credential issuance using the Kotlin And issuance method is credential offer And issuance is performed on a cross device When issuance flow is completed Then credential is stored in the Wallet When user presents the credential to the Proximity Verifier App And presentation is performed on a proximity case And user shares all attributes (full) Then verifier verifies the credential successfully with passed SUCCESS

Tags

US IMASPTAO TC 06   1 US RAPDCAPISD   9 US IMASPTAO TC 02   1 US RAPDCAPICD TC 12   2 US RIAWIOUR   6 US RAPDCAPICD TC 04   1 Ios   63 US RAPDCAPICD TC 08   2 US RIAWIOUR TC 04   1 US IMASPTAO TC 05   1 US IMASPTAO TC 01   1 Execution   20 US RAPDCAPICD TC 01   2 US RAPDCAPICD   12 US RAPDCAPICD TC 09   2 US RIAWIOUR TC 01   1 US RAPDCAPICD TC 05   1 US RIAWIOUR TC 05   1 US IMASPTAO TC 04   1 Manual   33 US ETESM   10 US RAPDCAPICD TC 02   2 US RAPDCAPICD TC 10   2 US RIAWIOUR TC 02   1 US RAPDCAPICD TC 06   2 US RIAWIOUR TC 06   1 US IMASPTAO TC 03   1 US CIPSDPYMDL   20 Automated   20 Q1 2026   43 US RAPDCAPICD TC 03   1 US RAPDCAPICD TC 11   2 US IMASPTAO   6 US RIAWIOUR TC 03   1 US RAPDCAPICD TC 07   2
Manual
Serenity BDD version 4.2.22