Secrets store sensitive data like API tokens and credentials. Add secrets to workflows via the CLI, then reference them in test files using templates. This prevents hardcoding sensitive values in configuration files.
name: Binarly Scandescription: Test the firmware with Binarly#The binarly test works without a DUT, therefore we can leave the pre- & post-stage emptypre-stage: emptypost-stage: emptystages:
- name: Binarly Scansteps:
- cmd: binarly reportname: Binarly Scanparameters:
url: "[[secrets.BinarlyURL]]"token: "[[secrets.BinarlyToken]]"file_path: "[[input.Binary]]"
Defaults
YAML Anchors reduce redundant configuration in tests. Define anchors under the defaults keyword and reference them using the *anchor_name syntax.
# Boot Test Configuration for ARM-based boardname: Boot Testdescription: This test verifies that the ARM-based board boots correctly.defaults:
transport: &transportproto: sshoptions:
host: "[[attributes.Host]]"user: rootpassword: rootstages:
- name: Boot Stagesteps:
- cmd: pingname: Wait for SSH serviceoptions:
timeout: 2mparameters:
host: "[[attributes.Host]]" - cmd: cmdname: Run echo "Hello" on the devicetransport: *transportparameters:
executable: echoargs: ["Hello"]
- cmd: cmdname: Run echo "World!" on the devicetransport: *transportparameters:
executable: echoargs: ["World!"]