In REST Assured, which method is used to validate HTTP response status codes?

In REST Assured, which method is used to validate HTTP response status codes?

• A. checkStatus()
• B. assertThat()
• C. validateResponse()
• D. responseStatus()

Answer: (B)

The method used to validate HTTP response status codes in REST Assured is assertThat(). This method is part of the fluent interface provided by REST Assured, which allows for a more readable and expressive way to write tests. By using assertThat(), you can chain together various assertions to validate different aspects of the response, including the status code. For example, you can use assertThat() in conjunction with the statusCode() matcher to check if the response status code is what you expect. This approach promotes clarity in your test assertions, making it easier to understand the intent behind each validation. In contrast, the other options do not represent valid methods in REST Assured for checking HTTP response status codes. Using assertThat() aligns with the overall design philosophy of REST Assured, which is to provide a clear and concise way to formulate expectations about RESTful services.

The method used to validate HTTP response status codes in REST Assured is assertThat(). This method is part of the fluent interface provided by REST Assured, which allows for a more readable and expressive way to write tests. By using assertThat(), you can chain together various assertions to validate different aspects of the response, including the status code.

For example, you can use assertThat() in conjunction with the statusCode() matcher to check if the response status code is what you expect. This approach promotes clarity in your test assertions, making it easier to understand the intent behind each validation.

In contrast, the other options do not represent valid methods in REST Assured for checking HTTP response status codes. Using assertThat() aligns with the overall design philosophy of REST Assured, which is to provide a clear and concise way to formulate expectations about RESTful services.