Back to challenges
API TestingAPIIntermediate
Search API
?
Scenario
Your interview prompt
A `GET /articles/search` endpoint accepts `q`, `tags`, `authorId`, `page`, and `sort`. It returns ranked results, highlighted snippets, total count, and suggestions for no-result queries.
List flows, risks, edge cases, data conditions, UX, security, API/backend, and performance concerns.
Tip: a stronger answer usually mixes happy path, negative cases, state changes, data, backend, UX, accessibility, and risk.
How to structure your answer
Happy pathNegative casesData rulesSecurity/API risksUX/performance