mirror of
https://github.com/espressif/esp-idf.git
synced 2024-10-05 20:47:46 -04:00
39319c0750
pytest_panic used to do 'from conftest import PanicTestDut'. This stopped working when another conftest.py file was added in tools/test_build_system/conftest.py. In this case we can't rename conftest.py since both are necessary for pytest to install the hooks in the respective test cases. Fix by moving PanicTestDut into a separate module, then importing it from there. |
||
---|---|---|
.. | ||
main | ||
test_panic_util | ||
CMakeLists.txt | ||
conftest.py | ||
panic_utils.py | ||
pytest_panic.py | ||
README.md | ||
sdkconfig.ci.coredump_flash_bin_crc | ||
sdkconfig.ci.coredump_flash_elf_sha | ||
sdkconfig.ci.coredump_uart_bin_crc | ||
sdkconfig.ci.coredump_uart_elf_crc | ||
sdkconfig.ci.gdbstub | ||
sdkconfig.ci.panic | ||
sdkconfig.defaults |
Supported Targets | ESP32 | ESP32-C3 | ESP32-H2 | ESP32-S2 | ESP32-S3 |
---|
Building
Several configurations are provided as sdkconfig.ci.XXX
and serve as a template.
Example with configuration "panic" for target ESP32
idf.py set-target esp32
cat sdkconfig.defaults sdkconfig.ci.panic > sdkconfig
idf.py build
Running
All the setup needs to be done as described in the test apps README, except that the test cases need to be specified when running the app:
python app_test.py test_panic_illegal_instruction
Multiple test cases are passed as additional arguments:
python app_test.py test_panic_illegal_instruction test_panic_int_wdt test_panic_storeprohibited
Note that you need to pick the correct test cases at run time according to the configuration you built before. The above examples are for configuration "panic"