rt-thread.git/components/utilities/utest, branch copilot/remove-vbus-code-implementation

utest/msh: supports autocomplete of utest cases for utest_run (#10701)

2025-10-20T04:46:44Z

* utest/msh: supports autocomplete of utest cases for utest_run * docs/utest: explanation of adding the automatic completion function for utest_run * fix[utest]: Improvement of annotation description * remove outdated code

utest: Improve the strings displayed in the menu

2025-10-16T10:34:43Z

Use "Test" instead of "Unit Testcases" to make string shorter. Use uppercase to make it look more eye-catching. Signed-off-by: Chen Wang

utest: UTEST_SELF_PASS_TC -> RT_UTEST_SELF_PASS

2025-10-15T01:43:16Z

Signed-off-by: Chen Wang

utest: remove RT_UTEST_USING_ALL_CASES

2025-09-26T01:57:54Z

Many modules' utests currently don't support enabling all tests at once. Furthermore, some modules' tests are complex, for example due to their numerous dependencies on other modules. This makes it nearly impossible to enable all tests with a single global switch. Consequently, the previously defined `RT_UTEST_USING_ALL_CASES` has lost its original meaning. We recommend deprecating this configuration switch. If a module needs to enable a group of functional tests through its own configuration, this local enable all switch should be implemented by the module itself, and a global RTT enable switch will no longer be provided. If such a requirement arises in the future, we recommend careful design, especially considering how to ensure that turning on a single switch enables all dependencies for all involved modules for ease of use. Signed-off-by: Chen Wang

utest: update naems using new rule

2025-09-15T11:40:31Z

The names of the utest cases defined in their respective modules have been updated. Some utest case names are not yet in their respective modules because their paths need to be finalized before their unique names can be determined. Currently, these names do not appear to conflict with the unified names. These include: - utest cases still in examples - bsp/qemu-virt64-riscv/applications/test/test_vector/test_vector.c. The entire test case should probably be placed in libcpu/risc-v rather than bsp. Signed-off-by: Chen Wang

utest/utest: intergare testcases into utest framework (#10665)

2025-09-02T10:48:07Z

* utest: move testcases of Utest from example to Utest folder Create unit-test-cases for the Utest framework subsystem according to "How to add utest cases into RT-Thread for your module." [1] Link: https://rt-thread.github.io/rt-thread/page_component_utest.html#autotoc_md804 [1] The original `components/utilities/utest` directory already has unit testcases, which are more comprehensive than the testcases in `examples/utest/testcases/utest/`. Therefore, simply deleted the test cases in `examples` and used the existing testcases in the utest framework. Signed-off-by: Chen Wang * utest/utest: rename name and add license text Signed-off-by: Chen Wang --------- Signed-off-by: Chen Wang

componnets: utest: fix case-name matching problem

2025-06-10T11:22:25Z

There is a problem with the matching of case names in the original code. Due to original code use memcmp with len, if the input case name and the existing case name have an inclusion relationship, for example, if the actual case name is "gpip_irq", and run `utest_run gpio` will also match successfully, but it's not expected. Modify the logic of exact matching and use strcmp instead. Keep the original wildcard logic, that is, `utest_run gpio*` can match both "gpio_irq" and "gpio". Signed-off-by: Chen Wang

feat: ci script associated with auto_utest. (#9933)

2025-03-10T03:08:21Z

* feat: ci script associated with auto_utest.

[utest] fix twice operation of uassert

2025-01-15T02:26:40Z

[utest] make RT_USING_CI_ACTION to be clear

2025-01-09T22:45:15Z

RT_USING_CI_ACTION will select RT_UTEST_USING_AUTO_RUN and RT_UTEST_USING_ALL_CASES