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
Testing
Most browser automation tools assume the web is stable and predictable. Skyvern doesn't. Built around the insight that modern web applications are dynamic, multi-step, and increasingly protected against bots, Skyvern approaches browser automation as an AI agent problem rather than a scripting problem. This post covers what Skyvern
Testing
Browser automation has always been a brittle affair. You write a selector like #submit-btn, the design team renames it to .cta-button, and suddenly your entire test suite is broken. Stagehand, an open-source framework built by Browserbase, takes a fundamentally different approach: instead of hard-coded selectors, it uses large language models
Testing
Playwright is already one of the most capable browser automation frameworks available. Fast, cross-browser, with excellent TypeScript support and a rich assertion library — it sets a high bar for traditional test automation. But the AI wave hasn't left Playwright behind. A growing ecosystem of extensions, plugins, and integrations
Testing
When Anthropic released Claude's computer use capability in 2024, it marked a shift from LLMs that generate text to LLMs that take actions. Computer-use models can see a screen, reason about what's on it, and control a computer through mouse clicks, keyboard input, and scrolling — just
Testing
The Python AI ecosystem has exploded with tools for building LLM-powered applications, but most of them operate on text. Browser Use bridges the gap: it's a Python library that gives LLMs the ability to actually interact with web browsers, making it a natural fit for teams building AI-powered
Testing
Gradual rollouts and canary deployments reduce risk but introduce new testing problems: how do you test that the rollout percentage is correct, that monitoring detects regressions, and that rollback works before you need it in production? This guide covers testing strategies for the full progressive delivery lifecycle. What Makes Progressive
Test Automation
Billing is where bugs have the most direct financial impact. Overcharging customers, webhooks that fail silently, or subscriptions that don't cancel properly — these bugs erode trust fast. This guide covers how to test your Stripe billing integration systematically using Stripe's test mode, the Stripe CLI for
Test Automation
Temporal workflows are deterministic, durable, and long-running — which makes testing them different from testing ordinary async code. The key challenges are: testing workflow logic without running a full Temporal server, testing activity implementations, and verifying that histories replay correctly after code changes. This guide covers all three. Why Temporal Testing
Test Automation
Sidekiq is the standard background job processor for Ruby on Rails. Testing Sidekiq workers well requires understanding three modes: fake (in-memory queue, no Redis), inline (synchronous execution), and real (full Redis-backed queue). Each mode serves a different testing layer. Setup # Gemfile gem 'sidekiq' gem 'sidekiq-testing', group: