| phase | testing |
|---|---|
| title | Testing Strategy |
| description | Testing plan for project-configurable memory database paths |
- Cover 100% of new and changed code related to config parsing and path resolution.
- Verify both configured-path and default-path flows.
- Keep standalone
@ai-devkit/memoryserver behavior unchanged.
- Reads
memory.pathwhen it is a non-empty string - Ignores missing, blank, and non-string
memory.path - Resolves relative
memory.pathfrom the project config directory Implemented inpackages/cli/src/__tests__/lib/Config.test.ts
-
memory storeuses configured path when project config exists -
memory searchuses configured path when project config exists -
memory updateuses configured path when project config exists - Commands fall back to
~/.ai-devkit/memory.dbwhen no project override exists Verified by defaultdbPath: undefinedexpectations and configured-path expectations inpackages/cli/src/__tests__/commands/memory.test.ts
- Schema initialization succeeds when the configured path points to a new file
- Memory API store/search/update calls use an explicit configured
dbPathImplemented inpackages/memory/tests/integration/api.test.ts - Standalone memory MCP server remains out of scope and unchanged Covered by design/requirements scope, not by new behavior tests
- Automated CLI e2e test uses a temp-project
.ai-devkit.jsonwith repo-localmemory.pathImplemented ine2e/cli.e2e.ts - Manual smoke test with a checked-in
.ai-devkit.jsonusing a repo-local memory DB Verified via built CLI store/search run in a temporary project directory with.ai-devkit.jsonpointing to.ai-devkit/project-memory.db
- Temporary project directories with generated
.ai-devkit.json - Temporary database file paths for isolated runs
- Ran
npm test -- --runInBand Config.test.ts memory.test.tsinpackages/cli - Ran
npm test -- --runInBand tests/integration/api.test.tsinpackages/memory - Ran
npm run test:e2e -- cli.e2e.ts - Ran
npx ai-devkit@latest lint --feature memory-db-path-config - Did not run a full coverage report command in this phase; targeted suites were used for feature verification
- Confirmed a repo-local configured DB file is created on first write
- Confirmed built CLI search reads back from the configured repo-local DB
- Default fallback is covered by unit tests rather than a separate manual run
- No dedicated performance testing required beyond regression confidence
- Watch for regressions where one CLI memory subcommand omits
dbPathand reverts to~/.ai-devkit/memory.db