Test Automation

[jjeroch]

Description

Further develop e2e test automation for automatic test after deployment and to find issues quickly

Current Impl State

Health Check Tests
Health check is needed to be executed to make sure that the appropriate endpoints are available and return a non-empty response. It can be run separately or before functional tests.

PortalHealthCheck
Portal health check is implemented for administration and registration services in order to check the load of static data and availability of additional endpoints.

InterfacePartnerHealthCheck
Interface Partner Health Check is now implemented for BPDM, ClearingHouse, SdFactory and Wallet.

Functional E2E Tests
Functional E2E tests are designed to check the behavior of an application under different scenarios. Following scenarios were implemented:

Registration scenarios
Registration scenarios suppose to check if registration process runs as expected. The following scenarios were implemented completely: registration without bpn, update of company detail data after confirmation, in-registration invitation. Two scenarios (registration without bpn and registration without document upload) were partly implemented as adjustments in productive code are needed. Some additional scenarios can be added later. For example, validation of the right company detail data depending on the selected country.

Notification initial scenario
Notification initial scenario checks if a new random portal role can be assigned and unassigned and if appropriate notification, to the respective right person and with the correct content is created.

Service Account CUD Scenarios
Create-Update-Delete Scenarios suppose to check if new service accounts can be correctly created, updated and deleted.

---

Impact

Additional information / Linked tickets

• E2E Testing - Rework Registration / Invitation portal-backend#846
• E2E Testing | Change to umbrella env where possible portal-backend#617
• Test Automation Script - enable rc.dev run portal-backend#460
• ..