Repository navigation
feat(testing): resolve grouped feature ids in run-e2e #9587
Description
Slice A8 of #9507, shrunk to run-e2e's chooser: drive's grouped-id resolution ships with A1.
Problem
run-e2e's feature chooser resolves only single-level feature ids.
Fix
- run-e2e's chooser resolves
<module>/<feature>and a single-level id, in drive's order (features/<id>/README.md, thenfeatures/<id>.md). - Evals
grouped-feature-id-resolvesandflat-feature-id-resolves. Fragment: testing minor.
Done when
- Both evals pass, and run-e2e's existing cases are non-inferior.
Blocked by: A6 (same file) and poteto's B1.
Activity
github-actions commentedon Oct 24, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Understood: run-e2e's feature chooser should resolve
<module>/<feature>ids as well as single-level ids, using drive's lookup order (features/<id>/README.md, thenfeatures/<id>.md). It should also add the evalsgrouped-feature-id-resolvesandflat-feature-id-resolves, plus a testing minor fragment. The done-when is that both evals pass and run-e2e's existing cases stay non-inferior.Nothing is missing for the scope. The issue says it is blocked by A6 (same file) and B1, so work should wait for those. No clear duplicates in the open list. Related: #9507 (parent) and #9579 (grouped ids at plugin level).
Automated triage, applied by the lanes App.
melodic-automation-lanes commentedon Oct 24, 2026
Not admitted to the issue lane yet: blocker #9586 is not closed as completed by a listed human or a merge.
kyle-sexton commentedon Oct 24, 2026
Holding this slice for the lanes: it edits
plugins/testing/skills/run-e2e/SKILL.md, as does the desktop session's B1 (run-e2e shrink). It starts only after B1 merges and the order is agreed on #9507. That dependency is cross-session, not a GitHub blocked-by edge, sostatus: needs-decisionstands in for it until then. The interactive session that owns #9507 removes the hold.