docs: clarify uv run pytest rationale in plan
This commit is contained in:
@@ -20,7 +20,7 @@
|
||||
- i18n catalogs zh/en are updated in lockstep (same keys, same ICU vars) and the new domain module is registered in both `index.ts` files AND in the module list of `src/i18n/messages/messages.test.ts` (that test hardcodes the list — forgetting it fails the suite).
|
||||
- Backend `expected_revision` is deprecated (last-write-wins); import bodies still send the current revision because the BFF PUT route requires it, but no 409/conflict handling is built.
|
||||
- WebUI tests: vitest node env, include pattern `src/**/*.test.ts` only (no Testing Library, no jsdom, no `.tsx` tests). All testable logic lives in pure `.ts` modules.
|
||||
- Test commands — backend: `cd /Users/m4/Projects/EvoSci/OriginEvoScientist/EvoScientist && uv run pytest tests/test_config_export.py -v` (plain `uv run pytest` has no pytest module). WebUI: `cd /Users/m4/Projects/EvoSci/OriginEvoScientist/EvoScientist-WebUI && npx vitest run <file>` and `npx tsc --noEmit`.
|
||||
- Test commands — backend: `cd /Users/m4/Projects/EvoSci/OriginEvoScientist/EvoScientist && uv run pytest tests/test_config_export.py -v` (system `python` has no pytest module; always use `uv run pytest`). WebUI: `cd /Users/m4/Projects/EvoSci/OriginEvoScientist/EvoScientist-WebUI && npx vitest run <file>` and `npx tsc --noEmit`.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user