| /Zephyr-latest/tests/benchmarks/sys_kernel/ |
| D | README.txt | 5 The SysKernel test measures the performance of semaphore,
12 MODULE: kernel API test
15 Each test below is repeated 10 times;
18 TEST CASE: Semaphore #1
19 TEST COVERAGE:
23 Starting test. Please wait...
24 TEST RESULT: SUCCESSFUL
26 END TEST CASE
28 TEST CASE: Semaphore #2
29 TEST COVERAGE:
[all …]
|
| /Zephyr-latest/samples/tfm_integration/tfm_regression_test/ |
| D | README.rst | 3 TF-M Regression Test Sample
11 The build system will replace the Zephyr application with the Non-Secure TF-M test application,
46 #### Execute test suites for the Secure area ####
50 Running Test Suite PS reliability tests (TFM_PS_TEST_3XXX)...
54 TEST: TFM_PS_TEST_3001 - PASSED!
58 TEST: TFM_PS_TEST_3002 - PASSED!
63 *** Secure test suites summary ***
64 Test suite 'PSA protected storage S interface tests (TFM_PS_TEST_2XXX)' has PASSED
65 Test suite 'PS reliability tests (TFM_PS_TEST_3XXX)' has PASSED
66 Test suite 'PS rollback protection tests (TFM_PS_TEST_4XXX)' has PASSED
[all …]
|
| /Zephyr-latest/samples/boards/nxp/adsp/number_crunching/ |
| D | README.rst | 72 [Library Test] == Vector Sum test ==
74 [Library Test] Vector Sum takes 6886 cycles
75 [Library Test] == Vector Sum test end with 1 ==
77 [Library Test] == Vector power sum test ==
79 [Library Test] Vector power sum takes 6659 cycles
80 [Library Test] == Vector power sum test end with 1 ==
82 [Library Test] == Vector power sum test ==
84 [Library Test] Vector power sum takes 3681 cycles
85 [Library Test] == Vector power sum test end ==
87 [Library Test] == Fast Fourier Transform on Real Data test ==
[all …]
|
| /Zephyr-latest/tests/cmake/snippets/ |
| D | Kconfig | 10 # Snippet test types used by the test implementation to steer the test logic
12 prompt "Snippet Test Type"
16 bool "Test Type: None"
18 Test the initial state with no snippets applied.
21 bool "Test Type: Foo"
23 Test the `foo` snippet from the default application snippet root.
26 bool "Test Type: Bar"
28 Test the `bar` snippet from an extra snippet root.
31 bool "Test Type: Foo-Bar"
33 Test the snippet processing order (1. foo, 2. bar)
[all …]
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/ |
| D | README.rst | 5 subsystem. The tests run on the BabbleSim simulator, using the BabbleSim test
11 src/ directory containing the necessary test harnesses to execute the tests.
13 There's only a single test application for all the Bluetooth Mesh BabbleSim
14 tests. The test application is built from this directory, and includes all test
15 harnesses in every build. The overlying bsim test framework selects the harness
16 to use at runtime, using the test identifiers passed in the test scripts.
30 Individual test harnesses can be run outside of ``RunTest()`` by setting the
36 When running test applications independently, make sure to assign the original
39 Example: To debug the ``transport_tx_seg_block`` test harness in the transport
40 seg_block test, change transport/seg_block.sh to
[all …]
|
| /Zephyr-latest/samples/boards/nxp/adsp/number_crunching/src/ |
| D | math_ops.c | 32 int ret = 1; /* test passed successfully */ in test_vec_sum_int16_op()
34 printk("[Library Test] == Vector Sum test ==\r\n"); in test_vec_sum_int16_op()
37 /* Run test function */ in test_vec_sum_int16_op()
44 printk("[Library Test] Vector Sum takes %d cycles\r\n", stop - start); in test_vec_sum_int16_op()
45 printk("[Library Test] == Vector Sum test end with %d ==\r\n\r\n", ret); in test_vec_sum_int16_op()
51 int ret = 1; /* test passed successfully */ in test_power_int16_op()
53 printk("[Library Test] == Vector power sum test ==\r\n"); in test_power_int16_op()
56 /* Run test function */ in test_power_int16_op()
62 printk("[Library Test] Mismatch: expected %lld result %lld\r\n", in test_power_int16_op()
64 ret = 0; /* test failed */ in test_power_int16_op()
[all …]
|
| /Zephyr-latest/tests/drivers/disk/disk_performance/ |
| D | README.txt | 1 Disk Performance Test
4 This test is intended to test the performance of disk devices under Zephyr. It
6 The test has the following phases:
8 * Setup test: simply sets up the disk, and reads data such as the sector count
11 * Sequential read test: This test performs sequential reads, first only over one
14 * Random read test: This test performs random reads across the disk, each one
17 * Sequential write test: This test performs sequential writes, first only over
20 * Random write test: This test performs random writes across the disk, each one
|
| /Zephyr-latest/tests/lib/cmsis_dsp/matrix/ |
| D | Kconfig | 5 bool "Test: Matrix Unary Q7"
8 bool "Test: Matrix Unary Q15"
11 bool "Test: Matrix Unary Q31"
14 bool "Test: Matrix Unary F16"
18 bool "Test: Matrix Unary F32"
21 bool "Test: Matrix Unary F64"
24 bool "Test: Matrix Binary Q7"
27 bool "Test: Matrix Binary Q15"
30 bool "Test: Matrix Binary Q31"
33 bool "Test: Matrix Binary F16"
[all …]
|
| /Zephyr-latest/subsys/testsuite/ztest/include/zephyr/ |
| D | ztest_test.h | 43 * @brief The expected result of a test.
49 ZTEST_EXPECTED_RESULT_FAIL = 0, /**< Expect a test to fail */
50 ZTEST_EXPECTED_RESULT_SKIP, /**< Expect a test to pass */
60 const char *test_suite_name; /**< The test suite's name for the expectation */
61 const char *test_name; /**< The test's name for the expectation */
78 * @brief Expect a test to fail (mark it passing if it failed)
80 * Adding this macro to your logic will allow the failing test to be considered passing, example:
88 * @param _test_name The name of the test
94 * @brief Expect a test to skip (mark it passing if it failed)
96 * Adding this macro to your logic will allow the failing test to be considered passing, example:
[all …]
|
| /Zephyr-latest/tests/cmake/yaml/ |
| D | CMakeLists.txt | 29 cmake_parse_arguments(TA_ARG "" "COMMENT" "TEST" ${ARGN})
35 "Test: ${TA_ARG_TEST}\n"
43 yaml_get(actual NAME yaml-test KEY cmake test key-string)
45 test_assert(TEST ${expected} STREQUAL ${actual}
52 yaml_length(actual NAME yaml-test KEY cmake test key-list-string)
53 test_assert(TEST ${expected} EQUAL ${actual}
58 yaml_get(actual NAME yaml-test KEY cmake test key-list-string)
61 test_assert(TEST "${e}" STREQUAL "${a}"
69 yaml_get(actual NAME yaml-test KEY cmake test key-int)
71 test_assert(TEST ${expected} EQUAL ${actual}
[all …]
|
| /Zephyr-latest/subsys/testsuite/ztest/ |
| D | Kconfig | 6 select TEST
14 int "Test function thread stack size"
33 Enable shell to manage test execution and selection.
40 which a 1cpu type test may execute on a multicpu system. The default
43 value. Please be aware that increasing it for long-running test cases
47 bool "Abort on first failing test"
49 Stop and abort on first failing test. Do not continue with other
79 bool "Reset the board to test again if the test passed"
82 If the test passed reset the board so it is run again. This
90 do actions in your test case, this option often enabled when doing
[all …]
|
| /Zephyr-latest/tests/lib/cmsis_dsp/transform/ |
| D | Kconfig | 5 bool "Test: Transform CQ15"
8 bool "Test: Transform RQ15"
11 bool "Test: Transform CQ31"
14 bool "Test: Transform RQ31"
17 bool "Test: Transform CF16"
21 bool "Test: Transform RF16"
25 bool "Test: Transform CF32"
28 bool "Test: Transform RF32"
31 bool "Test: Transform CF64"
34 bool "Test: Transform RF64"
|
| /Zephyr-latest/scripts/west_commands/tests/ |
| D | conftest.py | 11 RC_BUILD_DIR = '/test/build-dir'
12 RC_BOARD_DIR = '/test/zephyr/boards/test-arch/test-board'
13 RC_KERNEL_ELF = 'test-zephyr.elf'
14 RC_KERNEL_EXE = 'test-zephyr.exe'
15 RC_KERNEL_HEX = 'test-zephyr.hex'
16 RC_KERNEL_BIN = 'test-zephyr.bin'
17 RC_GDB = 'test-none-gdb'
18 RC_OPENOCD = 'test-openocd'
19 RC_OPENOCD_SEARCH = ['/test/openocd/search']
|
| /Zephyr-latest/samples/subsys/usb/testusb/ |
| D | README.rst | 5 Test USB device drivers using a loopback function.
8 to test USB device drivers and the device stack connected to a Linux host
48 /dev/bus/usb/009/016 test 0, 0.000007 secs
49 /dev/bus/usb/009/016 test 9, 4.994475 secs
50 /dev/bus/usb/009/016 test 10, 11.990054 secs
69 /dev/bus/usb/009/017 test 0, 0.000008 secs
70 /dev/bus/usb/009/017 test 1, 2.000001 secs
71 /dev/bus/usb/009/017 test 2, 2.003058 secs
72 /dev/bus/usb/009/017 test 3, 1.054082 secs
73 /dev/bus/usb/009/017 test 4, 1.001010 secs
[all …]
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/src/ |
| D | main.c | 14 extern struct bst_test_list *test_dfu_install(struct bst_test_list *test);
15 extern struct bst_test_list *test_blob_pst_install(struct bst_test_list *test);
16 extern struct bst_test_list *test_lcd_install(struct bst_test_list *test);
17 extern struct bst_test_list *test_sar_pst_install(struct bst_test_list *test);
18 extern struct bst_test_list *test_brg_install(struct bst_test_list *test);
20 extern struct bst_test_list *test_proxy_sol_install(struct bst_test_list *test);
23 extern struct bst_test_list *test_adv_install(struct bst_test_list *test);
24 extern struct bst_test_list *test_suspend_install(struct bst_test_list *test);
29 extern struct bst_test_list *test_suspend_install(struct bst_test_list *test);
30 extern struct bst_test_list *test_adv_install(struct bst_test_list *test);
[all …]
|
| /Zephyr-latest/tests/drivers/disk/disk_access/ |
| D | README.txt | 1 Disk Access Test
4 This test is intended to verify the functionality of disk devices in Zephyr.
5 It is designed to test the NXP USDHC disk driver, but can be used for other
6 disk devices as well. The test has the following phases:
8 * Setup test: Verifies that disk initialization works, as well as testing
10 Note that this test also verifies the memory buffers reserved for read/write
14 * Read test: Verifies that the driver can consistently read sectors. This test
17 The test deliberately will read sectors beyond the end of the disk, and if
22 * Write test: Verifies that the driver can consistently write sectors. This test
23 follows the same flow as the read test, but at each step writes data to the
[all …]
|
| /Zephyr-latest/subsys/net/pkt_filter/ |
| D | ethernet.c | 26 static bool addr_match(struct npf_test *test, struct net_eth_addr *pkt_addr) in addr_match() argument
29 CONTAINER_OF(test, struct npf_test_eth_addr, test); in addr_match()
44 bool npf_eth_src_addr_match(struct npf_test *test, struct net_pkt *pkt) in npf_eth_src_addr_match() argument
48 return addr_match(test, ð_hdr->src); in npf_eth_src_addr_match()
51 bool npf_eth_src_addr_unmatch(struct npf_test *test, struct net_pkt *pkt) in npf_eth_src_addr_unmatch() argument
53 return !npf_eth_src_addr_match(test, pkt); in npf_eth_src_addr_unmatch()
56 bool npf_eth_dst_addr_match(struct npf_test *test, struct net_pkt *pkt) in npf_eth_dst_addr_match() argument
60 return addr_match(test, ð_hdr->dst); in npf_eth_dst_addr_match()
63 bool npf_eth_dst_addr_unmatch(struct npf_test *test, struct net_pkt *pkt) in npf_eth_dst_addr_unmatch() argument
65 return !npf_eth_dst_addr_match(test, pkt); in npf_eth_dst_addr_unmatch()
[all …]
|
| /Zephyr-latest/doc/develop/test/ |
| D | ztest.rst | 3 Test Framework
6 The Zephyr Test Framework (Ztest) provides a simple testing framework intended
8 test structure.
13 Creating a test suite
16 Using Ztest to create a test suite is as easy as calling the :c:macro:`ZTEST_SUITE`. The macro
21 test will run. The predicate will get a pointer to the global state passed in through
23 * :c:type:`ztest_suite_setup_t` - An optional setup function which returns a test fixture. This
24 will be called and run once per test suite run.
26 test in this suite.
28 test in this suite.
[all …]
|
| /Zephyr-latest/include/zephyr/sys/ |
| D | __assert.h | 54 #define __ASSERT_LOC(test) \ argument
56 Z_STRINGIFY(test), \
61 #define __ASSERT_LOC(test) \ argument
67 #define __ASSERT_LOC(test) \ argument
69 Z_STRINGIFY(test))
73 #define __ASSERT_LOC(test) \ argument
97 * When the assert test mode is enabled, the default kernel fatal error handler
98 * and the custom assert hook function may return in order to allow the test to
111 #define __ASSERT_NO_MSG(test) \ argument
113 if (!(test)) { \
[all …]
|
| /Zephyr-latest/tests/benchmarks/thread_metric/ |
| D | thread_metric_readme.txt | 1 Thread-Metric RTOS Test Suite
4 1. Thread-Metric Test Suite
6 The Thread-Metric test suite consists of 8 distinct RTOS
8 of an RTOS. The test measures the total number of RTOS events
12 1.1. Basic Processing Test
14 This is the baseline test consisting of a single thread. This
15 should execute the same on every operating system. Test values
17 relative to the difference between the values of this test.
19 1.2. Cooperative Scheduling Test
21 This test consists of 5 threads created at the same priority that
[all …]
|
| /Zephyr-latest/tests/kernel/workq/work_queue/ |
| D | README.txt | 1 Title: Test workqueue APIs
33 Starting sequence test
34 - Initializing test items
35 - Submitting test items
37 - Running test item 1
41 - Running test item 2
45 - Running test item 3
46 - Running test item 4
47 - Running test item 5
48 - Running test item 6
[all …]
|
| /Zephyr-latest/subsys/bluetooth/controller/ |
| D | Kconfig.dtm | 12 Enable support for Direct Test Mode in the Controller.
15 bool "Direct Test Mode over HCI"
19 Enable support for Direct Test Mode over the HCI transport.
24 bool "HCI LE Receiver Test v3"
27 Enable support for the DTM Receiver test command v3.
30 bool "HCI LE Transmitter Test v3"
33 Enable support for the DTM Transmitter test command v3.
36 bool "HCI LE Transmitter Test v4"
39 Enable support for the DTM Transmitter test command v4.
56 test packets transmission interval.
|
| /Zephyr-latest/tests/subsys/sd/mmc/ |
| D | README.txt | 1 MMC Subsystem Test
4 This test is designed to verify the MMC protocol stack implementation,
7 this test also serves as a complete test for the SDHC driver implementation in
9 perform destructive I/O on the card, wiping any data present. The test has
12 * Init test: verify the SD host controller can detect card presence, and
13 test the initialization flow of the MMC subsystem to verify that the stack
16 * IOCTL test: verify the SD subsystem correctly implements IOCTL calls required
19 * Read test: verify that single block reads work, followed by multiple
23 * Write test: verify that single block writes work, followed by multiple
27 * R/W test: write data to the MMC card, and verify that it is able
|
| /Zephyr-latest/tests/subsys/sd/sdmmc/ |
| D | README.txt | 1 SDMMC Subsystem Test
4 This test is designed to verify the SD subsystem stack implementation,
7 this test also serves as a complete test for the SDHC driver implementation in
9 perform destructive I/O on the card, wiping any data present. The test has
12 * Init test: verify the SD host controller can detect card presence, and
13 test the initialization flow of the SDMMC subsystem to verify that the stack
16 * IOCTL test: verify the SD subsystem correctly implements IOCTL calls required
19 * Read test: verify that single block reads work, followed by multiple
23 * Write test: verify that single block writes work, followed by multiple
27 * R/W test: write data to the SD card, and verify that it is able
|
| /Zephyr-latest/samples/boards/microchip/mec172xevb_assy6906/rom_api/ |
| D | sample.yaml | 10 - "Test Zephyr crypto hash API for multiblock plus remainder"
11 - "Test Zephyr crypto hash API for multiblock plus remainder returned 0"
12 - "Test Zephyr crypto arbitrary chunk size = \\d+"
13 - "Test Zephyr crypto arbitrary chunk size returned 0"
14 - "Test Zephyr crypto arbitrary chunk size = \\d+"
15 - "Test Zephyr crypto arbitrary chunk size returned 0"
16 - "Test Zephyr crypto arbitrary chunk size = \\d+"
17 - "Test Zephyr crypto arbitrary chunk size returned 0"
|
