REST Assured Tutorial 14 –RequestSpecification – How the request will look like
Introduction
As a part of End to End REST Assured Tutorial, in this post, we will learn about RequestSpecification in Rest Assured. We will learn what, when, and how to use RequestSpecification in Rest Assured.
Prerequisite
I have used below dependency of Rest Assured library for this post:-
|
1 2 3 4 5 6 7 |
<!-- https://mvnrepository.com/artifact/io.rest-assured/rest-assured --> <dependency> <groupId>io.rest-assured</groupId> <artifactId>rest-assured</artifactId> <version>4.3.1</version> <scope>test</scope> </dependency> |
Why RequestSpecification?
Observe the below lines of codes carefully. You will find that we have some common statements in both @Test methods after given() method call.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 |
package RequestSpecificationExamples; import org.testng.annotations.Test; import io.restassured.RestAssured; public class WithoutUsingRequestSpecification { @Test public void getAllBookings() { // Given RestAssured .given() // Common baseURI and basePath .baseUri("https://restful-booker.herokuapp.com") .basePath("/booking") // When .when() // Then .then() .statusLine("HTTP/1.1 200 OK"); } @Test public void getBookingDetailsWithInvalidFirstName() { // Given RestAssured .given() // Common baseURI and basePath .baseUri("https://restful-booker.herokuapp.com") .basePath("/booking") .param("firstName", "Rahul") // When .when() // Then .then() .statusLine("HTTP/1.1 200 OK"); } } |
Above we have only two tests but in real-time you may have many. A group of tests will have some common specifications to create a request. Following the DRY principle is the best way to write clean code. We have repeated common request specifications in both tests which is not a good practice. If we need to modify then we need to make changes every placed used.
To club common request specifications together and put as a common entity, we can use RequestSpecification in Rest Assured. RequestSpecification is an interface that allows you to specify how the request will look like. This interface has readymade methods to define base URL, base path, headers, etc. We need to use given() method of RestAssured class to get a reference for RequestSpecification. Remember RequestSpecification is an interface and we can not create an object of it. RequestSpecificationImpl is its implemented class.
How to use RequestSpecification?
A RequestSpecification with some specifications can be created as below:-
|
1 2 3 |
RequestSpecification requestSpecification = RestAssured.given(); requestSpecification.baseUri("https://restful-booker.herokuapp.com") requestSpecification.basePath("/booking"); |
Or instead of calling RequestSpecification reference multiple times, we can use the builder pattern as below:-
|
1 2 3 4 |
RequestSpecification requestSpecification = RestAssured.given() .baseUri("https://restful-booker.herokuapp.com") .basePath("/booking"); |
We can add a RequestSpecification to a request in multiple ways as shown below:-
|
1 2 3 |
RestAssured.given(requestSpecification) OR RestAssured.given().spec(requestSpecification) |
Example Program
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 |
package RequestSpecificationExamples; import org.testng.annotations.BeforeClass; import org.testng.annotations.Test; import io.restassured.RestAssured; import io.restassured.specification.RequestSpecification; public class WithRequestSpecification { RequestSpecification requestSpecification; @BeforeClass public void setupRequestSpecification() { requestSpecification = RestAssured.given() .baseUri("https://restful-booker.herokuapp.com") .basePath("/booking"); } @Test public void getAllBookings() { // Given RestAssured .given() .spec(requestSpecification) // When .when() // Then .then() .statusLine("HTTP/1.1 200 OK"); } @Test public void getBookingDetailsWithInvalidFirstName() { // Given RestAssured .given(requestSpecification) .param("firstName", "Rahul") // When .when() // Then .then() .statusLine("HTTP/1.1 200 OK"); } } |
There are two methods in RestAssured class to start creating Request specifications:-
- given()
- with()
The return type of both methods is RequestSpecification. There is no difference between the above two methods. The only difference is syntactical. An example code is below:-
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 |
package RequestSpecificationExamples; import io.restassured.RestAssured; import io.restassured.response.Response; import io.restassured.specification.RequestSpecification; public class RequestSpecificationExample { public static void main(String[] args) { // Creating request specification using given() RequestSpecification request1 = RestAssured.given(); // Setting Base URI request1.baseUri("https://restful-booker.herokuapp.com"); // Setting Base Path request1.basePath("/booking"); // Creating request specification using with() RequestSpecification request2 = RestAssured.with(); // Setting Base URI request2.baseUri("https://restful-booker.herokuapp.com"); // Setting Base Path request2.basePath("/ping"); // You can also use builder pattern as below RequestSpecification request3 = RestAssured.with(); request3.baseUri("https://restful-booker.herokuapp.com").basePath("/ping"); } } |
You can download/clone the above sample project from here.
You can subscribe to my YouTube channel RetargetCommon to learn from video tutorials.
If you have any doubt, feel free to comment below.
If you like my posts, please like, comment, share and subscribe.
#ThanksForReading
#HappyLearning
Find all Selenium related posts here, all API manual and automation related posts here, and find frequently asked Java Programs here.
Many other topics you can navigate through the menu.
Thank you but my question is – without the http verbs like get/post how come the above program is running.. is get considered by default?