integration-test

Execute Go integration tests with Dockerized PostgreSQL and MinIO services.

23|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/PeterBooker/veloria --skill integration-test-peterbooker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-test
Source: https://github.com/PeterBooker/veloria/tree/main/.claude/skills/integration-test
Command: npx skills add https://github.com/PeterBooker/veloria --skill integration-test-peterbooker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows you to run integration tests that depend on external services like databases and object storage, ensuring your application components interact correctly in a realistic environment.

Core Features & Use Cases

  • Containerized Testing: Leverages Docker and testcontainers-go to spin up necessary services (Postgres, MinIO) on demand.
  • Targeted Testing: Supports running all integration tests or tests within a specific Go package.
  • Use Case: Before merging a new feature that modifies database interactions, run this Skill to confirm that the changes work as expected with a live PostgreSQL instance managed by Docker.

Quick Start

Run all integration tests by executing the integration-test skill.

Frequently Asked Questions about integration-test

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

FAQPage Schema
How do I run Docker-based integration tests for Go applications?

Run Docker-based integration tests by executing the integration-test skill, which utilizes the 'integration' build tag and testcontainers-go to spin up necessary services like PostgreSQL and MinIO on demand. It validates database and storage interactions within a realistic Dockerized environment.

What is testcontainers-go used for in integration testing?

Testcontainers-go is used for environment setup and teardown during integration testing. It leverages Docker to spin up necessary external services, such as PostgreSQL and MinIO, on demand to validate that your application components interact correctly in a realistic ecosystem.

Can I run integration tests for a specific Go package instead of all tests?

Yes, targeted testing supports running all integration tests or tests within a specific Go package. This allows you to validate database and storage interactions for a particular module before merging new features that modify application components.

Do I need Docker to validate PostgreSQL and MinIO interactions in my tests?

Yes, Docker is required for containerized testing. The tests use testcontainers-go to manage Dockerized services like PostgreSQL and MinIO, ensuring your application components are validated against live database and storage instances rather than mocked dependencies.

Why use the integration build tag when running Go integration tests?

The 'integration' build tag is used to separate integration tests from standard unit tests. This ensures that Docker-dependent tests requiring external services like PostgreSQL and MinIO are only executed when explicitly requested, preventing accidental environment setup during routine development.