79e936bd68
The existing 380-test backend suite runs entirely against the in-memory
datastore provider, which treats every partition-key value as equivalent.
This hid one entire class of bug — partition-key mismatches — until
production. D7 closes that gap.
Implementation:
- backend/src/test-helpers.ts adds useCosmosDatastore() that swaps the
active provider for CosmosDatastoreProvider using COSMOS_ENDPOINT /
COSMOS_KEY / COSMOS_DATABASE. Throws synchronously when env is missing
so a misconfigured run fails loudly instead of silently falling back
to in-memory.
- backend/vitest.config.ts now excludes src/**/*.cosmos.test.ts so the
default 'pnpm test' run stays green for contributors without Docker.
- backend/vitest.cosmos.config.ts (new) includes ONLY *.cosmos.test.ts,
bumps testTimeout to 30s / hookTimeout to 60s for the real client
round-trips, and locks DB_PROVIDER=cosmos in test env.
- backend/src/cosmos.smoke.cosmos.test.ts (new) covers the four most
important partition-key contracts in NoteLett:
workspaces /userId
notes /workspaceId
note_tasks /workspaceId
note_shares /workspaceId (full create → resolve → delete → null)
Each test also asserts that a wrong-partition-key lookup returns null,
which is the failure mode the in-memory provider cannot simulate.
- backend/package.json adds 'test:cosmos' script.
- .github/workflows/ci.yml gains a backend-cosmos job that boots the
official mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator
container as a service, waits for it to be ready (60 × 5s polls of
/_explorer/emulator.pem), then runs pnpm test:cosmos against it.
The job depends on the existing backend job so the emulator only
spins up after unit tests pass.
Verified locally:
- pnpm --filter @notelett/backend test: 380/380 (cosmos suite excluded)
- vitest list --config vitest.cosmos.config.ts: 4 tests under the cosmos
smoke suite, as designed
- pnpm run verify: end-to-end green (backend 380/380, web 96/96,
mobile 97/97)
- ci.yml passes Python yaml.safe_load
CI verification: the new job will execute on the next push. Local
verification against the emulator requires Docker on the dev host.
34 lines
1.1 KiB
TypeScript
34 lines
1.1 KiB
TypeScript
import { defineConfig } from 'vitest/config';
|
|
|
|
/**
|
|
* Cosmos-emulator integration test runner.
|
|
*
|
|
* Only includes files matching `**\/*.cosmos.test.ts`. These suites must NOT
|
|
* run under the default vitest config because they need a live Azure Cosmos
|
|
* endpoint (the official `mcr.microsoft.com/cosmosdb/linux/azure-cosmos-emulator`
|
|
* image in CI, or a local emulator instance).
|
|
*
|
|
* Required env at runtime:
|
|
* COSMOS_ENDPOINT e.g. https://localhost:8081
|
|
* COSMOS_KEY the well-known dev key for the emulator
|
|
* COSMOS_DATABASE defaults to "notelett_test"
|
|
* NODE_TLS_REJECT_UNAUTHORIZED=0 (emulator uses a self-signed cert)
|
|
*
|
|
* Run via: `pnpm --filter @notelett/backend run test:cosmos`
|
|
*/
|
|
export default defineConfig({
|
|
test: {
|
|
globals: true,
|
|
include: ['src/**/*.cosmos.test.ts'],
|
|
exclude: ['**/node_modules/**'],
|
|
// Cosmos calls are slower than in-memory; give the suite headroom.
|
|
testTimeout: 30_000,
|
|
hookTimeout: 60_000,
|
|
passWithNoTests: false,
|
|
env: {
|
|
ALLOW_ANONYMOUS_DEV: 'true',
|
|
DB_PROVIDER: 'cosmos',
|
|
},
|
|
},
|
|
});
|