Skip navigation
“We have tests” is not a testing strategy.
0:00

“We have tests” is not a testing strategy.

#1 #apitesting #softwaretesting

“We have tests” is not a testing strategy. Nine types of API testing exist, and they fall into three families. Most teams live in one of them and get blindsided by the other two. CORRECTNESS — does it do the right thing? 1️⃣ Smoke — GET /health → 200 OK. Shallow checks on critical endpoints. Catches a dead deploy in seconds. 2️⃣ Functional — POST /orders → is total, tax and status actually right? Catches wrong business logic. 3️⃣ Contract — does the response schema still match what consumers expect? Catches the breaking change you shipped without noticing. 4️⃣ Integration — one call, four services. Stock reserved, payment authorized, email sent. Catches broken handoffs. 5️⃣ Regression — old tests against the new build. Catches the thing you silently re-broke. PERFORMANCE — does it hold up? 6️⃣ Load — 1000 virtual users at steady state. Does p95 stay under target? Catches slow-under-real-traffic. 7️⃣ Stress — ramp past capacity until it breaks. Where’s the knee, and does it degrade gracefully or fall over? Catches having no headroom. SAFETY — can it be abused? 8️⃣ Security — User A requests User B’s order → must be 403. Catches broken access control, which is the #1 item on the OWASP API list for a reason. 9️⃣ Fuzz — qty = -1, a 4MB string, malformed JSON. Does it return 400 or does it 500 and leak a stack trace? Catches unhandled edge cases. Here’s the pattern I see: teams build a solid correctness suite, ship, then get paged at 2am for something in the performance or safety column. Those two families never fail in CI. They fail in production, under real load, with a real attacker. You don’t need all nine on day one. You need to know which family you’re blind in. Save this before your next system design round 📌 Which family does your team actually cover? Be honest — most people have five of nine. More free breakdowns → algoinsight.io #apitesting #softwaretesting #systemdesign #backenddevelopment qa

Comments

Comments from the original post on Instagram

No comments yet