I used to follow the orthodox TDD approach: unit tests first, then integration. I've reversed this for most of my work…
20 discussions
I used to follow the orthodox TDD approach: unit tests first, then integration. I've reversed this for most of my work…
Here's the checklist I run through when writing API tests for a new endpoint. Not exhaustive but covers 90% of what…
We ran our first real k6 load test last quarter targeting 500 concurrent users. A few things that surprised us: The…
Most testing focuses on the output: did the API return the right response? But I've started treating observability as a…
1 vote · select an option to vote
We needed to mock 3 external APIs for our integration test suite. Tried three approaches over 6 months: WireMock -…
I have a FastAPI service with a well-maintained OpenAPI spec (auto-generated by FastAPI). I want to generate a…
We have 8 microservices. Testing strategy question: where do you draw the line between testing each service in…
My company is adding basic security testing requirements. Leadership wants SDETs to own it since we already own…
I'm testing a FastAPI application with pytest-asyncio and httpx.AsyncClient and hitting a few rough edges. Issues I've…
We integrate with: Stripe (payments), SendGrid (email), Twilio (SMS), and Segment (analytics). Each has a sandbox/test…
Our payments API calls Stripe, our notifications API calls SendGrid, and our geolocation API calls Google Maps. All…
We have two teams: one owns a user service (Python/FastAPI), one owns a frontend (Next.js). The user service API is the…
Our API test suite uses a real PostgreSQL database (Docker, spun up in CI). Each test creates data and we need…
REST API testing feels natural with pytest + requests, but I'm not sure how to apply the same discipline to GraphQL.…
We're an SDET team testing a service that uses a database we don't own — the schema is managed by a platform team and…
As our API test suite grows I'm realising ad-hoc test data in each test function is a maintenance nightmare. Three…
I need to validate API response structures in pytest tests. Three paths I see: 1. jsonschema — explicit, dict-based…
Our test suite hits a third-party API (Stripe sandbox) and we occasionally get 429s in CI, causing random test…
Our auth tokens expire after 1 hour. Most CI runs complete in 30–40 minutes so it's fine, but nightly full-suite runs…