integration-test-runner

Run Spring Boot integration tests in Windows Podman environments.

Updated Jul 2, 2025
One-click install
npx skills add https://github.com/junechen7414/SpringBoot --skill integration-test-runner-junechen7414
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integration-test-runner
Source: https://github.com/junechen7414/SpringBoot/tree/main/.bob/skills/integration-test-runner
Command: npx skills add https://github.com/junechen7414/SpringBoot --skill integration-test-runner-junechen7414

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you run Spring Boot integration tests reliably in a Windows plus Podman setup, avoiding common failures such as missing Docker provider errors, Oracle container connection refusals, and flaky local-versus-CI mismatches.

Core Features & Use Cases

  • Podman-aware test execution: Detects when code changes will trigger Testcontainers and advises when to stop or restart compose services.
  • Environment repair guidance: Fixes ~/.testcontainers.properties to point at the correct Podman pipe so Testcontainers can connect.
  • Failure diagnosis: Explains and resolves known issues like DockerClientProviderStrategy errors, ORA-12541, and singleton container lifecycle bugs.
  • Use case: Before pushing code, use this Skill to verify whether integration tests will start containers and to choose the safest run sequence for a green build.

Quick Start

Ask the Skill to check your Windows Podman setup and guide you through running Spring Boot integration tests without Docker provider or Oracle container errors.

Frequently Asked Questions about integration-test-runner

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

FAQPage Schema
How do I fix Testcontainers DockerClientProviderStrategy errors on Windows Podman?

Resolve ORA-12541 Oracle container connection refusals by implementing a singleton Oracle container pattern. This lifecycle management ensures the database container remains stable and accessible during Spring Boot integration testing.

Why does my Spring Boot integration test fail with ORA-12541 in Podman?

Spring Boot integration tests fail with ORA-12541 due to Oracle container connection refusals. Implementing a singleton Oracle container pattern stabilizes the database lifecycle and prevents connection drops during local and CI runs.

How do I run Spring Boot integration tests reliably in a Windows Podman environment?

Run Spring Boot integration tests reliably by applying safe compose stop and start sequencing. Correct Podman pipe configuration and a singleton Oracle container pattern prevent Testcontainers startup failures and compose lifecycle conflicts.

Can I use Testcontainers with Podman for CI pipeline integration testing?

You can use Testcontainers with Podman for CI integration testing by ensuring correct pipe configuration and safe compose sequencing. This prevents flaky local-versus-CI mismatches and resolves container lifecycle conflicts.

What causes compose lifecycle conflicts during local integration testing and how do I prevent them?

Compose lifecycle conflicts occur when code changes trigger Testcontainers without proper sequencing. Prevent these conflicts by following safe compose stop and start sequencing guidelines before running Spring Boot integration tests.