Documentation Agent Tests
Minimal test definitions that simulate real user prompts. Tests are intentionally sparse - the agent must figure out how to accomplish the goal using only the documentation.How to Run
Use the/test command:
Doc Source Modes
Published docs (default) - Uses the Runpod Docs MCP server to search published documentation:.mdx files in this repository instead of querying the MCP server.
Test Tiers
Smoke tests - Fast tests that don’t deploy GPU resources. Use for quick validation:Test Format
Each test has:- ID: Unique identifier for the test
- Goal: What a user would ask (one sentence, no hints)
- Expected Outcome: What constitutes PASS (objective, measurable)
doc_test_ prefix.
Smoke Tests
Fast tests that don’t require GPU deployments. Run these for quick validation.
Run smoke tests:
Flash SDK
Serverless Endpoints
Important: Do NOT use public endpoints for these tests. The goal is to test the full deployment workflow: deploy an endpoint, send requests, and verify the integration works. Public endpoints are a separate product and skip the deployment steps we need to validate.
vLLM
Important: Do NOT use public endpoints for these tests. Deploy your own vLLM endpoint to test the full workflow. Public endpoints skip the deployment and configuration steps we need to validate.
Pods
Storage
Templates
Instant Clusters
SDKs & APIs
CLI (runpodctl)
Model Caching
Integrations
Public Endpoints
Tutorials (End-to-End)
Cleanup Rules
All test resources must use thedoc_test_ prefix. After each test:
- endpoints: Delete endpoints matching
doc_test_* - pods: Delete pods matching
doc_test_* - templates: Delete templates matching
doc_test_* - network-volumes: Delete network volumes matching
doc_test_* - clusters: Delete clusters matching
doc_test_* - none: No cleanup needed (read-only test)