rabbitmq-server/selenium/bin/components
Marcial Rosales 4da45996ca Minor refactor
Improve logging
Fix an issue running selenium tests locally
WIP modify schema to configure queryParameters for
oauth2 endpoints
2024-10-08 08:17:47 +02:00
..
README.md Move selenium to the root of the repo 2024-09-04 14:59:58 +01:00
devkeycloak Move selenium to the root of the repo 2024-09-04 14:59:58 +01:00
fakeportal Move selenium to the root of the repo 2024-09-04 14:59:58 +01:00
fakeproxy Move selenium to the root of the repo 2024-09-04 14:59:58 +01:00
keycloak Move selenium to the root of the repo 2024-09-04 14:59:58 +01:00
mock-auth-backend-http Move selenium to the root of the repo 2024-09-04 14:59:58 +01:00
mock-auth-backend-ldap Move selenium to the root of the repo 2024-09-04 14:59:58 +01:00
prodkeycloak Move selenium to the root of the repo 2024-09-04 14:59:58 +01:00
proxy Move selenium to the root of the repo 2024-09-04 14:59:58 +01:00
rabbitmq Minor refactor 2024-10-08 08:17:47 +02:00
selenium Move selenium to the root of the repo 2024-09-04 14:59:58 +01:00
uaa Move selenium to the root of the repo 2024-09-04 14:59:58 +01: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.