| /hal_espressif-3.5.0/tools/unit-test-app/ |
| D | README.md | 1 # Unit Test App
3 … tests are run using Unit Test App. The app can be built with the unit tests for a specific compon…
5 # Building Unit Test App
11 * Change into `tools/unit-test-app` directory
12 * `idf.py menuconfig` to configure the Unit Test App.
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
22 * `make menuconfig` to configure the Unit Test App.
23 …nts to be included in the test app. Or `make TESTS_ALL=1` to build the test app with all the tests…
[all …]
|
| /hal_espressif-3.5.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.5.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…
9 Normal Test Cases
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.
[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…
10 Normal Test Cases
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…
[all …]
|
| /hal_espressif-3.5.0/components/efuse/test/ |
| D | esp_efuse_test_table.c | 17 {EFUSE_BLK3, 0, 8}, // TEST field,
21 {EFUSE_BLK3, 10, 8}, // TEST field,
22 {EFUSE_BLK3, 80, 8}, // TEST field,
26 {EFUSE_BLK3, 22, 6}, // TEST field,
30 {EFUSE_BLK1, 22, 49}, // TEST field,
31 {EFUSE_BLK1, 89, 39}, // TEST field,
32 {EFUSE_BLK1, 71, 18}, // TEST field,
33 {EFUSE_BLK1, 0, 16}, // TEST field,
34 {EFUSE_BLK2, 0, 17}, // TEST field,
35 {EFUSE_BLK2, 60, 43}, // TEST field,
[all …]
|
| D | esp_efuse_test_table.csv | 10 # ./efuse_table_gen.py test/esp_efuse_test_table.csv
12 TEST1_LEN_8, EFUSE_BLK3, 0, 8, TEST field
14 TEST2_LEN_16, EFUSE_BLK3, 10, 8, TEST field
15 , EFUSE_BLK3, 80, 8, TEST field
17 TEST3_LEN_6, EFUSE_BLK3, 22, 6, TEST field
19 TEST4_LEN_182, EFUSE_BLK1, 22, 49, TEST field
20 , EFUSE_BLK1, 89, 39, TEST field
21 , EFUSE_BLK1, 71, 18, TEST field
22 , EFUSE_BLK1, 0, 16, TEST field
23 , EFUSE_BLK2, 0, 17, TEST field
[all …]
|
| /hal_espressif-3.5.0/components/unity/ |
| D | unity_runner.c | 26 // Pointers to the head and tail of linked list of test description structs:
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()
117 // Unit test runner expects to see test name before the test starts 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()
[all …]
|
| /hal_espressif-3.5.0/tools/ci/python_packages/tiny_test_fw/ |
| D | TinyFW.py | 15 """ Interface for test cases. """
31 …Raise this exception if one or more test cases fail in a 'normal' way (ie the test runs but fails,…
36 'cases' argument is the names of one or more test cases
38 …message = 'Test case{} failed: {}'.format('s' if len(cases) > 1 else '', ', '.join(str(c) for c in…
44 default test configs. There're 3 places to set configs, priority is (high -> low):
46 1. overwrite set by caller of test method
87 # wrapper for junit test report
91 JUNIT_DEFAULT_TEST_SUITE = 'test-suite'
100 """ Output current test result to file. """
107 By default, the test framework will handle junit test report automatically.
[all …]
|
| /hal_espressif-3.5.0/tools/test_apps/peripherals/i2c_wifi/ |
| D | README.md | 1 # I2C-WIFI Test
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…
36 Open the project configuration menu (`idf.py menuconfig`). Then go into `Test Configuration` menu.
58 ## Test Output
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
[all …]
|
| /hal_espressif-3.5.0/tools/ci/python_packages/ttfw_idf/ |
| D | unity_test_parser.py | 2 Modification version of https://github.com/ETCLabs/unity-test-parser/blob/develop/unity_test_parser…
7 Parse the output of the Unity Test Framework for C. Parsed results are held in the TestResults
17 _UNITY_FIXTURE_VERBOSE_PREFIX_REGEX = re.compile(r'(?P<prefix>TEST\((?P<test_group>[^\s,]+), (?P<te…
37 """Statistics about a test collection"""
56 Class representing the result of a single test.
58 Contains the test name, its result (either PASS, FAIL or IGNORE), the file and line number if
59 the test result was not PASS, and an optional message.
97 """The test name."""
101 """The test result, one of PASS, FAIL or IGNORED."""
106 The test group, if applicable.
[all …]
|
| /hal_espressif-3.5.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…
28 … unit tests. Top level project is the actual application being developed. Test project included wi…
32 Inside the `testable` component, unit tests are added into `test` directory. `test` directory conta…
39 - test - Test directory of the component
41 * test_mean.c - Test source file
46 When the main application project is compiled, tests are not included. Test project includes the te…
56 As explained above, this example contains two projects: application project and test project.
[all …]
|
| /hal_espressif-3.5.0/examples/bluetooth/bluedroid/ble/ble_compatibility_test/ |
| D | ble_compatibility_test_case.md | 1 # Test Case for BLE Smartphone Compatibility
3 This document provides a test case for BLE smartphone compatibility and includes detailed procedure…
9 * ESP device which needs to flash [this test program] (https://github.com/espressif/esp-idf/blob/ma…
17 * Set the maximum transmission unit (MTU) of the device to 33 bytes, to test the assembly and divis…
19 * Before flashing the test program onto the ESP device, make sure to erase the contents of the flas…
25 … affect the results of these tests. If such a test fails, it does not mean the phone fails to meet…
26 …g "Test for Connection Success Rate" as an example: if the test cannot be passed for 10 consecutiv…
30 ## Test for ADV Performance (*)
36 ### Test Results
38 The test is passed, if you get the following results:
[all …]
|
| /hal_espressif-3.5.0/tools/ci/ |
| D | test_check_kconfigs.py | 49 self.expect_error('\ttest', expect=' test')
50 self.expect_error('\t test', expect=' test')
51 self.expect_error(' \ttest', expect=' test')
52 self.expect_error(' \t test', expect=' test')
53 self.expt_success(' test')
54 self.expt_success('test')
59 self.expect_error('test ', expect='test')
60 self.expt_success('test')
69 self.expect_error('test \\', expect=None)
80 self.expect_error('source "notKconfig.test"', expect='source "Kconfig.notKconfig.test"')
[all …]
|
| /hal_espressif-3.5.0/.gitlab/ci/ |
| D | target-test.yml | 21 TEST_FW_PATH: "$CI_PROJECT_DIR/tools/tiny-test-fw"
23 ENV_FILE: "$CI_PROJECT_DIR/ci-test-runner-configs/$CI_RUNNER_DESCRIPTION/EnvConfig.yml"
27 # first test if config file exists, if not exist, exit 0
29 …und. Consider decreasing the parallel count of this job in ".gitlab/ci/target-test.yml"'; exit 0; }
30 # clone test env configs
32 - python $CHECKOUT_REF_SCRIPT ci-test-runner-configs ci-test-runner-configs
33 # git clone the known failure cases repo, run test
35 # run test
50 - .rules:test:example_test-esp32
70 - .rules:test:example_test-esp32
[all …]
|
| /hal_espressif-3.5.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.5.0/tools/ldgen/test/ |
| D | test_fragments.py | 46 FRAGMENT_TYPES['test'] = SampleFragment
82 [test:test]
103 [test:test]
112 [test:test]
120 [test:test]
138 [test:test]
158 [test:test]
188 [test:test]
210 [test:test]
224 [test:test]
[all …]
|
| /hal_espressif-3.5.0/examples/peripherals/twai/twai_self_test/ |
| D | README.md | 1 # TWAI Self Test Example
5 …Test Example demonstrates how a node can transmit TWAI messages to itself using the TWAI driver's …
48 I (345) TWAI Self Test: Driver installed
49 I (345) TWAI Self Test: Driver started
50 I (355) TWAI Self Test: Msg received - Data = 0
52 I (1335) TWAI Self Test: Msg received - Data = 99
53 I (1335) TWAI Self Test: Driver stopped
54 I (1435) TWAI Self Test: Driver started
55 I (1435) TWAI Self Test: Msg received - Data = 0
57 I (2425) TWAI Self Test: Msg received - Data = 99
[all …]
|
| /hal_espressif-3.5.0/components/esptool_py/esptool/ |
| D | .gitlab-ci.yml | 5 - test
21 stage: test
51 junit: test/report.xml
56 PYTHONPATH: "$PYTHONPATH:${CI_PROJECT_DIR}/test"
57 COVERAGE_PROCESS_START: "${CI_PROJECT_DIR}/test/.covconf"
58 PYTEST_ADDOPTS: "-sv --junitxml=test/report.xml --color=yes"
60 - coverage run --parallel-mode -m pytest ${CI_PROJECT_DIR}/test/test_imagegen.py
61 - coverage run --parallel-mode -m pytest ${CI_PROJECT_DIR}/test/test_espsecure.py
62 - coverage run --parallel-mode -m pytest ${CI_PROJECT_DIR}/test/test_merge_bin.py
63 - coverage run --parallel-mode -m pytest ${CI_PROJECT_DIR}/test/test_image_info.py
[all …]
|
| /hal_espressif-3.5.0/components/freertos/test/ |
| D | test_freertos_backported_functions.c | 2 * Test features that are backported from version FreeRTOS 9.0.0.
4 * 1) Test backported timer functions
6 * 2) Test backported queue/semaphore functions
10 * 3) Test static allocation of tasks
12 * 4) Test static allocation of event group
14 * 5) Test Thread Local Storage Pointers and Deletion Callbacks
19 * the following test cases (see Queue Registry test cases instead)
32 /* ---------------------Test 1: Backported Timer functions-----------------------
33 * Test xTimerCreateStatic(), vTimerSetTimerId(), xTimerGetPeriod(), xTimerGetExpiryTime()
35 * This test creates a one-shot static timer, sets/checks the timer's id and period. Then ensures
[all …]
|
| /hal_espressif-3.5.0/tools/ci/python_packages/tiny_test_fw/Utility/ |
| D | CIAssignTest.py | 16 Common logic to assign test cases to CI jobs.
20 * Gitlab CI jobs are static in ``.gitlab-ci.yml``. We can't dynamically create test jobs
21 * For test job running on DUT, we use ``tags`` to select runners with different test environment
22 * We have ``assign_test`` stage, will collect cases, and then assign them to correct test jobs
25 * dynamically filter test case we want to test
26 * alert user if they forget to add CI jobs and guide how to add test jobs
27 * the last step of ``assign_test`` is to output config files, then test jobs will run these cases
29 The Basic logic to assign test cases is as follow:
36 4. parse and filter the test jobs from CI config file
63 # Matching CI job rules could be different from the way we want to group test cases.
[all …]
|
| /hal_espressif-3.5.0/tools/test_apps/ |
| D | README.md | 1 # Test Apps
5 various conditions or combination with other components, including custom test frameworks.
7 The test apps are not intended to demonstrate the ESP-IDF functionality in any way.
9 # Test Apps projects
11 Test applications are treated the same way as ESP-IDF examples, so each project directory shall con…
14 * Test executor in `ttfw_idf` format if the project is intended to also run tests (otherwise the ex…
15 - test file in the project dir must end with `_test.py`, by should be named `app_test.py`
16 - test cases shall be decorated with `@ttfw_idf.idf_custom_test(env_tag="...")`
33 ## Test Execution
35 …e test or test app test supports more targets than just `ESP32`, then the `app_test.py` file needs…
[all …]
|
| /hal_espressif-3.5.0/tools/unit-test-app/tools/ |
| D | UnitTestParser.py | 23 'auto test': 'Yes',
25 'test point 1': 'basic function',
27 'test environment': 'UT_T1_1',
31 'Test App': 'UT',
36 """ parse unit test cases from build files and create files for test bench """
44 TAG_DEF_FILE = os.path.join('tools', 'unit-test-app', 'tools', 'TagDefinition.yml')
45 MODULE_DEF_FILE = os.path.join('tools', 'unit-test-app', 'tools', 'ModuleDefinition.yml')
46 CONFIG_DEPENDENCY_FILE = os.path.join('tools', 'unit-test-app', 'tools', 'ConfigDependency.yml')
49 UT_CONFIG_FOLDER = os.path.join('tools', 'unit-test-app', 'configs')
50 ELF_FILE = 'unit-test-app.elf'
[all …]
|
| /hal_espressif-3.5.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.5.0/components/driver/test/param_test/include/ |
| D | param_test.h | 7 * Parameterized Test Framework
10 * This framework helps to test different parameter sets with the same program.
13 * A parameter group is a group of several parameter sets. Each unit test performs
16 * The test will be execute in the following sequence:
20 * 4. ``loop``: execute test program for the set in the initialized context
29 * //The test work till the frequency below,
72 * 3. Define your test functions, and wrap them in the ``param_test_func_t``:
83 …* 5. Declare the test function by TEST_SINGLE_BOARD (for single board test), or TEST_MASTER_SLAVE(…
89 …* NOTE: suggest to define your own macro to wrap 4 and 5 if your tag and test functions are the sa…
102 #define PTEST_MASTER_NAME(name) PTEST_MASTER_##name ///< test function name of master
[all …]
|
| /hal_espressif-3.5.0/tools/test_idf_py/ |
| D | idf_ext.py | 6 print('Output from test-verbose')
14 'names': ['--test-0'],
19 'names': ['--test-1'],
24 'names': ['--test-2'],
29 'names': ['--test-3'],
36 'names': ['--test-4'],
44 'names': ['--test-5'],
54 'test-verbose': {
58 'test-0': {
63 'names': ['--test-sub-0'],
[all …]
|
