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

Tag: US RAAQESTD

16 tests |

Overview

Test Outcomes

Test Performance

Functional Coverage Overview

Features

Key Statistics

Number of Scenarios 8
Total Number of Test Cases 16
Number of Manual Test Cases 16
Tests Started Oct 06, 2026 11:29:47
Tests Finished Oct 06, 2026 11:29:55
Total Duration 7s
Fastest Test 5ms
Slowest Test 21ms
Average Execution Time 9ms
Total Execution Time 147ms

Functional Coverage Details

Features

Feature Scenarios StepsText Test Cases % Pass Result Coverage
Android > transaction data enabling binding between the users identification authentication and the users authorization wallet 228 > review and authorise QES transaction data 393 > Review and authorise QES transaction data 8 Given the user has initiated a QES signing operation When the Wallet presents the transaction information for review Then the Wallet displays the QES transaction type and applicable trust framework And the Wallet displays the document name or description Given the QES transaction contains a reference to the document to be signed where provided When the Wallet presents the transaction information Then the user can access the document associated with the signing transaction Given the QES transaction contains additional document or signing information When the Wallet presents the transaction information for review Then the Wallet displays the applicable DTBSR information And the Wallet displays the signed attributes and requested credentials where applicable Given optional QES transaction information is provided When the Wallet presents the transaction information for review Then the Wallet displays the OTP where provided And the Wallet displays the Response URI where applicable And the Wallet displays the document integrity status And the Wallet displays the signature format and conformance level where provided Given the user has reviewed the transaction information and document When the user explicitly approves the QES transaction Then the Wallet continues the QES signing process Given the user is reviewing the QES transaction When the user rejects or cancels the transaction Then the QES signing operation does not proceed Given the QES transaction has been completed When the user accesses the Transaction Log Then the QES transaction is available in the Transaction Log Given the QES transaction is available in the Transaction Log When the user opens the recorded QES transaction Then the Wallet displays the relevant Transaction Data associated with the transaction And the Wallet displays the user's recorded decision to approve or reject the transaction 8 75%
Ios > transaction data enabling binding between the users identification authentication and the users authorization wallet 228 > review and authorise QES transaction data 393 > Review and authorise QES transaction data 8 Given the user has initiated a QES signing operation When the Wallet presents the transaction information for review Then the Wallet displays the QES transaction type and applicable trust framework And the Wallet displays the document name or description Given the QES transaction contains a reference to the document to be signed where provided When the Wallet presents the transaction information Then the user can access the document associated with the signing transaction Given the QES transaction contains additional document or signing information When the Wallet presents the transaction information for review Then the Wallet displays the applicable DTBSR information And the Wallet displays the signed attributes and requested credentials where applicable Given optional QES transaction information is provided When the Wallet presents the transaction information for review Then the Wallet displays the OTP where provided And the Wallet displays the Response URI where applicable And the Wallet displays the document integrity status And the Wallet displays the signature format and conformance level where provided Given the user has reviewed the transaction information and document When the user explicitly approves the QES transaction Then the Wallet continues the QES signing process Given the user is reviewing the QES transaction When the user rejects or cancels the transaction Then the QES signing operation does not proceed Given the QES transaction has been completed When the user accesses the Transaction Log Then the QES transaction is available in the Transaction Log Given the QES transaction is available in the Transaction Log When the user opens the recorded QES transaction Then the Wallet displays the relevant Transaction Data associated with the transaction And the Wallet displays the user's recorded decision to approve or reject the transaction 8 62%

Tags

Manual

Key Statistics

Number of Scenarios 8 Total Duration 7s
Total Number of Test Cases 16 Fastest Test 5ms
Number of Manual Test Cases 16 Slowest Test 21ms
Tests Started Oct 06, 2026 11:29:47 Average Execution Time 9ms
Tests Finished Oct 06, 2026 11:29:55 Total Execution Time 147ms

Automated Scenarios

No automated tests were executed

Manual Tests

## Scenario Context Steps StepsText Result
Review and authorise QES transaction data Display QES transaction information before authorisation 4 Given the user has initiated a QES signing operation When the Wallet presents the transaction information for review Then the Wallet displays the QES transaction type and applicable trust framework And the Wallet displays the document name or description SUCCESS
Review and authorise QES transaction data Provide access to the document to be signed 3 Given the QES transaction contains a reference to the document to be signed where provided When the Wallet presents the transaction information Then the user can access the document associated with the signing transaction PENDING
Review and authorise QES transaction data Display document and signing information when available 4 Given the QES transaction contains additional document or signing information When the Wallet presents the transaction information for review Then the Wallet displays the applicable DTBSR information And the Wallet displays the signed attributes and requested credentials where applicable SUCCESS
Review and authorise QES transaction data Display additional QES transaction information when available 6 Given optional QES transaction information is provided When the Wallet presents the transaction information for review Then the Wallet displays the OTP where provided And the Wallet displays the Response URI where applicable And the Wallet displays the document integrity status And the Wallet displays the signature format and conformance level where provided PENDING
Review and authorise QES transaction data Approve the QES transaction 3 Given the user has reviewed the transaction information and document When the user explicitly approves the QES transaction Then the Wallet continues the QES signing process SUCCESS
Review and authorise QES transaction data Reject the QES transaction 3 Given the user is reviewing the QES transaction When the user rejects or cancels the transaction Then the QES signing operation does not proceed SUCCESS
Review and authorise QES transaction data Record the QES transaction in the Transaction Log 3 Given the QES transaction has been completed When the user accesses the Transaction Log Then the QES transaction is available in the Transaction Log SUCCESS
Review and authorise QES transaction data Display recorded QES transaction information 4 Given the QES transaction is available in the Transaction Log When the user opens the recorded QES transaction Then the Wallet displays the relevant Transaction Data associated with the transaction And the Wallet displays the user's recorded decision to approve or reject the transaction SUCCESS
Review and authorise QES transaction data Display QES transaction information before authorisation 4 Given the user has initiated a QES signing operation When the Wallet presents the transaction information for review Then the Wallet displays the QES transaction type and applicable trust framework And the Wallet displays the document name or description SUCCESS
Review and authorise QES transaction data Provide access to the document to be signed 3 Given the QES transaction contains a reference to the document to be signed where provided When the Wallet presents the transaction information Then the user can access the document associated with the signing transaction PENDING
Review and authorise QES transaction data Display document and signing information when available 4 Given the QES transaction contains additional document or signing information When the Wallet presents the transaction information for review Then the Wallet displays the applicable DTBSR information And the Wallet displays the signed attributes and requested credentials where applicable SUCCESS
Review and authorise QES transaction data Display additional QES transaction information when available 6 Given optional QES transaction information is provided When the Wallet presents the transaction information for review Then the Wallet displays the OTP where provided And the Wallet displays the Response URI where applicable And the Wallet displays the document integrity status And the Wallet displays the signature format and conformance level where provided PENDING
Review and authorise QES transaction data Approve the QES transaction 3 Given the user has reviewed the transaction information and document When the user explicitly approves the QES transaction Then the Wallet continues the QES signing process SUCCESS
Review and authorise QES transaction data Reject the QES transaction 3 Given the user is reviewing the QES transaction When the user rejects or cancels the transaction Then the QES signing operation does not proceed SUCCESS
Review and authorise QES transaction data Record the QES transaction in the Transaction Log 3 Given the QES transaction has been completed When the user accesses the Transaction Log Then the QES transaction is available in the Transaction Log SUCCESS
Review and authorise QES transaction data Display recorded QES transaction information 4 Given the QES transaction is available in the Transaction Log When the user opens the recorded QES transaction Then the Wallet displays the relevant Transaction Data associated with the transaction And the Wallet displays the user's recorded decision to approve or reject the transaction PENDING

Tags

Manual
Serenity BDD version 4.2.22