...
For your convenience, the Actor Testing Framework comes with a custom imasdb, located under: testing/input_pulse_file/ITER directory path that must be accessed from the relative path of the project root directory.
CI script
Repository side CI scripts
ITER has a convention to put all CI-related scripts in the ci_scripts/ directory. Actor Testing Framework follows this convention, but can be extended with an additional file in the root directory: ci_scripts/ci_atf.sh. Then, in this upper CI script, you need to execute the lower file: tests/ci_scripts/.iter-ci.sh.
| Code Block | ||
|---|---|---|
| ||
Project_root ├── ci_scripts/ │ ├── ci_atf.sh # <-- Upper CI script │ ├── ... │ └── ci_...sh │ ├── root_files.extension ├── root_directiories/ │ └── tests/ └── ci_scripts/ └── .iter-ci.sh # <-- Lower CI script ############################################## - example: inside upper ci script: ci_atf.sh ############################################## #!/bin/sh ./$(dirname $0)/../tests/ci_scripts/.iter-ci.sh |
Remote ITER CI side
On the remote side of ITER CI - Bamboo CI, you need to create a dedicated job for the Actor Testing Framework and a task to run the CI script. The image below shows how such a task can be configured with the top CI script.
