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. |
||
---|---|---|
.. | ||
components/unity | ||
configs | ||
main | ||
tools | ||
Makefile | ||
partition_table_unit_test_app.csv | ||
README.md | ||
sdkconfig.defaults | ||
unit_test.py |
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=
withTEST_COMPONENTS
set to names of the components to be included in the test app. Ormake TESTS_ALL=1
to build the test app with all the tests for components havingtest
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