Result from a backup batch operation with checkpoint info

Backup run data class for tracking backup progress

Thread-safe statistics service for tracking backup job metrics. Uses lock-free atomic operations for high-performance concurrent updates.

Level 1: Pure unit tests for BackupStatisticsService. Tests counters, report generation, and thread-safety.

Result from a pipelined batch operation. Contains the download result and optionally a future for the next Bulk Query.

Checkpoint data containing the safe position where all prior records are complete

Number of rows removed per table by a retention cleanup.

Per-period breakdown of what a retention cleanup would remove (one CSV file == one S3 object).

Dry-run summary of what a retention cleanup would remove.

Task for downloading a single ContentVersion from Salesforce and streaming it to S3. Uses in-memory buffering to avoid temp disk files (acceptable sin

Sliding window progress tracker for ContentVersion downloads. Tracks which files have been downloaded and maintains a checkpoint of the "safe" positi

Record class for ContentVersion data from CSV

Result of ContentVersion download task

Result from downloading CSV (before S3/PostgreSQL processing). Used for pipeline optimization to allow starting the next Bulk Query while processing t

Exception thrown when CSV validation fails (truncated data, missing Id, etc.)

A single period's contribution to the preview/result, with a human-readable label.

Level 1: Pure unit tests for PostgresService CSV parsing and utility methods. No Spring context, no mocking, no database.

Level 3: Integration tests for PostgresService with a real PostgreSQL database. Requires Docker running (Testcontainers).

Level 3: Shared Testcontainers PostgreSQL setup for integration tests. Extend this class to get a PostgreSQL container available for your tests.

Internal class to hold record data before batch insert

Level 3: Integration tests for RestoreService database queries. Uses real PostgreSQL via Testcontainers with mocked S3Service.

Level 1: Pure unit tests for RestoreService static/pure methods. No Spring context, no mocking, no database.

Final batch step that runs the retention cleanup. The backup job runs daily, so this is gated to one day of the month (run-on-day) and is opt-in (clea

Unit tests for the monthly cleanup gate. The batch job runs daily; the gate must let cleanup through exactly once a month (on run-on-day) and only whe

Dry-run summary of what a cleanup would remove (one CSV file == one S3 object).

Outcome of an executed cleanup.

Retention cleanup: removes backups older than a configurable window (default 3 months). Deletes the period-partitioned CSV objects from S3 and the cor

Level 3 integration test: retention cleanup against a real PostgreSQL (Testcontainers). Pins the safety invariants — archives (period < 0) and fresh p

Unit tests for the retention cutoff math. period is YYMM-encoded, so the window must be computed via YearMonth — naive subtraction would corrupt it ac

Utility class for executing operations with retry logic and exponential backoff. Only retries transient errors (network issues, 5xx errors, S3 throttl

Level 1: Pure unit tests for RetryUtil. Tests retry logic, backoff, and error classification without any Spring context.

Level 2: Unit tests for WebController with mocked dependencies. Uses Mockito without Spring context.