A requirement whose surface matches no surface is never checked and never disclosed
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 56/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- playwright, typescript
- 领域
- accessibility, testing
调研方向
Start with src/intake/map-to-providers.ts to see how requirements are scoped by surface, then trace the run sequencer and the existing single-page handling in checkPage. Compare loaded requirement surfaces with scanned screen ids and report unmatched ones as not-covered gaps using ref requirement:<id>. Done means a requirement naming an unscanned surface is reported with that surface, including in the CLI run.
由索引模型根据 Issue 内容生成。
描述
What happens
Each content or flow requirement becomes a provider that runs only when the screen id equals requirement.surface (src/intake/map-to-providers.ts). Its comment says the wrong surface is out of scope and that "coverage wiring decides this later". Nothing does. If a requirement names a surface that no configured or discovered surface has, for example a typo, its provider returns nothing on every screen and the run reports no gap for it.
Why it matters
A requirement the run never checked reads as met. That is a false green, and a typo is enough to cause it.
Fix direction
After the scan, compare each loaded requirement's surface with the set of scanned screen ids. A requirement that matched no scanned screen becomes a not-covered gap with ref requirement:<id> that names the surface. checkPage already does this for its single page. The CLI side touches the run sequencer, which is a guarded path.
- 主要语言
- TypeScript
- 星标
- 0
- 派生
- 0
- 平均合并
- 2 小时 48 分钟
- 30 天内合并 PR
- 8
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
usabl-dev/usabl 的其他 Issue
-
area: engine bug
难度 2/5 1-3 小时 新手友好度 86/100
-
Stop hook allows a stop on an unknown verdict, and the self-check prints IDLE for a null verdict未关闭area: assistants bug
难度 2/5 1-3 小时 新手友好度 75/100
-
area: engine bug security
难度 2/5 1-3 小时 新手友好度 72/100
-
Overlay: browser context failures are counted per plugin, not per browser, and close is not shared未关闭area: overlay bug
难度 2/5 1-3 小时 新手友好度 64/100
-
area: engine enhancement performance
难度 2/5 1-3 小时 新手友好度 68/100
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
braintrustdata/braintrust-sdk-javascript#2659 ·
维护者通常 1 天内回复
-
body-parser 2.3.0 in the published ai-dial-chat-bff image is vulnerable (CVE-2026-111181, HIGH)可能已有人在做 @illya-havsiyevych 今天认领。 未关闭bug
难度 1/5 1-3 小时 新手友好度 87/100
epam/ai-dial-chat#9566 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 83/100
维护者通常 1 天内回复
-
はさみアイコンを修正する未关闭bug
难度 1/5 1 小时以内 新手友好度 68/100
-
area: core
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复