Database
Flyway migrations can silently corrupt production databases if shipped without proper testing. This post covers a layered testing strategy: unit tests with H2 for fast feedback, Testcontainers for real-database fidelity, rollback testing, checksum validation, and CI pipeline integration. Key Takeaways Test migrations against a real database engine. H2 is
Database
Testing Firestore well means combining the Firebase Emulator for integration tests, @firebase/rules-unit-testing for security rule validation, and carefully structured async tests for real-time listeners — all without touching production Firestore. Key Takeaways Security rules are code — test them like code. Every path in your firestore.rules file
Database
Testing DynamoDB effectively requires a combination of local emulation with LocalStack, fast unit tests with mocked clients, and targeted integration tests that validate single-table designs, GSIs/LSIs, and PartiQL queries — without touching production AWS. Key Takeaways Use LocalStack for integration tests, not the real AWS endpoint. LocalStack emulates DynamoDB
Database
CockroachDB's distributed architecture introduces failure modes that standard database tests miss: transaction conflicts requiring retries, serializable isolation violations, and behavior under network partition. Your test suite needs to cover all three to have confidence in production. Key Takeaways Transaction retry logic is not optional in CockroachDB. The database
Testing
Integration tests live and die by their data. A test that creates an order needs a product to exist. That product needs a category. That category has constraints. Building this state in every test is tedious and produces tests that are tightly coupled to unrelated domain objects. Getting it wrong