OVMS3-idf/tools/unit-test-app
Anton Maklakov f3d61015f7 build: Fix problems with building kconfig and generating sdkconfig
We had some problems:
    simultaneous compiling of kconfig in the same tree;
    attempt to use menuconfig in some examples and ut in batch mode (w/o interactive console)

Also increase debug abilities in CI:
    force non-interactive building;
    add variable DEBUG_SHELL to toggle verbosity of scripts
2018-03-28 10:39:20 +08:00
..
components/unity unit-test-app: use '-' to show test history 2018-02-05 06:58:22 +00:00
configs unit tests: add psram configuration 2017-11-06 11:23:15 +08:00
main freertos/fix SMP bug with Idle task clean up 2017-12-05 18:13:56 +08:00
tools CI: new CI ut framework, and can run it in local PC 2018-02-05 06:58:22 +00:00
Makefile build: Fix problems with building kconfig and generating sdkconfig 2018-03-28 10:39:20 +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.defaults esp_timer: add documentation, expose profiling option in Kconfig 2017-11-29 11:44:46 +08:00
unit_test.py CI: new CI ut framework, and can run it in local PC 2018-02-05 06:58:22 +00: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