Lines Matching refs:component

7 …test framework. They can be integrated into an ESP-IDF component by placing them in the component'…
13 Unit tests are located in the ``test`` subdirectory of a component. Tests are written in C, and a s…
32 …component CMakeLists.txt <component-directories>`, since they are themselves components (i.e., a t…
169 * ``idf.py -T all build`` - build unit test app with tests for each component having tests in the `…
170 … (For instance: ``idf.py -T heap build`` - build unit tests only for ``heap`` component directory).
291 …component, (i.e., the component under test), software mocking allows the dependencies of the compo…
293 …he component under test is dependent on should be mocked, thus allowing the test environment compl…
313 …component, called a *component mock*, the component needs to be overwritten in a particular way. O…
315 In the component mock, the following parts are specified:
320 …- Dependencies of the mock component (this is necessary e.g. if the headers include files from oth…
322 …NENT_OVERRIDEN_DIR`` to access the component directory of the original component and then register…
326 …idf_component_get_property(original_component_dir <original-component-name> COMPONENT_OVERRIDEN_DI…
332 The component mock also requires a separate ``mock`` directory containing a ``mock_config.yaml`` fi…
343 …component mock does not have to mock the original component in its entirety. As long as the test p…
345 …amples of component mocks can be found under :idf:`tools/mocks` in the IDF directory. General info…
350 …component with the mock component). This is done by either placing the component mock into the pro…
356 …xisting components in ESP-IDF with the component mock. The latter is particularly convenient if yo…
358 …nt_file:`esp_event/host_test/esp_event_unit_test/CMakeLists.txt` as an example of a component mock.