Declared inputs and alwaysRunTests find no pytest or Maven tests
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- typescript
Research direction
Start in src/repo/impact.ts and trace how knownTestPaths is populated from profile.tests, then how declared input and alwaysRunTests globs select tests. Reproduce with the pytest examples in the issue, then check the Maven case under src/test/java/**. Done means matching pytest and Maven tests are selected for declared inputs and always-run globs; an open linked pull request (#272) is already addressing this issue.
Written by the indexing model from the issue text.
Description
In src/repo/impact.ts, knownTestPaths only collects graph nodes while iterating profile.tests, the JavaScript test locations. pytest and Maven repositories have none, so the list is empty:
- every declared input in
diffci.jsonfails with "Declared input ... selects no tests; full validation required", even when itstestsglob matches real tests; alwaysRunTestsglobs select nothing, so the listed tests are silently not run.
Repro: pytest repository (testpaths = ["tests"]) with diffci.json {"inputs": [{"files": ["data/model.bin"], "tests": ["tests/test_model.py"]}]}. Change data/model.bin. For the second case, set alwaysRunTests: ["tests/test_smoke.py"] and change any module.
Expected: tests/test_model.py is selected; tests/test_smoke.py is always added.
Actual: full fallback for the declared input; tests/test_smoke.py is missing from the affected tests. Maven (src/test/java/**) behaves the same.
This means the workaround mentioned in #255 falls back rather than selecting tests. Related: #162.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 4
- Avg merge
- 18h 41m
- Merged PRs (30d)
- 48
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the 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 DiffCI/core
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Planner: splitParts regex is quadratic on a quote followed by many backticks, so the fuzz test fails at randomPossibly taken @FredApps claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Agent tools: changed_files lists only the new path of a renamed filePossibly taken @FredApps claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
adapter good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
Similar issues
-
agent-ready area: ui-server priority: p3 type: test
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
schlessera/brain-kit#4249 ·
Maintainers usually reply within 1 day
-
documentation tool triaged
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
can1357/oh-my-pi#19608 · 2 comments ·
Maintainers usually reply within 1 day
-
dependencies tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
bcgov/nr-waste-plus#1549 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-token-meta#17 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-tx-parse#18 ·