integration-test-v2

Develop and verify integration tests with Testcontainers against merged implementations.

3|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/drdatarulz/TI-Engineering-Standards --skill integration-test-v2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-test-v2
Source: https://github.com/drdatarulz/TI-Engineering-Standards/tree/main/skills/archive/integration-test-v2
Command: npx skills add https://github.com/drdatarulz/TI-Engineering-Standards --skill integration-test-v2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured workflow to validate a merged software implementation by writing end-to-end integration tests using Testcontainers, ensuring changes are reliable before release.

Core Features & Use Cases

  • Establishes end-to-end test patterns for repositories, endpoints, and migrations, following a deterministic workflow with fixtures, containers, and real database interactions.
  • Guides test planning, design, and execution, including setup, seeding, and assertion patterns compatible with the project's conventions.
  • Covers the full life cycle from loading project standards to committing and creating pull requests for test artifacts.

Quick Start

Initialize and run the integration test workflow against the merged implementation using Testcontainers, seed data, execute tests, and open a PR.

Frequently Asked Questions about integration-test-v2

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

FAQPage Schema
How do I automate integration tests on merged code using Testcontainers?

Automate integration tests by developing and verifying end-to-end test patterns against merged implementations using Testcontainers. This workflow establishes repository-level and endpoint tests with real database interactions, fixtures, and containerized environments to ensure changes are reliable before release.

What is the best way to validate a merged software implementation with end-to-end tests?

Validate a merged software implementation by executing a deterministic end-to-end test workflow that covers happy-path, edge-cases, and fix-mode validation. This approach uses seeded data and real infrastructure via Testcontainers to confirm endpoint and repository integrations.

Does this integration testing workflow support both happy-path and edge-case validation?

Yes, the integration testing workflow explicitly supports happy-path, edge-cases, and fix-mode validation during reviews. It guides test planning, design, and execution compatible with project conventions to ensure comprehensive coverage of merged code.

Can I use Testcontainers to run repository-level and endpoint integration tests?

Yes, Testcontainers is used to run repository-level and endpoint integration tests against real infrastructure. The workflow handles setup, seeding, and assertion patterns to verify database interactions and endpoint behaviors in a containerized environment.

Do I need existing test fixtures and merged PR details to run end-to-end integration tests?

Yes, you need merged PR details and access to existing test fixtures to run end-to-end integration tests. The workflow requires these inputs to scope repository-level and endpoint integrations and to execute tests accurately in a containerized environment.

How do I create a pull request for integration test artifacts after execution?

Create a pull request for integration test artifacts by completing the test life cycle workflow, which covers loading project standards, executing tests, and committing the resulting test artifacts. This ensures validated test patterns are reviewed and merged.