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

Tag: US PAIOACRPIRSD

4 tests |

Overview

Test Outcomes

Test Performance

Functional Coverage Overview

Features

Key Statistics

Number of Scenarios 1
Total Number of Test Cases 4
Tests Started Sep 23, 2026 16:22:51
Tests Finished Sep 25, 2026 14:36:38
Total Duration 1d 22h 13m 46s
Fastest Test 2m 48s
Slowest Test 5m 41s
Average Execution Time 4m 30s
Total Execution Time 18m 2s

Functional Coverage Details

Features

Feature Scenarios StepsText Test Cases % Pass Result Coverage
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 > 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 1 Total Duration 1d 22h 13m 46s
Total Number of Test Cases 4 Fastest Test 2m 48s
Number of Manual Test Cases 0 Slowest Test 5m 41s
Tests Started Sep 23, 2026 16:22:51 Average Execution Time 4m 30s
Tests Finished Sep 25, 2026 14:36:38 Total Execution Time 18m 2s

Automated Scenarios

## Scenario Context Steps StepsText Started Total Duration Result
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
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