diff options
| author | CYFS <[email protected]> | 2026-06-11 15:51:46 +0800 |
|---|---|---|
| committer | Rbb666 <[email protected]> | 2026-06-12 14:22:53 +0800 |
| commit | bb4aace00f49ea89d0888d1d4af65142fc82c469 (patch) | |
| tree | 6ccbecf173094bb49b6384b0f3b785b9cc22ae6f /documentation | |
| parent | 103d4c1d92f3844dfcf4473957593af3449bec06 (diff) | |
utest: move utestcases Kconfig to utest component
Signed-off-by: CYFS <[email protected]>
Diffstat (limited to 'documentation')
| -rw-r--r-- | documentation/6.components/utest/utest.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/documentation/6.components/utest/utest.md b/documentation/6.components/utest/utest.md index aa70ee96df..aae598523c 100644 --- a/documentation/6.components/utest/utest.md +++ b/documentation/6.components/utest/utest.md @@ -308,7 +308,7 @@ The utest_run tool now supports dynamic auto-completion for test case names. Aft # How-to add utest cases into RT-Thread for your module -The source code of utest cases is recommended to be placed in each module for maintenance, but the entry of Kconfig should all be placed(rsourced) in `Kconfig.utestcases` for unified maintenance. In this way, when executing menuconfig, people can enter and configure from one place, avoiding searching for utest configuration switches scattering in the menuconfig interface. +The source code of utest cases is recommended to be placed in each module for maintenance, but the entry of Kconfig should all be placed(rsourced) in `components/utilities/utest/Kconfig` for unified maintenance. In this way, when executing menuconfig, people can enter and configure from one place, avoiding searching for utest configuration switches scattering in the menuconfig interface. For each module, you can maintain unit testcases in a unified manner in the following way: @@ -322,7 +322,7 @@ For each module, you can maintain unit testcases in a unified manner in the foll - `SConscript` file, when adding src files, you need to rely on `RT_UTEST_XXXX`. -After completing the above steps, rsource the path of the Kconfig file of utest of this module to the file `Kconfig.utestcases`. +After completing the above steps, rsource the path of the Kconfig file of utest of this module to the file `components/utilities/utest/Kconfig`. You can find a good example in <a href="https://github.com/RT-Thread/rt-thread/blob/master/src/klibc/utest/">"klibc"</a>. |