EUDI Wallet Test Report
Home > Tag > Android
Application version
Version 2026.10.43-Demo
Report generated 06-10-2026 16:02:09

Tag: Android

194 tests |

Overview

Test Outcomes

Test Performance

Functional Coverage Overview

Features

Key Statistics

Number of Scenarios 109
Total Number of Test Cases 194
Number of Manual Test Cases 137
Tests Started Sep 23, 2026 14:08:24
Tests Finished Oct 06, 2026 11:29:48
Total Duration 12d 21h 21m 23s
Fastest Test 6ms
Slowest Test 11m 9s
Average Execution Time 1m 36s
Total Execution Time 5h 10m 54s

Functional Coverage Details

Features

Feature Scenarios StepsText Test Cases % Pass Result Coverage
Android > eudi wallet trust mark 245 > access list of certified wallet solutions 354 > Access the official list of certified Wallet Solutions 4 Given the user opens the Wallet for the first time Then the Wallet displays the Trust Mark view When the user selects Continue Then the Wallet displays the Login screen Given the authenticated user is on the Wallet home screen When the user selects the burger menu and chooses About EUDI Wallet Then the Wallet displays the Trust Mark view Given the user is viewing the Trust Mark screen When the Trust Mark content is displayed Then the Wallet displays a link to the EUDI Wallet Provider Trusted List Given the EUDI Wallet Provider Trusted List link is displayed When the user selects the link Then the Wallet opens the European Commission-hosted webpage in an external browser or supported web view And the webpage allows the user to view the officially certified Wallet Solutions 4 100%
Android > eudi wallet trust mark 245 > verify certification status of the wallet solution 353 > Access Wallet Solution certification status information 4 Given the user opens the Wallet for the first time Then the Wallet displays the Trust Mark view When the user selects Continue Then the Wallet displays the Login screen Given the authenticated user is on the Wallet home screen When the user selects the burger menu and chooses About EUDI Wallet Then the Wallet displays the Trust Mark view Given the user is viewing the Trust Mark screen When the Trust Mark content is displayed Then the Wallet displays a link to the Wallet Solution certification information page Given the certification information link is displayed in the Trust Mark view When the user selects the certification information link Then the Wallet opens the European Commission-hosted certification information page in an external browser or supported web view And the page allows the user to verify the certification status of the Wallet Solution 4 100%
Android > eudi wallet trust mark 245 > view wallet certification information 352 > View Wallet Solution certification information 3 Given the user opens the Wallet for the first time Then the Wallet displays the Trust Mark view When the user selects Continue Then the Wallet displays the Login screen Given the authenticated user is on the Wallet home screen When the user selects the burger menu and chooses About EUDI Wallet Then the Wallet displays the Trust Mark view Given the user is viewing the Trust Mark screen When the Trust Mark content is displayed Then the Wallet displays general informational text explaining the certification of Wallet Solutions within the EUDI Wallet ecosystem And the informational text is displayed according to the device language settings 3 100%
Android > eudi wallet trust mark 245 > view wallet trust mark 351 > View Wallet Trust Mark 4 Given the user opens the Wallet for the first time Then the Wallet displays the Trust Mark view When the user selects Continue Then the Wallet displays the Login screen Given the authenticated user is on the Wallet home screen When the user selects the burger menu and chooses About EUDI Wallet Then the Wallet displays the Trust Mark view Given the user is viewing the Trust Mark screen When the Trust Mark content is displayed Then the Wallet displays the official EU Digital Identity Wallet Trust Mark graphics or logo And the Wallet displays informational text according to the device language settings And the Wallet provides links to certification status information Given the user is viewing the Trust Mark screen When the user selects the back arrow Then the Wallet returns to the Wallet home screen 4 100%
Android > initiate data deletion request privacy dashboard 36 > initiate data deletion request 223 > Initiate a data deletion request 8 Given the authenticated user has selected a presentation transaction from the Wallet History When the Presentation Information screen is displayed Then the Wallet displays the intended use of the presentation request And the Wallet displays the applicable privacy policy when available And the Wallet displays the attributes shared during the presentation transaction Given the authenticated user has selected a presentation transaction from the Wallet History When the user views the Presentation Information screen Then the Wallet displays the Initiate Deletion Request button Given user views the presentation information screen When the user selects the Initiate Deletion Request button Then the Wallet displays an informational screen explaining that the user is about to leave the Wallet And explains that the Wallet facilitates the initiation of the request by opening the appropriate communication channel And states that the Wallet does not submit, manage or track the request And states that the user is responsible for completing and submitting the request outside the Wallet And states that the Relying Party is responsible for evaluating and processing the request Given the WRPRC contains a website for the Relying Party When the Wallet displays the informational screen Then the Wallet displays a single action button Continue to [Relying Party]'s website Given the WRPRC contains a website for the Relying Party When the user selects the Continue to [Relying Party]'s website button Then the Wallet opens the Relying Party website in the device's default browser Given the user is viewing the informational screen When the user selects the Back navigation button Then the Wallet returns to the Presentation Information screen Given the user has initiated a data deletion request When the selected external application is successfully launched Then the Wallet records the data deletion request initiation Given contact information are not available in the WRPRC When contact information cannot be retrieved from the WRPRC Then the data deletion request cannot be initiated And the Initiate Deletion Request button in is disabled 8 100%
Android > initiate data deletion request privacy dashboard 36 > view previously attempted data deletion requests 222 > View previously attempted data deletion requests 6 Given the authenticated user has presentation transactions in the Wallet History When the user selects a presentation transaction Then the Wallet displays the Presentation Information for the selected transaction Given the selected presentation transaction has one or more recorded data deletion request attempts When the user views the Presentation Information screen Then the Wallet displays the View previously attempted requests link Given the selected presentation transaction has no recorded data deletion request attempts When the user views the Presentation Information screen Then the Wallet does not display the View previously attempted requests link Given the selected presentation transaction has one or more recorded data deletion request attempts When the user selects the View previously attempted requests link Then the Wallet opens the Data Deletion Request History screen And the Wallet displays the corresponding title And the Wallet displays explanatory text above the list of previous attempts And the Wallet displays the previous attempts associated with the selected presentation transaction Given the Data Deletion Request History screen contains previous attempts When the user views the list of previous attempts Then each attempt displays the date of the attempt And each attempt displays the communication method used Given the user is viewing the Data Deletion Request History screen When the user selects the Back navigation option Then the Wallet returns to the Presentation Information screen 6 100%
Android > initiate suspicious transaction report privacy dashboard 35 > initiate suspicious transaction report 221 > Initiate a report for an unlawful or suspicious data request 11 Given the authenticated user has presentation transactions in the Wallet History When the user selects a presentation transaction from the History screen Then the Wallet displays the Presentation Information for the selected transaction Given the user has selected a presentation transaction from the History screen When the Presentation Information screen is displayed Then the Wallet displays the intended use of the presentation request And the Wallet displays the applicable privacy policy And the Wallet displays the attributes shared during the presentation transaction Given the user selects a presentation transaction When the user views the Presentation Information screen Then the Wallet displays the Initiate Transaction Report button Given the user is viewing the Presentation Information for a presentation transaction When the user selects the Initiate Transaction Report button Then the Wallet displays the transaction report information screen Given the transaction report information screen has been opened When the screen content is displayed Then the Wallet identifies the responsible Data Protection Authority And the Wallet informs the user that the Wallet does not submit or track the report And the Wallet informs the user that the report must be completed directly with the identified Data Protection Authority Given the responsible Data Protection Authority provides website, email, and phone contact information When the Wallet displays the communication methods Then the Wallet displays Website, Email, and Phone as available options Given the Website communication method is available When the user selects the Website communication method Then the Wallet opens the DPA reporting website in the device's default browser Given the Email communication method is available When the user selects the Email communication method Then the Wallet opens the device's default email application with a pre-filled email And the pre-filled email contains the Data Protection Authority email address And the pre-filled email subject indicates an allegedly unlawful or suspicious presentation request And the pre-filled email content identifies the relevant Relying Party Given the Phone communication method is available When the user selects the Phone communication method Then the Wallet opens the device's phone application using the DPA telephone number Given the user has selected an available communication method When the corresponding external application is successfully launched Then the Wallet records the transaction report initiation Given the user is viewing the transaction report information screen When the user selects the Back navigation option Then the Wallet returns to the Presentation Information screen 11 100%
Android > initiate suspicious transaction report privacy dashboard 35 > view previously attempted transaction reports 394 > View previously attempted transaction reports 9 Given the authenticated user has presentation transactions in the Wallet History When the user selects a presentation transaction from the History screen Then the Wallet displays the Presentation Information for the selected transaction Given the selected presentation transaction has one or more recorded transaction report attempts When the user views the Presentation Information screen Then the Wallet displays the corresponding link Given the selected presentation transaction has no recorded transaction report attempts When the user views the Presentation Information screen Then the Wallet does not display the corresponding link Given the selected presentation transaction has one or more recorded transaction report attempts When the user selects the View previously attempted requests link Then the Wallet opens the transaction report History screen Given the user has opened the transaction report History for a selected presentation transaction When the transaction report History screen is displayed Then the title is displayed as Previous transaction report for [Relying Party Name] Given the user has opened the transaction report History for a selected presentation transaction When the transaction report History screen is displayed Then explanatory text is displayed above the list of previous attempts Given previous transaction report attempts are associated with the selected presentation transaction When the user opens the transaction report History screen Then the Wallet displays only the previous transaction report attempts associated with the selected presentation transaction And each transaction report attempt displays the date of the attempt Given the selected presentation transaction has previously attempted transaction reports When the transaction report History screen displays the previous attempts Then each transaction report attempt displays the communication method used And the Wallet does not display any indication of its completion, submission, or processing status Given the user is viewing the transaction report History screen When the user selects the Back navigation option Then the Wallet returns to the Presentation Information screen for the selected transaction 9 100%
Android > regression tests > automated regression tests > Issuing and storing attestations in the EUDI Wallet via QR code 1 1: Add a document to the EUDI Wallet by scanning a QR code ({issuer=Python}) Given the user visits the Issuer service, generates a QR code for a PID attestation using Python and returns to the Home screen of the Wallet When the user opens the Documents screen Then the Documents screen is displayed When the user taps the add document button on the Documents screen Then the wallet displays the Add document screen When the user selects the option to scan a QR code Then the wallet opens the scanner to scan the QR code rendered by the Issuer When the user scans a valid QR code rendered by the Issuer Then the wallet displays the credential offer with the attestation to be issued and the name of the issuer When the user selects the Cancel button on the credential offer Then the issuing process is canceled And the user is returned to the Documents screen When the user scans a valid QR code rendered by the Issuer And the user selects the Add document button on the credential offer Then the user proceeds with the attestation issuing flow And the wallet displays a success screen with the details of the issued attestation When the user closes the success screen Then the attestation is added to the EUDI Wallet 2: Add a document to the EUDI Wallet by scanning a QR code ({issuer=Kotlin}) Given the user visits the Issuer service, generates a QR code for a PID attestation using Kotlin and returns to the Home screen of the Wallet When the user opens the Documents screen Then the Documents screen is displayed When the user taps the add document button on the Documents screen Then the wallet displays the Add document screen When the user selects the option to scan a QR code Then the wallet opens the scanner to scan the QR code rendered by the Issuer When the user scans a valid QR code rendered by the Issuer Then the wallet displays the credential offer with the attestation to be issued and the name of the issuer When the user selects the Cancel button on the credential offer Then the issuing process is canceled And the user is returned to the Documents screen When the user scans a valid QR code rendered by the Issuer And the user selects the Add document button on the credential offer Then the user proceeds with the attestation issuing flow And the wallet displays a success screen with the details of the issued attestation When the user closes the success screen Then the attestation is added to the EUDI Wallet 2 100%
Android > regression tests > automated regression tests > Deferred Credential Issuance 1 1: Completing the deferred credential delivery process with Python Issuer ({issuer=Python}) Given the user is accessing Python service When the user chooses to deliver a deferred credential to the wallet with Python Then the EUDI Wallet application is opened And the issuance information is displayed to the user for Python Then the user selects the ISSUE button for Python And the user is redirected to the issuer service for authentication and authorization for Python When the user completes authentication and confirms the issuance for Python And the user is navigated to the EUDI wallet application And a notification indicates that the credential request is being processed When the user dismisses the notification by pressing OK And the user is on the Home page And the document is displayed as unavailable with a pending status When the issuer provides the requested credential to the wallet Then the user receives a confirmation message indicating that the document has been issued When the user chooses to inspect the document details Then the issued credential information is displayed for Python And the user presses the X button to close the document Then the document details are no longer displayed And the document appears on the documents screen for Python 2: Completing the deferred credential delivery process with Python Issuer ({issuer=Kotlin}) Given the user is accessing Kotlin service When the user chooses to deliver a deferred credential to the wallet with Kotlin Then the EUDI Wallet application is opened And the issuance information is displayed to the user for Kotlin Then the user selects the ISSUE button for Kotlin And the user is redirected to the issuer service for authentication and authorization for Kotlin When the user completes authentication and confirms the issuance for Kotlin And the user is navigated to the EUDI wallet application And a notification indicates that the credential request is being processed When the user dismisses the notification by pressing OK And the user is on the Home page And the document is displayed as unavailable with a pending status When the issuer provides the requested credential to the wallet Then the user receives a confirmation message indicating that the document has been issued When the user chooses to inspect the document details Then the issued credential information is displayed for Kotlin And the user presses the X button to close the document Then the document details are no longer displayed And the document appears on the documents screen for Kotlin 2 100%
Android > regression tests > automated regression tests > EUDI Wallet Documents Screen 1 1: Documents screen consolidates and lists issued attestations ({credential=PID (MSO Mdoc), issuer=Python}) Given the user issues a PID (MSO Mdoc) attestation using Python And the user issues the second attestation for Python And the user is on the Home screen of the Wallet Then the bottom navigation bar shows the Home, Documents, and History tabs When the user opens the Documents screen Then the Documents tab becomes highlighted after selection And the Documents screen provides a Search bar And the Documents screen provides a Filter control And the Documents screen lists the issued attestations And the listed attestations are organized by category And each attestation card shows the attestation name, the issuer, and the validity end date When the user taps twice on an attestation from the list Then the attestation details are displayed 2: Documents screen consolidates and lists issued attestations ({credential=PID (MSO Mdoc), issuer=Kotlin}) Given the user issues a PID (MSO Mdoc) attestation using Kotlin And the user issues the second attestation for Kotlin And the user is on the Home screen of the Wallet Then the bottom navigation bar shows the Home, Documents, and History tabs When the user opens the Documents screen Then the Documents tab becomes highlighted after selection And the Documents screen provides a Search bar And the Documents screen provides a Filter control And the Documents screen lists the issued attestations And the listed attestations are organized by category And each attestation card shows the attestation name, the issuer, and the validity end date When the user taps twice on an attestation from the list Then the attestation details are displayed 2 100%
Android > regression tests > automated regression tests > EUDI Wallet Home Screen 1 Given the user is viewing the EUDI Wallet Home screen Then the bottom navigation bar displays Home, Documents, and Transactions When the user chooses the Home option from the bottom navigation bar Then the Home option appears highlighted And the Home screen presents the Authenticate and Sign a document sections When the user taps the Authenticate section Then the Authenticate section provides In Person and Online options When the user selects the Sign a document section Then the Sign Document screen appears 1 100%
Android > regression tests > automated regression tests > 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) and from list 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=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) and from list 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 3: 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) and credential offer 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 4: 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) and credential offer 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 5: 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) and credential offer 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=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) and credential offer 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=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 Kotlin And the issuance method is from list And the issuance is performed on a same device for the mDL (MSO Mdoc) and from list 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=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 Kotlin And the issuance method is from list And the issuance is performed on a same device for the mDL (MSO Mdoc) and from list 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 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=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) and credential offer 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 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=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) and credential offer 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 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) and credential offer 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=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) and credential offer 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 12 100%
Android > regression tests > automated regression tests > Issuance and presentation - PID (MSO Mdoc) 2 1: Successful credential issuance and presentation with selective disclosure - Python Issuer - PID (MSO Mdoc) ({credential=PID (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 PID (MSO Mdoc) issuance using the Python And the issuance method is from list And the issuance is performed on a same device for the PID (MSO Mdoc) and from list 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 PID (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 - PID (MSO Mdoc) ({credential=PID (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 PID (MSO Mdoc) issuance using the Python And the issuance method is from list And the issuance is performed on a same device for the PID (MSO Mdoc) and from list 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 PID (MSO Mdoc) Then the verifier verifies the credential successfully with cross device for specific attributes 3: Successful credential issuance and presentation with selective disclosure - Python Issuer - PID (MSO Mdoc) ({credential=PID (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 PID (MSO Mdoc) issuance using the Python And the issuance method is credential offer And the issuance is performed on a same device for the PID (MSO Mdoc) and credential offer 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 PID (MSO Mdoc) Then the verifier verifies the credential successfully with same device for specific attributes 4: Successful credential issuance and presentation with selective disclosure - Python Issuer - PID (MSO Mdoc) ({credential=PID (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 PID (MSO Mdoc) issuance using the Python And the issuance method is credential offer And the issuance is performed on a same device for the PID (MSO Mdoc) and credential offer 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 PID (MSO Mdoc) Then the verifier verifies the credential successfully with cross device for specific attributes 5: Successful credential issuance and presentation with selective disclosure - Python Issuer - PID (MSO Mdoc) ({credential=PID (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 PID (MSO Mdoc) issuance using the Python And the issuance method is credential offer And the issuance is performed on a cross device for the PID (MSO Mdoc) and credential offer 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 PID (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 - PID (MSO Mdoc) ({credential=PID (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 PID (MSO Mdoc) issuance using the Python And the issuance method is credential offer And the issuance is performed on a cross device for the PID (MSO Mdoc) and credential offer 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 PID (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 - PID (MSO Mdoc) ({credential=PID (MSO Mdoc), issuer=Kotlin, issuance_method=from list, issue_scenario=same device, verifier=Web verifier, presentation_scenario=same device, selective_disclosure=specific attributes}) Given the user initiates a PID (MSO Mdoc) issuance using the Kotlin And the issuance method is from list And the issuance is performed on a same device for the PID (MSO Mdoc) and from list 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 PID (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 - PID (MSO Mdoc) ({credential=PID (MSO Mdoc), issuer=Kotlin, issuance_method=from list, issue_scenario=same device, verifier=Web verifier, presentation_scenario=cross device, selective_disclosure=specific attributes}) Given the user initiates a PID (MSO Mdoc) issuance using the Kotlin And the issuance method is from list And the issuance is performed on a same device for the PID (MSO Mdoc) and from list 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 PID (MSO Mdoc) Then the verifier verifies the credential successfully with cross device for specific attributes 3: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - PID (MSO Mdoc) ({credential=PID (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 PID (MSO Mdoc) issuance using the Kotlin And the issuance method is credential offer And the issuance is performed on a same device for the PID (MSO Mdoc) and credential offer 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 PID (MSO Mdoc) Then the verifier verifies the credential successfully with same device for specific attributes 4: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - PID (MSO Mdoc) ({credential=PID (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 PID (MSO Mdoc) issuance using the Kotlin And the issuance method is credential offer And the issuance is performed on a same device for the PID (MSO Mdoc) and credential offer 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 PID (MSO Mdoc) Then the verifier verifies the credential successfully with cross device for specific attributes 5: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - PID (MSO Mdoc) ({credential=PID (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 PID (MSO Mdoc) issuance using the Kotlin And the issuance method is credential offer And the issuance is performed on a cross device for the PID (MSO Mdoc) and credential offer 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 PID (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 - PID (MSO Mdoc) ({credential=PID (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 PID (MSO Mdoc) issuance using the Kotlin And the issuance method is credential offer And the issuance is performed on a cross device for the PID (MSO Mdoc) and credential offer 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 PID (MSO Mdoc) Then the verifier verifies the credential successfully with cross device for specific attributes 12 100%
Android > regression tests > automated regression tests > Issuance and presentation - PID (SD-JWT) 2 1: Successful credential issuance and presentation with selective disclosure - Python Issuer - PID (SD-JWT) ({credential=PID (SD-JWT), 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 PID (SD-JWT) issuance using the Python And the issuance method is from list And the issuance is performed on a same device for the PID (SD-JWT) and from list 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 PID (SD-JWT) Then the verifier verifies the credential successfully with same device for specific attributes 2: Successful credential issuance and presentation with selective disclosure - Python Issuer - PID (SD-JWT) ({credential=PID (SD-JWT), 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 PID (SD-JWT) issuance using the Python And the issuance method is from list And the issuance is performed on a same device for the PID (SD-JWT) and from list 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 PID (SD-JWT) Then the verifier verifies the credential successfully with cross device for specific attributes 3: Successful credential issuance and presentation with selective disclosure - Python Issuer - PID (SD-JWT) ({credential=PID (SD-JWT), 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 PID (SD-JWT) issuance using the Python And the issuance method is credential offer And the issuance is performed on a same device for the PID (SD-JWT) and credential offer 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 PID (SD-JWT) Then the verifier verifies the credential successfully with same device for specific attributes 4: Successful credential issuance and presentation with selective disclosure - Python Issuer - PID (SD-JWT) ({credential=PID (SD-JWT), 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 PID (SD-JWT) issuance using the Python And the issuance method is credential offer And the issuance is performed on a same device for the PID (SD-JWT) and credential offer 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 PID (SD-JWT) Then the verifier verifies the credential successfully with cross device for specific attributes 5: Successful credential issuance and presentation with selective disclosure - Python Issuer - PID (SD-JWT) ({credential=PID (SD-JWT), 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 PID (SD-JWT) issuance using the Python And the issuance method is credential offer And the issuance is performed on a cross device for the PID (SD-JWT) and credential offer 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 PID (SD-JWT) Then the verifier verifies the credential successfully with same device for specific attributes 6: Successful credential issuance and presentation with selective disclosure - Python Issuer - PID (SD-JWT) ({credential=PID (SD-JWT), 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 PID (SD-JWT) issuance using the Python And the issuance method is credential offer And the issuance is performed on a cross device for the PID (SD-JWT) and credential offer 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 PID (SD-JWT) Then the verifier verifies the credential successfully with cross device for specific attributes 1: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - PID (SD-JWT) ({credential=PID (SD-JWT), issuer=Kotlin, issuance_method=from list, issue_scenario=same device, verifier=Web verifier, presentation_scenario=same device, selective_disclosure=specific attributes}) Given the user initiates a PID (SD-JWT) issuance using the Kotlin And the issuance method is from list And the issuance is performed on a same device for the PID (SD-JWT) and from list 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 PID (SD-JWT) Then the verifier verifies the credential successfully with same device for specific attributes 2: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - PID (SD-JWT) ({credential=PID (SD-JWT), issuer=Kotlin, issuance_method=from list, issue_scenario=same device, verifier=Web verifier, presentation_scenario=cross device, selective_disclosure=specific attributes}) Given the user initiates a PID (SD-JWT) issuance using the Kotlin And the issuance method is from list And the issuance is performed on a same device for the PID (SD-JWT) and from list 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 PID (SD-JWT) Then the verifier verifies the credential successfully with cross device for specific attributes 3: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - PID (SD-JWT) ({credential=PID (SD-JWT), 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 PID (SD-JWT) issuance using the Kotlin And the issuance method is credential offer And the issuance is performed on a same device for the PID (SD-JWT) and credential offer 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 PID (SD-JWT) Then the verifier verifies the credential successfully with same device for specific attributes 4: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - PID (SD-JWT) ({credential=PID (SD-JWT), 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 PID (SD-JWT) issuance using the Kotlin And the issuance method is credential offer And the issuance is performed on a same device for the PID (SD-JWT) and credential offer 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 PID (SD-JWT) Then the verifier verifies the credential successfully with cross device for specific attributes 5: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - PID (SD-JWT) ({credential=PID (SD-JWT), 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 PID (SD-JWT) issuance using the Kotlin And the issuance method is credential offer And the issuance is performed on a cross device for the PID (SD-JWT) and credential offer 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 PID (SD-JWT) Then the verifier verifies the credential successfully with same device for specific attributes 6: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - PID (SD-JWT) ({credential=PID (SD-JWT), 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 PID (SD-JWT) issuance using the Kotlin And the issuance method is credential offer And the issuance is performed on a cross device for the PID (SD-JWT) and credential offer 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 PID (SD-JWT) Then the verifier verifies the credential successfully with cross device for specific attributes 12 100%
Android > regression tests > automated regression tests > Batch Issuance of Attestations in EUDI Wallet 1 1: Batch Issuance of Attestations in EUDI Wallet ({credential=PID (MSO Mdoc), issuer=Python, issuance_method=from list, issue_scenario=same device}) Given the user initiates a PID (MSO Mdoc) issuance using the Python And the issuance method is from list And the issuance is performed on a same device for the PID (MSO Mdoc) and from list When the issuance flow is completed Then the credential is stored in the Wallet And the issuer service generates multiple attestations And the Wallet shows a counter indicating the total number of attestations issued When the issuer advertised maximum batch size is below the Wallet internal minimum threshold Then the issuance process continues with the issuer's maximum batch size And the Wallet saves the attestations based on the issuer-defined batch size 2: Batch Issuance of Attestations in EUDI Wallet ({credential=PID (MSO Mdoc), issuer=Kotlin, issuance_method=from list, issue_scenario=same device}) Given the user initiates a PID (MSO Mdoc) issuance using the Kotlin And the issuance method is from list And the issuance is performed on a same device for the PID (MSO Mdoc) and from list When the issuance flow is completed Then the credential is stored in the Wallet And the issuer service generates multiple attestations And the Wallet shows a counter indicating the total number of attestations issued When the issuer advertised maximum batch size is below the Wallet internal minimum threshold Then the issuance process continues with the issuer's maximum batch size And the Wallet saves the attestations based on the issuer-defined batch size 3: Batch Issuance of Attestations in EUDI Wallet ({credential=PID (MSO Mdoc), issuer=Python, issuance_method=credential offer, issue_scenario=same device}) Given the user initiates a PID (MSO Mdoc) issuance using the Python And the issuance method is credential offer And the issuance is performed on a same device for the PID (MSO Mdoc) and credential offer When the issuance flow is completed Then the credential is stored in the Wallet And the issuer service generates multiple attestations And the Wallet shows a counter indicating the total number of attestations issued When the issuer advertised maximum batch size is below the Wallet internal minimum threshold Then the issuance process continues with the issuer's maximum batch size And the Wallet saves the attestations based on the issuer-defined batch size 4: Batch Issuance of Attestations in EUDI Wallet ({credential=PID (MSO Mdoc), issuer=Kotlin, issuance_method=credential offer, issue_scenario=same device}) Given the user initiates a PID (MSO Mdoc) issuance using the Kotlin And the issuance method is credential offer And the issuance is performed on a same device for the PID (MSO Mdoc) and credential offer When the issuance flow is completed Then the credential is stored in the Wallet And the issuer service generates multiple attestations And the Wallet shows a counter indicating the total number of attestations issued When the issuer advertised maximum batch size is below the Wallet internal minimum threshold Then the issuance process continues with the issuer's maximum batch size And the Wallet saves the attestations based on the issuer-defined batch size 5: Batch Issuance of Attestations in EUDI Wallet ({credential=PID (MSO Mdoc), issuer=Python, issuance_method=credential offer, issue_scenario=cross device}) Given the user initiates a PID (MSO Mdoc) issuance using the Python And the issuance method is credential offer And the issuance is performed on a cross device for the PID (MSO Mdoc) and credential offer When the issuance flow is completed Then the credential is stored in the Wallet And the issuer service generates multiple attestations And the Wallet shows a counter indicating the total number of attestations issued When the issuer advertised maximum batch size is below the Wallet internal minimum threshold Then the issuance process continues with the issuer's maximum batch size And the Wallet saves the attestations based on the issuer-defined batch size 6: Batch Issuance of Attestations in EUDI Wallet ({credential=PID (MSO Mdoc), issuer=Kotlin, issuance_method=credential offer, issue_scenario=cross device}) Given the user initiates a PID (MSO Mdoc) issuance using the Kotlin And the issuance method is credential offer And the issuance is performed on a cross device for the PID (MSO Mdoc) and credential offer When the issuance flow is completed Then the credential is stored in the Wallet And the issuer service generates multiple attestations And the Wallet shows a counter indicating the total number of attestations issued When the issuer advertised maximum batch size is below the Wallet internal minimum threshold Then the issuance process continues with the issuer's maximum batch size And the Wallet saves the attestations based on the issuer-defined batch size 6 100%
Android > regression tests > automated regression tests > Pre-authorization code same device 1 Given the user is accessing the issuer service When the user selects to issue a document using pre-authorization Then the user provides their personal information And a transaction code is generated And the user chooses to register through the EUDI wallet app And the user is navigated to the EUDI wallet application And the user provides the PIN When the issuer request is shown in the wallet app Then the user selects ISSUE button And the Wallet app prompts for the transaction code And the user enters the transaction code received from the Issuer And the Wallet application shows a successful issuance message And the user selects the CONTINUE button Then the document appears on the documents screen 1 100%
Android > regression tests > automated regression tests > Presentation of Batch Issued Attestations in EUDI Wallet 1 1: Relying Party initiated presentation flow ({credential=PID (MSO Mdoc), issuer=Python, issuance_method=from list, issue_scenario=same device, verifier=Web verifier, presentation_scenario=same device}) Given the user is registered to a valid EUDI Wallet on their mobile device And the EUDI Wallet and the Relying Party User Interface reside on the same device And there is an active internet connection Given the user initiates a PID (MSO Mdoc) issuance using the Python And the issuance method is from list And the issuance is performed on a same device for the PID (MSO Mdoc) and from list When the issuance flow is completed Then the credential is stored in the Wallet And the user accesses the Relying Party service through their mobile device using Web verifier When the user chooses to present an attestation type Then the Relying Party service navigates the user to the EUDI Wallet When the user is unable to authenticate using a six-digit PIN or Biometrics Then the Wallet displays an authentication error And the user is allowed to attempt the authentication again When the user verifies their identity using a six-digit PIN or Biometrics And the authentication is completed successfully Then the EUDI Wallet notifies the user that the Relying Party is requesting an attestation with same device 2: Relying Party initiated presentation flow ({credential=PID (MSO Mdoc), issuer=Kotlin, issuance_method=from list, issue_scenario=same device, verifier=Web verifier, presentation_scenario=same device}) Given the user is registered to a valid EUDI Wallet on their mobile device And the EUDI Wallet and the Relying Party User Interface reside on the same device And there is an active internet connection Given the user initiates a PID (MSO Mdoc) issuance using the Kotlin And the issuance method is from list And the issuance is performed on a same device for the PID (MSO Mdoc) and from list When the issuance flow is completed Then the credential is stored in the Wallet And the user accesses the Relying Party service through their mobile device using Web verifier When the user chooses to present an attestation type Then the Relying Party service navigates the user to the EUDI Wallet When the user is unable to authenticate using a six-digit PIN or Biometrics Then the Wallet displays an authentication error And the user is allowed to attempt the authentication again When the user verifies their identity using a six-digit PIN or Biometrics And the authentication is completed successfully Then the EUDI Wallet notifies the user that the Relying Party is requesting an attestation with same device 2 100%
Android > regression tests > automated regression tests > EUDI Wallet Online Document Presentation 1 1: User can cancel and then complete an online data sharing presentation ({credential=PID (MSO Mdoc), issuer=Python}) Given the user issues a PID (MSO Mdoc) attestation using Python And the user is on the Home screen of the Wallet And a Relying Party renders a presentation request as a QR code When the user opens the Online option from the Authenticate section And the Wallet scans the Relying Party's presentation request QR code Then the Wallet displays the attestation details requested for sharing When the user cancels the presentation request Then the user returns to the Wallet Home screen And a Relying Party renders a presentation request as a QR code When the user opens the Online option from the Authenticate section And the Wallet scans the Relying Party's presentation request QR code Then the Wallet displays the attestation details requested for sharing When the user selects the Share button And the user enters their six-digit PIN correctly Then a success message is displayed for the successful presentation of the PID When the user closes the success screen Then the user returns to the Wallet Home screen 1 100%
Android > regression tests > automated regression tests > Sign Document through EUDI Wallet 1 1: Sign a document through the EUDI Wallet ({issuer=Kotlin}) Given the user uploads a document and an attestation using Kotlin and selects a QTSP When the EUDI Wallet fetches the Credential ID details from the QTSP Then the EUDI Wallet displays the Credential ID details to the user And the user agrees to proceed with the signing operation When the user opts not to proceed Then the user selects the Abort operation option And the EUDI Wallet redirects the user to the main page When the EUDI Wallet asks the user to consent to the release of the requested attestation And the user successfully authenticates in the Wallet Then the EUDI Wallet shares the requested attestation with the QTSP And a success screen appears with the signed document When the EUDI Wallet obtains the signed document Then the EUDI Wallet allows the user to share the document or close the process 2: Sign a document through the EUDI Wallet ({issuer=Python}) Given the user uploads a document and an attestation using Python and selects a QTSP When the EUDI Wallet fetches the Credential ID details from the QTSP Then the EUDI Wallet displays the Credential ID details to the user And the user agrees to proceed with the signing operation When the user opts not to proceed Then the user selects the Abort operation option And the EUDI Wallet redirects the user to the main page When the EUDI Wallet asks the user to consent to the release of the requested attestation And the user successfully authenticates in the Wallet Then the EUDI Wallet shares the requested attestation with the QTSP And a success screen appears with the signed document When the EUDI Wallet obtains the signed document Then the EUDI Wallet allows the user to share the document or close the process 2 100%
Android > regression tests > automated regression tests > View, bookmark and manage attestations in the EUDI Wallet 1 1: View, bookmark, inspect and delete an attestation through the EUDI Wallet ({credential=PID (MSO Mdoc), issuer=Python}) Given the user issues a PID (MSO Mdoc) attestation using Python And the user is on the Home screen of the Wallet When the user opens the Documents screen Then the Documents screen lists the issued attestations When the user taps on an attestation from the list Then the attestation details are displayed And the attestation details are blurred by default And an eye icon is shown to reveal the attestation details When the user taps on the eye icon Then the attestation details are no longer blurred And the user can view the full attestation details When the user taps the bookmark icon on the attestation Then the attestation gets marked as bookmarked And the bookmark icon updates to indicate the bookmarked state When the user opens the issuer details from the attestation Then the issuer details are displayed to the user When the user closes the attestation details without deleting it Then the user lands back on the Documents screen When the user reopens the attestation and selects the delete option Then the attestation gets removed from the EUDI Wallet And the Documents screen no longer lists the deleted attestation 2: View, bookmark, inspect and delete an attestation through the EUDI Wallet ({credential=PID (MSO Mdoc), issuer=Kotlin}) Given the user issues a PID (MSO Mdoc) attestation using Kotlin And the user is on the Home screen of the Wallet When the user opens the Documents screen Then the Documents screen lists the issued attestations When the user taps on an attestation from the list Then the attestation details are displayed And the attestation details are blurred by default And an eye icon is shown to reveal the attestation details When the user taps on the eye icon Then the attestation details are no longer blurred And the user can view the full attestation details When the user taps the bookmark icon on the attestation Then the attestation gets marked as bookmarked And the bookmark icon updates to indicate the bookmarked state When the user opens the issuer details from the attestation Then the issuer details are displayed to the user When the user closes the attestation details without deleting it Then the user lands back on the Documents screen When the user reopens the attestation and selects the delete option Then the attestation gets removed from the EUDI Wallet And the Documents screen no longer lists the deleted attestation 2 100%
Android > transaction data enabling binding between the users identification authentication and the users authorization wallet 228 > review and authorise QES transaction data 393 > Review and authorise QES transaction data 8 Given the user has initiated a QES signing operation When the Wallet presents the transaction information for review Then the Wallet displays the QES transaction type and applicable trust framework And the Wallet displays the document name or description Given the QES transaction contains a reference to the document to be signed where provided When the Wallet presents the transaction information Then the user can access the document associated with the signing transaction Given the QES transaction contains additional document or signing information When the Wallet presents the transaction information for review Then the Wallet displays the applicable DTBSR information And the Wallet displays the signed attributes and requested credentials where applicable Given optional QES transaction information is provided When the Wallet presents the transaction information for review Then the Wallet displays the OTP where provided And the Wallet displays the Response URI where applicable And the Wallet displays the document integrity status And the Wallet displays the signature format and conformance level where provided Given the user has reviewed the transaction information and document When the user explicitly approves the QES transaction Then the Wallet continues the QES signing process Given the user is reviewing the QES transaction When the user rejects or cancels the transaction Then the QES signing operation does not proceed Given the QES transaction has been completed When the user accesses the Transaction Log Then the QES transaction is available in the Transaction Log Given the QES transaction is available in the Transaction Log When the user opens the recorded QES transaction Then the Wallet displays the relevant Transaction Data associated with the transaction And the Wallet displays the user's recorded decision to approve or reject the transaction 8 75%
Android > transaction log ARF alignment 193 > delete transactions from transaction log 331 > Delete a transaction from transaction log 10 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry from the list Then the transaction details screen opens And a delete button is visible in the top right corner Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user has opened the details screen of a transaction When the user clicks the delete button Then a confirmation dialog is displayed And no transaction is removed yet Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the confirmation dialog is displayed Then the dialog include a warning message indicating the consequences of deleting the transaction And the dialog provides a Confirm deletion button and a Cancel button Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the confirmation dialog is displayed for a transaction When the user selects Cancel Then the dialog closes And the user remains on the details screen of the same transaction And the transaction log is unchanged Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user has cancelled the deletion of a transaction When the user navigates back to the History screen Then the transaction is still visible in the list Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the confirmation dialog is displayed for a transaction When the user selects Confirm deletion Then the dialog closes And the user is returned to the History screen And the transaction is no longer shown in the list Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user has deleted a transaction and knows its relying party name, type, status and date When the user searches for it or applies matching filters Then the deleted transaction is not returned in any of the search or filter Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the transaction log contains exactly one transaction When the user deletes that transaction and confirms Then the history screen shows the empty state message Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user reached a transaction through an active search or filter When the user deletes that transaction and confirms Then the user returns to the same filtered or search view And the deleted transaction is missing from the results And the other results remain displayed Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user has one transaction of each category available When the user deletes them one by one via the delete button and confirmation dialog Then the same warning dialog appear for every category And each transaction disappears from the list search and filters 10 100%
Android > transaction log ARF alignment 193 > filter and sort transactions 330 > Filter and Sort Transactions in History tab 9 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user enters the History screen Then no filter is applied, the default option And the transactions are sorted by transaction date descending, the default sort option And the filter button has no visual indication that a user filter option is applied Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user taps the filter button Then the filter bottom sheet options slide up from the bottom screen And the filter options are displayed in separate sections And each section under the title displays the available filter options Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the filter bottom sheet When the user selects to filter by Date Then the user can select the date range (date from and date to) using a calendar Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the filter bottom sheet When the user selects to filter by Status Then the user can select an operation status option to filter the transactions Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the filter bottom sheet When the user selects to filter by Relying Party Then the user can filter the transactions by selecting or deselecting the corresponding parties listed Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the filter bottom sheet When the user selects to filter by Transaction Type Then a list of all supported transaction types is displayed And the user can filter by selecting or deselecting the corresponding types listed Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the filter bottom sheet When the user taps the Reset all button Then the filters are reset to the default values And the filter button has no visual indication that a user filter option is applied Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the filter bottom sheet When the user taps the Apply button Then the bottom sheet slides down and disappears And the EUDI Wallet applies a filter options to the transactions list And the filter button has visual indication that user filter options have been applied Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user applies a filter option When no matching transactions are found Then the EUDI Wallet displays an informative message in the list section And if no results are found within a period group, then the period group is not displayed 9 100%
Android > transaction log ARF alignment 193 > list transactions 327 > List Transactions in History tab 5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the EUDI Wallet main screen When the user selects the History option in the bottom navigation bar Then the History button is highlighted And the History screen is displayed Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the History screen includes a Search bar And the History screen includes a Filter button 1: History screen lists transactions grouped by period ({Group=Today, Description=Transactions that occurred today}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the transactions are listed grouped by period as follows by Today and Transactions that occurred today And the transactions are sorted in chronological order within each group 2: History screen lists transactions grouped by period ({Group=This Week, Description=Transactions that occurred this week}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the transactions are listed grouped by period as follows by This Week and Transactions that occurred this week And the transactions are sorted in chronological order within each group 3: History screen lists transactions grouped by period ({Group=Month, Description=Transactions grouped by month}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the transactions are listed grouped by period as follows by Month and Transactions grouped by month And the transactions are sorted in chronological order within each group 1: User views transaction entry details ({Detail=Transaction Type, Description=presentation, issuance, signing, deletion, etc.}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Transaction Type and presentation, issuance, signing, deletion, etc. 2: User views transaction entry details ({Detail=Status, Description=The transaction result, Completed or Not Completed}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Status and The transaction result, Completed or Not Completed 3: User views transaction entry details ({Detail=Relying Party, Description=The Relying Party name or document name as follows:}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Relying Party and The Relying Party name or document name as follows: 4: User views transaction entry details ({Detail=Relying Party, Description=For presentation transactions: 'Service Provider name'}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Relying Party and For presentation transactions: 'Service Provider name' 5: User views transaction entry details ({Detail=Relying Party, Description=For issuance transactions: 'PID Provider or Attestation Provider name'}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Relying Party and For issuance transactions: 'PID Provider or Attestation Provider name' 6: User views transaction entry details ({Detail=Relying Party, Description=For signing transactions: 'Signing Service Provider name'}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Relying Party and For signing transactions: 'Signing Service Provider name' 7: User views transaction entry details ({Detail=Datetime, Description=The datetime of the transaction as follows:}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Datetime and The datetime of the transaction as follows: 8: User views transaction entry details ({Detail=Datetime, Description=X minutes ago for transactions in the last 60 minutes}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Datetime and X minutes ago for transactions in the last 60 minutes 9: User views transaction entry details ({Detail=Datetime, Description=Time (e.g., 11:07 AM) for transactions within the day}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Datetime and Time (e.g., 11:07 AM) for transactions within the day 10: User views transaction entry details ({Detail=Datetime, Description=Datetime (e.g., 14 Feb 2024 11:07 AM) for transactions before today}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Datetime and Datetime (e.g., 14 Feb 2024 11:07 AM) for transactions before today 1: Transaction types displayed on the History screen ({Type=Credential (PID or attestation) issuance and re-issuance transactions, Displayed=Y}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the transaction type Credential (PID or attestation) issuance and re-issuance transactions is Y on the History screen 2: Transaction types displayed on the History screen ({Type=PID or attestation presentation transactions, Displayed=Y}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the transaction type PID or attestation presentation transactions is Y on the History screen 3: Transaction types displayed on the History screen ({Type=Signature or seal creation transactions, Displayed=Y}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the transaction type Signature or seal creation transactions is Y on the History screen 4: Transaction types displayed on the History screen ({Type=Data deletion requests sent to a Relying Party, Displayed=N}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the transaction type Data deletion requests sent to a Relying Party is N on the History screen 5: Transaction types displayed on the History screen ({Type=Suspicious Transaction Reports sent to a Data Protection Authority, Displayed=N}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the transaction type Suspicious Transaction Reports sent to a Data Protection Authority is N on the History screen 6: Transaction types displayed on the History screen ({Type=Credential (PID or attestation) deletion by the User, Displayed=Y}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the transaction type Credential (PID or attestation) deletion by the User is Y on the History screen 21 100%
Android > transaction log ARF alignment 193 > search transactions 329 > Transaction Search in History tab 6 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the Home screen When the user clicks the History button Then the History screen is displayed And all transactions are displayed And no search or filters are applied 1: History screen display features ({options=the transactions are grouped by period}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user observes the transactions screen Then the following are displayed the transactions are grouped by period: And if there are no transactions for a period group, then this group is not displayed 2: History screen display features ({options=the search field is empty and enabled}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user observes the transactions screen Then the following are displayed the search field is empty and enabled: And if there are no transactions for a period group, then this group is not displayed 3: History screen display features ({options=the search field contains a search icon on the left side}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user observes the transactions screen Then the following are displayed the search field contains a search icon on the left side: And if there are no transactions for a period group, then this group is not displayed 4: History screen display features ({options=the search field displays a hinted search text "Search"}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user observes the transactions screen Then the following are displayed the search field displays a hinted search text "Search": And if there are no transactions for a period group, then this group is not displayed Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user previously searched for a text When the user taps on the search field Then the user can edit the text And a Clear icon button (e.g. X) is displayed And the search field contains the edited text And returns the new results Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user types on the search field When the user taps on the Clear icon button Then any existing text in the search field is cleared And the EUDI Wallet resets any previously applied search And the screen lists all transactions that respects the filtering and sorting already in force Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user previously searched for a text and results are displayed When the user search with an empty search field Then the EUDI Wallet resets any previously applied search And the screen lists all transactions that respects the filtering and sorting already in force 1: Search using the search field ({options=Relying Party name (attestation presentation)}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user taps on the search field When the user types a text Then the EUDI Wallet applies the search text to the attributes of Relying Party name (attestation presentation): And the transactions matching the search text are displayed And if no matching transactions are found, then the EUDI Wallet displays an informative message in the list section 2: Search using the search field ({options=Intermediary name (attestation presentation)}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user taps on the search field When the user types a text Then the EUDI Wallet applies the search text to the attributes of Intermediary name (attestation presentation): And the transactions matching the search text are displayed And if no matching transactions are found, then the EUDI Wallet displays an informative message in the list section 3: Search using the search field ({options=Document name (signing transactions)}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user taps on the search field When the user types a text Then the EUDI Wallet applies the search text to the attributes of Document name (signing transactions): And the transactions matching the search text are displayed And if no matching transactions are found, then the EUDI Wallet displays an informative message in the list section 4: Search using the search field ({options=PID Provider or Attestation Provider name (PID/attestation issuance and re-issuance transactions)}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user taps on the search field When the user types a text Then the EUDI Wallet applies the search text to the attributes of PID Provider or Attestation Provider name (PID/attestation issuance and re-issuance transactions): And the transactions matching the search text are displayed And if no matching transactions are found, then the EUDI Wallet displays an informative message in the list section 5: Search using the search field ({options=Attestation type (PID/attestation deletion)}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user taps on the search field When the user types a text Then the EUDI Wallet applies the search text to the attributes of Attestation type (PID/attestation deletion): And the transactions matching the search text are displayed And if no matching transactions are found, then the EUDI Wallet displays an informative message in the list section 6: Search using the search field ({options=Provider name (PID/attestation deletion)}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user taps on the search field When the user types a text Then the EUDI Wallet applies the search text to the attributes of Provider name (PID/attestation deletion): And the transactions matching the search text are displayed And if no matching transactions are found, then the EUDI Wallet displays an informative message in the list section 14 100%
Android > transaction log ARF alignment 193 > view transactions 328 > View Transactions in History tab 6 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the Home screen When the user clicks the History button Then the user navigates to the Transactions screen And all transactions are displayed 1: User views credential presentation transaction details ({Detail=Relying Party name, Description=The Interacting Party name with a verification badge next to it, for trusted Parties (if available)}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by Relying Party name and The Interacting Party name with a verification badge next to it, for trusted Parties (if available) 2: User views credential presentation transaction details ({Detail=Relying Party information, Description=URL, country and contact details (if available)}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by Relying Party information and URL, country and contact details (if available) 3: User views credential presentation transaction details ({Detail=Intermediary RP information, Description=Intermediary Relying Party information (if applicable)}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by Intermediary RP information and Intermediary Relying Party information (if applicable) 4: User views credential presentation transaction details ({Detail=DateTime, Description=The presentation operation was performed in ISO8601 format}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by DateTime and The presentation operation was performed in ISO8601 format 5: User views credential presentation transaction details ({Detail=Status, Description=The presentation result (Completed or Not Completed), reason of non-completion shown where available}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by Status and The presentation result (Completed or Not Completed), reason of non-completion shown where available 6: User views credential presentation transaction details ({Detail=Credential(s), Description=Each credential details shared presented as an expandable/collapsible card; only attribute identifiers displayed (no values)}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by Credential(s) and Each credential details shared presented as an expandable/collapsible card; only attribute identifiers displayed (no values) 7: User views credential presentation transaction details ({Detail=Intended use, Description=The purpose and privacy policy link, where available}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by Intended use and The purpose and privacy policy link, where available 8: User views credential presentation transaction details ({Detail=Transaction Data, Description=Transactional data displayed only if explicitly required by the applicable technical specification}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by Transaction Data and Transactional data displayed only if explicitly required by the applicable technical specification 9: User views credential presentation transaction details ({Detail="View previously attempted requests" and "Initiate Deletion Request" button, Description=The user can request deletion of personal data previously shared with the Relying Party (only for presentation transactions)}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by "View previously attempted requests" and "Initiate Deletion Request" button and The user can request deletion of personal data previously shared with the Relying Party (only for presentation transactions) 10: User views credential presentation transaction details ({Detail="View previously attempted requests" and "Initiate Transaction report" button, Description=The user can report any suspicious operations related to this presentation}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by "View previously attempted requests" and "Initiate Transaction report" button and The user can report any suspicious operations related to this presentation 1: User views signing/sealing transaction details ({Detail=DateTime, Description=The datetime the operation was performed}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a signing sealing transaction entry from the list Then the EUDI Wallet presents the following details by DateTime and The datetime the operation was performed 2: User views signing/sealing transaction details ({Detail=Purpose, Description=Purpose/type of the transaction, where applicable}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a signing sealing transaction entry from the list Then the EUDI Wallet presents the following details by Purpose and Purpose/type of the transaction, where applicable 3: User views signing/sealing transaction details ({Detail=Status, Description=The transaction result (Completed or Not Completed)}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a signing sealing transaction entry from the list Then the EUDI Wallet presents the following details by Status and The transaction result (Completed or Not Completed) 4: User views signing/sealing transaction details ({Detail=Relying Party, Description=The Interacting Party name}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a signing sealing transaction entry from the list Then the EUDI Wallet presents the following details by Relying Party and The Interacting Party name 5: User views signing/sealing transaction details ({Detail=signingTransactionIdentifier, Description=where applicable}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a signing sealing transaction entry from the list Then the EUDI Wallet presents the following details by signingTransactionIdentifier and where applicable 6: User views signing/sealing transaction details ({Detail=Document/data, Description=The document or data signed or sealed, if available}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a signing sealing transaction entry from the list Then the EUDI Wallet presents the following details by Document/data and The document or data signed or sealed, if available 1: User views credential (PID/attestation) issuance/re-issuance transaction details ({Detail=DateTime, Description=The date and time of the transaction}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential issuance or reissuance transaction entry from the list Then the EUDI Wallet presents the following details by DateTime and The date and time of the transaction 2: User views credential (PID/attestation) issuance/re-issuance transaction details ({Detail=Status, Description=The transaction result (Completed or Not Completed), reason of non-completion shown where available}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential issuance or reissuance transaction entry from the list Then the EUDI Wallet presents the following details by Status and The transaction result (Completed or Not Completed), reason of non-completion shown where available 3: User views credential (PID/attestation) issuance/re-issuance transaction details ({Detail=Interacting Party name, Description=i.e. PID Provider or Attestation Provider name}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential issuance or reissuance transaction entry from the list Then the EUDI Wallet presents the following details by Interacting Party name and i.e. PID Provider or Attestation Provider name 4: User views credential (PID/attestation) issuance/re-issuance transaction details ({Detail=Credential, Description=The credential requested and issued}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential issuance or reissuance transaction entry from the list Then the EUDI Wallet presents the following details by Credential and The credential requested and issued 5: User views credential (PID/attestation) issuance/re-issuance transaction details ({Detail=Re-issuance, Description=Whether User-triggered or automatically initiated by the Wallet Unit and Interacting Party contact details (if available)}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential issuance or reissuance transaction entry from the list Then the EUDI Wallet presents the following details by Re-issuance and Whether User-triggered or automatically initiated by the Wallet Unit and Interacting Party contact details (if available) 1: User views credential (PID/attestation) deletion transaction details ({Detail=DateTime, Description=The date and time of the deletion}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential deletion transaction entry from the list Then the EUDI Wallet presents the following details by DateTime and The date and time of the deletion 2: User views credential (PID/attestation) deletion transaction details ({Detail=Credential, Description=The credential deleted}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential deletion transaction entry from the list Then the EUDI Wallet presents the following details by Credential and The credential deleted 3: User views credential (PID/attestation) deletion transaction details ({Detail=Provider name, Description=The original PID Provider or Attestation Provider name}) Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential deletion transaction entry from the list Then the EUDI Wallet presents the following details by Provider name and The original PID Provider or Attestation Provider name Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is viewing the details of a transaction entry When the user presses the back button on top of the screen Then the user is returned to the History page 26 100%

Tags

US ISTR TC 11   1 US LT TC 02   1 US DTFTL TC 05   1 US IDDR TC 02   1 US VT   26 US ISTR TC 10   1 US LT TC 01   1 US IDDR   8 US DTFTL TC 06   1 US FAST TC 09   1 US VD   2 US PAIOACRPIRSD TC 01   2 US VT TC 06   1 US VPATR TC 01   1 US IDDR TC 01   1 PID Mso Mdoc   12 US ISTR TC 01   1 US LT TC 04   10 US FAST TC 08   1 US VT TC 05   3 US DTFTL TC 03   1 US IDDR TC 04   1 US VPATR TC 02   1 US VWCI TC 01   1 US ETESA   36 US FAST TC 07   1 US LT TC 03   3 US DS   2 US DTFTL TC 04   1 US VT TC 04   5 US IDDR TC 03   1 US VWCI TC 02   1 US ADBSQRC   2 US VPATR TC 03   1 US HS TC 01   1 US IMIOACIIRCASD   6 US ISTR   11 Q4 2024   1 US VT TC 03   6 US DTFTL TC 01   1 US IDDR TC 06   1 US VWCI TC 03   1 US RAAQESTD TC 02   1 US LT   21 US VPADDR TC 06   1 US VCSOTWS   4 US LT TC 05   6 Execution Q2 2026   24 US DTFTL TC 02   1 US VT TC 02   10 Q3 2026   137 Mdl   12 US IDDR TC 05   1 US ALOCWS TC 01   1 US RAAQESTD TC 01   1 US VPADDR TC 05   1 US VT TC 01   1 US ST   14 US IDDR TC 08   1 US VD TC 01   2 US SD   2 US VCSOTWS TC 04   1 US VPADDR   6 US VWTM TC 01   1 US IDDR TC 07   1 US FAST   9 US ISTR TC 07   1 US VPATR TC 09   1 US DS TC 01   2 US FAST TC 02   1 US PDO TC 01   1 US VCSOTWS TC 03   1 US VWTM TC 02   1 US VPADDR TC 02   1 US RAAQESTD TC 06   1 US ALOCWS TC 04   1 US DTFTL   10 US PAIOACRPIRSD   2 US PACSD TC 01   1 US ISTR TC 06   1 US VCSOTWS TC 02   1 US FAST TC 01   1 US PDO   1 US DTFTL TC 10   1 US VWTM TC 03   1 US VPADDR TC 01   1 US RAAQESTD TC 05   1 US VWCI   3 US SD TC 01   2 US ST TC 01   1 US DI   2 Manual   137 US ISTR TC 09   1 US VCSOTWS TC 01   1 GENERAL TESTS   21 US VPADDR TC 04   1 US VWTM TC 04   1 US RAAQESTD TC 04   1 US ALOCWS   4 US ALOCWS TC 02   1 US ST TC 02   4 PID Sdjwt   12 US HS   1 US ISTR TC 08   1 Q2 2025   8 Android   194 Automated   57 US VPADDR TC 03   1 US RAAQESTD TC 03   1 US VWTM   4 US ALOCWS TC 03   1 US ST TC 03   1 US FAST TC 06   1 US ISTR TC 03   1 US PACSD   1 US DTFTL TC 09   1 US VPATR TC 04   1 US ST TC 04   1 US FAST TC 05   1 US ISTR TC 02   1 US VPATR TC 05   1 US VPATR   9 US ADBSQRC TC 01   2 US ST TC 05   1 US FAST TC 04   1 US ISTR TC 05   1 US RAAQESTD   8 US DTFTL TC 07   1 US VPATR TC 07   1 US RAAQESTD TC 08   1 US VPATR TC 06   1 US ST TC 06   6 US DTFTL TC 08   1 US ISTR TC 04   1 US VPATR TC 08   1 US FAST TC 03   1 US DI TC 01   2 US RAAQESTD TC 07   1
Manual

Key Statistics

Number of Scenarios 109 Total Duration 12d 21h 21m 23s
Total Number of Test Cases 194 Fastest Test 6ms
Number of Manual Test Cases 137 Slowest Test 11m 9s
Tests Started Sep 23, 2026 14:08:24 Average Execution Time 1m 36s
Tests Finished Oct 06, 2026 11:29:48 Total Execution Time 5h 10m 54s

Automated Scenarios

## Scenario Context Steps StepsText Started Total Duration Result
Issuing and storing attestations in the EUDI Wallet via QR code Add a document to the EUDI Wallet by scanning a QR code
2 passing test cases
18 Given the user visits the Issuer service, generates a QR code for a PID attestation using <issuer> and returns to the Home screen of the Wallet When the user opens the Documents screen Then the Documents screen is displayed When the user taps the add document button on the Documents screen Then the wallet displays the Add document screen When the user selects the option to scan a QR code Then the wallet opens the scanner to scan the QR code rendered by the Issuer When the user scans a valid QR code rendered by the Issuer Then the wallet displays the credential offer with the attestation to be issued and the name of the issuer When the user selects the Cancel button on the credential offer Then the issuing process is canceled And the user is returned to the Documents screen When the user scans a valid QR code rendered by the Issuer And the user selects the Add document button on the credential offer Then the user proceeds with the attestation issuing flow And the wallet displays a success screen with the details of the issued attestation When the user closes the success screen Then the attestation is added to the EUDI Wallet 15:18:21 15m 40s SUCCESS
Deferred Credential Issuance Completing the deferred credential delivery process with Python Issuer
2 passing test cases
19 Given the user is accessing <issuer> service When the user chooses to deliver a deferred credential to the wallet with <issuer> Then the EUDI Wallet application is opened And the issuance information is displayed to the user for <issuer> Then the user selects the ISSUE button for <issuer> And the user is redirected to the issuer service for authentication and authorization for <issuer> When the user completes authentication and confirms the issuance for <issuer> And the user is navigated to the EUDI wallet application And a notification indicates that the credential request is being processed When the user dismisses the notification by pressing OK And the user is on the Home page And the document is displayed as unavailable with a pending status When the issuer provides the requested credential to the wallet Then the user receives a confirmation message indicating that the document has been issued When the user chooses to inspect the document details Then the issued credential information is displayed for <issuer> And the user presses the X button to close the document Then the document details are no longer displayed And the document appears on the documents screen for <issuer> 15:34:01 7m 24s SUCCESS
EUDI Wallet Documents Screen Documents screen consolidates and lists issued attestations
2 passing test cases
13 Given the user issues a <credential> attestation using <issuer> And the user issues the second attestation for <issuer> And the user is on the Home screen of the Wallet Then the bottom navigation bar shows the Home, Documents, and History tabs When the user opens the Documents screen Then the Documents tab becomes highlighted after selection And the Documents screen provides a Search bar And the Documents screen provides a Filter control And the Documents screen lists the issued attestations And the listed attestations are organized by category And each attestation card shows the attestation name, the issuer, and the validity end date When the user taps twice on an attestation from the list Then the attestation details are displayed 15:41:26 9m 23s SUCCESS
EUDI Wallet Home Screen Bottom navigation bar options 9 Given the user is viewing the EUDI Wallet Home screen Then the bottom navigation bar displays Home, Documents, and Transactions When the user chooses the Home option from the bottom navigation bar Then the Home option appears highlighted And the Home screen presents the Authenticate and Sign a document sections When the user taps the Authenticate section Then the Authenticate section provides In Person and Online options When the user selects the Sign a document section Then the Sign Document screen appears 15:50:49 51s 666ms SUCCESS
Issuance and presentation - mDL Successful credential issuance and presentation with selective disclosure - Python Issuer - mDL
6 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> and <issuance_method> 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> 14:09:33 45m 19s SUCCESS
Issuance and presentation - mDL Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - mDL
6 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> and <issuance_method> 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> 14:54:52 25m 45s SUCCESS
Issuance and presentation - PID (MSO Mdoc) Successful credential issuance and presentation with selective disclosure - Python Issuer - PID (MSO Mdoc)
6 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> and <issuance_method> 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> 14:08:35 50m 4s SUCCESS
Issuance and presentation - PID (MSO Mdoc) Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - PID (MSO Mdoc)
6 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> and <issuance_method> 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> 14:58:38 30m 18s SUCCESS
Issuance and presentation - PID (SD-JWT) Successful credential issuance and presentation with selective disclosure - Python Issuer - PID (SD-JWT)
6 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> and <issuance_method> 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> 14:08:24 35m 17s SUCCESS
Issuance and presentation - PID (SD-JWT) Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - PID (SD-JWT)
6 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> and <issuance_method> 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> 14:43:42 28m 9s SUCCESS
Batch Issuance of Attestations in EUDI Wallet Batch Issuance of Attestations in EUDI Wallet
6 passing test cases
10 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> and <issuance_method> When the issuance flow is completed Then the credential is stored in the Wallet And the issuer service generates multiple attestations And the Wallet shows a counter indicating the total number of attestations issued When the issuer advertised maximum batch size is below the Wallet internal minimum threshold Then the issuance process continues with the issuer's maximum batch size And the Wallet saves the attestations based on the issuer-defined batch size 15:51:41 25m 26s SUCCESS
Pre-authorization code same device User initiates credential issuance 14 Given the user is accessing the issuer service When the user selects to issue a document using pre-authorization Then the user provides their personal information And a transaction code is generated And the user chooses to register through the EUDI wallet app And the user is navigated to the EUDI wallet application And the user provides the PIN When the issuer request is shown in the wallet app Then the user selects ISSUE button And the Wallet app prompts for the transaction code And the user enters the transaction code received from the Issuer And the Wallet application shows a successful issuance message And the user selects the CONTINUE button Then the document appears on the documents screen 15:42:58 9m 16s SUCCESS
Presentation of Batch Issued Attestations in EUDI Wallet Relying Party initiated presentation flow
2 passing test cases
14 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> and <issuance_method> When the issuance flow is completed Then the credential is stored in the Wallet And the user accesses the Relying Party service through their mobile device using <verifier> When the user chooses to present an attestation type Then the Relying Party service navigates the user to the EUDI Wallet When the user is unable to authenticate using a six-digit PIN or Biometrics Then the Wallet displays an authentication error And the user is allowed to attempt the authentication again When the user verifies their identity using a six-digit PIN or Biometrics And the authentication is completed successfully Then the EUDI Wallet notifies the user that the Relying Party is requesting an attestation with <presentation_scenario> 16:22:51 6m 54s SUCCESS
EUDI Wallet Online Document Presentation User can cancel and then complete an online data sharing presentation
1 passing test case
17 Given the user issues a <credential> attestation using <issuer> And the user is on the Home screen of the Wallet And a Relying Party renders a presentation request as a QR code When the user opens the Online option from the Authenticate section And the Wallet scans the Relying Party's presentation request QR code Then the Wallet displays the attestation details requested for sharing When the user cancels the presentation request Then the user returns to the Wallet Home screen And a Relying Party renders a presentation request as a QR code When the user opens the Online option from the Authenticate section And the Wallet scans the Relying Party's presentation request QR code Then the Wallet displays the attestation details requested for sharing When the user selects the Share button And the user enters their six-digit PIN correctly Then a success message is displayed for the successful presentation of the PID When the user closes the success screen Then the user returns to the Wallet Home screen 16:29:46 3m 27s SUCCESS
Sign Document through EUDI Wallet Sign a document through the EUDI Wallet
2 passing test cases
13 Given the user uploads a document and an attestation using <issuer> and selects a QTSP When the EUDI Wallet fetches the Credential ID details from the QTSP Then the EUDI Wallet displays the Credential ID details to the user And the user agrees to proceed with the signing operation When the user opts not to proceed Then the user selects the Abort operation option And the EUDI Wallet redirects the user to the main page When the EUDI Wallet asks the user to consent to the release of the requested attestation And the user successfully authenticates in the Wallet Then the EUDI Wallet shares the requested attestation with the QTSP And a success screen appears with the signed document When the EUDI Wallet obtains the signed document Then the EUDI Wallet allows the user to share the document or close the process 16:33:12 10m 6s SUCCESS
View, bookmark and manage attestations in the EUDI Wallet View, bookmark, inspect and delete an attestation through the EUDI Wallet
2 passing test cases
21 Given the user issues a <credential> attestation using <issuer> And the user is on the Home screen of the Wallet When the user opens the Documents screen Then the Documents screen lists the issued attestations When the user taps on an attestation from the list Then the attestation details are displayed And the attestation details are blurred by default And an eye icon is shown to reveal the attestation details When the user taps on the eye icon Then the attestation details are no longer blurred And the user can view the full attestation details When the user taps the bookmark icon on the attestation Then the attestation gets marked as bookmarked And the bookmark icon updates to indicate the bookmarked state When the user opens the issuer details from the attestation Then the issuer details are displayed to the user When the user closes the attestation details without deleting it Then the user lands back on the Documents screen When the user reopens the attestation and selects the delete option Then the attestation gets removed from the EUDI Wallet And the Documents screen no longer lists the deleted attestation 16:43:19 7m 30s SUCCESS

Manual Tests

## Scenario Context Steps StepsText Result
Access the official list of certified Wallet Solutions Display Trust Mark when opening the Wallet for the first time 4 Given the user opens the Wallet for the first time Then the Wallet displays the Trust Mark view When the user selects Continue Then the Wallet displays the Login screen SUCCESS
Access the official list of certified Wallet Solutions Access Trust Mark from the Wallet menu 3 Given the authenticated user is on the Wallet home screen When the user selects the burger menu and chooses About EUDI Wallet Then the Wallet displays the Trust Mark view SUCCESS
Access the official list of certified Wallet Solutions Display EUDI Wallet Provider Trusted List link 3 Given the user is viewing the Trust Mark screen When the Trust Mark content is displayed Then the Wallet displays a link to the EUDI Wallet Provider Trusted List SUCCESS
Access the official list of certified Wallet Solutions Open the certified Wallet Solutions list 4 Given the EUDI Wallet Provider Trusted List link is displayed When the user selects the link Then the Wallet opens the European Commission-hosted webpage in an external browser or supported web view And the webpage allows the user to view the officially certified Wallet Solutions SUCCESS
Access Wallet Solution certification status information Display Trust Mark when opening the Wallet for the first time 4 Given the user opens the Wallet for the first time Then the Wallet displays the Trust Mark view When the user selects Continue Then the Wallet displays the Login screen SUCCESS
Access Wallet Solution certification status information Access Trust Mark from the Wallet menu 3 Given the authenticated user is on the Wallet home screen When the user selects the burger menu and chooses About EUDI Wallet Then the Wallet displays the Trust Mark view SUCCESS
Access Wallet Solution certification status information Display certification information link 3 Given the user is viewing the Trust Mark screen When the Trust Mark content is displayed Then the Wallet displays a link to the Wallet Solution certification information page SUCCESS
Access Wallet Solution certification status information Open Wallet certification information 4 Given the certification information link is displayed in the Trust Mark view When the user selects the certification information link Then the Wallet opens the European Commission-hosted certification information page in an external browser or supported web view And the page allows the user to verify the certification status of the Wallet Solution SUCCESS
View Wallet Solution certification information Display Trust Mark when opening the Wallet for the first time 4 Given the user opens the Wallet for the first time Then the Wallet displays the Trust Mark view When the user selects Continue Then the Wallet displays the Login screen SUCCESS
View Wallet Solution certification information Access Trust Mark from the Wallet menu 3 Given the authenticated user is on the Wallet home screen When the user selects the burger menu and chooses About EUDI Wallet Then the Wallet displays the Trust Mark view SUCCESS
View Wallet Solution certification information Display Wallet certification information 4 Given the user is viewing the Trust Mark screen When the Trust Mark content is displayed Then the Wallet displays general informational text explaining the certification of Wallet Solutions within the EUDI Wallet ecosystem And the informational text is displayed according to the device language settings SUCCESS
View Wallet Trust Mark Display Trust Mark when opening the Wallet for the first time 4 Given the user opens the Wallet for the first time Then the Wallet displays the Trust Mark view When the user selects Continue Then the Wallet displays the Login screen SUCCESS
View Wallet Trust Mark Access Trust Mark from the Wallet menu 3 Given the authenticated user is on the Wallet home screen When the user selects the burger menu and chooses About EUDI Wallet Then the Wallet displays the Trust Mark view SUCCESS
View Wallet Trust Mark Display Wallet Trust Mark information 5 Given the user is viewing the Trust Mark screen When the Trust Mark content is displayed Then the Wallet displays the official EU Digital Identity Wallet Trust Mark graphics or logo And the Wallet displays informational text according to the device language settings And the Wallet provides links to certification status information SUCCESS
View Wallet Trust Mark Return to the Wallet home screen 3 Given the user is viewing the Trust Mark screen When the user selects the back arrow Then the Wallet returns to the Wallet home screen SUCCESS
Initiate a data deletion request Display Presentation Information 5 Given the authenticated user has selected a presentation transaction from the Wallet History When the Presentation Information screen is displayed Then the Wallet displays the intended use of the presentation request And the Wallet displays the applicable privacy policy when available And the Wallet displays the attributes shared during the presentation transaction SUCCESS
Initiate a data deletion request Display Initiate Deletion Request button 3 Given the authenticated user has selected a presentation transaction from the Wallet History When the user views the Presentation Information screen Then the Wallet displays the Initiate Deletion Request button SUCCESS
Initiate a data deletion request Display informational screen before leaving the Wallet 7 Given user views the presentation information screen When the user selects the Initiate Deletion Request button Then the Wallet displays an informational screen explaining that the user is about to leave the Wallet And explains that the Wallet facilitates the initiation of the request by opening the appropriate communication channel And states that the Wallet does not submit, manage or track the request And states that the user is responsible for completing and submitting the request outside the Wallet And states that the Relying Party is responsible for evaluating and processing the request SUCCESS
Initiate a data deletion request Display single action button for Website communication method 3 Given the WRPRC contains a website for the Relying Party When the Wallet displays the informational screen Then the Wallet displays a single action button Continue to [Relying Party]'s website SUCCESS
Initiate a data deletion request Use Website as the preferred communication method 3 Given the WRPRC contains a website for the Relying Party When the user selects the Continue to [Relying Party]'s website button Then the Wallet opens the Relying Party website in the device's default browser SUCCESS
Initiate a data deletion request Return to Presentation Information using Back navigation 3 Given the user is viewing the informational screen When the user selects the Back navigation button Then the Wallet returns to the Presentation Information screen SUCCESS
Initiate a data deletion request Record data deletion request initiation 3 Given the user has initiated a data deletion request When the selected external application is successfully launched Then the Wallet records the data deletion request initiation SUCCESS
Initiate a data deletion request Disable deletion request when contact information cannot be retrieved 4 Given contact information are not available in the WRPRC When contact information cannot be retrieved from the WRPRC Then the data deletion request cannot be initiated And the Initiate Deletion Request button in is disabled SUCCESS
View previously attempted data deletion requests Display Presentation Information 3 Given the authenticated user has presentation transactions in the Wallet History When the user selects a presentation transaction Then the Wallet displays the Presentation Information for the selected transaction SUCCESS
View previously attempted data deletion requests Display previously attempted requests link 3 Given the selected presentation transaction has one or more recorded data deletion request attempts When the user views the Presentation Information screen Then the Wallet displays the View previously attempted requests link SUCCESS
View previously attempted data deletion requests Hide previously attempted requests link when no attempts exist 3 Given the selected presentation transaction has no recorded data deletion request attempts When the user views the Presentation Information screen Then the Wallet does not display the View previously attempted requests link SUCCESS
View previously attempted data deletion requests Display Data Deletion Request History information 6 Given the selected presentation transaction has one or more recorded data deletion request attempts When the user selects the View previously attempted requests link Then the Wallet opens the Data Deletion Request History screen And the Wallet displays the corresponding title And the Wallet displays explanatory text above the list of previous attempts And the Wallet displays the previous attempts associated with the selected presentation transaction SUCCESS
View previously attempted data deletion requests Display details for previous data deletion request attempts 4 Given the Data Deletion Request History screen contains previous attempts When the user views the list of previous attempts Then each attempt displays the date of the attempt And each attempt displays the communication method used SUCCESS
View previously attempted data deletion requests Return to Presentation Information 3 Given the user is viewing the Data Deletion Request History screen When the user selects the Back navigation option Then the Wallet returns to the Presentation Information screen SUCCESS
Initiate a report for an unlawful or suspicious data request View Presentation Information from History 3 Given the authenticated user has presentation transactions in the Wallet History When the user selects a presentation transaction from the History screen Then the Wallet displays the Presentation Information for the selected transaction SUCCESS
Initiate a report for an unlawful or suspicious data request Display Presentation Information details 5 Given the user has selected a presentation transaction from the History screen When the Presentation Information screen is displayed Then the Wallet displays the intended use of the presentation request And the Wallet displays the applicable privacy policy And the Wallet displays the attributes shared during the presentation transaction SUCCESS
Initiate a report for an unlawful or suspicious data request Display the "Initiate Transaction Report" button for a successful presentation transaction 3 Given the user selects a presentation transaction When the user views the Presentation Information screen Then the Wallet displays the Initiate Transaction Report button SUCCESS
Initiate a report for an unlawful or suspicious data request Open the transaction report information screen 3 Given the user is viewing the Presentation Information for a presentation transaction When the user selects the Initiate Transaction Report button Then the Wallet displays the transaction report information screen SUCCESS
Initiate a report for an unlawful or suspicious data request Display transaction report information 5 Given the transaction report information screen has been opened When the screen content is displayed Then the Wallet identifies the responsible Data Protection Authority And the Wallet informs the user that the Wallet does not submit or track the report And the Wallet informs the user that the report must be completed directly with the identified Data Protection Authority SUCCESS
Initiate a report for an unlawful or suspicious data request Display all available communication methods 3 Given the responsible Data Protection Authority provides website, email, and phone contact information When the Wallet displays the communication methods Then the Wallet displays Website, Email, and Phone as available options SUCCESS
Initiate a report for an unlawful or suspicious data request Open the DPA reporting website 3 Given the Website communication method is available When the user selects the Website communication method Then the Wallet opens the DPA reporting website in the device's default browser SUCCESS
Initiate a report for an unlawful or suspicious data request Open the default email application 6 Given the Email communication method is available When the user selects the Email communication method Then the Wallet opens the device's default email application with a pre-filled email And the pre-filled email contains the Data Protection Authority email address And the pre-filled email subject indicates an allegedly unlawful or suspicious presentation request And the pre-filled email content identifies the relevant Relying Party SUCCESS
Initiate a report for an unlawful or suspicious data request Open the phone application with the DPA telephone number 3 Given the Phone communication method is available When the user selects the Phone communication method Then the Wallet opens the device's phone application using the DPA telephone number SUCCESS
Initiate a report for an unlawful or suspicious data request Record the transaction report initiation after successful external application launch 3 Given the user has selected an available communication method When the corresponding external application is successfully launched Then the Wallet records the transaction report initiation SUCCESS
Initiate a report for an unlawful or suspicious data request Return to Presentation Information using Back navigation 3 Given the user is viewing the transaction report information screen When the user selects the Back navigation option Then the Wallet returns to the Presentation Information screen SUCCESS
View previously attempted transaction reports View Presentation Information from History 3 Given the authenticated user has presentation transactions in the Wallet History When the user selects a presentation transaction from the History screen Then the Wallet displays the Presentation Information for the selected transaction SUCCESS
View previously attempted transaction reports Display the "View previously attempted requests" link when previous attempts exist 3 Given the selected presentation transaction has one or more recorded transaction report attempts When the user views the Presentation Information screen Then the Wallet displays the corresponding link SUCCESS
View previously attempted transaction reports Do not display the "View previously attempted requests" link when no previous attempts exist 3 Given the selected presentation transaction has no recorded transaction report attempts When the user views the Presentation Information screen Then the Wallet does not display the corresponding link SUCCESS
View previously attempted transaction reports Open transaction report History 3 Given the selected presentation transaction has one or more recorded transaction report attempts When the user selects the View previously attempted requests link Then the Wallet opens the transaction report History screen SUCCESS
View previously attempted transaction reports Display the transaction report History title 3 Given the user has opened the transaction report History for a selected presentation transaction When the transaction report History screen is displayed Then the title is displayed as Previous transaction report for [Relying Party Name] SUCCESS
View previously attempted transaction reports Display explanatory text for previous transaction report attempts 3 Given the user has opened the transaction report History for a selected presentation transaction When the transaction report History screen is displayed Then explanatory text is displayed above the list of previous attempts SUCCESS
View previously attempted transaction reports Display previous transaction reports associated with the selected presentation transaction 4 Given previous transaction report attempts are associated with the selected presentation transaction When the user opens the transaction report History screen Then the Wallet displays only the previous transaction report attempts associated with the selected presentation transaction And each transaction report attempt displays the date of the attempt SUCCESS
View previously attempted transaction reports Display the communication method for each previous transaction report attempt 4 Given the selected presentation transaction has previously attempted transaction reports When the transaction report History screen displays the previous attempts Then each transaction report attempt displays the communication method used And the Wallet does not display any indication of its completion, submission, or processing status SUCCESS
View previously attempted transaction reports Return to Presentation Information using Back navigation 3 Given the user is viewing the transaction report History screen When the user selects the Back navigation option Then the Wallet returns to the Presentation Information screen for the selected transaction SUCCESS
Delete a transaction from transaction log Delete button is displayed 6 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry from the list Then the transaction details screen opens And a delete button is visible in the top right corner SUCCESS
Delete a transaction from transaction log Warning dialog appears before deletion 6 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user has opened the details screen of a transaction When the user clicks the delete button Then a confirmation dialog is displayed And no transaction is removed yet SUCCESS
Delete a transaction from transaction log Warning dialog content and options are displayed 5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the confirmation dialog is displayed Then the dialog include a warning message indicating the consequences of deleting the transaction And the dialog provides a Confirm deletion button and a Cancel button SUCCESS
Delete a transaction from transaction log User cancels the deletion 7 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the confirmation dialog is displayed for a transaction When the user selects Cancel Then the dialog closes And the user remains on the details screen of the same transaction And the transaction log is unchanged SUCCESS
Delete a transaction from transaction log Cancelled transaction still appears in the list 5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user has cancelled the deletion of a transaction When the user navigates back to the History screen Then the transaction is still visible in the list SUCCESS
Delete a transaction from transaction log User confirms the deletion of a transaction 7 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the confirmation dialog is displayed for a transaction When the user selects Confirm deletion Then the dialog closes And the user is returned to the History screen And the transaction is no longer shown in the list SUCCESS
Delete a transaction from transaction log Deleted transaction is not retrievable via search, filter or sort 5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user has deleted a transaction and knows its relying party name, type, status and date When the user searches for it or applies matching filters Then the deleted transaction is not returned in any of the search or filter SUCCESS
Delete a transaction from transaction log Deleting the only remaining transaction empties the log 5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the transaction log contains exactly one transaction When the user deletes that transaction and confirms Then the history screen shows the empty state message SUCCESS
Delete a transaction from transaction log Deleting a transaction keeps the active filter or search applied 7 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user reached a transaction through an active search or filter When the user deletes that transaction and confirms Then the user returns to the same filtered or search view And the deleted transaction is missing from the results And the other results remain displayed SUCCESS
Delete a transaction from transaction log Deletion flow is uniform across all transaction categories 6 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user has one transaction of each category available When the user deletes them one by one via the delete button and confirmation dialog Then the same warning dialog appear for every category And each transaction disappears from the list search and filters SUCCESS
Filter and Sort Transactions in History tab Initial state of filter option 6 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user enters the History screen Then no filter is applied, the default option And the transactions are sorted by transaction date descending, the default sort option And the filter button has no visual indication that a user filter option is applied SUCCESS
Filter and Sort Transactions in History tab Display filter bottom sheet 7 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user taps the filter button Then the filter bottom sheet options slide up from the bottom screen And the filter options are displayed in separate sections And each section under the title displays the available filter options SUCCESS
Filter and Sort Transactions in History tab Filter transactions by Transaction Date Period 5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the filter bottom sheet When the user selects to filter by Date Then the user can select the date range (date from and date to) using a calendar SUCCESS
Filter and Sort Transactions in History tab Filter transactions by status 5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the filter bottom sheet When the user selects to filter by Status Then the user can select an operation status option to filter the transactions SUCCESS
Filter and Sort Transactions in History tab Filter transactions by relying party 5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the filter bottom sheet When the user selects to filter by Relying Party Then the user can filter the transactions by selecting or deselecting the corresponding parties listed SUCCESS
Filter and Sort Transactions in History tab Filter transactions by transaction type 6 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the filter bottom sheet When the user selects to filter by Transaction Type Then a list of all supported transaction types is displayed And the user can filter by selecting or deselecting the corresponding types listed SUCCESS
Filter and Sort Transactions in History tab Reset all filter options 6 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the filter bottom sheet When the user taps the Reset all button Then the filters are reset to the default values And the filter button has no visual indication that a user filter option is applied SUCCESS
Filter and Sort Transactions in History tab Apply filter options 7 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the filter bottom sheet When the user taps the Apply button Then the bottom sheet slides down and disappears And the EUDI Wallet applies a filter options to the transactions list And the filter button has visual indication that user filter options have been applied SUCCESS
Filter and Sort Transactions in History tab No matching transactions found 6 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user applies a filter option When no matching transactions are found Then the EUDI Wallet displays an informative message in the list section And if no results are found within a period group, then the period group is not displayed SUCCESS
List Transactions in History tab History button in bottom navigation bar 6 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the EUDI Wallet main screen When the user selects the History option in the bottom navigation bar Then the History button is highlighted And the History screen is displayed SUCCESS
List Transactions in History tab History screen content 5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the History screen includes a Search bar And the History screen includes a Filter button SUCCESS
List Transactions in History tab 1: History screen lists transactions grouped by period
Group=Today, Description=Transactions that occurred today 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the transactions are listed grouped by period as follows by Today and Transactions that occurred today And the transactions are sorted in chronological order within each group SUCCESS
List Transactions in History tab 2: History screen lists transactions grouped by period
Group=This Week, Description=Transactions that occurred this week 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the transactions are listed grouped by period as follows by This Week and Transactions that occurred this week And the transactions are sorted in chronological order within each group SUCCESS
List Transactions in History tab 3: History screen lists transactions grouped by period
Group=Month, Description=Transactions grouped by month 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the transactions are listed grouped by period as follows by Month and Transactions grouped by month And the transactions are sorted in chronological order within each group SUCCESS
List Transactions in History tab 1: User views transaction entry details
Detail=Transaction Type, Description=presentation, issuance, signing, deletion, etc. 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Transaction Type and presentation, issuance, signing, deletion, etc. SUCCESS
List Transactions in History tab 2: User views transaction entry details
Detail=Status, Description=The transaction result, Completed or Not Completed 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Status and The transaction result, Completed or Not Completed SUCCESS
List Transactions in History tab 3: User views transaction entry details
Detail=Relying Party, Description=The Relying Party name or document name as follows: 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Relying Party and The Relying Party name or document name as follows: SUCCESS
List Transactions in History tab 4: User views transaction entry details
Detail=Relying Party, Description=For presentation transactions: 'Service Provider name' 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Relying Party and For presentation transactions: 'Service Provider name' SUCCESS
List Transactions in History tab 5: User views transaction entry details
Detail=Relying Party, Description=For issuance transactions: 'PID Provider or Attestation Provider name' 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Relying Party and For issuance transactions: 'PID Provider or Attestation Provider name' SUCCESS
List Transactions in History tab 6: User views transaction entry details
Detail=Relying Party, Description=For signing transactions: 'Signing Service Provider name' 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Relying Party and For signing transactions: 'Signing Service Provider name' SUCCESS
List Transactions in History tab 7: User views transaction entry details
Detail=Datetime, Description=The datetime of the transaction as follows: 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Datetime and The datetime of the transaction as follows: SUCCESS
List Transactions in History tab 8: User views transaction entry details
Detail=Datetime, Description=X minutes ago for transactions in the last 60 minutes 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Datetime and X minutes ago for transactions in the last 60 minutes SUCCESS
List Transactions in History tab 9: User views transaction entry details
Detail=Datetime, Description=Time (e.g., 11:07 AM) for transactions within the day 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Datetime and Time (e.g., 11:07 AM) for transactions within the day SUCCESS
List Transactions in History tab 10: User views transaction entry details
Detail=Datetime, Description=Datetime (e.g., 14 Feb 2024 11:07 AM) for transactions before today 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a transaction entry Then a card is displayed for each transaction entry including Datetime and Datetime (e.g., 14 Feb 2024 11:07 AM) for transactions before today SUCCESS
List Transactions in History tab 1: Transaction types displayed on the History screen
Type=Credential (PID or attestation) issuance and re-issuance transactions, Displayed=Y 		4 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the transaction type Credential (PID or attestation) issuance and re-issuance transactions is Y on the History screen SUCCESS
List Transactions in History tab 2: Transaction types displayed on the History screen
Type=PID or attestation presentation transactions, Displayed=Y 		4 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the transaction type PID or attestation presentation transactions is Y on the History screen SUCCESS
List Transactions in History tab 3: Transaction types displayed on the History screen
Type=Signature or seal creation transactions, Displayed=Y 		4 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the transaction type Signature or seal creation transactions is Y on the History screen SUCCESS
List Transactions in History tab 4: Transaction types displayed on the History screen
Type=Data deletion requests sent to a Relying Party, Displayed=N 		4 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the transaction type Data deletion requests sent to a Relying Party is N on the History screen SUCCESS
List Transactions in History tab 5: Transaction types displayed on the History screen
Type=Suspicious Transaction Reports sent to a Data Protection Authority, Displayed=N 		4 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the transaction type Suspicious Transaction Reports sent to a Data Protection Authority is N on the History screen SUCCESS
List Transactions in History tab 6: Transaction types displayed on the History screen
Type=Credential (PID or attestation) deletion by the User, Displayed=Y 		4 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen Then the transaction type Credential (PID or attestation) deletion by the User is Y on the History screen SUCCESS
Transaction Search in History tab Initial state of the History screen 7 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the Home screen When the user clicks the History button Then the History screen is displayed And all transactions are displayed And no search or filters are applied SUCCESS
Transaction Search in History tab 1: History screen display features
options=the transactions are grouped by period 		6 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user observes the transactions screen Then the following are displayed the transactions are grouped by period: And if there are no transactions for a period group, then this group is not displayed SUCCESS
Transaction Search in History tab 2: History screen display features
options=the search field is empty and enabled 		6 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user observes the transactions screen Then the following are displayed the search field is empty and enabled: And if there are no transactions for a period group, then this group is not displayed SUCCESS
Transaction Search in History tab 3: History screen display features
options=the search field contains a search icon on the left side 		6 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user observes the transactions screen Then the following are displayed the search field contains a search icon on the left side: And if there are no transactions for a period group, then this group is not displayed SUCCESS
Transaction Search in History tab 4: History screen display features
options=the search field displays a hinted search text "Search" 		6 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user observes the transactions screen Then the following are displayed the search field displays a hinted search text "Search": And if there are no transactions for a period group, then this group is not displayed SUCCESS
Transaction Search in History tab Edit previous search text 8 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user previously searched for a text When the user taps on the search field Then the user can edit the text And a Clear icon button (e.g. X) is displayed And the search field contains the edited text And returns the new results SUCCESS
Transaction Search in History tab Search field "Clear" icon button 7 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user types on the search field When the user taps on the Clear icon button Then any existing text in the search field is cleared And the EUDI Wallet resets any previously applied search And the screen lists all transactions that respects the filtering and sorting already in force SUCCESS
Transaction Search in History tab Search with empty search field 6 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user previously searched for a text and results are displayed When the user search with an empty search field Then the EUDI Wallet resets any previously applied search And the screen lists all transactions that respects the filtering and sorting already in force SUCCESS
Transaction Search in History tab 1: Search using the search field
options=Relying Party name (attestation presentation) 		7 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user taps on the search field When the user types a text Then the EUDI Wallet applies the search text to the attributes of Relying Party name (attestation presentation): And the transactions matching the search text are displayed And if no matching transactions are found, then the EUDI Wallet displays an informative message in the list section SUCCESS
Transaction Search in History tab 2: Search using the search field
options=Intermediary name (attestation presentation) 		7 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user taps on the search field When the user types a text Then the EUDI Wallet applies the search text to the attributes of Intermediary name (attestation presentation): And the transactions matching the search text are displayed And if no matching transactions are found, then the EUDI Wallet displays an informative message in the list section SUCCESS
Transaction Search in History tab 3: Search using the search field
options=Document name (signing transactions) 		7 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user taps on the search field When the user types a text Then the EUDI Wallet applies the search text to the attributes of Document name (signing transactions): And the transactions matching the search text are displayed And if no matching transactions are found, then the EUDI Wallet displays an informative message in the list section SUCCESS
Transaction Search in History tab 4: Search using the search field
options=PID Provider or Attestation Provider name (PID/attestation issuance and re-issuance transactions) 		7 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user taps on the search field When the user types a text Then the EUDI Wallet applies the search text to the attributes of PID Provider or Attestation Provider name (PID/attestation issuance and re-issuance transactions): And the transactions matching the search text are displayed And if no matching transactions are found, then the EUDI Wallet displays an informative message in the list section SUCCESS
Transaction Search in History tab 5: Search using the search field
options=Attestation type (PID/attestation deletion) 		7 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user taps on the search field When the user types a text Then the EUDI Wallet applies the search text to the attributes of Attestation type (PID/attestation deletion): And the transactions matching the search text are displayed And if no matching transactions are found, then the EUDI Wallet displays an informative message in the list section SUCCESS
Transaction Search in History tab 6: Search using the search field
options=Provider name (PID/attestation deletion) 		7 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user taps on the search field When the user types a text Then the EUDI Wallet applies the search text to the attributes of Provider name (PID/attestation deletion): And the transactions matching the search text are displayed And if no matching transactions are found, then the EUDI Wallet displays an informative message in the list section SUCCESS
View Transactions in History tab User navigates to the History screen 6 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the Home screen When the user clicks the History button Then the user navigates to the Transactions screen And all transactions are displayed SUCCESS
View Transactions in History tab 1: User views credential presentation transaction details
Detail=Relying Party name, Description=The Interacting Party name with a verification badge next to it, for trusted Parties (if available) 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by Relying Party name and The Interacting Party name with a verification badge next to it, for trusted Parties (if available) SUCCESS
View Transactions in History tab 2: User views credential presentation transaction details
Detail=Relying Party information, Description=URL, country and contact details (if available) 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by Relying Party information and URL, country and contact details (if available) SUCCESS
View Transactions in History tab 3: User views credential presentation transaction details
Detail=Intermediary RP information, Description=Intermediary Relying Party information (if applicable) 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by Intermediary RP information and Intermediary Relying Party information (if applicable) SUCCESS
View Transactions in History tab 4: User views credential presentation transaction details
Detail=DateTime, Description=The presentation operation was performed in ISO8601 format 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by DateTime and The presentation operation was performed in ISO8601 format SUCCESS
View Transactions in History tab 5: User views credential presentation transaction details
Detail=Status, Description=The presentation result (Completed or Not Completed), reason of non-completion shown where available 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by Status and The presentation result (Completed or Not Completed), reason of non-completion shown where available SUCCESS
View Transactions in History tab 6: User views credential presentation transaction details
Detail=Credential(s), Description=Each credential details shared presented as an expandable/collapsible card; only attribute identifiers displayed (no values) 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by Credential(s) and Each credential details shared presented as an expandable/collapsible card; only attribute identifiers displayed (no values) SUCCESS
View Transactions in History tab 7: User views credential presentation transaction details
Detail=Intended use, Description=The purpose and privacy policy link, where available 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by Intended use and The purpose and privacy policy link, where available SUCCESS
View Transactions in History tab 8: User views credential presentation transaction details
Detail=Transaction Data, Description=Transactional data displayed only if explicitly required by the applicable technical specification 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by Transaction Data and Transactional data displayed only if explicitly required by the applicable technical specification SUCCESS
View Transactions in History tab 9: User views credential presentation transaction details
Detail="View previously attempted requests" and "Initiate Deletion Request" button, Description=The user can request deletion of personal data previously shared with the Relying Party (only for presentation transactions) 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by "View previously attempted requests" and "Initiate Deletion Request" button and The user can request deletion of personal data previously shared with the Relying Party (only for presentation transactions) SUCCESS
View Transactions in History tab 10: User views credential presentation transaction details
Detail="View previously attempted requests" and "Initiate Transaction report" button, Description=The user can report any suspicious operations related to this presentation 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential presentation transaction entry from the list Then the EUDI Wallet presents the following details by "View previously attempted requests" and "Initiate Transaction report" button and The user can report any suspicious operations related to this presentation SUCCESS
View Transactions in History tab 1: User views signing/sealing transaction details
Detail=DateTime, Description=The datetime the operation was performed 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a signing sealing transaction entry from the list Then the EUDI Wallet presents the following details by DateTime and The datetime the operation was performed SUCCESS
View Transactions in History tab 2: User views signing/sealing transaction details
Detail=Purpose, Description=Purpose/type of the transaction, where applicable 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a signing sealing transaction entry from the list Then the EUDI Wallet presents the following details by Purpose and Purpose/type of the transaction, where applicable SUCCESS
View Transactions in History tab 3: User views signing/sealing transaction details
Detail=Status, Description=The transaction result (Completed or Not Completed) 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a signing sealing transaction entry from the list Then the EUDI Wallet presents the following details by Status and The transaction result (Completed or Not Completed) SUCCESS
View Transactions in History tab 4: User views signing/sealing transaction details
Detail=Relying Party, Description=The Interacting Party name 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a signing sealing transaction entry from the list Then the EUDI Wallet presents the following details by Relying Party and The Interacting Party name SUCCESS
View Transactions in History tab 5: User views signing/sealing transaction details
Detail=signingTransactionIdentifier, Description=where applicable 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a signing sealing transaction entry from the list Then the EUDI Wallet presents the following details by signingTransactionIdentifier and where applicable SUCCESS
View Transactions in History tab 6: User views signing/sealing transaction details
Detail=Document/data, Description=The document or data signed or sealed, if available 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a signing sealing transaction entry from the list Then the EUDI Wallet presents the following details by Document/data and The document or data signed or sealed, if available SUCCESS
View Transactions in History tab 1: User views credential (PID/attestation) issuance/re-issuance transaction details
Detail=DateTime, Description=The date and time of the transaction 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential issuance or reissuance transaction entry from the list Then the EUDI Wallet presents the following details by DateTime and The date and time of the transaction SUCCESS
View Transactions in History tab 2: User views credential (PID/attestation) issuance/re-issuance transaction details
Detail=Status, Description=The transaction result (Completed or Not Completed), reason of non-completion shown where available 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential issuance or reissuance transaction entry from the list Then the EUDI Wallet presents the following details by Status and The transaction result (Completed or Not Completed), reason of non-completion shown where available SUCCESS
View Transactions in History tab 3: User views credential (PID/attestation) issuance/re-issuance transaction details
Detail=Interacting Party name, Description=i.e. PID Provider or Attestation Provider name 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential issuance or reissuance transaction entry from the list Then the EUDI Wallet presents the following details by Interacting Party name and i.e. PID Provider or Attestation Provider name SUCCESS
View Transactions in History tab 4: User views credential (PID/attestation) issuance/re-issuance transaction details
Detail=Credential, Description=The credential requested and issued 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential issuance or reissuance transaction entry from the list Then the EUDI Wallet presents the following details by Credential and The credential requested and issued SUCCESS
View Transactions in History tab 5: User views credential (PID/attestation) issuance/re-issuance transaction details
Detail=Re-issuance, Description=Whether User-triggered or automatically initiated by the Wallet Unit and Interacting Party contact details (if available) 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential issuance or reissuance transaction entry from the list Then the EUDI Wallet presents the following details by Re-issuance and Whether User-triggered or automatically initiated by the Wallet Unit and Interacting Party contact details (if available) SUCCESS
View Transactions in History tab 1: User views credential (PID/attestation) deletion transaction details
Detail=DateTime, Description=The date and time of the deletion 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential deletion transaction entry from the list Then the EUDI Wallet presents the following details by DateTime and The date and time of the deletion SUCCESS
View Transactions in History tab 2: User views credential (PID/attestation) deletion transaction details
Detail=Credential, Description=The credential deleted 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential deletion transaction entry from the list Then the EUDI Wallet presents the following details by Credential and The credential deleted SUCCESS
View Transactions in History tab 3: User views credential (PID/attestation) deletion transaction details
Detail=Provider name, Description=The original PID Provider or Attestation Provider name 		5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is on the History screen When the user selects a credential deletion transaction entry from the list Then the EUDI Wallet presents the following details by Provider name and The original PID Provider or Attestation Provider name SUCCESS
View Transactions in History tab Details screen back button 5 Given the user is registered to a valid EUDI Wallet on their mobile device And the user is authenticated in the EUDI Wallet Given the user is viewing the details of a transaction entry When the user presses the back button on top of the screen Then the user is returned to the History page SUCCESS
Review and authorise QES transaction data Display QES transaction information before authorisation 4 Given the user has initiated a QES signing operation When the Wallet presents the transaction information for review Then the Wallet displays the QES transaction type and applicable trust framework And the Wallet displays the document name or description SUCCESS
Review and authorise QES transaction data Provide access to the document to be signed 3 Given the QES transaction contains a reference to the document to be signed where provided When the Wallet presents the transaction information Then the user can access the document associated with the signing transaction PENDING
Review and authorise QES transaction data Display document and signing information when available 4 Given the QES transaction contains additional document or signing information When the Wallet presents the transaction information for review Then the Wallet displays the applicable DTBSR information And the Wallet displays the signed attributes and requested credentials where applicable SUCCESS
Review and authorise QES transaction data Display additional QES transaction information when available 6 Given optional QES transaction information is provided When the Wallet presents the transaction information for review Then the Wallet displays the OTP where provided And the Wallet displays the Response URI where applicable And the Wallet displays the document integrity status And the Wallet displays the signature format and conformance level where provided PENDING
Review and authorise QES transaction data Approve the QES transaction 3 Given the user has reviewed the transaction information and document When the user explicitly approves the QES transaction Then the Wallet continues the QES signing process SUCCESS
Review and authorise QES transaction data Reject the QES transaction 3 Given the user is reviewing the QES transaction When the user rejects or cancels the transaction Then the QES signing operation does not proceed SUCCESS
Review and authorise QES transaction data Record the QES transaction in the Transaction Log 3 Given the QES transaction has been completed When the user accesses the Transaction Log Then the QES transaction is available in the Transaction Log SUCCESS
Review and authorise QES transaction data Display recorded QES transaction information 4 Given the QES transaction is available in the Transaction Log When the user opens the recorded QES transaction Then the Wallet displays the relevant Transaction Data associated with the transaction And the Wallet displays the user's recorded decision to approve or reject the transaction SUCCESS

Tags

US ISTR TC 11   1 US LT TC 02   1 US DTFTL TC 05   1 US IDDR TC 02   1 US VT   26 US ISTR TC 10   1 US LT TC 01   1 US IDDR   8 US DTFTL TC 06   1 US FAST TC 09   1 US VD   2 US PAIOACRPIRSD TC 01   2 US VT TC 06   1 US VPATR TC 01   1 US IDDR TC 01   1 PID Mso Mdoc   12 US ISTR TC 01   1 US LT TC 04   10 US FAST TC 08   1 US VT TC 05   3 US DTFTL TC 03   1 US IDDR TC 04   1 US VPATR TC 02   1 US VWCI TC 01   1 US ETESA   36 US FAST TC 07   1 US LT TC 03   3 US DS   2 US DTFTL TC 04   1 US VT TC 04   5 US IDDR TC 03   1 US VWCI TC 02   1 US ADBSQRC   2 US VPATR TC 03   1 US HS TC 01   1 US IMIOACIIRCASD   6 US ISTR   11 Q4 2024   1 US VT TC 03   6 US DTFTL TC 01   1 US IDDR TC 06   1 US VWCI TC 03   1 US RAAQESTD TC 02   1 US LT   21 US VPADDR TC 06   1 US VCSOTWS   4 US LT TC 05   6 Execution Q2 2026   24 US DTFTL TC 02   1 US VT TC 02   10 Q3 2026   137 Mdl   12 US IDDR TC 05   1 US ALOCWS TC 01   1 US RAAQESTD TC 01   1 US VPADDR TC 05   1 US VT TC 01   1 US ST   14 US IDDR TC 08   1 US VD TC 01   2 US SD   2 US VCSOTWS TC 04   1 US VPADDR   6 US VWTM TC 01   1 US IDDR TC 07   1 US FAST   9 US ISTR TC 07   1 US VPATR TC 09   1 US DS TC 01   2 US FAST TC 02   1 US PDO TC 01   1 US VCSOTWS TC 03   1 US VWTM TC 02   1 US VPADDR TC 02   1 US RAAQESTD TC 06   1 US ALOCWS TC 04   1 US DTFTL   10 US PAIOACRPIRSD   2 US PACSD TC 01   1 US ISTR TC 06   1 US VCSOTWS TC 02   1 US FAST TC 01   1 US PDO   1 US DTFTL TC 10   1 US VWTM TC 03   1 US VPADDR TC 01   1 US RAAQESTD TC 05   1 US VWCI   3 US SD TC 01   2 US ST TC 01   1 US DI   2 Manual   137 US ISTR TC 09   1 US VCSOTWS TC 01   1 GENERAL TESTS   21 US VPADDR TC 04   1 US VWTM TC 04   1 US RAAQESTD TC 04   1 US ALOCWS   4 US ALOCWS TC 02   1 US ST TC 02   4 PID Sdjwt   12 US HS   1 US ISTR TC 08   1 Q2 2025   8 Android   194 Automated   57 US VPADDR TC 03   1 US RAAQESTD TC 03   1 US VWTM   4 US ALOCWS TC 03   1 US ST TC 03   1 US FAST TC 06   1 US ISTR TC 03   1 US PACSD   1 US DTFTL TC 09   1 US VPATR TC 04   1 US ST TC 04   1 US FAST TC 05   1 US ISTR TC 02   1 US VPATR TC 05   1 US VPATR   9 US ADBSQRC TC 01   2 US ST TC 05   1 US FAST TC 04   1 US ISTR TC 05   1 US RAAQESTD   8 US DTFTL TC 07   1 US VPATR TC 07   1 US RAAQESTD TC 08   1 US VPATR TC 06   1 US ST TC 06   6 US DTFTL TC 08   1 US ISTR TC 04   1 US VPATR TC 08   1 US FAST TC 03   1 US DI TC 01   2 US RAAQESTD TC 07   1
Manual
Serenity BDD version 4.2.22