Testing
Dialogflow CX agents require testing at three levels: the built-in Test Cases console feature for conversation regression, Python client library for automated route and parameter testing, and Flask test client for webhook validation. This guide covers all three with production-ready examples. Dialogflow CX introduced a significantly more structured
Testing
Alexa Skill testing requires a layered approach: unit tests for individual intent handlers, integration tests for full request/response cycles, and end-to-end simulation with Bespoken. This guide covers all three layers with concrete examples in Node.js and Python. Building a reliable Alexa Skill is only half the
Testing
Rasa testing has three distinct layers: NLU model accuracy tests using rasa test nlu, conversation flow tests using rasa test core with story files, and unit tests for custom actions using pytest with mocked trackers. Each layer catches different categories of bugs. Rasa Open Source gives you full control over
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)
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
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.
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
Python
Jupyter notebooks are the primary artifact for data science work—model training, data exploration, report generation. Yet most teams treat them as write-only documents. Notebooks break silently when dependencies update, when data shapes change, or when code paths that ran during development are skipped during the final run. Testing
Python
Papermill is a tool for parameterizing and executing Jupyter notebooks programmatically. It was designed for production notebook workflows—running the same analysis against different datasets, date ranges, or configuration sets—but it also makes notebooks significantly more testable. By injecting parameters and capturing outputs, you can test a notebook against
Python
mutmut is the most widely adopted Python mutation testing tool. It works by making small, targeted modifications to your source code — flipping + to -, changing True to False, removing return values — and running your test suite against each modification. If your tests don't fail when the code changes, those