utest: move testcases to components#11467
Conversation
📌 Code Review Assignment🏷️ Tag: componentsReviewers: Maihuanyi Changed Files (Click to expand)
🏷️ Tag: components_lwpReviewers: xu18838022837 Changed Files (Click to expand)
🏷️ Tag: workflowReviewers: Rbb666 kurisaW supperthomas Changed Files (Click to expand)
📊 Current Review Status (Last Updated: 2026-06-11 15:53 CST)
📝 Review Instructions
|
|
👋 感谢您对 RT-Thread 的贡献!Thank you for your contribution to RT-Thread! 为确保代码符合 RT-Thread 的编码规范,请在你的仓库中执行以下步骤运行代码格式化工作流(如果格式化CI运行失败)。 🛠 操作步骤 | Steps
完成后,提交将自动更新至 如有问题欢迎联系我们,再次感谢您的贡献!💐 |
Signed-off-by: CYFS <2805686936@qq.com>
Signed-off-by: CYFS <2805686936@qq.com>
Signed-off-by: CYFS <2805686936@qq.com>
Signed-off-by: CYFS <2805686936@qq.com>
Signed-off-by: CYFS <2805686936@qq.com>
拉取/合并请求描述:(PR description)
[
为什么提交这份PR (why to submit this PR)
当前部分 utest case 仍集中放在
examples/utest/testcases下,打包工程时不会随对应组件一起进入工程,导致 menuconfig 中无法看到或配置这些测试用例。将测试用例按所属模块维护,可以让组件自身携带对应的 utest 入口和构建脚本。同时,utest 自动化测试使用的配置文件只服务于 GitHub Actions CI,不属于示例工程本身。将这些配置从
examples/utest/configs移到.github/utest/configs,可以让 CI 资源与示例目录解耦。你的解决方案是什么 (what is your solution)
examples/utest/testcases/mm移动到components/mm/utest,并由components/mm/SConscript引入。examples/utest/testcases/tmpfs移动到components/dfs/dfs_v2/filesystems/tmpfs/utest,并由 tmpfs 组件引入。examples/utest/testcases/lwp移动到components/lwp/utest,新增RT_UTEST_LWP配置项并由 lwp 组件引入。components/utilities/utest,根 Kconfig 只保留对components/utilities/utest/Kconfig的引用。examples/utest/configs移动到.github/utest/configs,并更新utest_auto_run.yml的引用和触发路径。tools/env_utility.py、tools/mkdist.py与 utest 文档中的路径。请提供验证的bsp和config (provide the config and bsp)
BSP: local Kconfig parse only
.config: N/A
action: N/A
Validation performed locally:
python -m py_compile tools/building.py tools/env_utility.py tools/mkdist.pyRT_USING_UTESTCASES,RT_UTEST_LWP,RT_UTEST_MM_API,RT_UTEST_TMPFS_CPrgcheck confirmed there are no remaining references toexamples/utest/README,examples/utest/configs,Kconfig.utestcases, oraction_utest]
当前拉取/合并请求的状态 Intent for your PR
必须选择一项 Choose one (Mandatory):
代码质量 Code Quality:
我在这个拉取/合并请求中已经考虑了 As part of this pull request, I've considered the following:
#if 0代码,不包含已经被注释了的代码 All redundant code is removed and cleaned up