alex/esp-idf
alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2024-10-05 20:47:46 -04:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
esp-idf/tools/test_apps
History
Ivan Grokhotkov c3d2942675 panic: skip over the first invalid PC in case of InstrFetchProhibited 
InstrFetchProhibited usually occurs because of a jump to an invalid
pointer. In this case, PC in the exception frame is the address of
the jump destination. 'esp_ptr_executable' check in print_backtrace
function recognizes the first frame as invalid, and the backtrace is
interrupted. This prevents the user from finding the location where
the invalid pointer is dereferenced.

Bypass the 'esp_ptr_executable' check if the exception cause is
InstrFetchProhibited. Update the test case to no longer ignore this
issue.
2020-09-04 20:45:38 +02:00
..
protocols
ppp-test: wait for graceful disconnect when PPP shutdowns
2020-04-23 05:55:17 +00:00
security/secure_boot
build_app: make multi target support readable
2020-04-09 16:40:57 +08:00
system
panic: skip over the first invalid PC in case of InstrFetchProhibited
2020-09-04 20:45:38 +02:00
README.md
feat/secure_boot_v2: Adding tools support for secure boot v2 ECO3
2020-02-25 01:28:22 +05:30

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 - Default configuration for the project
    • sdkconfig.ci.<CONFIG> - Other configurations, where <CONFIG> indicates name of the configuration
  • Test executor in ttfw_idf format if the project is intended to also run tests (otherwise the example is build only)
    • test file in the project dir must end with _test.py, by should be named app_test.py
    • test cases shall be decorated with @ttfw_idf.idf_custom_test(env_tag="...")

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.

Test Apps local execution

  • Append relevant sdkconfig.ci.<CONFIG> to the sdkconfig for the configuration under test
  • Run idf.py menuconfig to configure local project attributes
  • Run idf.py build to build the test app
  • Run python app_test.py to run the test locally