zephyr/samples/basic/button/sample.yaml

sample:
  name: Button Sample
tests:
  sample.basic.button:
    tags: button gpio
    filter: dt_enabled_alias_with_parent_compat("sw0", "gpio-keys")
    depends_on: gpio
    harness: button
tests: samples: convert testcase files to yaml This will prepare test cases and samples with metadata and information that will be consumed by the sanitycheck script which will be changed to parse YAML files instead of ini. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-04-05 11:11:22 +08:00			`sample:`
samples: remove more build_only tags Remove build_only and add harness type needed for the sample/test to allow running with sanitycheck and on devices once we have harness support. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-12-12 01:35:31 +08:00			`name: Button Sample`
tests: samples: convert testcase files to yaml This will prepare test cases and samples with metadata and information that will be consumed by the sanitycheck script which will be changed to parse YAML files instead of ini. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-04-05 11:11:22 +08:00			`tests:`
tests: fix test identifiers 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> 2019-12-02 01:29:43 +08:00			`sample.basic.button:`
tests/samples: cleanup tags Remove redundant 'sample' tag and add something that matches the functionality and features being tested, demonstrated. Avoid short abbriviations and using full names for fs. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2018-10-16 03:28:35 +08:00			`tags: button gpio`
twister: replace dt_compat_enabled_with_alias filter Originally added in 7733b942246cfbfa354328d28a8a469e1c135f37. This filter is not well-formed. It's meant to match nodes like /leds/led_0 in this DTS: / { aliases { led0 = &led0; }; leds { compatible = "gpio-leds"; led0: led_0 { gpios = <...>; label = "LED 0"; }; }; }; Uses look like this: filter: dt_compat_enabled_with_alias("gpio-leds", "led0") But notice how the led_0 node doesn't have compatible "gpio-leds"; it's actually the parent node that has that compatible. Replace this with a new filter, dt_enabled_alias_with_parent_compat(), which is used like this: filter: dt_enabled_alias_with_parent_compat("led0", "gpio-leds") This has a name and argument order that makes the meaning of the filter clearer. Replace in-tree users with the new filter. Deprecate the old filter and warn about its use using the standard logging module. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no> 2021-02-26 23:50:27 +08:00			`filter: dt_enabled_alias_with_parent_compat("sw0", "gpio-keys")`
samples: remove more build_only tags Remove build_only and add harness type needed for the sample/test to allow running with sanitycheck and on devices once we have harness support. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2017-12-12 01:35:31 +08:00			`depends_on: gpio`
samples: define harness for samples Most of the basic tests trigger LEDs or expect button press and would hang in device testing because we can't parse success or failure from the console. Define harness for this with the intent to skip those in sanitycheck device testing and until we have a better way to test those. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2019-03-03 23:07:25 +08:00			`harness: button`