rabbitmq-server/selenium/bin/components
Marcial Rosales 8fb36030a5 Add spring authorization server for testing purposes
with Selenium. And ci job to build the docker image
2025-08-06 10:33:49 +02:00
..
README.md
devkeycloak
devkeycloak-proxy Renconcile changes from tanzu rabbitmq 2025-04-08 11:06:50 +02:00
fakeportal Add spring authorization server for testing purposes 2025-08-06 10:33:49 +02:00
fakeproxy
forward-proxy Renconcile changes from tanzu rabbitmq 2025-04-08 11:06:50 +02:00
keycloak Renconcile changes from tanzu rabbitmq 2025-04-08 11:06:50 +02:00
mock-auth-backend-http
mock-auth-backend-ldap
other-rabbitmq Add functions to mgt-api for selenium 2025-05-07 17:38:31 +02:00
prodkeycloak
prodkeycloak-proxy Renconcile changes from tanzu rabbitmq 2025-04-08 11:06:50 +02:00
proxy
rabbitmq Exclude other_rabbitmq when running start-others. And fix some issues 2025-05-08 18:29:54 +02:00
selenium Make Selenium image configurable 2025-02-25 14:00:41 +00:00
spring Add spring authorization server for testing purposes 2025-08-06 10:33:49 +02:00
uaa Add spring authorization server for testing purposes 2025-08-06 10:33:49 +02:00

README.md

These shell scripts are not meant to be executed directly. Instead they are imported by bin/suite_template script.

Each component required to run a test, for instance, uaa or keycloak, has its own script with its corresponding function: start_()

Although there is a convention to have two functions, the entrypoint start_<ComponentName>(), and init_<ComponentName>(). The latter is called by the former to initialize environment variables. There is a third entry point for third party components (i.e. all except rabbitmq), the ensure_<ComponentName>(). This function starts the component if it is not running. Whereas start_<ComponentName>() kills the component's container if it is running and start it again.