![]() ![]() and tags tell the test runner whether a test case is a multiple devices or multiple stages test case. ![]() Module name in square brackets to run all test cases for a specific module Test case index to run a single test case Test case name in quotation marks to run a single test case Test cases can be run by inputting one of the following: Master slave cases will also print the sub-menu (the registered test function names). Normal case will print the case name and description. Here 's the test menu, pick your combo: ( 1 ) "esp_ota_begin() verifies arguments" ( 2 ) "esp_ota_get_next_update_partition logic" ( 3 ) "Verify bootloader image in flash" ( 4 ) "Verify unit test app image" ( 5 ) "can use new and delete" ( 6 ) "can call virtual functions" ( 7 ) "can use static initializers for non-POD types" ( 8 ) "can use std::vector" ( 9 ) "static initialization guards work as expected" ( 10 ) "global initializers run in the correct order" ( 11 ) "before scheduler has started, static initializers work correctly" ( 12 ) "adc2 work with wifi" ( 13 ) "gpio master/slave test example" ( 1 ) "gpio_master_test" ( 2 ) "gpio_slave_test" ( 14 ) "SPI Master clockdiv calculation routines" ( 15 ) "SPI Master test" ( 16 ) "SPI Master test, interaction of multiple devs" ( 17 ) "SPI Master no response when switch from host1 (HSPI) to host2 (VSPI)" ( 18 ) "SPI Master DMA test, TX and RX in different regions" ( 19 ) "SPI Master DMA test: length, start, not aligned" ( 20 ) "reset reason check for deepsleep" ( 1 ) "trigger_deepsleep" ( 2 ) "check_deepsleep_reset_reason" Use menuconfig to set the serial port for flashing. Everything needed will be rebuilt automatically before flashing. You can also run idf.py flash -T all or idf.py flash -T xxx to build and flash. You can simply run idf.py flash to flash all build output. When the build finishes, it will print instructions for flashing the chip. (For instance: idf.py build -T all -E ulp mbedtls - build all unit tests exludes ulp and mbedtls components). Idf.py build -T all -E xxx - build unit test app with all unit tests, except for unit tests of some components. Idf.py build -T xxx - build unit test app with tests for specific components. Idf.py build -T all - build unit test app with tests for each component having tests in the test subdirectory. Idf.py menuconfig - configure unit test app. Make sure that IDF_PATH environment variable is set to point to the path of esp-idf top-level directory.Ĭhange into tools/unit-test-app directory to configure and build it: DUT UART console will prompt and requires user interaction:įollow the setup instructions in the top-level esp-idf README. We provide unity_wait_for_signal and unity_send_signal to support synchronizing with UART.Īs the secnario in the above example, slave should get GPIO level after master set level. Running test cases from different DUTs could require synchronizing between DUTs. The macro TEST_CASE_MULTIPLE_DEVICES is used to declare multiple devices test cases.įirst argument is test case name, second argument is test case description.įrom the third argument, upto 5 test functions can be defined, each function will be the entry point of tests running on each DUT. Void gpio_master_test () TEST_CASE_MULTIPLE_DEVICES ( "gpio multiple devices test example", "", gpio_master_test, gpio_slave_test ) ![]()
0 Comments
Leave a Reply. |