| /hal_espressif-3.4.0/docs/en/api-guides/ |
| D | linux-host-testing.rst | 5 …on esp32.com is highly welcome, though and may influence the future design of the host-based tests.
7 …verview of unit tests with IDF on Linux. For using unit tests on the target, please refer to :doc:…
9 Embedded Software Tests
12 Embedded software tests are challenging due to the following factors:
14 - Difficulties running tests efficiently.
17 …ost-based tests with `CMock <https://www.throwtheswitch.org/cmock>`_ are introduced. Linux host-ba…
25 …d using mocks does not fully represent the target device. Thus, two kinds of tests are recommended:
27 1. Unit tests which test program logic on a Linux machine, isolated through mocks.
28 2. System/Integration tests which test the interaction of components and the whole system. They run…
30 …first kind of tests. Refer to :doc:`target based unit testing <unit-tests>` for more information o…
[all …]
|
| D | unit-tests.rst | 7 …tests using a central unit test application which runs on the {IDF_TARGET_PATH_NAME}. These tests …
8 - Linux-host based unit tests in which all the hardware is abstracted via mocks. Linux-host based t…
13 Unit tests are located in the ``test`` subdirectory of a component. Tests are written in C, and a s…
17 Tests are added in a function in the C file as follows:
27 …tifier in square brackets. Identifiers are used to group related test, or tests with specific prop…
32 …`should list their sources manually <cmake-file-globbing>`; for component tests however, this requ…
42 See http://www.throwtheswitch.org/unity for more information about writing tests in Unity.
82 …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…
119 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-3.4.0/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-3.4.0/examples/protocols/http_server/advanced_tests/ |
| D | README.md | 1 # HTTP server advanced tests
5 HTTP server example to perform some advanced tests
40 I (5581) TESTS: Started HTTP server on port: '1234'
41 I (5581) TESTS: Max URI handlers: '9'
42 I (5581) TESTS: Max Open Sessions: '7'
43 I (5591) TESTS: Max Header Length: '512'
44 I (5591) TESTS: Max URI Length: '512'
45 I (5601) TESTS: Max Stack Size: '4096'
46 I (5601) TESTS: Registering basic handlers
47 I (5601) TESTS: No of handlers = 9
[all …]
|
| 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-3.4.0/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-3.4.0/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-3.4.0/components/esptool_py/esptool/ |
| D | CONTRIBUTING.rst | 104 Automated Integration Tests
107 …test <https://docs.pytest.org/>`_ integration suite with some integration tests for ``esptool.py``…
109 …`esptool.py`` installed (see `Development Setup`_) in your environment in order to run these tests.
111 The following tests run automatically by GitHub Actions for each Pull Request. You can run them loc…
113 * ``test_imagegen.py`` tests the ``elf2image`` command
114 * ``test_image_info.py`` tests the ``image_info`` command
115 * ``test_mergebin.py`` tests the ``merge_bin`` command
116 * ``test_modules.py`` tests the modules used by ``esptool.py`` for regressions
117 * ``test_espsecure.py`` tests ``espsecure.py`` functionality
119 The following tests are not run automatically by GitHub Actions, because they need real connected h…
[all …]
|
| /hal_espressif-3.4.0/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-3.4.0/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-3.4.0/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-3.4.0/components/mdns/test_afl_fuzz_host/ |
| D | README.md | 6 ## Building and running the tests using AFL
7 To build and run the tests using AFL(afl-clang-fast) instrumentation
16 ## Building the tests using GCC INSTR(off)
17 …tests without AFL instrumentations and instead of that use GCC compiler(In this case it will only …
|
| /hal_espressif-3.4.0/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-3.4.0/components/esp_rom/host_test/rom_test/ |
| D | README.md | 6 This unit test tests only if some of the supplied Linux functions seem to work correctly. The test …
30 Ideally, all tests pass, which is indicated by "All tests passed" in the last line:
36 All tests passed (8 assertions in 6 test cases)
|
| /hal_espressif-3.4.0/components/lwip/test_afl_host/ |
| D | README.md | 6 ## Building and running the tests using AFL
7 To build and run the tests using AFL(afl-clang-fast) instrumentation
16 ## Building the tests using GCC INSTR(off)
17 …tests without AFL instrumentations and instead of that use GCC compiler(In this case it will only …
|
| /hal_espressif-3.4.0/examples/cxx/experimental/experimental_cpp_component/host_test/esp_timer/ |
| D | README.md | 6 This unit test tests basic functionality of the `ESPTimer` class. The test does not use mocks. Inst…
30 Ideally, all tests pass, which is indicated by "All tests passed" in the last line:
35 All tests passed (9 assertions in 11 test cases)
|
| /hal_espressif-3.4.0/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-3.4.0/components/log/host_test/log_test/ |
| D | README.md | 6 This unit test tests basic functionality of the log component. The test does not use mocks. Instead…
30 Ideally, all tests pass, which is indicated by "All tests passed" in the last line:
35 All tests passed (8 assertions in 6 test cases)
|
| /hal_espressif-3.4.0/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…
14 * Test executor in `ttfw_idf` format if the project is intended to also run tests (otherwise the ex…
55 * `network` contains system network tests
56 * `system` contains tests on the internal chip features, debugging and development tools.
57 * `security` contains tests on the chip security features.
|
| /hal_espressif-3.4.0/components/libsodium/test/ |
| D | test_sodium.c | 10 …of these libsodium test programs assert() things, but they're not complete unit tests - most expect
36 TEST_CASE("box tests", "[libsodium]")
47 TEST_CASE("ed25519_convert tests", "[libsodium][timeout=60]")
55 TEST_CASE("sign tests", "[libsodium]")
63 TEST_CASE("hash tests", "[libsodium]")
|
| /hal_espressif-3.4.0/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-3.4.0/tools/ldgen/ |
| D | README.md | 19 ### Tests subsection
21 Unit tests are in the `test` directory. These tests are run as part of CI in the job `test_ldgen_on…
|
