metrics.json file does not support feature integration tests in module repo
还没有人认领这个 Issue。
评估
调研方向
首先,使用链接的 lifecycle 集成测试和 feature-requirements 路径作为复现上下文,检查 score_metrics_include_external_needs 和 score_metrics_requirement_types 如何影响生成的 metrics.json 文件。将当前的 module-repo 输出与请求的 cross-repository 设置进行比较;完成的标准是,metrics.json 仅包含与该模块或 feature 相关的 feature requirements,同时保留集成测试链接。
由索引模型根据 Issue 内容生成。
描述
What
Problem
The metrics.json file file from score_lifecycle does not display the linking between feature requirements and feature integration tests.
Context
Within lifecycle feature team we have the following setup:
- score_lifecycle repo contains feature integration tests, linking to feature requirements
- score repo contains the feature requirements for lifecycle
This repo setup is described also in the process documentation .
By default, the resulting metrics.json file from the score_lifecycle repo does not contain any feature requirements linking, but only the linking to component requirements (which are defined in the same score_lifecycle repo).
When following dashboards_and_quality_gates documentation and setting score_metrics_include_external_needs = True & score_metrics_requirement_types = "feat_req,comp_req,aou_req" the metrics.json file gets polluted with all feature requirements of all modules.
I am not aware of any other settings that would support the use case.
Expectation
score_metrics supports the use case of feature requirements and feature integration tests within different repos.
It shall be possible to generate a metrics.json file from the module repo that contains only the feature requirements that are relevant for the module/feature.
Acceptance Criteria (DoD)
- score_metrics supports cross repo linking for a single feature/module to support the use case feature requirements and feature integration tests in different repos
How
No response
- 主要语言
- Python
- 星标
- 11
- 派生
- 33
- 平均合并
- 22 小时 43 分钟
- 30 天内合并 PR
- 65
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
eclipse-score/docs-as-code 的其他 Issue
-
good first issue
难度 2/5 1-3 小时 新手友好度 75/100
eclipse-score/docs-as-code#850 ·
-
难度 2/5 1-3 小时 新手友好度 68/100
eclipse-score/docs-as-code#771 · 已指派 1 人 ·
-
documentation
难度 2/5 1-3 小时 新手友好度 68/100
eclipse-score/docs-as-code#613 · 1 条评论 ·
-
update py_venv 未关闭
难度 2/5 1-3 小时 新手友好度 65/100
eclipse-score/docs-as-code#606 ·
-
bug waiting_for_author
难度 2/5 1-3 小时 新手友好度 70/100
eclipse-score/docs-as-code#288 · 2 条评论 ·
查看 eclipse-score/docs-as-code 的全部 Issue
相似的 Issue
-
area: harness bug status: needs-triage
难度 2/5 1-3 小时 新手友好度 75/100
Human-Agent-Society/reef#625 ·
-
难度 2/5 1-3 小时 新手友好度 70/100
-
难度 1/5 1 小时以内 新手友好度 80/100
learningequality/kolibri#15351 · 2 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 75/100
-
Name consistency 未关闭
难度 2/5 1-3 小时 新手友好度 75/100
eellak/triplestore#65 · 1 条评论 ·