Testing
Crystal ships with a built-in testing framework: crystal spec. It uses an RSpec-like API with describe, it, context, before_each, after_each, and expect. No external library needed. This guide covers writing Crystal specs, using matchers, testing exceptions, and setting up CI. Key Takeaways Crystal's Spec
Testing
Nim has three testing approaches: the standard library unittest module (simple but limited), unittest2 (modern replacement with better output), and testament (Nim's own compiler test tool used for its standard library). For application code, unittest2 is the recommended choice. Nim also supports doctests through the runnableExamples pragma. Key
Testing
Zig has a built-in test runner — no external framework needed. Write test "name" { ... } blocks anywhere in your code, run zig test src/main.zig, and the compiler compiles and runs them. The std.testing module provides assertions, and comptime blocks can be tested too. This guide covers
Database
Liquibase changelogs applied without testing are a production incident waiting to happen. This post covers every layer of the Liquibase testing stack: updateSQL dry-runs, Testcontainers-backed integration tests, rollback verification, and precondition testing to guard against environmental assumptions. Key Takeaways Dry-run before you apply. liquibase updateSQL generates the
Game Development
Godot uses GUT (third-party, community-maintained), while Unity ships with its own Test Framework (built-in, supported by Unity Technologies). Both enable unit and integration testing of game code, but they differ in setup complexity, CI/CD integration, test isolation, and framework maturity. This comparison helps you understand the
Testing
Email testing is more than "did it send?" Good email testing covers HTML rendering across clients, spam score validation, deliverability checks, template regression, and the full user journey from trigger to action. This guide covers the complete email testing pyramid with practical tooling and CI strategies. Key Takeaways
Game Development
Integration tests in Godot verify that multiple nodes, scenes, and autoloads work together correctly. Unlike unit tests that test a single script, integration tests instantiate real scenes, trigger real signals, and assert on the resulting state. GUT supports this with add_child_autoqfree(), scene instantiation helpers, and frame-await utilities.
Testing
SendGrid powers email delivery for many production applications. Testing SendGrid integration involves mocking the API client for unit tests, using SendGrid's sandbox mode for integration tests, and testing Event Webhooks for delivery tracking. This guide covers all three layers with Node.js examples. Key Takeaways Enable sandbox mode
Testing
Nodemailer is the most popular Node.js email library. Testing Nodemailer flows has two approaches: mock the transporter entirely (unit tests) or use Ethereal's fake SMTP server (integration tests). This guide covers both approaches, with Jest examples for testing email content, attachments, and error handling without sending real
Game Development
Godot 4 runs headlessly with --headless — no display required in CI. Combined with GUT's CLI runner, you can run your full test suite in GitHub Actions on every push. This guide covers setting up the CI pipeline, caching the Godot binary, running GUT tests, and reporting results. Key
Testing
MailHog is an open-source local SMTP server that captures all outgoing emails and exposes them via a web UI and HTTP API. No signups, no internet connection required, and no risk of emails reaching real users. This guide covers running MailHog in Docker, asserting on captured emails via its
Testing
React Native's cross-platform model means accessibility bugs can appear on iOS, Android, or both, often in different forms. A layered testing approach — jest-native for component tests, react-native-axe-core for runtime audits, and Detox for end-to-end screen reader behavior — catches issues at every