Historia

Sonika Rathi 12e7e3f1a2 Merge branch 'update/sdmmc_test_app' into 'master' fix(sdmmc): Migrate erase/trim test cases from unit-test-app to component-test-app See merge request espressif/esp-idf!26799		2023-12-15 23:50:08 +08:00
..
build_system	feat(ci): Enable p4 example, test_apps and unit tests CI build	2023-08-24 12:51:19 +08:00
configs	feat(freertos): Exposed Kconfig option for configUSE_LIST_DATA_INTEGRITY_CHECK_BYTES	2023-11-09 14:54:13 +01:00
linux_compatible	fix(freertos/idf): Fix invalid xCoreID arguments in single-core	2023-12-02 15:46:07 +08:00
peripherals/i2c_wifi	…
phy	ci(tsens): add new test tsens phy coexist	2023-07-31 12:13:24 +08:00
protocols	ci(mqtt): Move publish tests to nightly	2023-10-20 07:44:35 +02:00
security	feat(secure_boot): add secure boot support for esp32p4	2023-10-12 10:12:54 +05:30
storage	fix(sdmmc): remove the legacy test cases from 'components/sdmmc/test'	2023-12-06 11:14:20 +01:00
system	feat(esp32c5): support esp32c5 g0 components	2023-12-08 15:12:24 +08:00
.build-test-rules.yml	feat(esp32c5): support esp32c5 g0 components	2023-12-08 15:12:24 +08:00
README.md	ci: remove ttfw related info in tools/test_apps	2023-04-07 12:29:30 +08:00

README.md

Test Apps

This directory contains a set of ESP-IDF projects to be used as tests only, which aim to exercise various configuration of components to check completely arbitrary functionality should it be building only, executing under various conditions or combination with other components, including custom test frameworks.

The test apps are not intended to demonstrate the ESP-IDF functionality in any way.

Test Apps projects

Test applications are treated the same way as ESP-IDF examples, so each project directory shall contain

Build recipe in cmake and the main component with app sources
Configuration files, sdkconfig.ci and similar (see below)
Python test scripts, pytest_....py (optional)

Test Apps layout

The test apps should be grouped into subdirectories by category. Categories are:

protocols contains test of protocol interactions.
network contains system network tests
system contains tests on the internal chip features, debugging and development tools.
security contains tests on the chip security features.

CI Behavior

Configuration Files

For each project in test_apps (and also examples):

If a file sdkconfig.ci exists then it's built as the default CI config.
If any additional files sdkconfig.ci.<CONFIG> exist then these are built as alternative configs, with the specified <CONFIG> name.

The CI system expects to see at least a "default" config, so add sdkconfig.ci before adding any sdkconfig.ci.CONFIG files.

By default, every CI configurations is built for every target SoC (an m * n configuration matrix). However if any sdkconfig.ci.* file contains a line of the form CONFIG_IDF_TARGET="targetname" then that CI config is only built for that one target. This only works in sdkconfig.ci.CONFIG, not in the default sdkconfig.ci.
Each configuration is also built with the contents of any sdkconfig.defaults file or a file named sdkconfig.defaults.<TARGET> appended. (Same as a normal ESP-IDF project build.)

Test Apps local execution

Some of the examples have pytest_....py scripts that are using the pytest as the test framework. For detailed information, please refer to the "Run the Tests Locally" Section under ESP-IDF tests in Pytest documentation