Files

Ivan Grokhotkov c61c2a63d0 unity: flush test name before starting the test, use printf everywhere

Unit test runner expects to see the test name echoed after test
selection is made. If the unit test immediately goes into sleep mode,
UART output will not be complete, and test runner will not see the
test name. This flushes the stream buffer and waits for UART FIFO to
be empty before starting the test.

Additionally some parts of code used unity_printf and some used
printf. Since unity_printf was only useful during very early tests
when newlib was not available, replace all its usages with printf.

2018-04-26 18:52:45 +08: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

Revert "Merge branch 'feature/vfs_select' into 'master'"

2018-04-20 11:51:41 +08:00

tools

unit-test-app: support multi stages test

2018-03-30 11:38:49 +08: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

unit-test-app: support multi stages test

2018-03-30 11:38:49 +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