Lines Matching refs:platforms

74 If you want to run tests on one or more specific platforms, you can use
76 option, test suites will only be built/run on the platforms specified.
378     hardware. Currently architectures/platforms/simulation are supported:
410     hardware. Currently both architectures and platforms are supported:
439     If true, attempt to build test scenario on all available platforms. This is mostly
444     will enable the test only those platforms that provide this feature.
481 platform_allow: <list of platforms>
482     Set of platforms that this test scenario should only be run for. Do not use
487 integration_platforms: <YML list of platforms/boards>
488     This option limits the scope to the listed platforms when twister is
493 platform_exclude: <list of platforms>
494     Set of platforms that this test scenario should not run on.
579     only those platforms that fulfill this external dependency.
896 One of the key features of Twister is its ability to decide on which platforms a given
898 a test runner for Zephyr's CI. With hundreds of available platforms and thousands of
902 Twister always prepares an initial list of platforms in scope for a given test,
904 platforms that don't fulfill the conditions required in the configuration yaml
912 * ``-p/--platform <platform_name>`` (can be used multiple times): only platforms
914 * ``-l/--all``: all available platforms;
915 * ``-G/--integration``: all platforms from an ``integration_platforms`` list in
920 *"Scope presumption"*: A list of Twister's :ref:`default platforms <twister_default_testing_board>`
946 the scope of builds and tests if applicable to platforms defined under the
968 Then, in :file:`custom_board/board.cmake`, set the supported emulation platforms to ``custom``:
1184 The above command will result in twister building tests for the platforms
1186 on those platforms.
1345 platforms to be put under quarantine. Such tests will be skipped and marked
1358 ``scenarios`` and ``platforms`` entries listing combinations of scenarios and platforms
1380       platforms:
1388     - platforms:
1400 improve coverage when targeting different sets of platforms.
1419 - Ability to ignore default platforms as defined in board definitions
1420   (Those are mostly emulation platforms used to run tests in upstream
1422 - Option to specify your own list of default platforms overriding what
1426   platforms you specify in the configuration file or on the command line.
1428   default platforms are not in scope.
1437   configuration and instead use the list of platforms provided in the
1438   configuration file as the list of default platforms. This option is set to
1442   only build and run tests on the specified platforms.
1443 - ``default_platforms``: A list of additional default platforms to add. This list
1444   can either be used to replace the existing default platforms or can extend it
1447 And example platforms configuration:
1451 	platforms:
1489 An example platforms plus level configuration:
1493 	platforms:
1536 dependencies between test cases. For native_sim platforms, you can provide