Database
Supabase testing starts with supabase start for a fully local Postgres stack, pgTAP for Row Level Security policy validation, and Deno's built-in test runner for Edge Functions — all running locally without any remote API calls. Key Takeaways RLS policies are database logic — test them in the database. pgTAP
Database
PlanetScale's database branching model lets you create isolated test databases from production schema in seconds. Pair that with automated schema change validation and Vitess compatibility checks, and you have a testing workflow that catches production incidents before they happen. Key Takeaways Database branches are your test environments. PlanetScale
Database
Neon's branching API makes test isolation cheap — create a branch per PR in seconds, run tests, delete it. But serverless Postgres has specific behaviors around cold starts, connection pooling, and branch state that need explicit testing coverage. Key Takeaways Branches are the unit of test isolation. Neon branches
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 fine
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 has a happy
DevOps
ArgoCD makes GitOps deployments feel effortless — until a bad sync silently rolls out a broken config to 40 namespaces via an ApplicationSet. This guide covers how to validate ArgoCD applications, ApplicationSets, and sync policies before they reach a production cluster, using argocd app diff, local kind/k3d clusters, and automated
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 locally
DevOps
Crossplane Compositions are Kubernetes-native infrastructure templates that expand a simple XR claim into tens of managed resources. A bug in a Composition can delete a production RDS instance when someone creates a new database claim. This guide covers how to test Composition logic with crossplane beta render, unit-test patch-and-transform functions,
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
DevOps
Backstage plugins live at the intersection of React frontend, Node.js backend, and Backstage's entity catalog — which makes them surprisingly tricky to test. This guide walks through unit testing plugin backends with @backstage/test-utils, integration-testing catalog API interactions, and running Cypress E2E tests against a real Backstage instance.
Testing
Every third-party API integration needs tests — but mocking, contract testing, and real integration testing each have different tradeoffs. Mocks are fast but drift from reality. Real integration tests are accurate but slow and expensive. Contract tests are the middle ground that most teams miss. This guide covers when to use
Game Development
Beyond basic assertions, GUT provides mock objects, spy capabilities, and signal testing that let you isolate and verify complex game behavior. This guide covers GUT's advanced features: creating doubles (mocks/stubs), asserting method calls, testing signal emissions, and testing scene interactions in GDScript. Key Takeaways GUT doubles (mocks)