Messaging
```tldr Apache RocketMQ testing uses an embedded broker for fast unit tests and a real RocketMQ cluster via Testcontainers for integration tests. Key areas to test: normal producer/consumer flows, ordered messages, delay levels, transaction messages, and consumer group failover. ``` ```takeaways **Use rocketmq-test or an embedded broker for unit
Robot Framework
Robot Framework and pytest both run Python under the hood, both have extensive library ecosystems, and both can test web apps, APIs, and more. Yet they make opposite tradeoffs, attract different users, and serve different needs. Picking the wrong one costs months of accumulated friction. This is a direct comparison
Testing Strategy
Business logic is where bugs are most expensive. A bug in your discount calculation, insurance eligibility rule, or loan approval logic doesn't just throw an error—it silently gives the wrong answer, affecting real customers and real money. Decision table testing is a systematic technique for deriving test
WebAssembly
Debugging WebAssembly in browsers has historically been painful — you were staring at raw WAT (WebAssembly Text format) with cryptic variable names like $var0 and $var1. That's changed dramatically. Chrome 90+ and Firefox support DWARF debug information, letting you set breakpoints in your original Rust, C, or AssemblyScript source.
Robot Framework
SeleniumLibrary is the standard way to do web UI testing with Robot Framework. It wraps Selenium WebDriver in RF's keyword model, giving you browser automation through readable keyword calls instead of raw Python. This guide covers everything from installation through production-ready patterns. Installation and Setup You need
Testing
Dead letter queues (DLQs) are the safety net of event-driven systems. When a message can't be processed after N retries, it goes to the DLQ for manual inspection or alternative processing. Most teams test the happy path but skip testing DLQ behavior — which means they discover bugs
Robot Framework
SeleniumLibrary is the bridge between Robot Framework's readable test syntax and Selenium WebDriver's browser automation capabilities. It wraps hundreds of WebDriver operations into keyword-friendly interfaces, handles common pain points like implicit waits, and integrates cleanly with Robot Framework's lifecycle hooks for setup, teardown,
Database Testing
Java applications that talk to a database face a persistent testing problem: how do you test database interactions without making tests slow, fragile, or dependent on production data? DbUnit solves this by providing a framework for managing test datasets — populating tables before tests and verifying their state afterward. This guide
Robot Framework
Browser automation gets most of the attention in Robot Framework discussions, but API testing is where keyword-driven testing often delivers the fastest return. APIs are deterministic, fast to execute, and free from the timing complexity that makes UI tests flaky. A well-designed API test suite runs in seconds,
Testing
dbt's schema tests (not_null, unique, relationships) verify data quality — they check the output of your models. But they can't verify whether your SQL logic is correct. A model that produces the wrong discount calculation or the wrong attribution logic might pass all schema tests while
Testing
dbt snapshots implement Slowly Changing Dimensions (SCD Type 2) — tracking how a record changes over time by keeping the full history. A bug in snapshot configuration silently corrupts your history, making past-dated reports wrong. Testing snapshots requires validating that history is captured correctly, records are updated (not duplicated), and
Robot Framework
Robot Framework has been around since 2005 and remains one of the most widely used test automation frameworks, particularly in enterprises. Its combination of keyword-driven syntax, extensive library ecosystem, and readable test reports makes it a strong choice for teams that need non-developers to participate in test automation.