@@ -103,6 +103,13 @@ or through a basic `environment_url.txt` file, then the Robot Framework test wil
:warning: all our deployment templates implement this design. Therefore even purely dynamic environments (such as review
environments) will automatically be propagated to your Robot Framework tests.
### Hook scripts
The Robot Framework template supports _optional_ **hook scripts** from your project, located in the `$ROBOT_TESTS_DIR` directory to perform additional project-specific logic:
*`pre-robot.sh` is executed **before** running Robot Framework,
*`post-robot.sh` is executed **after** running Robot Framework (whichever the tests status).
### How to manage Robot Framework tests in a separate GitLab repository
This template can obviously be used in an application repository that also embeds the Robot Framework test scripts.