vitest-dev / vitest-dev/vitest
Split tests in the monorepo
Open
Nobody has claimed this yet.
contributing
p1-chore
- Dominant language
- TypeScript
- Stars
- 17.1k
- Forks
- 2k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 94
Description
Clear and concise description of the problem
It is not intuitive to write new tests in the Vitest monorepo.
Suggested solution
Continue #9367
Move all integration tests into test/cli and rename to integration:
- snapshots
- config
- typescript
- workspaces, workspaces-browser
- coverage-test
dts-* testshttps://github.com/vitest-dev/vitest/pull/9566
Rename core to unit. In the end, we will have:
- browser
- integration
- unit
- ui for e2e tests
Alternative
No response
Additional context
No response
Validations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
Contributor 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.
Research direction
Start by inspecting the test/cli layout and the existing core test directory, then review the integration groups listed in the issue: snapshots, config, typescript, workspaces, coverage-test, and related tests. Done means the integration tests are under test/cli/integration, core is renamed to unit, and the final categories are browser, integration, unit, and ui.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100