Testing
ActiveMQ Classic provides an embedded broker you can start directly in your test JVM — no Docker, no external process. This makes JUnit tests fast and deterministic. This guide covers testing JMS queues and topics, transactional sending, and dead letter queue behavior using the embedded broker and Spring Boot's
Testing
Every headless CMS has different testing requirements. Contentful and Sanity are managed cloud services — you test your integration code against mock clients or their preview/test APIs. Strapi and Directus are self-hosted — you test against a real running instance. This guide maps out the testing layers for each, with tooling
Testing
Apache Pulsar testing requires a real broker for meaningful integration tests — the client library doesn't provide a simulation mode. Testcontainers solves this with an official Pulsar image that starts in seconds. This guide covers producer/consumer testing, schema validation, subscription types, and dead letter topic handling in Java
Testing
Strapi v5 exposes content via REST and GraphQL APIs. Testing these APIs involves three layers: unit tests for custom service logic, integration tests against a running Strapi instance with a test database, and permission tests that verify role-based access. This guide covers all three using Jest and Supertest. Key Takeaways
Testing
Contentful doesn't have a built-in testing framework, but its Delivery API client, content model structure, and rich text renderer are all testable in Jest. This guide covers mocking the Contentful SDK, testing content model shape assumptions, validating rich text output, and writing integration tests against the Preview API.
Testing
NATS testing is unusually clean compared to other message brokers: you can run an embedded NATS server in the same process as your tests with zero Docker setup. This guide covers testing core pub/sub, JetStream persistent streams, and the key-value store using Go's testing package and the
Testing
Drupal 10 ships with three PHPUnit test types: Unit (no Drupal), Kernel (real services, no browser), and Functional (full browser via BrowserKit). Each type makes different trade-offs between speed and coverage depth. This guide explains when to use each and how to write effective tests for custom modules. Key Takeaways
Testing
WordPress plugin unit tests don't need a running WordPress install. WP_Mock and Brain\Monkey let you mock WordPress functions, hooks, and globals so your PHPUnit tests run in isolation — fast, deterministic, and CI-friendly. This guide shows how to set up both tools and write meaningful tests for
Testing
Testing RabbitMQ code falls into two categories: unit tests that mock the AMQP connection and verify your business logic, and integration tests that spin up a real broker to confirm routing, acknowledgements, and dead letter queues work correctly. Testcontainers handles the real broker — no manual Docker setup required. Key Takeaways
Python
testbook bridges the gap between notebook exploration and software engineering rigor. While nbmake verifies that a notebook executes without error, testbook lets you write pytest test functions that call specific functions defined in a notebook, inject test data, and assert outputs—the same level of testing you'd apply
Python
Reproducibility is the foundation of scientific computing. A notebook that produces a result should produce the same result when re-executed—same inputs, same code, same environment. nbval enforces this by re-running a notebook and comparing each cell's output to the recorded output in the .ipynb file. Any difference
Python
nbmake is a pytest plugin that treats Jupyter notebooks as test cases. Install it, point pytest at a directory of notebooks, and every notebook that executes without error passes. Every notebook that raises an exception fails. It is the simplest possible notebook testing setup, and for most teams it is