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 user is successfully authenticated in the EUDI Wallet
When the user selects the option Show QR Code
Then the EUDI Wallet renders a QR code on the device screen
Given the EUDI Wallet User presents the QR code to the Relying Party device
When the Relying Party device scans the QR code
Then the connection is established between the two devices
Given the EUDI Wallet receives the attestation request
When the request is successfully validated
Then the Wallet presents a screen informing the user of the request details
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 | 12 | Total Duration | 2s |
| Total Number of Test Cases | 12 | Fastest Test | 169ms |
| Number of Manual Test Cases | 12 | Slowest Test | 191ms |
| Tests Started | Jul 28, 2025 16:29:24 | Average Execution Time | 180ms |
| Tests Finished | Jul 28, 2025 16:29:27 | Total Execution Time | 2s |
| feature | Scenario | Context | Steps | Result |
|---|---|---|---|---|
| Presentation of Batch Issued Attestations in Proximity Scenario | Successful authentication in the EUDI Wallet | 3 | ||
| Presentation of Batch Issued Attestations in Proximity Scenario | Unsuccessful authentication in the EUDI Wallet | 4 | ||
| Presentation of Batch Issued Attestations in Proximity Scenario | Presenting QR Code for attestation request | 3 | ||
| Presentation of Batch Issued Attestations in Proximity Scenario | Scanning QR Code by Relying Party device | 3 | ||
| Presentation of Batch Issued Attestations in Proximity Scenario | Validation of attestation request by EUDI Wallet | 3 | ||
| Presentation of Batch Issued Attestations in Proximity Scenario | Selection of attestation using Method A | 4 | ||
| Presentation of Batch Issued Attestations in Proximity Scenario | Selection of attestation using Method C | 3 | ||
| Presentation of Batch Issued Attestations in Proximity Scenario | No matching attestation available | 4 | ||
| Presentation of Batch Issued Attestations in Proximity Scenario | User consent for attestation presentation | 3 | ||
| Presentation of Batch Issued Attestations in Proximity Scenario | Unsuccessful consent authentication | 4 | ||
| Presentation of Batch Issued Attestations in Proximity Scenario | Presentation of attestation to Relying Party | 4 | ||
| Presentation of Batch Issued Attestations in Proximity Scenario | Confirmation of presentation outcome | 2 |