Receber por email
← Voltar para o catálogo

integration-testing-scaffolding

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

36estrelas
Atualizado há 8 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add LiorCohen/sdd

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/integration-testing-scaffolding/svg)](https://www.skillteca.com.br/skills/integration-testing-scaffolding)

Skills relacionadas

Ver todas de Automação →

Alerta por categoria

Receba novas skills de Automação toda segunda

1 email curto, só com as skills novas de Automação. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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:
  3. For each server: create API client helper
  4. For each database: create test database lifecycle (setup/teardown)
  5. Configure Vitest for integration test patterns
  6. Generate Testkube test suite definition (if helm components exist)
  7. 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.

Compartilhar X LinkedIn