Testing Tools
PostHog is unusual in the analytics tooling landscape: it's open-source, self-hostable, and combines session replay, product analytics, feature flags, A/B testing, and error tracking in a single platform. For QA engineers, this combination means behavioral analysis and experimentation infrastructure live in the same place. This
Testing
Calabash and Appium solve the same problem — automated UI testing of mobile apps — but with fundamentally different architectures, different language support, and very different maintenance trajectories. The short version: Calabash is deprecated and archived. Appium is actively maintained. If you are choosing a framework today, choose Appium. If you maintain
Testing
Calabash iOS works by embedding a small HTTP server (calabash.framework) into a special test build of your app. When the app launches, it listens on port 37265. Your Ruby test code sends HTTP requests to this server to query the view hierarchy and send touch events. The production build
Testing
NIST finalized its post-quantum cryptography standards in 2024: FIPS 203 (ML-KEM, based on CRYSTALS-Kyber), FIPS 204 (ML-DSA, based on CRYSTALS-Dilithium), and FIPS 205 (SLH-DSA, based on SPHINCS+). If you're running any system that encrypts data with RSA or ECDH, or signs with
Testing
Calabash uses Cucumber as its test runner, which means your tests are written in Gherkin — the same plain-language format used by web-focused BDD tools like Capybara. A Gherkin scenario describes behavior in terms a non-engineer can read. The Ruby step definitions underneath translate those sentences into Calabash
Testing
Calabash is a cross-platform mobile UI testing framework built on top of Cucumber. It lets you write tests in Gherkin (Given/When/Then) and execute them against real iOS and Android apps. The framework works by embedding a small HTTP server into your app at test time, giving your
Testing
Podman is a daemonless, rootless container engine that's fully compatible with Docker CLI syntax. For testing pipelines, this means you can run containers without a Docker daemon, without root privileges, and without the security concerns that come with a socket-exposed daemon. This guide covers how to use
Testing
Calabash Android tests run against a specially instrumented version of your APK. The instrumentation wraps your app with a small HTTP server (powered by Robotium) that Calabash's Ruby client talks to over a local socket. This means you never modify your production binary — the test build is a
Testing
Testing PLC programs is one of the most underinvested areas in industrial software engineering. A typical automation project ships after manual bench testing with a handful of scenarios, with no regression suite to protect against future changes. When a firmware update or logic modification breaks an edge case, you find
Cadence
Cadence is Uber's open-source workflow engine—the direct predecessor to Temporal. While many teams have migrated to Temporal, Cadence remains widely deployed at scale, and understanding its testing patterns is valuable both for maintaining Cadence codebases and for teams evaluating the migration path to Temporal. This guide
Redis
Phil Karlton famously said there are only two hard things in computer science: cache invalidation and naming things. Testing cache invalidation is hard for different reasons—the behavior is time-dependent, state-dependent, and often involves distributed components that are difficult to simulate in isolation. This guide covers the major
CI/CD
End-to-end tests written with Playwright are inherently slow. Each test spins up a real browser, navigates through actual UI flows, and waits for network responses. A suite of 300 E2E tests running sequentially can take 45 minutes — long enough that most teams either stop running E2E tests in