🤖 mutate-check: choose the test suites for a bounded run
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- testing
Research direction
Start in scripts/mutate/check.ts, where the script picks at most 10 test files from the import graph, and find where its arguments are parsed. Add a --tests option that accepts file paths and uses them instead of the graph selection, then check that make mutate-check passes it through MUTATE_CHECK_ARGS. Done when running with --tests against a named suite runs only those files.
Written by the indexing model from the issue text.
Description
Let make mutate-check target the suites that drive a method.
scripts/mutate/check.ts has no option to choose test files. It picks at most 10 tests from the import graph. For a file that many tests import (57 for taskService.ts), the chosen suites are mostly unrelated, so the report says nothing about the changed method. Every TaskService split in plan 8 needed a hand-built mutation runner, and those runners found real test gaps (#7806, #7810, #7814).
Suggested fix: add --tests <file...> (passed through MUTATE_CHECK_ARGS) so a bounded run can use named suites.
Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high
- Dominant language
- TypeScript
- Stars
- 2.1k
- Forks
- 139
- Avg merge
- 3h 35m
- Merged PRs (30d)
- 950
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from coder/xum
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
Similar issues
-
needs-area-label
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
liberation-data/drivine#615 ·
Maintainers usually reply within 1 day
-
backend bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
geolens-io/geolens#3639 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
radius-project/ai-extensions#1196 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 88/100