| /hal_espressif-3.4.0/tools/test_apps/system/panic/ |
| D | app_test.py | 4 import panic_tests as test namespace
11 test.task_wdt_inner(env, 'panic')
16 test.task_wdt_inner(env, 'coredump_uart_elf_crc')
21 test.task_wdt_inner(env, 'coredump_uart_bin_crc')
26 test.task_wdt_inner(env, 'coredump_flash_elf_sha')
31 test.task_wdt_inner(env, 'coredump_flash_bin_crc')
36 test.task_wdt_inner(env, 'gdbstub')
43 test.int_wdt_inner(env, 'panic')
48 test.int_wdt_inner(env, 'coredump_uart_elf_crc')
53 test.int_wdt_inner(env, 'coredump_uart_bin_crc')
[all …]
|
| /hal_espressif-3.4.0/components/unity/ |
| D | unity_runner.c | 111 static void unity_run_single_test(const test_desc_t *test) in unity_run_single_test() argument
114 UnityPrint(test->name); in unity_run_single_test()
120 Unity.TestFile = test->file; in unity_run_single_test()
121 Unity.CurrentDetail1 = test->desc; in unity_run_single_test()
124 if (test->test_fn_count == 1) { in unity_run_single_test()
125 unity_default_test_run(test->fn[0], test->name, test->line); in unity_run_single_test()
127 int selection = multiple_function_option(test); in unity_run_single_test()
129 if (selection != (test->test_fn_count - 1)) { in unity_run_single_test()
148 const test_desc_t *test; in unity_run_single_test_by_index() local
149 for (test = s_unity_tests_first; test != NULL && index != 0; test = test->next, --index) { in unity_run_single_test_by_index()
[all …]
|
| D | Kconfig | 25 bool "Colorize test output"
28 If set, Unity will colorize test results using console escape sequences.
32 bool "Include ESP-IDF test registration/running helpers"
37 - TEST_CASE macro which performs automatic registration of test functions
38 - Functions to run registered test functions: unity_run_all_tests,
40 - Interactive menu which lists test cases and allows choosing the tests to
43 Disable if a different test registration mechanism is used.
46 bool "Include Unity test fixture"
51 implement test groups.
54 bool "Print a backtrace when a unit test fails"
[all …]
|
| /hal_espressif-3.4.0/tools/test_apps/peripherals/i2c_wifi/ |
| D | README.md | 5 This test demonstrates basic usage of I2C driver with wifi softAP.
16 ## How to use test
20 To run this test, you should have at least one ESP development board for master. But to make this t…
64 I (359) I2C-wifi test: ESP_WIFI_MODE_AP
97 I (609) I2C-wifi test: wifi_init_softap finished. SSID:myssid password:mypassword channel:1
106 I (23609) I2C-wifi test: 6a 1b 05 1f 1f 08 01 20 19 03 27
107 I (23619) I2C-wifi test: 6a 1b 05 1f 1f 08 01 20 19 03 27
108 I (23629) I2C-wifi test: 6a 1b 05 1f 1f 08 01 20 19 03 27
109 I (23639) I2C-wifi test: 6a 1b 05 1f 1f 08 01 20 19 03 27
110 I (23649) I2C-wifi test: 6a 1b 05 1f 1f 08 01 20 19 03 27
[all …]
|
| /hal_espressif-3.4.0/docs/en/api-guides/ |
| D | unit-tests-legacy.rst | 7 …it test application that is based on the Unity - unit test framework. Unit tests are integrated in…
12 Unit tests are located in the ``test`` subdirectory of a component.
13 Tests are added in C files, a single C file can include multiple test cases.
14 Test files start with the word "test".
16 Each test file should include the ``unity.h`` header and the header for the C module to be tested.
22 TEST_CASE("test name", "[module name]"
24 // Add test here
27 The first argument is a descriptive name for the test, the second argument is an identifier in squa…
28 Identifiers are used to group related test, or tests with specific properties.
31 …`` and ``UNITY_END()`` in each test case. ``unity_platform.c`` will run ``UNITY_BEGIN()`` autonom…
[all …]
|
| D | unit-tests.rst | 5 ESP-IDF provides the following methods to test software.
7 …test application which runs on the {IDF_TARGET_PATH_NAME}. These tests use the `Unity <https://www…
13 …test`` subdirectory of a component. Tests are written in C, and a single C source file can contain…
15 Each test file should include the ``unity.h`` header and the header for the C module to be tested.
21 TEST_CASE("test name", "[module name]"
23 // Add test here
26 - The first argument is a descriptive name for the test.
27 …s an identifier in square brackets. Identifiers are used to group related test, or tests with spec…
30 …`` and ``UNITY_END()`` in each test case. ``unity_platform.c`` will run ``UNITY_BEGIN()`` autonom…
32 …test`` subdirectory should contain a :ref:`component CMakeLists.txt <component-directories>`, sinc…
[all …]
|
| /hal_espressif-3.4.0/tools/unit-test-app/ |
| D | README.md | 3 …be built with the unit tests for a specific component. Unit tests are in `test` subdirectories of …
11 * Change into `tools/unit-test-app` directory
13 …ts to be included in the test app. Or `idf.py -T all build` to build the test app with all the tes…
15 …test have a few preset sdkconfigs. It provides command `idf.py ut-clean-config_name` and `idf.py u…
21 * Change into `tools/unit-test-app` directory
23 …nts to be included in the test app. Or `make TESTS_ALL=1` to build the test app with all the tests…
25 …test have a few preset sdkconfigs. It provides command `make ut-clean-config_name` and `make ut-bu…
29 The unit test partition table assumes a 4MB flash size. When testing `-T all` or `TESTS_ALL=1` (Leg…
35 The unit test loader will prompt by showing a menu of available tests to run:
37 * Type a number to run a single test.
[all …]
|
| /hal_espressif-3.4.0/examples/system/unit_test/ |
| D | README.md | 7 * _Assertions_ (`TEST_ASSERT` and similar) are used when writing the test cases. See [the reference…
11 …ates _test registration_ feature of ESP-IDF. This feature works when unit test functions are decla…
22 + test — Test project directory
26 …/` and `Makefile` / `CMakeLists.txt`, this project includes a *test project* in its *test* subdire…
32 Inside the `testable` component, unit tests are added into `test` directory. `test` directory conta…
39 - test - Test directory of the component
56 As explained above, this example contains two projects: application project and test project.
58 For the test project, you can open the project configuration menu (`idf.py menuconfig`) and explore…
62 As explained above, this example contains two projects: application project and test project.
71 * Enter `test` directory (`unit_test/test`), and run `idf.py -p PORT flash monitor`.
[all …]
|
| /hal_espressif-3.4.0/examples/network/network_tests/ |
| D | README.md | 1 # Intel net test suite for LwIP network stack
3 This project provides a test interface to esp32 network stack in order to execute standard set of
4 Intel network test suite defined in TTCN3 framework.
7 *This is an internal ESP-IDF test and not a user project example*
9 ## Execute net test suite
17 * Clone a repository https://github.com/intel/net-test-suites.git and install titan core as describ…
18 …$IDF_PATH/components/lwip/weekend_test`) to `src` subdir of the cloned repository `net-test-suites`
19 * Rebuild the netsuite tests (according to README.md in net-test-suite) by executing `source make.s…
30 ## Run test
32 1) Start the test server which would pass packets from TTCN3 test suite into ESP32 board in `$IDF_P…
[all …]
|
| /hal_espressif-3.4.0/tools/ci/python_packages/ttfw_idf/ |
| D | unity_test_parser.py | 209 for test in self._tests:
210 if test.result() == 'PASS':
212 junit_xml.TestCase(name=test.name(), classname=test.group())
216 name=test.name(),
217 classname=test.group(),
218 file=test.file(),
219 line=test.line(),
221 if test.result() == 'FAIL':
223 message=test.message(), output=test.full_line()
225 elif test.result() == 'IGNORE':
[all …]
|
| /hal_espressif-3.4.0/tools/test_idf_size/ |
| D | app.map | 3 /home/user/esp/esp-idf/tools/unit-test-app/build/cxx/libcxx.a(cxx_guards.o)
5 /home/user/esp/esp-idf/tools/unit-test-app/build/cxx/libcxx.a(cxx_exception_stubs.o)
7 /home/user/esp/esp-idf/tools/unit-test-app/build/esp32/libesp32.a(panic.o)
8 … /home/user/esp/esp-idf/tools/unit-test-app/build/cxx/libcxx.a(cxx_guards.o) (abort)
9 /home/user/esp/esp-idf/tools/unit-test-app/build/esp32/libesp32.a(cpu_start.o)
11 /home/user/esp/esp-idf/tools/unit-test-app/build/esp32/libesp32.a(clk.o)
12 … /home/user/esp/esp-idf/tools/unit-test-app/build/esp32/libesp32.a(cpu_start.o) (esp_clk_init)
13 /home/user/esp/esp-idf/tools/unit-test-app/build/esp32/libesp32.a(esp_err_to_name.o)
14 … /home/user/esp/esp-idf/tools/unit-test-app/build/esp32/libesp32.a(panic.o) (esp_err_to_name)
15 /home/user/esp/esp-idf/tools/unit-test-app/build/esp32/libesp32.a(crosscore_int.o)
[all …]
|
| /hal_espressif-3.4.0/tools/test_idf_monitor/ |
| D | run_test_idf_monitor.py | 99 def test_iteration(runner, test): argument
105 … print('\nRunning test on {} with filter "{}" and expecting {}'.format(test[0], test[1], test[2]))
107 with open(OUT_DIR + test[2], 'w', encoding='utf-8') as o_f, \
111 '--print_filter', test[1],
113 '--elf-file', test[4]]
114 monitor_cmd += test[5].split()
118 print('\tMonitor timeout: {} seconds'.format(test[3]))
126 monitor_watchdog = threading.Timer(test[3], monitor_timeout, [proc])
137 with open(IN_DIR + test[0], 'rb') as f:
144 close_end_time = start + 0.75 * test[3] # time when the process is close to be killed
[all …]
|
| /hal_espressif-3.4.0/components/espcoredump/test_apps/ |
| D | README.md | 6 This test app is used to provide built binaries for the test cases under test folders
8 ## Update coredump.64 test data
10 To update `test/<target>/coredump.64` build a `test_apps` for a target, flash and get a base64 text…
12 ## Update expected_output test data
14 To update `test/<target>/expected_output` run
18 …p.py --chip $TARGET info_corefile -c ../test/$TARGET/coredump.b64 -t b64 -m ./build/test_core_dump…
25 ## Update ELF test binaries
27 The ELF test binaries are placed in a different git repository, _idf-coredump-elf_, to avoid puttin…
30 See _idf-coredump-elf/README.md_ to use `build_espcoredump.sh` and generate test ELF binaries
|
| /hal_espressif-3.4.0/components/bt/esp_ble_mesh/mesh_core/ |
| D | health_srv.c | 45 for (i = 0U; i < ARRAY_SIZE(srv->test.curr_faults); i++) { in health_get_curr_fault_count()
46 if (srv->test.curr_faults[i] != HEALTH_NO_FAULT) { in health_get_curr_fault_count()
62 array_size = current ? ARRAY_SIZE(srv->test.curr_faults) : ARRAY_SIZE(srv->test.reg_faults); in health_get_fault_value()
69 uint8_t fault = current ? srv->test.curr_faults[i] : srv->test.reg_faults[i]; in health_get_fault_value()
81 for (i = 0; i < srv->test.id_count; i++) { in health_is_test_id_exist()
82 if (srv->test.test_ids[i] == test_id) { in health_is_test_id_exist()
97 msg = bt_mesh_alloc_buf(4 + ARRAY_SIZE(srv->test.reg_faults) + 4); in health_send_fault_status()
104 net_buf_simple_add_u8(msg, srv->test.prev_test_id); in health_send_fault_status()
105 net_buf_simple_add_le16(msg, srv->test.company_id); in health_send_fault_status()
136 if (company_id != srv->test.company_id) { in health_fault_get()
[all …]
|
| /hal_espressif-3.4.0/tools/ci/ |
| D | executable-list.txt | 7 components/espcoredump/test/test_espcoredump.py
8 components/espcoredump/test/test_espcoredump.sh
74 tools/esp_app_trace/test/logtrace/test.sh
75 tools/esp_app_trace/test/sysview/test.sh
89 tools/kconfig_new/test/confgen/test_confgen.py
90 tools/kconfig_new/test/confserver/test_confserver.py
91 tools/kconfig_new/test/gen_kconfig_doc/test_kconfig_out.py
92 tools/kconfig_new/test/gen_kconfig_doc/test_target_visibility.py
94 tools/ldgen/test/test_entity.py
95 tools/ldgen/test/test_fragments.py
[all …]
|
| /hal_espressif-3.4.0/docs/zh_CN/api-guides/ |
| D | unit-tests-legacy.rst | 9 ESP-IDF 仓库中每个组件的 ``test`` 子目录中。
14 单元测试被添加在相应组件的 ``test`` 子目录中，测试用例写在 C 文件中，一个
15 C 文件可以包含多个测试用例。测试文件的名字要以 “test” 开头。
24 TEST_CASE("test name", "[module name]"
76 …TEST_CASE_MULTIPLE_DEVICES("gpio multiple devices test example", "[driver]", gpio_master_test, gpi…
155 切换到 ``tools/unit-test-app`` 目录下进行配置和编译：
159 - ``make TESTS_ALL=1`` - 编译单元测试程序，测试每个组件 ``test``
188 Here's the test menu, pick your combo:
192 (4) "Verify unit test app image" [bootloader_support]
201 (13) "gpio master/slave test example" [ignore][misc][test_env=UT_T2_1][multi_device]
[all …]
|
| D | unit-tests.rst | 7 - 一种是在目标芯片上运行并基于 ``Unity`` 测试框架的应用程序。这些单元测试用例都保存在 ESP-IDF 仓库中，分别存放在每个组件的 ``test`` 子目录中。本文主要介绍这种单元测试…
13 单元测试被添加在相应组件的 ``test`` 子目录中，测试用例写在 C 文件中，一个 C 文件可以包含多个测试用例。测试文件的名字要以 “test” 开头。
21 TEST_CASE("test name", "[module name]")
32 ``test`` 子目录应包含 :ref:`组件 CMakeLists.txt <component-directories>`，因为他们本身就是一种组件（即测试组件）。ESP-IDF 使用了 Un…
34 总的来说，``test`` 子目录下最小的 CMakeLists.txt 文件可能如下所示:
76 …TEST_CASE_MULTIPLE_DEVICES("gpio multiple devices test example", "[driver]", gpio_master_test, gpi…
127 TEST_CASE("a test that is not ready for esp32 and esp8266 yet", "[]")
147 - 请勿将测试代码放在 ``test/芯片版本`` 目录下面，然后用 CMakeLists.txt 来选择其中一个进行编译。这是因为测试代码比实现代码更容易被复用。如果你将一些代码放在 ``test…
166 切换到 ``tools/unit-test-app`` 目录下进行配置和编译：
169 * ``idf.py -T all build`` - 编译单元测试程序，测试每个组件 ``test`` 子目录下的用例。
[all …]
|
| /hal_espressif-3.4.0/examples/cxx/experimental/esp_event_cxx/ |
| D | README.md | 32 event base test, ID: 0; called first round
33 event base test, ID: 1; called first round
35 event base test, ID: 0; called second round
36 event base test, ID: 1; called second round
37 event base test, ID: 0; called second round
38 event base test, ID: 1; called second round
39 event base test, ID: 0; called second round
40 event base test, ID: 1; called second round
41 event base test, ID: 0; called second round
42 event base test, ID: 1; called second round
|
| /hal_espressif-3.4.0/tools/test_apps/protocols/mqtt/publish_connect_test/ |
| D | README.md | 4 # ESP-MQTT advanced publish and connect test project
6 Main purpose of this application is to test the MQTT library to correctly publish and receive messa…
7 It is possible to run this example manually without any test to exercise how the MQTT library deals…
15 - test-type: "conn" if connection test (host, port, test-case number)
16 - publish test:
25 …test-app can be executed on any ESP32 board, the only required interface is WiFi and connection to…
|
| /hal_espressif-3.4.0/tools/ci/python_packages/tiny_test_fw/docs/ |
| D | index.rst | 9 We have a lot of test which depends on interact with DUT via communication port.
10 Usually we send command to the port and then check response to see if the test succeed.
55 SOP for adding test cases
58 1. Import test framework:
64 2. Define test case:
67 1. Define test case ``test_xxx(env, extra_data)``
68 * env: instance of test env, see :doc:`Test Env <Env>` for details
69 * extra_data: extra data passed from test case caller
70 2. Add decorator for test case
71 * add decorator ``TinyFW.test_method`` to test method
[all …]
|
| /hal_espressif-3.4.0/ |
| D | .gitignore | 48 # Unit test app files
49 tools/unit-test-app/sdkconfig
50 tools/unit-test-app/sdkconfig.old
51 tools/unit-test-app/build
52 tools/unit-test-app/builds
53 tools/unit-test-app/output
54 tools/unit-test-app/test_configs
59 # test application build files
64 # IDF monitor test
|
| /hal_espressif-3.4.0/tools/test_apps/protocols/openssl/ |
| D | README.md | 4 # ESP-OPENSSL connect test project
6 Main purpose of this application is to test the ESP-OPENSSL library to correctly connect/refuse con…
7 It is possible to run this example manually without any test to exercise ESP-OPENSSL library.
11 test-type: "conn" connection test (host, port, test-case)
14 This test-app can be executed on any ESP32 board, the only required interface is WiFi and connectio…
|
| /hal_espressif-3.4.0/components/tcp_transport/test/ |
| D | test_transport_fixtures.c | 251 tcp_connect_test_t test = connect_test_setup(¶ms); in tcp_transport_test_connection_timeout() local
252 TEST_ASSERT_NOT_NULL(test); in tcp_transport_test_connection_timeout()
256 …EventBits_t bits = xEventGroupWaitBits(test->tcp_connect_done, TCP_CONNECT_DONE, true, true, test-… in tcp_transport_test_connection_timeout()
260 TEST_ASSERT_EQUAL(-1, test->connect_return_value); // Connection failed with -1 in tcp_transport_test_connection_timeout()
266 close_if_valid(&test->last_connect_sock); in tcp_transport_test_connection_timeout()
268 connect_test_teardown(test); in tcp_transport_test_connection_timeout()
287 tcp_connect_test_t test = connect_test_setup(¶ms); in tcp_transport_test_socket_options() local
288 TEST_ASSERT_NOT_NULL(test); in tcp_transport_test_socket_options()
291 xEventGroupWaitBits(test->tcp_connect_done, TCP_LISTENER_ACCEPTED, true, true, test->max_wait); in tcp_transport_test_socket_options()
310 connect_test_teardown(test); in tcp_transport_test_socket_options()
|
| /hal_espressif-3.4.0/.gitlab/ci/dependencies/ |
| D | README.md | 27 "test-{0}-{1}":
46 | test-a-c | a-c | a | build-a |
47 | test-a-d | a-d | a | build-a |
48 | test-b-c | b-c | b | build-b |
49 | test-b-d | b-d | b | build-b |
58 test-a-c:
63 `rule` `test-a-c` will be turned into:
67 | test-a-c | overwrite |
77 | test-a-c | a-c | a |
78 | test-a-d | a-d | a |
[all …]
|
| /hal_espressif-3.4.0/tools/unit-test-app/components/test_utils/ |
| D | Kconfig | 1 menu "IDF unit test"
4 int "Priority of Unity test task"
8 int "CPU to run Unity test task on"
12 int "Stack size of Unity test task, in bytes"
28 bool "Ignore performance test results"
34 but not fail the test if the threshold is not met.
|
