Sākums Izpētīt Palīdzība
Pierakstīties
RT-Thread-packages
/
esp-idf
spogulis no https://github-proxy.rt-thread.io/RT-Thread-packages/esp-idf.git
2
0
Atdalīts 0
Faili Problēmas 0 Vikivietne
Koks: dcab6368ce
Atzari Tagi
esp-idf
/
tools
/
test_apps
Marius Vikhammer 1a5e47bd07 ci: fixed test apps overriding pytest configs 2 gadi atpakaļ
..
build_system ff7fce9739 ci: fixed custom partition table subtype test not compiling for linux 2 gadi atpakaļ
configs 1a5e47bd07 ci: fixed test apps overriding pytest configs 2 gadi atpakaļ
linux_compatible d6fe302904 freertos: Added partial unit tests for Linux simulator 2 gadi atpakaļ
peripherals fd3e0b0b18 esp32h2(ci): enable target test 2 gadi atpakaļ
phy fd3e0b0b18 esp32h2(ci): enable target test 2 gadi atpakaļ
protocols e888bb0cf8 Merge branch 'bugfix/esp_netif_recieve_returns' into 'master' 2 gadi atpakaļ
security 01fd87bd05 ci: remove ttfw related info in tools/test_apps 2 gadi atpakaļ
system 620cc586a2 tools: setting components to main to reduce build time 2 gadi atpakaļ
.build-test-rules.yml d6fe302904 freertos: Added partial unit tests for Linux simulator 2 gadi atpakaļ
README.md 01fd87bd05 ci: remove ttfw related info in tools/test_apps 2 gadi atpakaļ

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