Documentation Index
Fetch the complete documentation index at: https://koreai-v2-agent-platform-dev.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Last Updated: 2026-03-25
Pages
Testing Philosophy
Every platform feature has a dedicated test specification generated through the SDLC pipeline. Test specs mandate:
- Minimum 5 E2E scenarios — real HTTP API interaction, no mocks, no direct DB access
- Minimum 5 integration scenarios — real service boundaries, no stubbed components
- Coverage matrix mapping every functional requirement to test types
- Security and isolation tests for tenant, project, and user boundaries
Summary
| Metric | Count |
|---|
| Total Test Specs | 77+ |
| Test Specs Complete | 77 |
| E2E Scenarios | 400+ |
| Integration Scenarios | 400+ |
| Test Specs Partial | 2 |
| Test Specs In Progress | 2 |
Completion by Priority
| Priority | Total | Done | Partial | In Progress |
|---|
| P0 | 12 | 11 | 1 | 0 |
| P1 | 16 | 16 | 0 | 0 |
| P2 | 25 | 25 | 0 | 0 |
| P3 | 24 | 22 | 1 | 1 |
| Total | 77 | 74 | 2 | 1 |
Notable Test Specs
Some features have expanded test coverage beyond the minimum:
| Feature | E2E | Integration | Notes |
|---|
| Reusable Agent Modules | 16 | 13 | Complex multi-tenant module system |
| Omnichannel Session Continuity | 46 | 15 | Cross-channel state management |
| SDK Rich Content Templates | 115 | 7 | Template rendering across SDKs |
| Environment Variables | 14 | 11 | Namespace resolution paths |
| SDK Chat UI Consolidation | 8 | 10 | UI component consolidation |
| Studio Theme & Docs Integration | 8 | 11 | Theme + MDX docs integration |
Live Testing Status
Features that have undergone live testing with the testing-toolkit:
| Feature | Status | Last Tested | Iterations | Gaps Open |
|---|
| Variable Namespaces + Tool Auto-Tagging | STABLE | 2026-03-14 | 6 | 2 |
| Alerts | ALPHA | 2026-03-22 | 0 | 10 |
| Omnichannel Session Continuity | ALPHA | 2026-03-23 | 1 | 6 |
| Identity Verification | BETA | 2026-03-25 | 2 | 4 |
Testing Infrastructure
| Component | Tool | Purpose |
|---|
| E2E Tests | Playwright | Browser automation, API testing |
| Unit / Integration | Vitest | Fast TypeScript test runner |
| Dev Login | Studio Dev Login | Configurable email for domain-gated testing |
| DB | MongoDB (Docker) | Real database for integration tests |
| Redis | Redis (Docker) | Real cache/queue for integration tests |
| CI | Harness CI | Automated test execution on every PR |
| Coverage | istanbul / c8 | Code coverage measurement |
Quality Gates
Tests must meet these standards before a feature can advance in status:
| Gate | Requirement |
|---|
| PLANNED -> ALPHA | Feature spec + test spec exist |
| ALPHA -> BETA | All E2E scenarios pass, all integration scenarios pass |
| BETA -> STABLE | Zero open gaps, full coverage matrix green, 2+ iterations |
| No mocks in E2E | vi.mock() / jest.mock() forbidden in E2E test files |
| API-only interaction | E2E tests use HTTP endpoints only, no direct DB access |
| Real servers | Express on random ports with full middleware chain |
