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

Tag: Q2 2025

16 tests |

Overview

Test Outcomes

Test Performance

Functional Coverage Overview

Features

Key Statistics

Number of Scenarios 2
Total Number of Test Cases 16
Tests Started Sep 23, 2026 15:51:41
Tests Finished Sep 30, 2026 13:48:32
Total Duration 6d 21h 56m 51s
Fastest Test 2m 40s
Slowest Test 23m 22s
Average Execution Time 5m 30s
Total Execution Time 1h 28m 3s

Functional Coverage Details

Features

Feature Scenarios StepsText Test Cases % Pass Result Coverage
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 > 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%
Ios > 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%
Ios > 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%

Tags

Key Statistics

Number of Scenarios 2 Total Duration 6d 21h 56m 51s
Total Number of Test Cases 16 Fastest Test 2m 40s
Number of Manual Test Cases 0 Slowest Test 23m 22s
Tests Started Sep 23, 2026 15:51:41 Average Execution Time 5m 30s
Tests Finished Sep 30, 2026 13:48:32 Total Execution Time 1h 28m 3s

Automated Scenarios

## Scenario Context Steps StepsText Started Total Duration Result
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
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
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 13:03:57 44m 35s 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> 14:25:29 11m 9s SUCCESS

Manual Tests

No manual tests were recorded

Tags
Serenity BDD version 4.2.22