70758c4374
The seasonal overhaul of test identifiers aligning the terms being used and creating a structure. This is hopefully the last time we do this, plan is to document the identifiers and enforce syntax. The end-goal is to be able to generate a testsuite description from the existing tests and sync it frequently with the testsuite in Testrail. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
30 lines
872 B
YAML
30 lines
872 B
YAML
sample:
|
|
name: Watchdog Driver Sample
|
|
tests:
|
|
sample.drivers.watchdog:
|
|
tags: drivers
|
|
harness: console
|
|
harness_config:
|
|
type: multi_line
|
|
ordered: true
|
|
regex:
|
|
- "Watchdog sample application"
|
|
- "Feeding watchdog..."
|
|
- "Waiting for reset..."
|
|
- "Watchdog sample application"
|
|
depends_on: watchdog
|
|
platform_exclude: nucleo_l496zg nucleo_f401re
|
|
sample.drivers.watchdog.nucleo_l496zg:
|
|
tags: drivers
|
|
harness: console
|
|
harness_config:
|
|
type: multi_line
|
|
ordered: true
|
|
regex:
|
|
- "Watchdog sample application"
|
|
- "Feeding watchdog..."
|
|
- "Waiting for reset..."
|
|
- "Watchdog sample application"
|
|
depends_on: watchdog
|
|
platform_whitelist: nucleo_l496zg
|
|
extra_args: CONF_FILE="prj.conf;nucleo_l496zg.conf"
|