49 posts
Contract testing and API testing solve different problems. Here's the difference, when to use each, and how to combine them in a microservices test pyramid.
Everything you need to load test an API: profiles, metrics, tools, CI/CD patterns, and how to read p95/p99 percentiles when results come back ugly.
Load test any REST API in under an hour: define SLOs, write a k6 script, simulate realistic users, run in CI, and interpret p95/p99 percentiles.
k6 or JMeter for load testing in 2026? A neutral comparison across scripting, scalability, CI/CD fit, and reporting — with the right tool for each scenario.
The complete guide to API testing in 2026 — from REST and GraphQL to gRPC, with the tools, test types, and CI/CD patterns that actually work in practice.
The formulas behind virtual users in load testing, when to use VUs vs requests per second, and how to size a realistic test for your API.
Automate API tests in CI/CD with GitHub Actions — including matrix strategies, secrets, JUnit reports, service containers, and ready-to-copy YAML examples.
Performance, load, stress, spike, soak, and smoke tests explained side by side — with a decision tree for picking the right test for the job.
Compare four ways to run Postman collections in CI without Newman — Postman CLI, Apidog CLI, k6, and dev.tools — with real GitHub Actions YAML for each.
Capture a HAR file in Chrome, sanitize sensitive data, and turn it into a runnable, repeatable API test in CI in under ten minutes.
LLMs can make a single API call just fine. But chain five together — auth, create, transform, validate, clean up — and they fall apart. Here is why multi-step API workflows break AI agents, and what infrastructure is actually missing.
API tokens in CI: design least-privilege scopes, rotate without downtime, and prevent leaks in logs, HAR, and artifacts for YAML-based API tests.
GitHub CI CD for API tests: shard YAML flows for parallel runs, upload JUnit artifacts per shard, merge reports, and keep failures readable in PRs.
Postman for testing API works until collections become brittle. Learn when to switch to Git-native YAML flows for CI, PR review, and request chaining.
Dev Tools for API Testing: standardize YAML flows, Git conventions, CI reports, request chaining, and assertions so teams ship deterministic tests at scale.
API testing from real traffic: capture a HAR, convert to reviewable YAML flows, chain requests, and enforce a CI gate with deterministic assertions.
Postman alternative for Git-first teams: store API tests as YAML in Git, review via PRs, chain requests deterministically, and run fast in CI with a runner.
Code review checklist for YAML API tests: chaining, deterministic assertions, secrets hygiene, and CI rules. Review flows in Git, no UI required.
Testing microservices APIs beyond the pyramid: contracts, service virtualization, Docker Compose environments, workflow chaining, and OpenTelemetry trace checks
API testing best practices 2026: why YAML test definitions, GitOps PR workflows, HAR and trace-based generation, and CI-first chaining for determinism.
Contract testing vs end-to-end API testing: use this decision framework and matrix to choose coverage by team size, APIs, release frequency, consumers.
Migrate Postman to automated API testing: export collections, convert to Git-friendly YAML flows, manage env secrets, and run deterministic CI tests.
Learn API chain testing with YAML: authenticate, create resources, assert responses, and clean up reliably in CI with Git-reviewed flows.
End-to-end API testing validates complete workflows, not isolated endpoints. Learn how to chain requests, pass variables, handle auth, and run multi-step API tests in CI.
Postman pricing 2026 limits Free to 1 user. Learn workflow impact and follow a practical migration from Postman/Newman to DevTools YAML tests in Git.
Step-by-step tutorial: build an end-to-end API test that logs in, creates a resource, verifies it, updates it, deletes it, and confirms deletion. Full YAML examples and CI setup included.
Single-request API tests give false confidence. Real bugs hide in the gaps between endpoints: stale tokens, broken chains, side effects that never fire. Here is what they miss and how to fix it.
Turn Chrome DevTools Network captures into a repeatable HAR→YAML flow pipeline for Git and CI, with request chaining, redaction, and stable assertions.
Chrome Web Developer Tools can record real API traffic. Turn HAR captures into replayable YAML tests in Git, with request chaining and CI runs.
Learn how to export a clean HAR in Chrome DevTools: preserve log, disable cache, filter by domain, remove third-party noise, and redact secrets safely.
Generate JUnit reports for API tests so GitHub Actions shows clean failures. Stable step names, artifacts, annotations, and exit-code patterns.
Learn practical JSON assertion patterns for API tests with YAML examples: JSONPath checks, array rules, chaining, and CI-friendly determinism.
Schema vs snapshot testing for APIs in CI: when to use contracts, when snapshots win, and a hybrid YAML strategy that stays deterministic in Git.
HAR to YAML API test flow: auto-extract tokens and IDs, chain requests, and keep tests reviewable in Git and CI with DevTools.
API regression testing checklist: 30 edge cases for auth, rate limits, pagination, idempotency, and partial failures, plus YAML snippets.
Copy-paste GitHub Actions workflow for YAML API tests: parallel matrix runs, caching, cancel-in-progress, plus JUnit and logs to cut CI time.
Deterministic API Assertions in CI: handle timestamps, UUIDs, unordered arrays, float tolerance, pagination, and redaction for stable JSON tests.
API assertions in YAML: validate status, JSONPath, headers, and timing thresholds. Keep tests reviewable in Git and reliable in CI.
Auditable API test runs: what to store in Git vs CI artifacts (YAML, JUnit, logs, HAR). Build reproducible, reviewable evidence in pipelines.
Build a Git workflow for YAML API tests with required PR checks, JUnit reports, and merge rules. Keep merges deterministic with CI-native, reviewable flows.
Pin GitHub Actions, runner images, and CLI tools (DevTools included) to stop CI breakage. Practical YAML examples, checksum tips, and safe update flow.
Git-friendly YAML API tests need stable formatting. Learn rules for clean diffs: key order, quoting, block scalars, sorted headers, and CI enforcement.
Learn to test file downloads in API flows using Content-Length, checksums, and headers, with YAML examples for Git and CI-friendly verification.
Redact HAR files safely: remove auth, cookies, and PII, then convert traffic into shareable YAML API tests that run locally and in CI.
API testing in GitHub Actions done right: manage secrets, handle auth, add safe retries, and respect rate limits (including GitHub API) with YAML flows.
YAML API test file structure conventions for clean Git diffs, deterministic CI/CD runs, and clear request chaining. Practical patterns and examples.
Convert HAR to YAML and generate API regression tests you can review in Git and run in CI. Includes GitHub Actions workflow tips and request chaining.
GitHub Flow explained for API testing teams: branching, PR checks, CI, and reviewable YAML workflows. Learn a practical setup and common pitfalls.
We're excited to announce DevTools, a local-first API testing and flow automation tool that turns browser traffic into executable YAML flows.
Star on GitHub