esp-idf/tools/unit-test-app
Angus Gratton 5d8bd1aa9e Merge branch 'bugfix/libsodium_mbedtls_sha' into 'master'
libsodium: Fix mbedTLS SHA256 & SHA512 implementation, make optional

See merge request !1329
2017-10-13 08:50:24 +08:00
..
components/unity test: update the format of TEST_ASSERT macro series in `unity.c` 2017-09-27 19:56:46 +08:00
main Add libsodium v1.0.12 2017-06-14 15:51:08 +10:00
tools CI: fix bug of duplicated unit test case ID: 2017-06-03 11:38:05 +08:00
Makefile CI: save download config in CI build jobs: 2017-05-02 13:17:56 +08:00
partition_table_unit_test_app.csv Add SPIFFS Component to IDF 2017-09-11 19:56:40 +03:00
README.md unit test runer: Add capability to use ![tag] to run all-tests-except-tag 2017-05-10 17:22:30 +10:00
sdkconfig libsodium: Fix mbedTLS SHA256 & SHA512 implementation, make optional 2017-10-06 11:51:55 +11:00

Unit Test App

ESP-IDF unit tests are run using Unit Test App. The app can be built with the unit tests for a specific component. Unit tests are in test subdirectories of respective components.

Building Unit Test App

  • Follow the setup instructions in the top-level esp-idf README.
  • Set IDF_PATH environment variable to point to the path to the esp-idf top-level directory.
  • Change into tools/unit-test-app directory
  • make menuconfig to configure the Unit Test App.
  • make TEST_COMPONENTS= with TEST_COMPONENTS set to names of the components to be included in the test app. Or make TESTS_ALL=1 to build the test app with all the tests for components having test subdirectory.
  • Follow the printed instructions to flash, or run make flash.

Running Unit Tests

The unit test loader will prompt by showing a menu of available tests to run:

  • Type a number to run a single test.
  • * to run all tests.
  • [tagname] to run tests with "tag"
  • ![tagname] to run tests without "tag" (![ignore] is very useful as it runs all CI-enabled tests.)
  • "test name here" to run test with given name