Browse categories
Explore
Fiverr Pro
English
$
USD
I will build automated API tests for your rest or graphql API
QA Automation Engineer
Most QA engineers add more tests. I fix the architecture.
QA Automation Engineer, Playwright specialist – 6 years across SaaS teams. One client: 45-min CI pipeline to 15 min, flake rate from 6% to un...
About this Gig
Your team ships features behind feature flags. The API contract drifts. Frontend breaks at the worst time.
Manual Postman runs catch nothing. Your QA missed it because nobody runs the collection on PR. The bug ships. The customer notices first.
My fix: I build a code-first API test suite that runs on every PR, validates contracts, and catches breakages before they ship. Not a Postman collection. **A real test suite in your repo.**
WHAT'S INCLUDED
- API test project in Playwright APIRequest, RestAssured, or pytest+httpx
- Auth flow (token, OAuth, session) configured once
- Happy-path tests for your top endpoints
- Error-contract tests (4xx, 5xx, validation)
- GitHub Actions or GitLab CI integration
- *EADME + run guide
WHY ME
Six years on SaaS teams. Built API test layers that run in under 2 minutes on every PR. 45-min CI cut to 15 min including API tests. I do not deliver a Postman folder you abandon in 30 days. I deliver tests your team runs every day.
MESSAGE ME FIRST
Send your API docs (OpenAPI, GraphQL schema, or a sample endpoint). One reply: yes I can help, or no and why. No pitch.
Testing application:
API
Development technology:
JavaScript
•
Node.js
•
TypeScript
Device:
Other
My Portfolio
FAQ
Why code-first tests instead of Postman?
Postman collections die at month two. Nobody runs them in CI consistently, nobody version-controls them well, nobody onboards juniors on them. Code-first tests live next to your app code, run on every PR, and survive team turnover.
Which tool do you use?
Default: Playwright APIRequest if your team already uses Playwright, RestAssured for Java teams, pytest+httpx for Python teams, Hurl for tooling-light teams. I pick based on your stack on the first message. Same architecture, different syntax.
Do you support GraphQL?
Yes. GraphQL is just HTTP POST with a structured body. Schema validation matters more than for REST. Premium includes it. Standard handles GraphQL endpoints but not schema diffing.
What about authentication?
Token, OAuth (client credentials, authorization code, refresh), session cookies, mTLS, API keys all supported. Auth runs once per test session in a setup hook. Tests reuse the token. This is what makes API tests fast.
Will the tests run against production?
No. API tests target staging or a dedicated test environment by default. Production smoke tests are a separate, narrow set with read-only endpoints, available as an extra.
Can your tests catch breaking changes?
Yes, that is half the point. Schema validation (Premium) compares the actual response shape to your OpenAPI or GraphQL schema. If a field changes type or disappears, the test fails before frontend does.
How fast do the tests run?
Well-architected API suites run in under 2 minutes for 30 to 50 endpoints. The bottleneck is usually auth setup, not request speed. I configure auth so it runs once per session, not per test.
What if my API has no documentation?
That is fine. I read sample requests and responses, infer the contract, and document it as I write tests. You get the test suite AND a usable contract sketch you did not have before.
Will the suite cover edge cases?
Standard covers happy paths and the obvious 4xx/5xx contracts. Premium adds edge cases: rate limits, pagination, sort orders, search corner cases, optimistic concurrency. We agree the edge-case list before I start writing.
Does this work with microservices?
Yes. Each service gets its own test directory. Cross-service tests live in a separate suite that runs on a longer schedule (nightly, not every PR). I structure the repo so this is the default, not an afterthought.
