...
| Code Block |
|---|
|
├── configs
│ ├── actor_configuration.yml # <-- this file
│ └── ids_configuration.yml
##############################################
- example: inside actor_configuration.yml:
##############################################
actor_name: NAME
actor_path: actor/description/file.yaml |
IDS configuration
The Actor Testing Framework assumes that the user needs to prepare input files, output files, and expected (reference) IDS pulse files to be used in the execution of the workflow and tests. On the user side, these files can be placed in the public, user, or custom imasdb path, but only the public and custom imasdb path can be used for the remote CI. This is set in the ids_configuration.yml file and must match the pulse files and IDS used by the actor workflow.
| Code Block |
|---|
|
├── configs
│ ├── actor_configuration.yml
│ └── ids_configuration.yml # <-- this file
##############################################
- example: inside ids_configuration.yml:
##############################################
input_ids:
user: ./tests/input_pulse_file
output_ids:
database: ITER
user: ./tests/input_pulse_file/
shot: 114100
run: 42
expected_ids:
database: ITER
user: ./tests/input_pulse_file/
shot: 114100
run: 43
|
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.
