test : add unit tests for _business_criticality_factor in risk_scoring
还没有人认领这个 Issue。
- #2266 来自 @tmdeveloper007 —— 已关闭，未合并
评估
调研方向
Read backend/secuscan/risk_scoring.py and inspect CRITICALITY_MAP and _business_criticality_factor, then review nearby tests under testing/backend/unit/. Add testing/backend/unit/test_risk_scoring_criticality_factor.py for known mappings, defaults, and case-insensitive input. Run the new unit test file and confirm each listed behavior passes. The issue names tmdeveloper007 as handling the task and links a closed pull request, so check the current status before starting.
由索引模型根据 Issue 内容生成。
描述
Summary of What Needs to be Done:
Write unit tests for _business_criticality_factor in backend/secuscan/risk_scoring.py. This private function maps business criticality strings to multiplier floats used in contextual risk scoring. It is currently only exercised indirectly through compute_risk_score but has no dedicated tests for its mapping behavior.
Changes that Need to be Made:
Create a new file: testing/backend/unit/test_risk_scoring_criticality_factor.py
Import _business_criticality_factor from backend.secuscan.risk_scoring and test:
- Known criticality levels return correct multipliers
- None input returns 1.0 (default)
- Unknown criticality returns 1.0 (default)
- Empty string returns 1.0 (default)
- Case insensitivity of input
Impact that it would Provide:
Direct tests catch regressions if CRITICALITY_MAP is modified. Tests the default fallback behavior which is critical for stability when encountering unexpected criticality values in production data.
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 天内回复