mirror of https://github.com/espressif/esp-idf.git synced 2024-09-20 00:36:01 -04:00

History

Jiang Jiang Jian d434034513 Merge branch 'bugfix/storage_spelling' into 'master' fix(storage,esp_pm): spelling fixes by codespell pre-commit hook See merge request espressif/esp-idf!29898		2024-03-29 11:59:48 +08:00
..
build_system	feat(esp_system): allow .bss to spill over into L2MEM above 0x4ff40000	2024-02-28 19:41:25 +04:00
configs	feat(freertos): Exposed Kconfig option for configUSE_LIST_DATA_INTEGRITY_CHECK_BYTES	2023-11-09 14:54:13 +01:00
linux_compatible	feat(log): Added PRIuSIZE printf formatter macro	2024-03-20 16:41:22 +08:00
peripherals/i2c_wifi	ci(p4): enable esp32p4 target test	2024-01-04 09:34:55 +08:00
phy	ci(p4): added todo jira for disabled tests on p4	2024-01-04 09:36:38 +08:00
protocols	refactor(uart_vfs): Move uart implementation of vfs to esp_driver_uart	2023-12-15 17:14:55 +08:00
security	feat(secure_boot): add secure boot support for esp32p4	2023-10-12 10:12:54 +05:30
storage	fix(storage): applied spelling fixes by codespell pre-commit hook	2024-03-28 13:00:54 +01:00
system	Merge branch 'fix/unused_mmap_include' into 'master'	2024-03-29 10:20:08 +08:00
.build-test-rules.yml	feat(esp32c61): ci enable header check, fix c61 build	2024-03-27 19:39:59 +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