zephyr/tests/ztest/fail
Alberto Escolar Piedras 0d5ac4ef11 tests/ztest: Use hwmv2 native targets identifiers
For the 64 bit targets, change identifiers to the new hwmv2 ones

Signed-off-by: Alberto Escolar Piedras <alberto.escolar.piedras@nordicsemi.no>
2024-03-15 16:13:12 +01:00
..
core tests/ztest/fail: Fix build for native_sim 2023-11-20 12:02:48 +01:00
src ztest: add framework tests for failed states 2022-08-29 10:27:00 +02:00
CMakeLists.txt tests/ztest/fail: Fix build for native_sim 2023-11-20 12:02:48 +01:00
Kconfig ztest: fix grammar for errors in bad test phases 2022-10-13 06:40:31 -04:00
prj.conf tests: remove CONFIG_ZTEST_NEW_API in all tests 2023-10-20 15:04:29 +02:00
README.rst tests/ztest/fail: Replace native_posix with native_sim 2023-11-20 12:02:48 +01:00
testcase.yaml tests/ztest: Use hwmv2 native targets identifiers 2024-03-15 16:13:12 +01:00

.. _ztest_framework_failure_tests:

Ztest framework failure tests
#############################

Overview
********

In order to test the actual framework's failure cases, this test suite has to do something unique.
There's a subdirectory to this test called 'core'. This project builds a sample as a
:ref:`native_sim <native_sim>` or `:ref:unit_testing <ztest_unit_testing>`
binary which is expected to fail by calling one of the following:
- ``ztest_test_fail()`` during either the ``after`` or ``teardown`` phase of the test suite
- ``ztest_test_skip()`` during either the ``after`` or ``teardown`` phase of the test suite
- ``ztest_test_pass()`` during either the ``after`` or ``teardown`` phase of the test suite

Note that these can be called indirectly through failed asserts or assumptions.

The binary by itself, when executed, will fail to run and return a code of ``1``. The main test
binary will use ``popen()`` to run the failing test binary and will assert both the return code and
the output. The output itself cannot be printed to the log as it will confuse ``twister`` by
reporting a failure.