Testing
Writing eBPF programs is hard. Testing them is harder. The kernel-userspace boundary, the BPF verifier, the lack of standard debugging tools — all of it conspires to make eBPF a domain where bugs hide for a long time. libbpf, the canonical C library for loading and interacting with BPF programs, provides
Testing
Modern software testing has a visibility problem. Unit tests tell you whether your code returns the right value. Integration tests confirm your services talk to each other. But neither tells you what the kernel is actually doing while your application runs — which syscalls fire, how long disk I/O blocks,
Testing
Odin is a systems programming language built for performance, clarity, and joy. It sits in a similar space to Zig and C3 — lower level than Go, safer than C, and with a syntax that prioritizes readability over terseness. Odin's testing story is built directly into the compiler: no
Testing
Gleam is a statically typed functional language that compiles to Erlang and JavaScript. It brings the reliability of the Erlang VM to a modern, approachable syntax — and its testing story is just as well-considered. If you are building with Gleam, gleeunit is your primary testing tool. This guide covers everything
Testing
Configuration bugs are responsible for a disproportionate share of production outages. The values look right until they do not, and by then something is already broken. CUE and Pkl are two languages built to make configuration correct by construction — and both come with testing and validation tooling that belongs in
Testing
Polars has become a serious alternative to pandas for data processing work. Its Rust core delivers performance that pandas cannot match, and its expressive lazy API makes complex transformations readable. But testing Polars code requires different patterns than testing ordinary Python or Rust functions. DataFrames are not simple values — they
Testing
The Linux kernel's BPF subsystem has one of the most sophisticated CI testing infrastructures in open-source software. The BPF selftests, the netdev CI, the QEMU-based kernel test framework — these systems catch regressions in hundreds of BPF programs across dozens of kernel versions before any code merges. If you
Testing
Every development team has some informal way of documenting API calls. Slack messages with curl commands. Postman collections that live on one person's laptop. A wiki page with example requests that went stale three sprints ago. None of these are good solutions. The VS Code REST Client extension
Testing
API testing has a tooling problem. Postman collections balloon into unmaintainable JSON blobs. Custom shell scripts with curl become brittle and unreadable. Language-specific frameworks require onboarding everyone to the same tech stack. Hurl cuts through all of that with a refreshingly simple idea: describe HTTP requests and assertions in plain
Testing
Microservices break apart functionality and introduce integration failure as a first-class risk. When Team A changes an API endpoint, Team B's service breaks — in production, during an incident, after everyone has gone home. Contract testing exists to catch these failures before they reach production, by codifying the agreement
Testing
There are two kinds of API testing tools: the ones that look impressive in demos and the ones that actually fit into your daily workflow. httpyac is firmly in the second category. It extends the familiar .http file format with scripting, environments, authentication helpers, and a capable CLI — then wraps
Testing
Writing HTTP API tests is the easy part. The test files exist, the assertions look right, and they pass on your laptop. Then CI comes into play and everything falls apart: secrets are not available, the test environment is not ready, tests run in the wrong order, results do not