Implemented automated end-2-end tests for Compass Manager

[tobiscr]

Description

To get rid of manual testing efforts and to ensure a consistent high quality of our deliverables, an automated end-2-end test for the Compass Manager is required.

Scope of the test is to verify that the Compass Manager could be successfully installed in a local Kubernetes cluster (e.g. k3d) and is able to interact successfully with a Compass-Director stub and the remote SKR cluster.

AC:

• Deploy the Compass Manager and a stub of the Compass Director in a local Kubernetes cluster (e.g. K3d cluster)
• Simulate the activation of the application connector module on an SKR (e.g. it's fine to use the same local K3d cluster to simulate an SKR instance)
• Verify that the Compass Directory is reacting on the App-Conn module activation and interacts with the Compass Director stub
• Simulate a successful application registration (happy path)
• Simulate a failing application registration and check that the retry mechanism of the Compass Manager works as expected (unhappy path)
• Simulate the unregistration of an application (TBC if this scenario is worth to be tested)

Reasons

Reduce manual testing efforts and ensure consistent high quality deliveries of the Compass Manager.

Attachments