...
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.
...
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.
Building Actor Native Codes
Inside the Actor Testing Framework test directory there is a dedicated directory for building native actor code instructions called: native_codes_build/. By default, there is a build_actor.sh script that should provide step-by-step instructions on how to build an actor. For example, it could be a simple make command, but first you need to change the directory your codes are in, basically it should be done the same way you build the codes from the root directory.
| Code Block | ||
|---|---|---|
| ||
tests ├── native_codes_build │ └── build_actor.sh # <-- This file . . . |
Run Actor
Inside the Actor Testing Framework test directory there is a dedicated directory to run the actor code, usually it will be a workflow, called main_code_run/. By default, there is a run_actor.sh script that should provide step-by-step instructions for starting an actor or executing a workflow. Basically, it should reflect the same way you run actor from the root directory.
| Code Block | ||
|---|---|---|
| ||
tests ├── main_code_run │ └── run_actor.sh # <-- This file . . . |