pi-mono/packages/coding-agent/test/suite
Mario Zechner a7acef92a7 fix(coding-agent): resource collision precedence, user/project skills override package skills
Sort resolved resources by precedence rank (project settings > project auto >
user settings > user auto > package) so first-wins collision logic produces
correct results. Also reorder CLI paths to prepend instead of append.

fixes #2781
2026-04-04 21:28:38 +02:00
..
regressions fix(coding-agent): resource collision precedence, user/project skills override package skills 2026-04-04 21:28:38 +02:00
agent-session-bash-persistence.test.ts test(coding-agent): add session lifecycle characterization suite 2026-04-01 22:59:49 +02:00
agent-session-compaction.test.ts test(coding-agent): add session lifecycle characterization suite 2026-04-01 22:59:49 +02:00
agent-session-model-extension.test.ts test(coding-agent): add session lifecycle characterization suite 2026-04-01 22:59:49 +02:00
agent-session-prompt.test.ts test(coding-agent): add session lifecycle characterization suite 2026-04-01 22:59:49 +02:00
agent-session-queue.test.ts test(coding-agent): add session lifecycle characterization suite 2026-04-01 22:59:49 +02:00
agent-session-retry-events.test.ts test(coding-agent): add session lifecycle characterization suite 2026-04-01 22:59:49 +02:00
agent-session-runtime.test.ts Renamed test 2026-04-04 21:07:08 +02:00
harness.ts test(coding-agent): add session lifecycle characterization suite 2026-04-01 22:59:49 +02:00
README.md refactor(coding-agent): replace AgentSessionRuntimeHost with closure-based AgentSessionRuntime 2026-04-03 20:14:12 +02:00

Coding agent suite tests

Use test/suite/ for the new harness-based test suite around AgentSession and AgentSessionRuntime.

Rules:

  • Use test/suite/harness.ts
  • Use the faux provider from packages/ai/src/providers/faux.ts
  • Do not use real provider APIs, real API keys, network calls, or paid tokens
  • Keep these tests CI-safe and deterministic
  • Do not use or extend the legacy test/test-harness.ts path unless a missing capability forces it

Organization:

  • Put broad lifecycle and characterization tests directly under test/suite/
  • Put issue-specific regression tests under test/suite/regressions/
  • Name regression tests as <issue-number>-<short-slug>.test.ts
  • Example: test/suite/regressions/2023-queued-slash-command-followup.test.ts