vp test positional paths do not select test files
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 176
- Forks
- 66
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 52
Description
Expected Behavior
pnpm test src/server/Mppx.test.ts runs the selected Node test file without unrelated integration setup.
Current Behavior
The command reports no matching test files, then executes global Tempo setup and fails when localhost:18545 is unavailable.
Possible Solution
Document or support a focused Node-test command that accepts repository-relative paths and skips unrelated global setup.
Minimal Reproducible Example
Run pnpm test src/server/Mppx.test.ts without a Tempo localnet on port 18545.
Context
This blocks fast iteration on isolated server unit tests.
Logged by Brendan Ryan in wevm/mppx at 47d6df7. Filed by Frog.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by running pnpm test src/server/Mppx.test.ts and inspect the test command entry point and the referenced src/server/Mppx.test.ts. Trace why the positional path matches no files and still triggers Tempo setup on port 18545. Done means the command selects that file and avoids unrelated integration setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100