You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a tester I want a golden record process that is starting up to indicate when it is ready to be tested.
Acceptance Criteria
Upon startup the Pool is ready when a successful connection to the Orchestrator has been made.
Upon startup the Cleaning Service Dummy is ready when a successful connection to the Orchestrator has been made.
Upon startup the Gate is ready when a successful connection to the Orchestrator and Pool has been made.
Additional Information
A BPDM application signals with a readiness endpoint whether the application is working fine and is ready to accept traffic. Upon startup the BPDM applications reach the ready state upon successfully connecting to the Postgres and Keycloak. However, there is no check for BPDM applications successfully connecting to other BPDM applications. This may lead to the application showing a successful ready state even though connection errors occur to its dependencies. However, I would expect the Pool for example only be ready if the Orchestrator is ready. A Gate, in turn, should only be ready if the Orchestrator and Pool are.
This behaviour is important during Helm Chart installation and testing. Here, the ready state indicates whether a BPDM deployment has been successfully set up. However, without the connection checks for readiness the deployment may indicate its working fine while the components are not being able to connect with each other.
This, in turn, makes automatic chart testing more difficult as there is currently no reliable way to tell, when the whole golden record process is actually working and ready to accept tests.
The text was updated successfully, but these errors were encountered:
Description
As a tester I want a golden record process that is starting up to indicate when it is ready to be tested.
Acceptance Criteria
Additional Information
A BPDM application signals with a readiness endpoint whether the application is working fine and is ready to accept traffic. Upon startup the BPDM applications reach the ready state upon successfully connecting to the Postgres and Keycloak. However, there is no check for BPDM applications successfully connecting to other BPDM applications. This may lead to the application showing a successful ready state even though connection errors occur to its dependencies. However, I would expect the Pool for example only be ready if the Orchestrator is ready. A Gate, in turn, should only be ready if the Orchestrator and Pool are.
This behaviour is important during Helm Chart installation and testing. Here, the ready state indicates whether a BPDM deployment has been successfully set up. However, without the connection checks for readiness the deployment may indicate its working fine while the components are not being able to connect with each other.
This, in turn, makes automatic chart testing more difficult as there is currently no reliable way to tell, when the whole golden record process is actually working and ready to accept tests.
The text was updated successfully, but these errors were encountered: