| /hal_espressif-2.7.6/examples/system/unit_test/ |
| D | README.md | 5 … use [Unity](https://github.com/ThrowTheSwitch/Unity) library to add unit tests to custom componen…
9 * `UNITY_BEGIN()` and `UNITY_END()` macros allow Unity to count the number of tests which have pass…
11 …xample demonstrates usage of `TEST_CASE` macro and of the functions which execute registered tests.
13 … use built-in Unity facility, unity_fixture.h, to declare and execute the tests. However this is o…
28 … tests. Top level project is the actual application being developed. Test project included within …
30 ## Unit tests for a component
32 …the `testable` component, unit tests are added into `test` directory. `test` directory contains so…
40 * component.mk / CMakeLists.txt - Component makefile of tests
46 When the main application project is compiled, tests are not included. Test project includes the te…
69 2. Test project is responsible for running the tests.
[all …]
|
| /hal_espressif-2.7.6/components/mbedtls/test/ |
| D | test_mbedtls.c | 1 /* mbedTLS self-tests as unit tests
6 See also test_hwcrypto.c in esp32 component, which tests hardware crypto without mbedTLS.
25 TEST_CASE("mbedtls AES self-tests", "[aes]")
28 TEST_ASSERT_FALSE_MESSAGE(mbedtls_aes_self_test(1), "AES self-tests should pass.");
32 TEST_CASE("mbedtls MPI self-tests", "[bignum]")
35 TEST_ASSERT_FALSE_MESSAGE(mbedtls_mpi_self_test(1), "MPI self-tests should pass.");
39 TEST_CASE("mbedtls RSA self-tests", "[bignum]")
42 TEST_ASSERT_FALSE_MESSAGE(mbedtls_rsa_self_test(1), "RSA self-tests should pass.");
|
| /hal_espressif-2.7.6/docs/test/ |
| D | README.md | 3 This folder contains the files needed for running tests the ESP-IDF documentation building system.
5 Tests are divided into two categories: unit tests and integration tests:
7 ## Unit Tests
11 ## Integration Tests
12 …o the thigh integration with Sphinx some functionality is difficult to test with simple unit tests.
16 # Running Tests
20 It's also possible to run the tests locally by running the following commands from the test folder:
|
| /hal_espressif-2.7.6/tools/unit-test-app/ |
| D | README.md | 3 ESP-IDF unit tests are run using Unit Test App. The app can be built with the unit tests for a spec…
13 …the test app. Or `idf.py -T all build` to build the test app with all the tests for components hav…
23 …in the test app. Or `make TESTS_ALL=1` to build the test app with all the tests for components hav…
31 …tests to run on a smaller flash size, edit `partition_table_unit_tests_app.csv` and use `-T <compo…
33 # Running Unit Tests
35 The unit test loader will prompt by showing a menu of available tests to run:
38 * `*` to run all tests.
39 * `[tagname]` to run tests with "tag"
40 * `![tagname]` to run tests without "tag" (`![ignore]` is very useful as it runs all CI-enabled tes…
43 # Testing Unit Tests with CI
[all …]
|
| D | partition_table_unit_test_app.csv | 9 # these OTA partitions are used for tests, but can't fit real OTA apps in them
13 # flash_test partition used for SPI flash tests, WL FAT tests, and SPIFFS tests
|
| D | partition_table_unit_test_two_ota.csv | 10 # flash_test partition used for SPI flash tests, WL FAT tests, and SPIFFS tests
|
| /hal_espressif-2.7.6/docs/en/api-guides/ |
| D | unit-tests.rst | 5 …t test application that is based on the Unity - unit test framework. Unit tests are integrated in …
10 Unit tests are located in the ``test`` subdirectory of a component.
11 Tests are written in C, and a single C source file can contain multiple test cases.
16 Tests are added in a function in the C file as follows:
26 Identifiers are used to group related test, or tests with specific properties.
31 …`should list their sources manually <cmake-file-globbing>`; for component tests however, this requ…
41 See http://www.throwtheswitch.org/unity for more information about writing tests in Unity.
81 …5 test functions can be defined, each function will be the entry point of tests running on each DU…
101 …need to check if reset happens). Sometimes we expect to run some specific tests after certain kind…
122 Tests For Different Targets
[all …]
|
| D | unit-tests-legacy.rst | 7 …t 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.
18 Tests are added in a function in the C file as follows:
28 Identifiers are used to group related test, or tests with specific properties.
37 See http://www.throwtheswitch.org/unity for more information about writing tests in Unity.
77 …5 test functions can be defined, each function will be the entry point of tests running on each DU…
111 …need to check if reset happens). Sometimes we expect to run some specific tests after certain kind…
142 * ``make TESTS_ALL=1`` - build unit test app with tests for each component having tests in the ``te…
143 * ``make TEST_COMPONENTS='xxx'`` - build unit test app with tests for specific components.
[all …]
|
| /hal_espressif-2.7.6/examples/system/unit_test/test/main/ |
| D | example_unit_test_test.c | 18 /* These are the different ways of running registered tests. in app_main()
22 * (number of tests executed/failed/ignored) of tests executed between these calls. in app_main()
29 print_banner("Running tests with [mean] tag"); in app_main()
34 print_banner("Running tests without [fails] tag"); in app_main()
39 print_banner("Running all the registered tests"); in app_main()
|
| /hal_espressif-2.7.6/tools/kconfig_new/test/confserver/ |
| D | README.md | 1 # KConfig Tests
3 ## confserver.py tests
7 Then run the tests manually like this:
10 ./test_confserver.py --logfile tests.log
13 If a weird error message comes up from the test, check the log file (`tests.log`) which has the ful…
|
| /hal_espressif-2.7.6/tools/test_apps/ |
| D | README.md | 3 This directory contains a set of ESP-IDF projects to be used as tests only, which aim to exercise v…
16 * Test executor in `ttfw_idf` format if the project is intended to also run tests (otherwise the ex…
24 * `network` contains system network tests
25 * `system` contains tests on the internal chip features, debugging and development tools.
26 * `security` contains tests on the chip security features.
|
| /hal_espressif-2.7.6/tools/ci/python_packages/ttfw_idf/ |
| D | unity_test_parser.py | 20 …r'^(?P<num_tests>\d+) Tests (?P<num_failures>\d+) Failures (?P<num_ignored>\d+) Ignored\s*\r?\n(?P…
157 """The total number of tests parsed."""
161 """The number of tests with result PASS."""
165 """The number of tests with result FAIL."""
169 """The number of tests with result IGNORE."""
173 """Get an iterator for iterating over individual tests.
183 def tests(self): member in TestResults
184 """Get a list of all the tests (TestResult objects)."""
191 Convert the tests to JUnit XML.
202 … errors="0" failures="1" name="[suite_name]" package="[suite_name]" skipped="0" tests="8" time="0">
[all …]
|
| /hal_espressif-2.7.6/components/ulp/test/ulp/ |
| D | test_jumps_esp32.S | 19 /* tests for LT (less than) condition */
32 /* tests for LE (less or equal) condition */
43 /* tests for EQ (equal) condition */
56 /* tests for GE (greater or equal) condition */
72 /* tests for GT (greater than) condition */
|
| /hal_espressif-2.7.6/examples/protocols/http_server/advanced_tests/ |
| D | http_server_advanced_test.py | 31 # some of the `advanced_tests` are ignored. These tests are intended for verifying
34 # It is advised that all these tests be run locally, when making changes or adding new
44 binary_file = os.path.join(dut1.app.binary_path, 'tests.bin')
73 Utility.console_log('Sessions and Context Tests...')
102 Utility.console_log('Basic HTTP Client Tests...')
124 Utility.console_log('Error code tests...')
153 Utility.console_log('More than 95% of stack got used during tests')
|
| /hal_espressif-2.7.6/tools/ci/config/ |
| D | target-test.yml | 41 - .rules:tests:example_test-schedule
54 - .rules:tests:custom_test-schedule
62 - .rules:tests:unit_test
82 - .rules:tests:unit_test_32
87 - .rules:tests:unit_test_s2
92 - .rules:tests:unit_test
100 - .rules:tests:unit_test_32
105 - .rules:tests:unit_test_s2
110 … - .rules:tests:unit_test_c3 # due to the lack of runners, c3 tests will only be triggered by label
115 - .rules:tests:integration_test
|
| D | rules.yml | 170 .rules:tests:example_test-schedule:
176 .rules:tests:custom_test-schedule:
182 .rules:tests:unit_test:
187 .rules:tests:unit_test_32:
193 .rules:tests:unit_test_s2:
199 .rules:tests:unit_test_c3:
205 .rules:tests:integration_test:
|
| /hal_espressif-2.7.6/examples/bluetooth/bluedroid/ble/ble_compatibility_test/ |
| D | ble_compatibility_test_case.md | 14 Prior to conducting tests, please initialize the smartphone and the ESP device as follows:
24 * For tests marked with (*) further in the document, please bear in mind the following:
25 …f these tests. If such a test fails, it does not mean the phone fails to meet the test requirement…
26 …utive times, you need to record how many times the test was passed and then arrange targeted tests.
167 The connection must be stable throughout the tests.
179 * Tests to be added in the future:
|
| /hal_espressif-2.7.6/tools/ci/ |
| D | check_ut_cmake_make.sh | 3 # While we support GNU Make & CMake together, check that unit tests support both
13 echo "Some unit tests are not in both CMake and GNU Make:"
18 echo "Unit tests match"
|
| /hal_espressif-2.7.6/components/libsodium/test/ |
| D | test_sodium.c | 5 …of these libsodium test programs assert() things, but they're not complete unit tests - most expect
31 TEST_CASE("box tests", "[libsodium]")
43 TEST_CASE("ed25519_convert tests", "[libsodium][timeout=60]")
52 TEST_CASE("sign tests", "[libsodium]")
60 TEST_CASE("hash tests", "[libsodium]")
|
| /hal_espressif-2.7.6/components/driver/test/param_test/include/ |
| D | param_test.h | 9 * tests among the sets in a group.
45 * //non-DMA tests
89 * Then declare tests conveniently by:
110 …void (*pre_test)(void** contxt); ///< Initialization function called before tests begin. Initia…
111 void (*post_test)(void* context); ///< Deinit function called after all tests are done.
|
| /hal_espressif-2.7.6/components/nvs_flash/test_nvs_host/ |
| D | README.md | 13 * Run all quick tests:
18 * Run all tests (takes several hours)
|
| /hal_espressif-2.7.6/tools/test_idf_monitor/ |
| D | README.md | 5 New tests can be added into `test_list` of `run_test_idf_monitor.py` and placing the corresponding …
6 `tests` directory.
|
| /hal_espressif-2.7.6/examples/protocols/mdns/main/ |
| D | Kconfig.projbuild | 20 These services are advertized and evaluated in automated tests.
29 for evaluation of tests in CI
|
| /hal_espressif-2.7.6/examples/cxx/experimental/experimental_cpp_component/ |
| D | README.md | 12 # Tests chapter
13 To build the tests, first add them to the unit test's CMakeLists.txt:
|
| /hal_espressif-2.7.6/tools/test_apps/protocols/esp_netif/build_config/main/ |
| D | main.cpp | 29 // Calling CPP initialization tests in app_main()
31 // Calling C initialization tests in app_main()
|
