java-test-library

Java integration tests with RabbitMQ and TimescaleDB use PodmanCompose to manage container lifecycles, providing isolated test environments. This pattern lets you spin up messaging and database services, run typed mock data assertions, and clean up database state automatically.

Typed mock data loading in Java tests uses a dedicated MockData API to bundle and parse JSON fixtures like Bybit or CMC data. This approach binds JSON files to typed Java objects, enabling reliable fixture-driven integration and end-to-end tests without manual parsing.

Podman Compose integrates with Maven-based Java test workflows by managing container lifecycles for test environments. It supports spinning up TimescaleDB and RabbitMQ containers directly during the Maven test phase, ensuring services are ready before assertions run and torn down afterward.

Simulating AMQP messaging streams in Java integration tests uses RabbitMQ utilities to replicate messaging behavior within containerized test environments. These helpers provide streams and AMQP APIs to publish and consume test messages, validating messaging logic without depending on a live external broker.

Validating database state and connectivity after Java integration tests uses DBUtils and Assertions utilities to check connection health and verify final database records. This ensures containerized TimescaleDB instances reflect expected post-test states and cleans up residual data automatically.

Modern crypto-scout integration test utilities require Java 25 to run Maven-based test workflows. This version supports the latest language features needed by MockData, PodmanCompose, and RabbitMQ test helper APIs for building robust end-to-end test suites.