36 articles
Wiring API tests into CI/CD: pipeline architecture, gating strategy, and tooling guides for Jenkins, GitHub Actions, Azure DevOps, and GitLab CI.
What API fuzz testing is, how mutation, generation and schema-based fuzzing differ, the main tools (Schemathesis, RESTler, ZAP, ffuf), a worked Schemathesis example against an OpenAPI spec, how to triage findings and how to run fuzzing in CI.
Is API testing integration testing? Sometimes. This guide explains API integration testing, how it differs from unit, contract and end-to-end tests, how to handle dependencies with Testcontainers, service virtualization and mocks, and walks through a docker-compose + pytest example that runs in CI.
How to load test an API properly: load, stress, spike and soak tests, the metrics that matter (p95, p99, throughput, error rate), open vs closed workload models, SLOs, a worked k6 and JMeter example, CI gating and the mistakes that make results meaningless.
A complete, fill-in API test plan template: scope, environments, entry and exit criteria, risk register, coverage targets, test data, tools, CI quality gates and reporting, plus a one-page API test strategy and a downloadable Markdown file.
A hands-on guide to API testing in C# on .NET 8: HttpClient with xUnit and NUnit, RestSharp, FluentAssertions, JSON schema checks, in-process tests with WebApplicationFactory, and running the suite in CI with dotnet test.
A practical guide to API testing with JavaScript: Jest and Supertest for Node.js services, Playwright's request API for external APIs, JSON Schema validation with Ajv, and a CI workflow, all with runnable code.
How to test API versioning and backward compatibility: URI, header and media-type strategies, breaking vs non-breaking changes, OpenAPI diff tools like oasdiff, consumer contracts, deprecation headers and CI gates.
A roundup of test data management tools grouped by job: synthetic generation, masking and subsetting, service virtualization and in-pipeline data. Licence models, what each tool is best at, how we evaluated them and how to choose.
How to gate AI-assisted development — why line coverage stops meaning anything, the four checks that hold, and where human review should be spent when volume outruns it.
