EUDI Wallet Test Report
Home > Tag > Android
Application version
Version 2026.08.41-Demo
Report generated 28-08-2026 21:04:19

Tag: Android

47 tests |

Overview

Test Outcomes

Test Performance

Functional Coverage Overview

Features

Key Statistics

Number of Scenarios 29
Total Number of Test Cases 47
Number of Manual Test Cases 25
Tests Started Jul 30, 2026 11:46:38
Tests Finished Aug 28, 2026 08:34:06
Total Duration 28d 20h 47m 27s
Fastest Test 16s
Slowest Test 31m 7s
Average Execution Time 3m 22s
Total Execution Time 2h 38m 26s

Functional Coverage Details

Features

Feature Scenarios StepsText Test Cases % Pass Result Coverage
Android > regression tests > automated regression Tests > MDL MSO mdoc > Issuance and presentation - mDL 2 1: Successful credential issuance and presentation with selective disclosure - Python Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Python, issuance_method=from list, issue_scenario=same device, verifier=Web verifier, presentation_scenario=same device, selective_disclosure=specific attributes}) Given the user initiates a mDL (MSO Mdoc) issuance using the Python And the issuance method is from list And the issuance is performed on a same device for the mDL (MSO Mdoc) 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=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 2: Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - mDL ({credential=mDL (MSO Mdoc), issuer=Kotlin, issuance_method=credential offer, issue_scenario=same device, verifier=Web verifier, presentation_scenario=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 3: 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 4: 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 10 100%
Android > regression tests > automated regression Tests > PID MSO mdoc > 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 > relying party registration certificate 184 > rp 03 wallet detects and warns about overasked attributes 308 > Warning for presentation requests that exceed RP's registered scope 9 Given the user visits the RP service and is requested to present certain attestations When the user clicks the corresponding button to present attestations from their installed Wallet Then the Wallet processes the presentation request against the RP's WRPRC Given all attributes requested by the RP are covered by its WRPRC When the Wallet evaluates the presentation request Then the consent screen proceeds normally without any warning Given one or more attributes requested by the RP are not covered by its WRPRC When the Wallet evaluates the presentation request Then a clear warning is displayed before any disclosure, listing the unregistered attributes Given the presentation request includes both registered and unregistered attributes When the consent screen is displayed Then registered attributes are shown with standard display and unregistered attributes are shown with a distinct warning indicator Given the warning for unregistered attributes is displayed on the consent screen When the user chooses to cancel Then the Wallet returns the user to the Home screen Given the warning for unregistered attributes is displayed on the consent screen When the user has not provided an explicit action to approve proceeding Then the Wallet does not treat this as approval and does not proceed with the presentation Given the Data Sharing screen is displayed with registered and unregistered attributes distinguished When the user reviews the information and consents to share the selected attributes Then the Wallet proceeds to the authentication step Given the user has consented to share the selected attributes When the user authenticates using their six digit PIN or biometrics Then the Wallet displays a confirmation of successful presentation Given the user has consented and successfully authenticated When the presentation is completed Then the Wallet displays a confirmation screen indicating successful presentation 9 100%
Android > relying party registration certificate 184 > rprc ISSU 01 validate EAA PID provider registration certificate 309 > Automatic validation of Provider's registration certificate before issuance 2 Given the user is authenticated to a valid EUDI Wallet on their device And a valid PID or QEAA or PuB-EAA or EAA Provider's Access Certificate is available And the Wallet Unit has verified that the requested attestation type is registered by the relevant Registrar And the Wallet retrieves issuer metadata during an issuance flow And the Wallet automatically and silently validates the provider's registration certificate, without requiring the user to opt in or manually trigger it Given the issuer metadata contains a registration certificate that is valid When the Wallet performs the automatic validation Then the validation passes And the issuance approval screen is displayed And the screen shows the provider details and the attestation or PID to be issued Given the user is authenticated to a valid EUDI Wallet on their device And a valid PID or QEAA or PuB-EAA or EAA Provider's Access Certificate is available And the Wallet Unit has verified that the requested attestation type is registered by the relevant Registrar And the Wallet retrieves issuer metadata during an issuance flow And the Wallet automatically and silently validates the provider's registration certificate, without requiring the user to opt in or manually trigger it Given the issuer metadata contains a registration certificate does not contain a registration certificate When the Wallet performs the automatic validation check Then the Wallet treats this as a validation failure 2 100%
Android > relying party registration certificate 184 > rprc ISSU 02 wallet warns wallet user when provider registration certificate validation fails 310 > Warning when the provider's registration certificate cannot be validated 3 Given the user is registered to a valid EUDI Wallet on their device And a Provider's Access Certificate is available And the issuer metadata includes a WRPRC And the Wallet automatically validates the WRPRC before displaying any issuance approval screen Given the user has opened the Wallet app and authenticated successfully using PIN or biometrics When the user selects Documents and then adds a document Then the Wallet redirects the user to the Provider's service, which sends the offer Given the user is registered to a valid EUDI Wallet on their device And a Provider's Access Certificate is available And the issuer metadata includes a WRPRC And the Wallet automatically validates the WRPRC before displaying any issuance approval screen Given the provider has sent an offer containing issuer metadata with a WRPRC When the WRPRC validation fails Then the Wallet does not display the issuance approval screen And the Wallet displays a blocker stating that the provider could not be validated Given the user is registered to a valid EUDI Wallet on their device And a Provider's Access Certificate is available And the issuer metadata includes a WRPRC And the Wallet automatically validates the WRPRC before displaying any issuance approval screen Given the blocker stating that the provider could not be validated is displayed When the user selects Cancel Then the Wallet returns the user to the issuance initiation request page 3 100%
Android > relying party registration certificate 184 > view relying party details during presentation request RP 02 307 > Display of RP's registered details on the Consent Screen 7 Given the user visits the RP service And the RP requests the presentation of certain attestations of attributes When the user selects to present attestations from their installed Wallet Unit by clicking the corresponding button Then the Wallet displays the Data Sharing Request User Approval screen And the screen shows the RP name And the screen shows the RP unique identifier And the screen shows a user friendly description of the RP's intended use of the data And the screen shows a link to the RP's privacy policy And the screen shows a validation status indicator confirming RP verified Given the Data Sharing Request User Approval screen is displayed with the RP's details When the user reviews the information, consents to share the selected attributes And the user authenticates by entering the correct six digit PIN Then the Wallet displays a confirmation of successful presentation Given the user has requested to present attestations via the Wallet When the Data Sharing Request User Approval screen is displayed Then a user friendly description of the RP's intended use of the requested data is shown Given the Wallet RP Registration Certificate (WRPRC) validation has failed When the Data Sharing Request screen is displayed Then a warning indicator is shown stating RP could not be verified And the warning indicator remains visible throughout the consent screen Given the Wallet RP Registration Certificate (WRPRC) validation has failed due to revoked certificate When the Data Sharing Request screen is displayed Then a warning indicator is shown stating RP could not be verified And the warning indicator remains visible throughout the consent screen Given the Data Sharing Request screen is displayed with the the warning indicator When the user gives consent to proceed Then the Wallet proceeds to the authentication step Given the user has consented to share the selected attributes When the user enters the correct six-digit PIN Then the Wallet displays a confirmation of successful presentation 7 100%
Android > relying party registration certificate 184 > wallet displays RP or attestation provider identity from WRPAC on consent screen 362 > Retrieval and display of the interacting party's identity from the Access Certificate 4 Given a presentation request is received from an RP presenting its registration certificate When the consent screen is displayed Then the screen shows the RP's user friendly trade name and the trade name of the specific service Given the RP uses an intermediary for the presentation request When the consent screen is displayed Then the Wallet does not inform the user of the intermediary's trade name or its service trade name Given the RP uses an intermediary for the presentation request When the transaction is completed Then the intermediary trade name is recorded in the Wallet transaction log Given an issuance request is received from a PID Provider or Attestation Provider presenting its access certificate When the issuance approval screen is displayed Then the screen shows the provider's identity as included in the subject information of the access certificate 4 100%

Tags

US VEAAPIDPRC   2 US VRPDDPR TC 04   1 US WWWUWPRCVF TC 03   1 Q3.1 2026   25 US VEAAPIDPRC TC 02   1 US WDAWAOA TC 01   1 US WDAWAOA TC 05   1 US WDRPAPIFWRPACCS TC 04   1 US WDAWAOA TC 09   1 Execution Q2 2026   22 US VRPDDPR TC 01   1 US VRPDDPR TC 05   1 US WWWUWPRCVF TC 02   1 Mdl   10 US WDRPAPIFWRPACCS TC 03   1 US VEAAPIDPRC TC 01   1 US WDAWAOA TC 02   1 US WDAWAOA TC 06   1 PID Mso Mdoc   12 Manual   25 US VRPDDPR TC 02   1 US WWWUWPRCVF TC 01   1 US WDRPAPIFWRPACCS TC 02   1 US VRPDDPR TC 06   1 US WWWUWPRCVF   3 US WDAWAOA TC 03   1 US VRPDDPR   7 US WDAWAOA TC 07   1 US WDRPAPIFWRPACCS   4 US ETESA   22 US WDAWAOA   9 Android   47 US VRPDDPR TC 03   1 Automated   22 US WDRPAPIFWRPACCS TC 01   1 US VRPDDPR TC 07   1 US WDAWAOA TC 04   1 US WDAWAOA TC 08   1
Manual

Key Statistics

Number of Scenarios 29 Total Duration 28d 20h 47m 27s
Total Number of Test Cases 47 Fastest Test 16s
Number of Manual Test Cases 25 Slowest Test 31m 7s
Tests Started Jul 30, 2026 11:46:38 Average Execution Time 3m 22s
Tests Finished Aug 28, 2026 08:34:06 Total Execution Time 2h 38m 26s

Automated Scenarios

## Scenario Context Steps StepsText Started Total Duration Result
Issuance and presentation - mDL Successful credential issuance and presentation with selective disclosure - Python Issuer - mDL
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> 11:46:58 1h 2m 30s SUCCESS
Issuance and presentation - mDL Successful credential issuance and presentation with selective disclosure - Kotlin Issuer - mDL
4 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> 12:49:27 18m 39s 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> 11:46:38 38m 56s 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> 12:25:35 31m 9s SUCCESS

Manual Tests

## Scenario Context Steps StepsText Result
Automatic validation of Provider's registration certificate before issuance Issuance proceeds to approval screen when the registration certificate is valid 10 Given the user is authenticated to a valid EUDI Wallet on their device And a valid PID or QEAA or PuB-EAA or EAA Provider's Access Certificate is available And the Wallet Unit has verified that the requested attestation type is registered by the relevant Registrar And the Wallet retrieves issuer metadata during an issuance flow And the Wallet automatically and silently validates the provider's registration certificate, without requiring the user to opt in or manually trigger it Given the issuer metadata contains a registration certificate that is valid When the Wallet performs the automatic validation Then the validation passes And the issuance approval screen is displayed And the screen shows the provider details and the attestation or PID to be issued SUCCESS
Automatic validation of Provider's registration certificate before issuance Validation fails when the registration certificate does not contain a registration certificate 8 Given the user is authenticated to a valid EUDI Wallet on their device And a valid PID or QEAA or PuB-EAA or EAA Provider's Access Certificate is available And the Wallet Unit has verified that the requested attestation type is registered by the relevant Registrar And the Wallet retrieves issuer metadata during an issuance flow And the Wallet automatically and silently validates the provider's registration certificate, without requiring the user to opt in or manually trigger it Given the issuer metadata contains a registration certificate does not contain a registration certificate When the Wallet performs the automatic validation check Then the Wallet treats this as a validation failure SUCCESS
Warning when the provider's registration certificate cannot be validated User requests to add a document and is redirected to the provider's service 7 Given the user is registered to a valid EUDI Wallet on their device And a Provider's Access Certificate is available And the issuer metadata includes a WRPRC And the Wallet automatically validates the WRPRC before displaying any issuance approval screen Given the user has opened the Wallet app and authenticated successfully using PIN or biometrics When the user selects Documents and then adds a document Then the Wallet redirects the user to the Provider's service, which sends the offer SUCCESS
Warning when the provider's registration certificate cannot be validated Issuance approval screen is not displayed when WRPRC validation fails 8 Given the user is registered to a valid EUDI Wallet on their device And a Provider's Access Certificate is available And the issuer metadata includes a WRPRC And the Wallet automatically validates the WRPRC before displaying any issuance approval screen Given the provider has sent an offer containing issuer metadata with a WRPRC When the WRPRC validation fails Then the Wallet does not display the issuance approval screen And the Wallet displays a blocker stating that the provider could not be validated SUCCESS
Warning when the provider's registration certificate cannot be validated User cancels from the blocker and returns to the issuance initiation request page 7 Given the user is registered to a valid EUDI Wallet on their device And a Provider's Access Certificate is available And the issuer metadata includes a WRPRC And the Wallet automatically validates the WRPRC before displaying any issuance approval screen Given the blocker stating that the provider could not be validated is displayed When the user selects Cancel Then the Wallet returns the user to the issuance initiation request page SUCCESS
Warning for presentation requests that exceed RP's registered scope User initiates presentation of attestations from the RP service 3 Given the user visits the RP service and is requested to present certain attestations When the user clicks the corresponding button to present attestations from their installed Wallet Then the Wallet processes the presentation request against the RP's WRPRC SUCCESS
Warning for presentation requests that exceed RP's registered scope No warning is shown when all requested attributes are covered by the WRPRC 3 Given all attributes requested by the RP are covered by its WRPRC When the Wallet evaluates the presentation request Then the consent screen proceeds normally without any warning SUCCESS
Warning for presentation requests that exceed RP's registered scope Warning is displayed when requested attributes are not covered by the WRPRC 3 Given one or more attributes requested by the RP are not covered by its WRPRC When the Wallet evaluates the presentation request Then a clear warning is displayed before any disclosure, listing the unregistered attributes SUCCESS
Warning for presentation requests that exceed RP's registered scope Consent screen visually distinguishes registered from unregistered attributes 3 Given the presentation request includes both registered and unregistered attributes When the consent screen is displayed Then registered attributes are shown with standard display and unregistered attributes are shown with a distinct warning indicator SUCCESS
Warning for presentation requests that exceed RP's registered scope User cancels the presentation after seeing the warning 3 Given the warning for unregistered attributes is displayed on the consent screen When the user chooses to cancel Then the Wallet returns the user to the Home screen SUCCESS
Warning for presentation requests that exceed RP's registered scope Silence or pre-ticked boxes are not accepted as approval to proceed 3 Given the warning for unregistered attributes is displayed on the consent screen When the user has not provided an explicit action to approve proceeding Then the Wallet does not treat this as approval and does not proceed with the presentation SUCCESS
Warning for presentation requests that exceed RP's registered scope User reviews the Data Sharing/Approval screen and consents to share selected attributes 3 Given the Data Sharing screen is displayed with registered and unregistered attributes distinguished When the user reviews the information and consents to share the selected attributes Then the Wallet proceeds to the authentication step SUCCESS
Warning for presentation requests that exceed RP's registered scope User authenticates successfully with PIN/biometrics after giving consent 3 Given the user has consented to share the selected attributes When the user authenticates using their six digit PIN or biometrics Then the Wallet displays a confirmation of successful presentation SUCCESS
Warning for presentation requests that exceed RP's registered scope Confirmation of successful presentation is displayed 3 Given the user has consented and successfully authenticated When the presentation is completed Then the Wallet displays a confirmation screen indicating successful presentation SUCCESS
Display of RP's registered details on the Consent Screen Successful display of RP details and completion of the presentation flow 9 Given the user visits the RP service And the RP requests the presentation of certain attestations of attributes When the user selects to present attestations from their installed Wallet Unit by clicking the corresponding button Then the Wallet displays the Data Sharing Request User Approval screen And the screen shows the RP name And the screen shows the RP unique identifier And the screen shows a user friendly description of the RP's intended use of the data And the screen shows a link to the RP's privacy policy And the screen shows a validation status indicator confirming RP verified SUCCESS
Display of RP's registered details on the Consent Screen User consents and completes the presentation successfully 4 Given the Data Sharing Request User Approval screen is displayed with the RP's details When the user reviews the information, consents to share the selected attributes And the user authenticates by entering the correct six digit PIN Then the Wallet displays a confirmation of successful presentation SUCCESS
Display of RP's registered details on the Consent Screen User-friendly description of the RP's intended use is displayed 3 Given the user has requested to present attestations via the Wallet When the Data Sharing Request User Approval screen is displayed Then a user friendly description of the RP's intended use of the requested data is shown SUCCESS
Display of RP's registered details on the Consent Screen Warning indicator is retained when WRPRC validation fails and the user chooses to proceed 4 Given the Wallet RP Registration Certificate (WRPRC) validation has failed When the Data Sharing Request screen is displayed Then a warning indicator is shown stating RP could not be verified And the warning indicator remains visible throughout the consent screen SUCCESS
Display of RP's registered details on the Consent Screen Warning indicator is retained when WRPRC validation fails due to revoked certificate 4 Given the Wallet RP Registration Certificate (WRPRC) validation has failed due to revoked certificate When the Data Sharing Request screen is displayed Then a warning indicator is shown stating RP could not be verified And the warning indicator remains visible throughout the consent screen SUCCESS
Display of RP's registered details on the Consent Screen User reviews information and consents to share selected attributes 3 Given the Data Sharing Request screen is displayed with the the warning indicator When the user gives consent to proceed Then the Wallet proceeds to the authentication step SUCCESS
Display of RP's registered details on the Consent Screen User authenticates successfully with PIN after giving consent 3 Given the user has consented to share the selected attributes When the user enters the correct six-digit PIN Then the Wallet displays a confirmation of successful presentation SUCCESS
Retrieval and display of the interacting party's identity from the Access Certificate Consent screen displays the RP's trade name and service trade name 3 Given a presentation request is received from an RP presenting its registration certificate When the consent screen is displayed Then the screen shows the RP's user friendly trade name and the trade name of the specific service SUCCESS
Retrieval and display of the interacting party's identity from the Access Certificate Intermediary's trade name is not disclosed to the user during the transaction 3 Given the RP uses an intermediary for the presentation request When the consent screen is displayed Then the Wallet does not inform the user of the intermediary's trade name or its service trade name SUCCESS
Retrieval and display of the interacting party's identity from the Access Certificate Intermediary's trade name is recorded in the transaction log 3 Given the RP uses an intermediary for the presentation request When the transaction is completed Then the intermediary trade name is recorded in the Wallet transaction log SUCCESS
Retrieval and display of the interacting party's identity from the Access Certificate Issuance approval screen displays the identity of the Provider 3 Given an issuance request is received from a PID Provider or Attestation Provider presenting its access certificate When the issuance approval screen is displayed Then the screen shows the provider's identity as included in the subject information of the access certificate SUCCESS

Tags

US VEAAPIDPRC   2 US VRPDDPR TC 04   1 US WWWUWPRCVF TC 03   1 Q3.1 2026   25 US VEAAPIDPRC TC 02   1 US WDAWAOA TC 01   1 US WDAWAOA TC 05   1 US WDRPAPIFWRPACCS TC 04   1 US WDAWAOA TC 09   1 Execution Q2 2026   22 US VRPDDPR TC 01   1 US VRPDDPR TC 05   1 US WWWUWPRCVF TC 02   1 Mdl   10 US WDRPAPIFWRPACCS TC 03   1 US VEAAPIDPRC TC 01   1 US WDAWAOA TC 02   1 US WDAWAOA TC 06   1 PID Mso Mdoc   12 Manual   25 US VRPDDPR TC 02   1 US WWWUWPRCVF TC 01   1 US WDRPAPIFWRPACCS TC 02   1 US VRPDDPR TC 06   1 US WWWUWPRCVF   3 US WDAWAOA TC 03   1 US VRPDDPR   7 US WDAWAOA TC 07   1 US WDRPAPIFWRPACCS   4 US ETESA   22 US WDAWAOA   9 Android   47 US VRPDDPR TC 03   1 Automated   22 US WDRPAPIFWRPACCS TC 01   1 US VRPDDPR TC 07   1 US WDAWAOA TC 04   1 US WDAWAOA TC 08   1
Manual
Serenity BDD version 4.2.22