Searched refs:Ztest (Results 1 – 12 of 12) sorted by relevance
3 Ztest framework failure tests
44 :ref:`Ztest framework <test-framework>`. Test documentation should only be done46 called directly by the Ztest framework. Those tests are going to appear in test
6 The Zephyr Test Framework (Ztest) provides a simple testing framework intended16 Using Ztest to create a test suite is as easy as calling the :c:macro:`ZTEST_SUITE`. The macro115 accessible. This is because the fixture memory is owned and initialized by kernel space. The Ztest149 Ztest will mark both as passed due to the expectation.183 While the Ztest framework provides a default :c:func:`test_main` function, it's possible that some244 on how Twister deals with Ztest application.357 Ztest can be used for unit testing. This means that rather than including the378 depends on, you have to provide function stubs in the test. Ztest provides
287 * **Ztest tests**:289 a Ztest suite name, and a Ztest test name:290 ``<Test Scenario identifier>.<Ztest suite name>.<Ztest test name>``306 #. **Ztest** Test Case names have only Ztest components ``<Ztest suite name>.<Ztest test name>``.
137 * Test Case names for Ztest now include Ztest suite name, so the resulting identifier has141 * The ``--no-detailed-test-id`` command line option also shortens Ztest Test Case names excluding
31 - Transitioning to new Ztest API was completed and legacy Ztest was deprecated.251 * Legacy Ztest API was deprecated. All new tests shall use the new Ztest API.1446 * Migrated all tests to new Ztest API and deprecated legacy Ztest.
1217 * :github:`9506` - Ztest becomes unresponsive while running SMP tests
1719 * :github:`21848` - sanitycheck duplicate tests Testing/Ztest
1869 * :github:`21216` - Ztest "1cpu" cases don't retarget interrupts on x86_64
1401 * :github:`13949` - tests: Ztest problem - not booting properly
27 bool "Ztest with shell support"227 Enable mocking support for Ztest. This allows the test to set
912 class Ztest(Test): class
