Lines Matching refs:harness
29 - The test configuration has defined a ``harness`` but you don't have
542 harness: <string>
543 A harness keyword in the ``testcase.yaml`` file identifies a Twister
544 harness needed to run a test successfully. A harness is a feature of
548 A harness can be seen as the handler that needs to be implemented in
550 keyboard harness is set on tests that require keyboard interaction to reach
552 harness implementation at the moment.
588 harness_config: <harness configuration options>
589 Extra harness configuration options to be used to select a board and/or
613 harness: robot
623 harness: robot
636 harness: robot
776 harness: console
802 Use ``gtest`` harness if you've already got tests written in the gTest
808 The :ref:`pytest harness <integration_with_pytest>` is used to execute pytest
809 test suites in the Zephyr test. The following options apply to the pytest harness:
855 harness: pytest
872 The ``console`` harness tells Twister to parse a test's text output for a
961 The ``robot`` harness is used to execute Robot Framework test suites
991 The shell harness is used to execute shell commands and parse the output and utilizes the pytest
992 framework and the pytest harness of twister.
994 The following options apply to the shell harness:
1026 If no file is specified, the shell harness will use the default file