roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Prepare for REST Assured interview questions on testing HTTP APIs from a Java or Kotlin suite. Covers the given/when/then DSL, reusable specs, body assertions, auth, filters and suite design.
223 of 223 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 223 new. 0 cut, outside your plan.
REST Assured comes up in SDET and QA automation loops, and in Java or Kotlin backend loops where developers own their API tests. It usually arrives as a short coding exercise: call an endpoint, assert on a nested field, reuse the id it returned in the next request. A conversation about a suite you have maintained follows, and from middle level up the interviewer hands you a test and asks why it passes against a broken service.
Those questions lean on the library's defaults rather than its syntax. Why does auth().basic(...) send no credentials until the server answers 401, and what does preemptive() change? When you attach a specification, which of its settings overwrite yours and which are added to them? Why can a JSON decimal fail an equalTo check written with a double literal? A junior answer writes the chain correctly. A senior answer says what a given then() block actually verified, how a static default set by one test class leaks into the next, and how a large suite that fails for reasons nobody trusts is made reliable again.
The plan opens on HTTP rather than on the library, because most of the DSL is a way of stating HTTP facts. Method and status semantics and the status codes an API contract chooses are what a negative test asserts. The given/when/then chain follows as one complete test, so every later module has a place in it to deepen.
The middle of the plan follows that chain from the request to the response. Request setup decides where a call lands and what it carries, and reusable specifications lift that setup out of each test, together with the merge rules that decide which value wins. On the response side, Hamcrest comes first because every body(...) expectation takes one of its matchers; the response API then adds paths, extractors and header checks. JSON Schema sits before payload binding for a similar reason: a schema assertion is only as useful as your reading of the schema it loads.
Credentials come once the chain is whole. The HTTP authentication schemes are taught as protocol before the calls that install them, since knowing when a server issues a challenge is what explains the preemptive option. Filters and logging cut across every request, so they wait until there are requests to intercept.
The last stretch is about running hundreds of tests rather than one. It starts with what an API case should assert and with waiting on a state that means ready instead of a fixed sleep, because REST Assured offers no polling of its own. Suite upkeep and the library's own client configuration and runner handoff close it.
For a first automation role, get the chain and the response side solid before anything else: narrow level to the range you are interviewing at and raise importance to must know, because junior questions are mostly about writing a correct test. If you have spent a few years on an existing suite, put your hours into specifications, auth and filters, where questions arrive as a failing or falsely passing test to diagnose. Asked to design an API test framework in the interview? Switch study order to by topics and work through the last module in full. REST Assured runs inside a test runner, but this plan does not teach JUnit or TestNG themselves. The [Java SDET roadmap](/roadmaps/java-sdet) carries the runner, the language and the rest of that loop. For Postman collections, Karate's feature files, stub servers or consumer-driven contracts, the [API Testing roadmap](/roadmaps/api-testing) sets this library beside the alternatives.
For a first automation role, get the chain and the response side solid before anything else: narrow level to the range you are interviewing at and raise importance to must know, because junior questions are mostly about writing a correct test. If you have spent a few years on an existing suite, put your hours into specifications, auth and filters, where questions arrive as a failing or falsely passing test to diagnose. Asked to design an API test framework in the interview? Switch study order to by topics and work through the last module in full.
REST Assured runs inside a test runner, but this plan does not teach JUnit or TestNG themselves. The Java SDET roadmap carries the runner, the language and the rest of that loop. For Postman collections, Karate's feature files, stub servers or consumer-driven contracts, the API Testing roadmap sets this library beside the alternatives.