Skip to content
cccskills
FreePublished on GitHub

integration-testing-scaffolding

Scaffolds integration test suite structure with database setup, API testing, and Testkube configuration.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Integration Testing Scaffolding

Scaffolds an integration testing component with test infrastructure for verifying component interactions against real dependencies.

Input

Invoked by the scaffolding orchestrator with:

  • component_name: Name of the testing component
  • project_name: Project name from settings
  • existing_components: Currently configured components (servers, databases)

Directory Structure

components/testing/integration/{name}/
├── src/
│   ├── setup/
│   │   ├── test-database.ts    # Test database lifecycle
│   │   └── test-server.ts      # Test server lifecycle
│   ├── helpers/
│   │   ├── api-client.ts       # HTTP client for API testing
│   │   └── fixtures.ts         # Test data factories
│   └── tests/
│       └── .gitkeep
├── vitest.config.ts
├── package.json
├── tsconfig.json
└── README.md

Workflow

  1. Create the testing directory structure
  2. Generate test setup files based on existing components:
    • For each server: create API client helper
    • For each database: create test database lifecycle (setup/teardown)
  3. Configure Vitest for integration test patterns
  4. Generate Testkube test suite definition (if helm components exist)
  5. Create README with testing conventions

Standards

Follow integration-testing-standards for test structure, database lifecycle, and naming conventions.

Output

Returns a declared actions response with register_component action for the new integration testing component.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Standards for authoring SDD plugin agents — frontmatter, self-containment, skill references, and no-user-interaction rules.

The English summary is being prepared. Showing the original description.

LiorCohen/sdd43Updated Feb 24, 2026

Scaffolds Node.js/TypeScript backend components with CMDO architecture, driven by component settings.

The English summary is being prepared. Showing the original description.

LiorCohen/sdd43Updated Feb 24, 2026

CMDO architecture standards for Node.js/TypeScript backends with strict layer separation.

The English summary is being prepared. Showing the original description.

LiorCohen/sdd43Updated Feb 24, 2026

Intent-to-command mappings for fullstack-typescript tech pack features.

The English summary is being prepared. Showing the original description.

LiorCohen/sdd43Updated Feb 24, 2026

Create change specification and implementation plan with dynamic phase generation. Supports feature, bugfix, refactor, and epic types.

The English summary is being prepared. Showing the original description.

LiorCohen/sdd43Updated Feb 24, 2026

Orchestrates the full change lifecycle — routes actions to phase-specific sub-files.

The English summary is being prepared. Showing the original description.

LiorCohen/sdd43Updated Feb 24, 2026

See all skills by LiorCohen

Report a problem with this skill