test : add unit tests for _build_triage_prompt helper in triage_engine
还没有人认领这个 Issue。
- #2263 来自 @tmdeveloper007 —— 已关闭，未合并
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 35/100
调研方向
Read backend/secuscan/triage_engine.py and locate _build_triage_prompt, then review existing triage_finding tests for test conventions. Add testing/backend/unit/test_triage_engine_prompt.py with the listed field, special-character, normal-input, and variable-format cases. Run the new unit test file; done when it directly covers these cases and passes.
由索引模型根据 Issue 内容生成。
描述
Summary of What Needs to be Done:
Write direct unit tests for the _build_triage_prompt function in backend/secuscan/triage_engine.py. This pure function builds the LLM prompt for SAST finding triage. It is currently only exercised indirectly through triage_finding integration tests but has no dedicated unit tests covering its output format and edge cases.
Changes that Need to be Made:
Create a new file: testing/backend/unit/test_triage_engine_prompt.py
Import _build_triage_prompt from backend.secuscan.triage_engine and test:
- Empty and None fields in the finding dict (title, category, severity, description)
- Empty and None fields in the context dict (snippet, variables, file, line)
- Mixed content with special characters
- Normal finding with all fields populated
- Variables list formatting
Impact that it would Provide:
Direct unit tests catch regressions in prompt format. Testing edge cases (missing fields) ensures the LLM always receives a well-formed prompt even with malformed finding data. Improves reliability of the AI-assisted triage feature.
Note: This task is being handled by tmdeveloper007 — please assign to that account when picking it up.
- 主要语言
- Python
- 星标
- 36
- 派生
- 234
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
utksh1/SecuScan 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
-
area:frontend good first issue level:intermediate priority:low type:testing
难度 2/5 1-3 小时 新手友好度 83/100
-
area:frontend good first issue level:intermediate priority:low type:testing
难度 2/5 1-3 小时 新手友好度 78/100
-
area:frontend good first issue level:beginner priority:low type:testing
难度 2/5 1-3 小时 新手友好度 76/100
-
area:frontend good first issue level:intermediate priority:low type:testing
难度 2/5 1-3 小时 新手友好度 82/100
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 83/100
维护者通常 1 天内回复
-
comp/desktop P3 type/feature
难度 2/5 1-3 小时 新手友好度 78/100
NousResearch/hermes-agent#154285 ·
维护者通常 1 天内回复
-
docs: qualify copied and custom kubectl debug policy notes可能已有人在做 @nym01 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
kubescape/cel-admission-library#166 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
SACGF/variantgrid#2804 · 1 条评论 ·
维护者通常 1 天内回复
-
[BUG] HTTP lifecycle dispatch treats a NO_PROXY-only environment as corporate egress and skips the resolve-and-pinned session可能已有人在做 @bodapatisaikrishna 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复