tdsk-integration

Runs end-to-end integration tests across API, browser, and Kubernetes infrastructure tiers.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/threadedstack/threadedstack --skill tdsk-integration-threadedstack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdsk-integration
Source: https://github.com/threadedstack/threadedstack/tree/main/.claude/skills/tdsk-integration
Command: npx skills add https://github.com/threadedstack/threadedstack --skill tdsk-integration-threadedstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating end-to-end integration tests across multiple services, UIs, and live Kubernetes infrastructure is error-prone, with scattered test utilities, auth setup, and environment configuration. This Skill consolidates the knowledge needed to run and extend the full integration test suite. ## Core Features & Use Cases - Three-Tier Test Coverage: Tier 1 API contract tests, Tier 2 Playwright browser E2E tests, and Tier 3 live Kubernetes infrastructure tests covering pods, SSH tunnels, and WebSocket sessions. - Shared Test Utilities: Typed API client with Bearer auth, JWT acquisition from Neon Auth, sandbox pod lifecycle helpers, and Playwright CRUD helpers for drawer and form interactions. - Environment Management: Centralized TDSK_IT_* environment variables for API keys, org IDs, auth credentials, and agent/project identifiers. - Use Case: After modifying the sandbox connect endpoint, run the tier3 sandbox-connect test against the live K8s cluster to verify auto-start behavior and concurrent request deduplication before merging. ## Quick Start Run the full API integration test suite with pnpm test from the repos/integration directory, or run a single tier3 test file with npx vitest using the configs/vitest.config.ts configuration.

Frequently Asked Questions about tdsk-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run end-to-end integration tests with vitest and Playwright?▼

Run pnpm test from repos/integration for the API suite (tier1 and tier3), pnpm test:ui for Playwright browser tests, or pnpm test:all for everything. Use npx vitest run with configs/vitest.config.ts to target a single test file.

How do I test Kubernetes pod lifecycle in integration tests?▼

Use the sandbox-helpers utilities: setupRunningPod() handles the full lifecycle from project creation through sandbox provisioning to a running pod, waitForPodState() polls until Running or Failed, and cleanupSandbox() performs best-effort teardown.

Why does vitest run all tests instead of my single file?▼

Placing -- before the file path when calling vitest directly causes it to ignore the file filter and run the entire suite. The -- separator is only for pnpm script passthrough, such as pnpm test:api -- src/tier3/file.test.ts.

How do I authenticate API requests in integration tests?▼

The proxy accepts Authorization Bearer tdsk_* API key tokens, which bypass social login for automation. For org creation tests, jwt-auth.ts acquires a real JWT from Neon Auth using TDSK_IT_USER_EMAIL and TDSK_IT_USER_PASSWORD.

What are the limitations of tier3 live infrastructure tests?▼

Tier3 tests require the K8s services to be running and take roughly two minutes per spec since they provision real pods, networking, and SSH tunnels. They are unsuitable for fast feedback loops; use tier1 API contract tests for quick validation.