Given the user visits the Relying Party service on a different device
When the user selects the option to present an attestation type
Then the Relying Party service renders a QR code
Given the user opens the EUDI Wallet
When the user authenticates using a six-digit PIN or Biometrics
Then the authentication is successful
Given the user opens the EUDI Wallet
When the user fails to authenticate using a six-digit PIN or Biometrics
Then the Wallet presents an error message
And the user can retry the authentication
Given the Relying Party service renders a QR code
When the user scans the QR code with the EUDI Wallet device
Then the Wallet presents a screen informing the user of the attestation request
And displays the name of the Relying Party and the attestation
Given Method A is configured for the attestation type
When the EUDI Wallet selects an available matching attestation
Then the Wallet uses an attestation not previously presented to any Relying Party
And the EUDI Wallet reduces the internal counter of unused attestations
Given Method C is configured for the attestation type
When the EUDI Wallet selects an available matching attestation
Then the Wallet uses an attestation from a batch in a random order
Given the EUDI Wallet attempts to match the attestation request
When no attestation matches the request
Then the Wallet stops the presentation flow
And presents an error message indicating no available attestations
Given the EUDI Wallet requests the user to consent
When the user consents by authenticating successfully
Then the authentication is successful
Given the EUDI Wallet requests the user to consent
When the user fails to authenticate using a six-digit PIN or Biometrics
Then the Wallet presents an error message
And the user can retry the authentication
Given the user consents to the attestation presentation
When the EUDI Wallet presents the requested attestation to the Relying Party
Then the Relying Party service receives the attestation
And verifies it, informing the user of the successful verification outcome
Given the Relying Party service verifies the attestation
Then the EUDI Wallet displays a confirmation message indicating the outcome
| Number of Scenarios | 11 | Total Duration | 2s |
| Total Number of Test Cases | 11 | Fastest Test | 170ms |
| Number of Manual Test Cases | 11 | Slowest Test | 186ms |
| Tests Started | Jul 28, 2025 16:29:20 | Average Execution Time | 179ms |
| Tests Finished | Jul 28, 2025 16:29:22 | Total Execution Time | 1s |
| feature | Scenario | Context | Steps | Result |
|---|---|---|---|---|
| Presentation of Batch Issued Attestations to Relying Party on Separate Device | Relying Party initiated presentation flow | 3 | ||
| Presentation of Batch Issued Attestations to Relying Party on Separate Device | Successful authentication in the EUDI Wallet | 3 | ||
| Presentation of Batch Issued Attestations to Relying Party on Separate Device | Unsuccessful authentication in the EUDI Wallet | 4 | ||
| Presentation of Batch Issued Attestations to Relying Party on Separate Device | Scanning QR Code with the EUDI Wallet device | 4 | ||
| Presentation of Batch Issued Attestations to Relying Party on Separate Device | Selection of attestation using Method A | 4 | ||
| Presentation of Batch Issued Attestations to Relying Party on Separate Device | Selection of attestation using Method C | 3 | ||
| Presentation of Batch Issued Attestations to Relying Party on Separate Device | No matching attestation available | 4 | ||
| Presentation of Batch Issued Attestations to Relying Party on Separate Device | User consent for attestation presentation | 3 | ||
| Presentation of Batch Issued Attestations to Relying Party on Separate Device | Unsuccessful consent authentication | 4 | ||
| Presentation of Batch Issued Attestations to Relying Party on Separate Device | Presentation of attestation to Relying Party | 4 | ||
| Presentation of Batch Issued Attestations to Relying Party on Separate Device | Confirmation of presentation outcome | 2 |