diff options
Diffstat (limited to 'documentation')
| -rw-r--r-- | documentation/6.components/utest/figures/utest_run_auto_option.png | bin | 0 -> 44606 bytes | |||
| -rw-r--r-- | documentation/6.components/utest/utest.md | 8 |
2 files changed, 7 insertions, 1 deletions
diff --git a/documentation/6.components/utest/figures/utest_run_auto_option.png b/documentation/6.components/utest/figures/utest_run_auto_option.png Binary files differnew file mode 100644 index 0000000000..aa8585ceef --- /dev/null +++ b/documentation/6.components/utest/figures/utest_run_auto_option.png diff --git a/documentation/6.components/utest/utest.md b/documentation/6.components/utest/utest.md index 81781e19ae..aa70ee96df 100644 --- a/documentation/6.components/utest/utest.md +++ b/documentation/6.components/utest/utest.md @@ -290,7 +290,13 @@ As shown in the figure above, the log of the test case run is divided into four From the above flow chart you can get the following: * The utest framework is a sequential execution of all **test units** in the *testcase* function -* Assert of the previous UTEST_UNIT_RUN macro has occurred, and all subsequent UTEST_UNIT_RUN will skip execution. +* Assert of the previous UTEST_UNIT_RUN macro has occurred, and all subsequent UTEST_UNIT_RUN will skip executio + +## utest_run auto-completion Function + +The utest_run tool now supports dynamic auto-completion for test case names. After entering the utest_run command in the terminal, users can press the TAB key to activate the auto-completion feature. The system will then dynamically match and suggest available test case names in real time. + + # NOTE |
