# Podman Testing > Podman Compose integration testing patterns for TimescaleDB and RabbitMQ container management Use when this capability is needed. - Skill: `tomevault-io/podman-testing` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/podman-testing` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/podman-testing/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Integrations & APIs - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/podman-testing --- ## What I Do Guide integration testing with Podman-managed containers for TimescaleDB (PostgreSQL 17) and RabbitMQ 4.1.4. ## Container Services ### TimescaleDB (crypto-scout-collector-db) - **Image**: `timescale/timescaledb:latest-pg17` - **Port**: `127.0.0.1:5432:5432` - **Database**: `crypto_scout` - **User/Password**: `crypto_scout_db` / `crypto_scout_db` - **Schema**: `crypto_scout` - **Resource Limits**: 1 CPU, 2GB RAM ### RabbitMQ (crypto-scout-mq) - **Image**: `rabbitmq:4.1.4-management` - **AMQP Port**: `127.0.0.1:5672:5672` - **Streams Port**: `127.0.0.1:5552:5552` - **User/Password**: `crypto_scout_mq` / `crypto_scout_mq` - **Default Stream**: `bybit-stream` - **Resource Limits**: 1 CPU, 512MB RAM ## Usage in Tests ```java import com.github.akarazhev.cryptoscout.test.PodmanCompose; import org.junit.jupiter.api.AfterAll; import org.junit.jupiter.api.BeforeAll; final class IntegrationTest { @BeforeAll static void setUp() { PodmanCompose.up(); // Starts containers, waits for readiness } @AfterAll static void tearDown() { PodmanCompose.down(); // Stops containers, removes volumes } @Test void shouldConnectToDatabase() throws Exception { assertTrue(DBUtils.canConnect()); } } ``` ## Configuration Properties | Property | Default | Description | |----------|---------|-------------| | `podman.compose.cmd` | `podman-compose` | Podman Compose binary | | `podman.cmd` | `podman` | Podman binary | | `podman.compose.up.timeout.min` | `3` | Startup timeout (minutes) | | `podman.compose.down.timeout.min` | `1` | Shutdown timeout (minutes) | | `podman.compose.ready.interval.sec` | `2` | Readiness check interval | ## Database Tables ### Bybit Spot (11 tables) - `crypto_scout.bybit_spot_tickers` - `crypto_scout.bybit_spot_kline_1m`, `_5m`, `_15m`, `_60m`, `_240m`, `_1d` - `crypto_scout.bybit_spot_public_trade` - `crypto_scout.bybit_spot_order_book_1`, `_50`, `_200`, `_1000` ### Bybit Linear (12 tables) - `crypto_scout.bybit_linear_tickers` - `crypto_scout.bybit_linear_kline_1m`, `_5m`, `_15m`, `_60m`, `_240m`, `_1d` - `crypto_scout.bybit_linear_public_trade` - `crypto_scout.bybit_linear_order_book_1`, `_50`, `_200`, `_1000` - `crypto_scout.bybit_linear_all_liquidation` ### Crypto Scout (6 tables) - `crypto_scout.cmc_fgi` - `crypto_scout.cmc_kline_1d`, `_1w` - `crypto_scout.bybit_lpl` - `crypto_scout.btc_price_risk` - `crypto_scout.btc_risk_price` ### System Tables (1 table) - `crypto_scout.stream_offsets` - Stream offset tracking **Total: 30 tables** ## Resource Files Located in `src/main/resources/podman/`: - `podman-compose.yml` - Service definitions with resource limits - `script/init.sql` - Database initialization and schema setup - `script/bybit_spot_tables.sql` - Spot table schemas - `script/bybit_linear_tables.sql` - Linear table schemas - `script/crypto_scout_tables.sql` - Crypto scout table schemas - `rabbitmq/enabled_plugins` - RabbitMQ plugins (streams enabled) - `rabbitmq/rabbitmq.conf` - RabbitMQ configuration - `rabbitmq/definitions.json` - RabbitMQ definitions (users, exchanges, queues) ## Running Tests ```bash # Standard test run mvn test # With extended timeout for slow environments mvn -q -Dpodman.compose.up.timeout.min=5 test # Custom database URL mvn -q -Dtest.db.jdbc.url=jdbc:postgresql://localhost:5432/crypto_scout test # Run specific test mvn test -Dtest=StreamConsumerPublisherTest # Run specific test method mvn test -Dtest=MockBybitSpotDataTest#shouldSpotKline1DataReturnMap ``` ## Troubleshooting ### Container not starting - Verify Podman is installed: `podman --version` - Check podman-compose: `podman-compose --version` - Increase timeout: `-Dpodman.compose.up.timeout.min=10` - Check if ports are already in use: `lsof -i :5432` or `lsof -i :5552` ### Database not reachable - Confirm port 5432 is free - Check credentials match defaults - Verify container is running: `podman ps` - Check database logs: `podman logs crypto-scout-collector-db` ### RabbitMQ Streams not reachable - Confirm port 5552 is free - Check `rabbitmq.conf` advertises `localhost` - Verify Streams plugin is enabled: `podman exec crypto-scout-mq rabbitmq-plugins list` - Check RabbitMQ logs: `podman logs crypto-scout-mq` ### Permission issues - Ensure user can run podman without sudo - Check SELinux settings if applicable - Verify podman socket is accessible ## PodmanCompose Implementation Details **Container Readiness Checks:** 1. `waitForDatabaseReady()` - Attempts JDBC connection with retry 2. `waitForMqReady()` - Creates temporary RabbitMQ Streams producer 3. `waitForContainerRemoval()` - Polls `podman ps` until containers gone **Resource Extraction:** When running from JAR, extracts podman resources to temp directory: - Creates temp dir with prefix `crypto-scout-podman-` - Registers shutdown hook for cleanup - Copies compose file, SQL scripts, and RabbitMQ config **Process Management:** - Uses `ProcessBuilder` for podman-compose commands - Daemon thread for reading process output - Forcibly destroys process on timeout - Captures partial output for debugging ## When to Use Me Use this skill when: - Setting up integration tests with containers - Troubleshooting container startup issues - Understanding the test infrastructure - Configuring Podman for CI/CD environments - Managing database state between tests - Adding new SQL initialization scripts --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/akarazhev) — claim your Tome and manage your conversions.