Etusivu Tutki Apua
Kirjaudu sisään
RT-Thread-packages
/
esp-idf
peilaus alkaen https://github-proxy.rt-thread.io/RT-Thread-packages/esp-idf.git
2
0
Haarauta 0
Tiedostot Esitykset 0 Wiki
Puu: 2fe4fe2c19
Haarat Tunnisteet
esp-idf
/
tools
/
test_apps
Ivan Grokhotkov 2fe4fe2c19 ci(system): re-enable build test app for C2 and C6, clean up configs 2 vuotta sitten
..
build_system 7dbd3f6909 feat(ci): Enable p4 example, test_apps and unit tests CI build 2 vuotta sitten
configs 1a5e47bd07 ci: fixed test apps overriding pytest configs 2 vuotta sitten
linux_compatible ede131ce73 Merge branch 'refactor/freertos_tslfcb_and_coproc_cleanup' into 'master' 2 vuotta sitten
peripherals fd3e0b0b18 esp32h2(ci): enable target test 2 vuotta sitten
phy fe1b03308e ci(tsens): add new test tsens phy coexist 2 vuotta sitten
protocols 10c21f704c Merge branch 'bugfix/module_logging_tag_lower_case' into 'master' 2 vuotta sitten
security 66bbe8c156 fix: Fix esptool usage in the secure boot test application 2 vuotta sitten
system 2fe4fe2c19 ci(system): re-enable build test app for C2 and C6, clean up configs 2 vuotta sitten
.build-test-rules.yml 2fe4fe2c19 ci(system): re-enable build test app for C2 and C6, clean up configs 2 vuotta sitten
README.md 01fd87bd05 ci: remove ttfw related info in tools/test_apps 2 vuotta sitten

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