EUDI Wallet Test Report
Home > Requirements > Ios > Relying party registration certificate 184
Report generated 28-08-2026 08:34

##: Relying party registration certificate 184

Relying Party Registration Certificate #184

Feature Coverage By Scenario

Requirements Overview

Key Statistics

Number of Scenarios 25
Total Number of Test Cases 25
Number of Manual Test Cases 25
Tests Started Aug 28, 2026 08:34:06
Tests Finished Aug 28, 2026 08:41:26
Total Duration 7m 20s
Fastest Test 16s
Slowest Test 18s
Average Execution Time 17s
Total Execution Time 7m 19s

Feature Coverage By Scenario

Test Outcomes

Test Performance

Key Statistics

Number of Scenarios 25 Total Duration 7m 20s
Total Number of Test Cases 25 Fastest Test 16s
Number of Manual Test Cases 25 Slowest Test 18s
Tests Started Aug 28, 2026 08:34:06 Average Execution Time 17s
Tests Finished Aug 28, 2026 08:41:26 Total Execution Time 7m 19s

Automated Tests

No automated tests were executed

Manual Tests

## Scenario Context Steps Result
Automatic validation of Provider's registration certificate before issuance Issuance proceeds to approval screen when the registration certificate is valid 10 SUCCESS
Automatic validation of Provider's registration certificate before issuance Validation fails when the registration certificate does not contain a registration certificate 8 SUCCESS
Warning when the provider's registration certificate cannot be validated User requests to add a document and is redirected to the provider's service 7 SUCCESS
Warning when the provider's registration certificate cannot be validated Issuance approval screen is not displayed when WRPRC validation fails 8 SUCCESS
Warning when the provider's registration certificate cannot be validated User cancels from the blocker and returns to the issuance initiation request page 7 SUCCESS
Warning for presentation requests that exceed RP's registered scope User initiates presentation of attestations from the RP service 3 SUCCESS
Warning for presentation requests that exceed RP's registered scope No warning is shown when all requested attributes are covered by the WRPRC 3 SUCCESS
Warning for presentation requests that exceed RP's registered scope Warning is displayed when requested attributes are not covered by the WRPRC 3 SUCCESS
Warning for presentation requests that exceed RP's registered scope Consent screen visually distinguishes registered from unregistered attributes 3 SUCCESS
Warning for presentation requests that exceed RP's registered scope User cancels the presentation after seeing the warning 3 SUCCESS
Warning for presentation requests that exceed RP's registered scope Silence or pre-ticked boxes are not accepted as approval to proceed 3 SUCCESS
Warning for presentation requests that exceed RP's registered scope User reviews the Data Sharing/Approval screen and consents to share selected attributes 3 SUCCESS
Warning for presentation requests that exceed RP's registered scope User authenticates successfully with PIN/biometrics after giving consent 3 SUCCESS
Warning for presentation requests that exceed RP's registered scope Confirmation of successful presentation is displayed 3 SUCCESS
Display of RP's registered details on the Consent Screen Successful display of RP details and completion of the presentation flow 9 SUCCESS
Display of RP's registered details on the Consent Screen User consents and completes the presentation successfully 4 SUCCESS
Display of RP's registered details on the Consent Screen User-friendly description of the RP's intended use is displayed 3 SUCCESS
Display of RP's registered details on the Consent Screen Warning indicator is retained when WRPRC validation fails and the user chooses to proceed 4 SUCCESS
Display of RP's registered details on the Consent Screen Warning indicator is retained when WRPRC validation fails due to revoked certificate 4 SUCCESS
Display of RP's registered details on the Consent Screen User reviews information and consents to share selected attributes 3 SUCCESS
Display of RP's registered details on the Consent Screen User authenticates successfully with PIN after giving consent 3 SUCCESS
Retrieval and display of the interacting party's identity from the Access Certificate Consent screen displays the RP's trade name and service trade name 3 SUCCESS
Retrieval and display of the interacting party's identity from the Access Certificate Intermediary's trade name is not disclosed to the user during the transaction 3 SUCCESS
Retrieval and display of the interacting party's identity from the Access Certificate Intermediary's trade name is recorded in the transaction log 3 FAILURE
Retrieval and display of the interacting party's identity from the Access Certificate Issuance approval screen displays the identity of the Provider 3 SUCCESS

Tags

Manual
Serenity BDD version 4.2.22