sscoble/pi-mono
1
0
Fork 0
mirror of https://github.com/badlogic/pi-mono.git synced 2026-11-05 23:37:25 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4
pi-mono/packages/coding-agent/test/suite
History
Exact
Armin Ronacher 8c61663f30 feat(ai): add developer message role
2026-07-11 13:07:54 +02:00
..
regressions feat(ai): support message-anchored tool loading (#6474) 2026-07-10 23:52:54 +02:00
agent-session-bash-persistence.test.ts chore: pin dependencies and use native TypeScript 2026-05-20 12:46:17 +02:00
agent-session-compaction.test.ts feat(coding-agent): expose post-compaction token estimates 2026-06-18 23:01:10 +02:00
agent-session-model-extension.test.ts feat(ai): add max thinking level 2026-07-09 22:30:53 +02:00
agent-session-prompt.test.ts Fix input event streaming behavior semantics 2026-05-28 10:13:06 +02:00
agent-session-queue.test.ts fix(coding-agent): drain follow-ups queued during agent_end 2026-05-28 18:27:39 +10:00
agent-session-retry-events.test.ts fix(coding-agent): add settled agent lifecycle event 2026-07-09 12:42:08 +02:00
agent-session-runtime.test.ts feat(ai): complete models runtime migration 2026-06-23 15:29:46 +02:00
harness.ts feat(coding-agent): add InlineExtension type for named inline extension factories (#6267) 2026-07-06 20:59:37 +02:00
lax-message-content.test.ts feat(ai): add developer message role 2026-07-11 13:07:54 +02:00
README.md refactor(coding-agent): replace AgentSessionRuntimeHost with closure-based AgentSessionRuntime 2026-04-03 20:14:12 +02:00

README.md

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