Skip to Content
Telegram MCPTestingTesting Documentation

Testing Documentation

This folder holds the testing strategy, instructions for running the suites locally and in CI, and coverage expectations.

When this gets populated

As tests are added. The first content lands with Phase 1 (when Vitest is installed and the first unit tests appear) and matures through every subsequent phase.

Each phase’s phase-n-*.md file lists the concrete Vitest unit-test cases for that phase’s deliverables. The overall strategy (unit / integration / MCP contract tests, Inngest local dev, CI shape, MCP Inspector for manual E2E) is documented in ../plan/operations-and-strategy.md.

When code exists, this folder should answer:

  • How do I run the test suite?
  • How do I add a new unit / integration / MCP contract test?
  • What’s the coverage target?
  • How do I spin up a local Postgres + Inngest dev server for integration tests?

See ../plan/ for what’s being built and when.

Component DocumentationSetup