Crash_Override/OVMS3-idf
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
OVMS3-idf/tools/unit-test-app
History
He Yin Ling 3b24bc42d2 CI: assign unit test cases according to sdkconfig: 
We have built unit-test-app with different configs.
Currently we use the config name as tags to match runners.
It's not easy to add new configs (need to update tags to existed runners).

Now we'll parse required test runner tags from `sdkconfig` file.
For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag.
This will make adding new configs easier.

In this commit we change the one behavior of assign test: match keys of
cases should be exactly the same with job tags. This fixes cases select
jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-24 03:40:03 +00:00
..
components/unity unity: flush test name before starting the test, use printf everywhere 2018-04-26 18:52:45 +08:00
configs unit tests: add psram configuration 2017-11-06 11:23:15 +08:00
main Allow VFS file descriptors in select() 2018-05-18 08:06:33 +02:00
tools CI: assign unit test cases according to sdkconfig: 2018-05-24 03:40:03 +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 Enable -Wwrite-strings when compiling IDF's own C files 2018-04-10 08:53:33 +02:00
unit_test.py CI: assign unit test cases according to sdkconfig: 2018-05-24 03:40:03 +00:00

README.md

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