REST Assured Interview Questions

How do you validate a nested JSON response in REST Assured?

How do you chain API requests (use a response value in the next request)?

extract() the value from the first response and pass it into the next request.

How do you avoid repeating headers and base config in REST Assured?

Build a RequestSpecification (base URI, path, content type, auth, logging) and a ResponseSpecification (status, content type, time budget) once, then reuse them in every test.

How do you serialise and deserialise payloads with POJOs?

Pass a POJO as the body and REST Assured serialises it with Jackson; call .as(Order.class) to deserialise the response into a typed object you can assert on.

How do you extract a value and chain it into the next request?

Use extract().path() or extract().jsonPath() to pull the id or token out of the response, store it in a variable, then use it in the next given().

How do you test a multipart file upload with REST Assured?

Use multiPart() with the file plus any form fields, set the content type to multipart/form-data, and assert both the response and that the stored document can be fetched back.

How do you validate deeply nested JSON without a POJO?

Use GPath through body() with Hamcrest matchers, or extract a JsonPath and assert on collections — findAll, collect and sum handle nesting cleanly.

What is given when then syntax, and why does it matter in REST Assured?

given when then syntax is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply given when then syntax in a production REST Assured project?

Apply given when then syntax through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is request specifications, and why does it matter in REST Assured?

request specifications is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply request specifications in a production REST Assured project?

Apply request specifications through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is response specifications, and why does it matter in REST Assured?

response specifications is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply response specifications in a production REST Assured project?

Apply response specifications through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is base URI configuration, and why does it matter in REST Assured?

base URI configuration is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply base URI configuration in a production REST Assured project?

Apply base URI configuration through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is path parameters, and why does it matter in REST Assured?

path parameters is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply path parameters in a production REST Assured project?

Apply path parameters through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is query parameters, and why does it matter in REST Assured?

query parameters is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply query parameters in a production REST Assured project?

Apply query parameters through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is headers and cookies, and why does it matter in REST Assured?

headers and cookies is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply headers and cookies in a production REST Assured project?

Apply headers and cookies through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is JSON serialization, and why does it matter in REST Assured?

JSON serialization is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply JSON serialization in a production REST Assured project?

Apply JSON serialization through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is JSON deserialization, and why does it matter in REST Assured?

JSON deserialization is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply JSON deserialization in a production REST Assured project?

Apply JSON deserialization through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is POJOs, and why does it matter in REST Assured?

POJOs is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply POJOs in a production REST Assured project?

Apply POJOs through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is JSONPath, and why does it matter in REST Assured?

JSONPath is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply JSONPath in a production REST Assured project?

Apply JSONPath through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is XMLPath, and why does it matter in REST Assured?

XMLPath is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply XMLPath in a production REST Assured project?

Apply XMLPath through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is schema validation, and why does it matter in REST Assured?

schema validation is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply schema validation in a production REST Assured project?

Apply schema validation through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is authentication, and why does it matter in REST Assured?

authentication is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply authentication in a production REST Assured project?

Apply authentication through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is filters, and why does it matter in REST Assured?

filters is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply filters in a production REST Assured project?

Apply filters through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is logging, and why does it matter in REST Assured?

logging is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply logging in a production REST Assured project?

Apply logging through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is multipart uploads, and why does it matter in REST Assured?

multipart uploads is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply multipart uploads in a production REST Assured project?

Apply multipart uploads through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is file downloads, and why does it matter in REST Assured?

file downloads is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply file downloads in a production REST Assured project?

Apply file downloads through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is session handling, and why does it matter in REST Assured?

session handling is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply session handling in a production REST Assured project?

Apply session handling through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is response time assertions, and why does it matter in REST Assured?

response time assertions is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply response time assertions in a production REST Assured project?

Apply response time assertions through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is custom matchers, and why does it matter in REST Assured?

custom matchers is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply custom matchers in a production REST Assured project?

Apply custom matchers through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is object mappers, and why does it matter in REST Assured?

object mappers is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply object mappers in a production REST Assured project?

Apply object mappers through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is parallel execution, and why does it matter in REST Assured?

parallel execution is a core REST Assured concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply parallel execution in a production REST Assured project?

Apply parallel execution through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.