Context
Devkit Node just split its test scripts into a clear 3-tier scheme : test:unit:coverage / test:integration:coverage / test:e2e (PRs #3558, #3559, #3561 — May 2026). Vue currently has :
test:unit — vitest run
test:coverage — vitest run --coverage
test:e2e — playwright
Vue does NOT have an "integration" tier, and test:coverage runs the same set as test:unit. The naming is asymmetric with Node, which makes context-switching between stacks confusing.
Proposal
Cosmetic rename for cross-stack consistency :
"test": "npm run test:unit",
"test:unit": "vitest run",
+ "test:unit:coverage": "vitest run --coverage",
- "test:coverage": "vitest run --coverage",
"test:e2e": "npx playwright test --config playwright.config.js",
Optional : keep test:coverage as a legacy alias for test:unit:coverage so existing CI / local muscle memory still works during transition.
Why NOT touch the architecture
- Vitest already runs workers natively (no
--runInBand problem like Jest had on Node)
- No shared MongoDB → no per-worker DB isolation needed
- Vue CI master runtime is already 2-3 min, not a bottleneck
- The Vue-specific memory leak was already fixed via
pool: 'forks' + restoreMocks (cf. feedback_subagent_models)
This is purely a naming alignment with Node, not a port of the Jest worker / matrix split work.
Effort
- 5 min : edit
package.json
- Update
.github/workflows/CI.yml if it references test:coverage directly
- Update README.md test section with the new script name(s)
- 1 PR
Low priority — bundle with the next stack housekeeping pass.
Context
Devkit Node just split its test scripts into a clear 3-tier scheme :
test:unit:coverage/test:integration:coverage/test:e2e(PRs #3558, #3559, #3561 — May 2026). Vue currently has :test:unit— vitest runtest:coverage— vitest run --coveragetest:e2e— playwrightVue does NOT have an "integration" tier, and
test:coverageruns the same set astest:unit. The naming is asymmetric with Node, which makes context-switching between stacks confusing.Proposal
Cosmetic rename for cross-stack consistency :
Optional : keep
test:coverageas a legacy alias fortest:unit:coverageso existing CI / local muscle memory still works during transition.Why NOT touch the architecture
--runInBandproblem like Jest had on Node)pool: 'forks'+restoreMocks(cf.feedback_subagent_models)This is purely a naming alignment with Node, not a port of the Jest worker / matrix split work.
Effort
package.json.github/workflows/CI.ymlif it referencestest:coveragedirectlyLow priority — bundle with the next stack housekeeping pass.