Lines Matching refs:will
21 test will run. The predicate will get a pointer to the global state passed in through
24 will be called and run once per test suite run.
25 * :c:type:`ztest_suite_before_t` - An optional before function which will run before every single
27 * :c:type:`ztest_suite_after_t` - An optional after function which will run after every single
29 * :c:type:`ztest_suite_teardown_t` - An optional teardown function which will run at the end of
57 that when :kconfig:option:`CONFIG_USERSPACE` is enabled, then the test will be run in a userspace
60 that the test function will already include a variable named ``fixture`` with the type
69 the same suite will require some initial setup followed by some form of reset between each test.
137 /** This will fail the test */
144 /** This will skip the test */
149 Ztest will mark both as passed due to the expectation.
184 applications will want to provide custom behavior. This is particularly true if there's some global
201 /* Only suites that use a predicate checking for phase == PWR_PHASE_0 will run. */
205 /* Only suites that use a predicate checking for phase == PWR_PHASE_1 will run. */
209 /* Only suites that use a predicate checking for phase == PWR_PHASE_2 will run. */
359 efforts into the specific module in question. This will speed up testing since
360 only the module will have to be compiled in, and the tested functions will be
390 test cases that a Zephyr *ztest* test image will expose.
454 The last argument of each context is the initial sleep time which will be adjusted throughout
484 These macros will instantly fail the test if the related assertion fails.
485 When an assertion fails, it will print the current file, line and function,
487 :kconfig:option:`CONFIG_ZTEST_ASSERT_VERBOSE` is 0, the assertions will only print the
504 These macros will continue test execution if the related expectation fails and subsequently fail the
505 test at the end of its execution. When an expectation fails, it will print the current file, line,
507 test. If the config :kconfig:option:`CONFIG_ZTEST_ASSERT_VERBOSE` is 0, the expectations will only …
517 The output will look something like:
531 These macros will instantly skip the test or suite if the related assumption fails.
532 When an assumption fails, it will print the current file, line, and function,
534 :kconfig:option:`CONFIG_ZTEST_ASSERT_VERBOSE` is 0, the assumptions will only print the
587 These will be surrounded by blocks such as:
601 randomize the order. The output from the test will display the seed for failed