Files

Darian Leung a6854b72cd freertos/make trace facility configurable

This commit makes configUSE_TRACE_FACILITY and
configUSE_STATS_FORMATTING_FUNCTIONS configurable in kconfig. Test cases fro the
functions enabled by the two configurations above have also been added.

Test cases for the following functions have been added...

- uxTaskGetSystemState()
- uxTaskGetTaskNumber()
- vTaskSetTaskNumber()

- xEventGroupClearBitsFromISR()
- xEventGroupSetBitsFromISR()
- uxEventGroupGetNumber()

- uxQueueGetQueueNumber()
- vQueueSetQueueNumber()
- ucQueueGetQueueType()

Test cases for the following functions were not required...

- prvListTaskWithinSingleList()
- prvWriteNameToBuffer()
- vTaskList()

2017-10-20 15:17:17 +08:00

components/unity

unit tests: fix warnings, build with -Werror

2017-10-19 21:35:23 +08:00

configs

unit-test-app: new targets for building different configurations

2017-10-19 21:35:19 +08:00

main

Add libsodium v1.0.12

2017-06-14 15:51:08 +10:00

tools

CI: support test UT with different config by CI

2017-10-19 21:35:20 +08:00

Makefile

unit-test-app: new targets for building different configurations

2017-10-19 21:35:19 +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

freertos/make trace facility configurable

2017-10-20 15:17:17 +08: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