mirror of https://github.com/espressif/esp-idf.git synced 2025-12-24 20:53:09 +00:00

Files

Frantisek Hrbata 1c92945f59 change(examples): switch examples to use a minimal build

Currently, several example dependencies rely on the fact that all
registered components are added to the build, along with components
specified in common requirements. This results in longer build times
because even unused components must be built. Switch all examples to use
idf_minimal_build to compile only the components actually required by
the example.

Signed-off-by: Frantisek Hrbata <frantisek.hrbata@espressif.com>

2024-11-20 20:14:40 +01:00

build_system

feat(partitions): Adds new partition types and subtypes for bootloader and partition_table

2024-10-01 14:22:22 +03:00

configs

feat(build): Add config to disable warn be considered as errors

2024-06-20 14:43:26 +08:00

linux_compatible

fix(pthread): Fix cxx pthread example build for linux platform

2024-08-13 10:48:17 +02:00

peripherals

feat(wifi): add wifi support for esp32c61

2024-08-30 20:43:06 +08:00

phy

feat(temperature_sensor): Add temperature sensor support on esp32c61

2024-11-13 10:52:47 +08:00

protocols

feat(esp32c61): disable unsupported build test

2024-07-16 16:06:19 +08:00

security

feat: enable security related testcases for c5 and c61

2024-10-21 14:24:36 +05:30

storage

change(examples): switch examples to use a minimal build

2024-11-20 20:14:40 +01:00

system

Merge branch 'feat/uart_line_ending' into 'master'

2024-11-20 15:36:01 +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