Testing
Google Actions testing spans three environments: the Actions Console simulator for interactive exploration, ngrok tunnels for local fulfillment development, and automated pytest suites for webhook logic and conversation flow regression. This guide covers all three with production-ready code. Google Actions (built with Actions Builder or the Actions SDK v3) presents
Testing
Puppeteer's page.pdf() generates PDFs from HTML pages — but verifying the output requires more than file existence checks. This guide covers testing PDF content via text extraction, visual regression diffs, layout assertions, and metadata checks using Node.js, Puppeteer, and the pdf-parse library. Key Takeaways Use pdf-parse to
Testing
MCP (Model Context Protocol) servers expose tools, resources, and prompts to AI agents. Testing them requires validating JSON-RPC protocol compliance, schema correctness, tool execution behavior, resource content, and error handling — none of which standard unit test frameworks handle out of the box. This guide covers how to test each MCP
Testing
Approval testing (also called snapshot testing or golden master testing) captures the output of your code and stores it as an "approved" baseline file. Future test runs compare actual output against the baseline — if they differ, the test fails. It's the right tool when the expected
Testing
RabbitMQ, NATS, and Kafka have dramatically different testing developer experiences. NATS wins on speed and simplicity with its embedded server. RabbitMQ is straightforward with Testcontainers. Kafka requires the most setup but has the richest ecosystem for testing. This comparison helps you understand what you're signing up for before
Testing
ZeroMQ is a brokerless messaging library — there's no server to start, which makes testing both easier and harder. Easier because you can test sockets in the same process. Harder because ZeroMQ's asynchronous socket behavior creates timing issues that require careful test design. This guide covers testing
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