EUDI Wallet Test Report
Home > Manual > Passed
Application version
Version 2026.05.37-Demo
Report generated 20-05-2026 17:01:25

Manual: Passed

73 tests |

Overview

Test Outcomes

Test Performance

Functional Coverage Overview

Features

Key Statistics

Number of Scenarios 50
Total Number of Test Cases 73
Number of Manual Test Cases 73
Tests Started May 20, 2026 11:24:10
Tests Finished May 20, 2026 12:04:22
Total Duration 40m 12s
Fastest Test 16s
Slowest Test 1m 49s
Average Execution Time 28s
Total Execution Time 35m 8s

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 cross device 305 > Cross-Device Presentation of Digital Attestations via EUDI Wallet 15 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 the Mobile Operating System evaluates installed Wallet Units Then suitable attestations matching the request are identified 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 suitable attestations exist on the mobile device When the Mobile Operating System prepares the selection interface Then a list of matching attestations is displayed Given the selector interface is displayed When the user views the list of attestations Then each attestation displays credential type, and wallet name Given multiple Wallet Units contain suitable attestations When the selector interface is shown Then each attestation indicates the Wallet Unit that holds it Given the selector interface displays matching attestations When the user selects one attestation Then the corresponding Wallet Unit is invoked Given the Wallet has verified the Relying Party 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 consents to share attributes and enters a valid six-digit PIN Then the attestation is presented successfully 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 15 100%
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%
Android > 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%
Android > 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 > 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%

Tags

US IMASPTAO TC 06   2 US RAPDCAPISD   22 US IMASPTAO TC 02   2 US RAPDCAPICD TC 12   3 US RIAWIOUR   12 US RAPDCAPICD TC 04   2 US RAPDCAPISD TC 07   1 US RAPDCAPISD TC 03   1 US RAPDCAPISD TC 11   1 Ios   33 US RAPDCAPICD TC 08   3 US RIAWIOUR TC 04   2 US IMASPTAO TC 05   2 US IMASPTAO TC 01   2 US RAPDCAPICD TC 01   3 US RAPDCAPICD TC 13   1 US RAPDCAPISD TC 06   1 US RAPDCAPICD   27 US RAPDCAPICD TC 09   3 US RAPDCAPISD TC 02   1 US RIAWIOUR TC 01   2 US RAPDCAPICD TC 05   2 US RIAWIOUR TC 05   2 US RAPDCAPISD TC 10   1 US IMASPTAO TC 04   2 Manual   73 US RAPDCAPICD TC 02   3 US RAPDCAPISD TC 09   1 US RAPDCAPICD TC 14   1 US RAPDCAPISD TC 05   1 US RAPDCAPICD TC 10   3 US RAPDCAPISD TC 13   1 US RAPDCAPISD TC 01   1 US RIAWIOUR TC 02   2 US RAPDCAPICD TC 06   3 US RIAWIOUR TC 06   2 US IMASPTAO TC 03   2 Android   40 Q1 2026   73 US RAPDCAPICD TC 03   2 US RAPDCAPICD TC 15   1 US RAPDCAPISD TC 08   1 US RAPDCAPICD TC 11   3 US IMASPTAO   12 US RIAWIOUR TC 03   2 US RAPDCAPISD TC 12   1 US RAPDCAPISD TC 04   1 US RAPDCAPICD TC 07   3
Manual

Key Statistics

Number of Scenarios 50 Total Duration 40m 12s
Total Number of Test Cases 73 Fastest Test 16s
Number of Manual Test Cases 73 Slowest Test 1m 49s
Tests Started May 20, 2026 11:24:10 Average Execution Time 28s
Tests Finished May 20, 2026 12:04:22 Total Execution Time 35m 8s

Automated Scenarios

No automated tests were executed

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 Mobile OS searches for matching attestations 3 Given the mobile device has received a presentation request When the Mobile Operating System evaluates installed Wallet Units Then suitable attestations matching the request are identified 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 Mobile OS displays selector with matching attestations 3 Given suitable attestations exist on the mobile device When the Mobile Operating System prepares the selection interface Then a list of matching attestations is displayed SUCCESS
Cross-Device Presentation of Digital Attestations via EUDI Wallet Attestation identifying information is displayed 3 Given the selector interface is displayed When the user views the list of attestations Then each attestation displays credential type, and wallet name SUCCESS
Cross-Device Presentation of Digital Attestations via EUDI Wallet Selector indicates Wallet Unit ownership 3 Given multiple Wallet Units contain suitable attestations When the selector interface is shown Then each attestation indicates the Wallet Unit that holds it SUCCESS
Cross-Device Presentation of Digital Attestations via EUDI Wallet User selects an attestation and Wallet opens 3 Given the selector interface displays matching attestations When the user selects one attestation Then the corresponding Wallet Unit is invoked SUCCESS
Cross-Device Presentation of Digital Attestations via EUDI Wallet Wallet displays requested attestations and attributes 3 Given the Wallet has verified the Relying Party When the presentation request screen is shown Then 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 Relying Party verifies attestation successfully 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 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 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
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
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

Tags

US IMASPTAO TC 06   2 US RAPDCAPISD   22 US IMASPTAO TC 02   2 US RAPDCAPICD TC 12   3 US RIAWIOUR   12 US RAPDCAPICD TC 04   2 US RAPDCAPISD TC 07   1 US RAPDCAPISD TC 03   1 US RAPDCAPISD TC 11   1 Ios   33 US RAPDCAPICD TC 08   3 US RIAWIOUR TC 04   2 US IMASPTAO TC 05   2 US IMASPTAO TC 01   2 US RAPDCAPICD TC 01   3 US RAPDCAPICD TC 13   1 US RAPDCAPISD TC 06   1 US RAPDCAPICD   27 US RAPDCAPICD TC 09   3 US RAPDCAPISD TC 02   1 US RIAWIOUR TC 01   2 US RAPDCAPICD TC 05   2 US RIAWIOUR TC 05   2 US RAPDCAPISD TC 10   1 US IMASPTAO TC 04   2 Manual   73 US RAPDCAPICD TC 02   3 US RAPDCAPISD TC 09   1 US RAPDCAPICD TC 14   1 US RAPDCAPISD TC 05   1 US RAPDCAPICD TC 10   3 US RAPDCAPISD TC 13   1 US RAPDCAPISD TC 01   1 US RIAWIOUR TC 02   2 US RAPDCAPICD TC 06   3 US RIAWIOUR TC 06   2 US IMASPTAO TC 03   2 Android   40 Q1 2026   73 US RAPDCAPICD TC 03   2 US RAPDCAPICD TC 15   1 US RAPDCAPISD TC 08   1 US RAPDCAPICD TC 11   3 US IMASPTAO   12 US RIAWIOUR TC 03   2 US RAPDCAPISD TC 12   1 US RAPDCAPISD TC 04   1 US RAPDCAPICD TC 07   3
Manual
Serenity BDD version 4.2.22