test-integration

Automate integration test setup and generation for Skaile packages.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/skaile-ai/ai-assets --skill test-integration-skaile-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-integration
Source: https://github.com/skaile-ai/ai-assets/tree/main/skaile-development/skills/test-integration
Command: npx skills add https://github.com/skaile-ai/ai-assets --skill test-integration-skaile-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the setup and generation of integration tests for Skaile packages, ensuring a consistent and isolated test harness across API routes, DB operations, and cross-module flows.

Core Features & Use Cases

  • Bootstraps integration test infrastructure within a target package, including setup.ts, fixtures, and Vitest configuration.
  • Generates per-endpoint/integration scenarios covering happy path, validation, and auth cases.
  • Supports multiple storage backends and isolation strategies tailored to forge/platform packages.

Quick Start

Run the integration scaffolding for a target package by selecting a mode and storage option.

Frequently Asked Questions about test-integration

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

FAQPage Schema
How do I scaffold integration tests for a monorepo package?

You can bootstrap integration test infrastructure by generating setup.ts, fixtures, and Vitest configuration, which creates a repeatable and isolated test harness for API routes and DB operations.

Can I generate Vitest integration tests for API routes automatically?

Yes, you can automatically generate per-endpoint integration scenarios that cover happy path, validation, and auth cases by leveraging built-in auth helpers and seed fixtures.

Does this integration testing approach support database operations and cross-module flows?

Yes, this approach supports database operations and cross-module flows by applying multiple storage backends and isolation strategies tailored to forge and platform packages.

What is the best way to isolate integration tests in a package?

The best way to isolate integration tests is by implementing isolation hooks and auth helpers, which ensures database operations and API routes remain repeatable without cross-test contamination.

Do I need specific test-utils to run integration tests across forge and platform packages?

You do not need external test-utils; the scaffolding process automatically generates the necessary seed fixtures, isolation hooks, and Vitest configuration within your target package.