zephyr/tests/test_config.yaml

platforms:
  override_default_platforms: false
  increased_platform_scope: true
levels:
  - name: smoke
    description: >
      A plan to be used verifying basic zephyr features on hardware.
    adds:
      - kernel.threads.*
      - kernel.timer.behavior
      - arch.interrupt
      - boards.*
  - name: acceptance
    description: >
      More coverage
    inherits:
      - smoke
    adds:
      - kernel.*
twister: add support for levels and test configuration Add support test levels and the ability to assign a specific test to one or more levels. Using command line options of twister it is then possible to select a level and just execute the tests included in this level. Additionally, a test configuration allows definiing level dependencies and additional inclusion of tests into a specific level if the test itself does not have this information already. In the configuration file you can include complete components using regular expressions and you can specify which test level to import from the same file, making management of levels easier. To help with testing outside of upstream CI infrastructure, additional options are available in the configuration file, which can be hosted locally. As of now, those options are available: - Ability to ignore default platforms as defined in board definitions (Those are mostly emulation platforms used to run tests in upstream CI) - Option to specify your own list of default platforms overriding what upstream defines. - Ability to override build_onl_all options used in some testscases. This will treat tests or sample as any other just build for default platforms you specify in the configuation file or on the command line. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2022-11-22 04:17:21 +08:00			`platforms:`
			`override_default_platforms: false`
			`increased_platform_scope: true`
			`levels:`
			`- name: smoke`
			`description: >`
			`A plan to be used verifying basic zephyr features on hardware.`
			`adds:`
			`- kernel.threads.*`
			`- kernel.timer.behavior`
			`- arch.interrupt`
			`- boards.*`
			`- name: acceptance`
			`description: >`
			`More coverage`
twister: tests: Use inheritance in test_config.yaml There is no need of repeating the same entries in a scope that is supposed to extend another one. Signed-off-by: Maciej Perkowski <Maciej.Perkowski@nordicsemi.no> 2023-11-22 23:56:02 +08:00			`inherits:`
			`- smoke`
twister: add support for levels and test configuration Add support test levels and the ability to assign a specific test to one or more levels. Using command line options of twister it is then possible to select a level and just execute the tests included in this level. Additionally, a test configuration allows definiing level dependencies and additional inclusion of tests into a specific level if the test itself does not have this information already. In the configuration file you can include complete components using regular expressions and you can specify which test level to import from the same file, making management of levels easier. To help with testing outside of upstream CI infrastructure, additional options are available in the configuration file, which can be hosted locally. As of now, those options are available: - Ability to ignore default platforms as defined in board definitions (Those are mostly emulation platforms used to run tests in upstream CI) - Option to specify your own list of default platforms overriding what upstream defines. - Ability to override build_onl_all options used in some testscases. This will treat tests or sample as any other just build for default platforms you specify in the configuation file or on the command line. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2022-11-22 04:17:21 +08:00			`adds:`
			`- kernel.*`