[Feature] 完善外设驱动 utest 覆盖清单
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- c
- Domain
- embedded-iot, testing
Research direction
The issue names components/drivers and a peripheral checklist; start by mapping each item to its actual directory and Kconfig name, then inspect existing utest coverage. Review the listed requirements for test instructions, smoke and loopback coverage, mock/QEMU/POSIX automation, hardware setup, naming, integration, and CI status. Done requires defining the scope and completing the agreed checklist items.
Written by the indexing model from the issue text.
Description
背景
目前 RT-Thread 外设驱动 utest 覆盖还不完整,需要先统计当前哪些外设已有 utest,哪些外设还没有,再按清单逐步补齐。
外设 utest 覆盖清单
说明:
[x]表示当前已有对应 utest。[ ]表示当前暂未发现对应 utest,需要后续补齐。serial_v2已有较完整的 loopback/QEMU/POSIX 测试。
已覆盖 / 待补齐
- adc
- dac
- i2c
- spi (PR #11549)
- can (PR #11752)
- pwm (PR #11754)
- rtc (PR #11755)
- watchdog
- timer
- sensor
- touch
- audio
- usb
- sdio (PR #11758)
- mtd
- flash
- ethernet
- wlan
- pin (PR #11445)
- serial_v2
- serial_bypass
- device_core
- ipc_completion
- ipc_workqueue
- smp_call
后续待办
- 确认 checklist 中每个外设在
components/drivers下对应的实际目录和 Kconfig 名称。 - 为已有 utest 的外设补充测试说明:依赖配置、测试命令、是否需要硬件连接。
- 为缺失 utest 的外设补充基础 smoke test。
- 对支持 loopback 的外设补充回环测试,例如 UART、CAN、GPIO、SPI。
- 对可模拟的外设补充 mock/QEMU/POSIX 自动化测试。
- 对只能依赖真实硬件的外设补充 BSP、config 和接线说明。
- 统一外设 utest 的 Kconfig/SConscript 接入方式。
- 统一 testcase 命名,例如
components.drivers.<peripheral>.<scenario>。 - 梳理哪些外设 utest 可以进入 CI,哪些保留为手动板级验证。
- Dominant language
- C
- Stars
- 12.4k
- Forks
- 5.5k
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 79
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from RT-Thread/rt-thread
-
Arch: ARM/AArch64 Doc
Difficulty 1/5 Under an hour Newbie friendliness 90/100
RT-Thread/rt-thread#12082 · 1 comment ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
RT-Thread/rt-thread#11951 · 2 comments ·
Maintainers usually reply within 2 days
-
[Bug] [libc] timer_gettime 拆秒前将总纳秒截断为 uint32_t,剩余时间查询错误May be free again @Yunlk claimed this 28 days ago, and no pull request is open. Openin progress
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
RT-Thread/rt-thread#11924 · 7 comments · 1 assignee ·
Maintainers usually reply within 2 days
-
[Bug] dfs_v2 tmpfs: ftruncate(fd, 0) frees the file buffer but reports success — use-after-free read/write and double free from a legal POSIX callPossibly taken @remukisama claimed this 33 days ago. Openin progress
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
RT-Thread/rt-thread#11902 · 4 comments · 1 assignee ·
Maintainers usually reply within 2 days
-
[bsp][stm32][bluepill] README「快速上手」缺少重新生成 MDK 工程这一步,按文档操作无法编译通过May be free again @moment-NEW claimed this 50 days ago, and no pull request is open. Openin progress
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
RT-Thread/rt-thread#11818 · 4 comments · 1 assignee ·
Maintainers usually reply within 2 days
All issues in RT-Thread/rt-thread
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/nuttx-apps#4108 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
trezor/trezor-firmware#8357 ·
Maintainers usually reply within 2 days
-
ivorysql_ora: DBMS_SESSION lacks SLEEP (documented, not covered by #2763)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
good first issue kernel
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
JackFurton/who-would-build-a-kernel-in-java#316 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
PE5PVB/TEF6686_ESP32#970 ·