test(cucumber_get_post): use datatable instead of chaining And

Author: romainVanhee

src/test/java/feature/StepDefinition.java

@@ -3,11 +3,14 @@
 import com.fasterxml.jackson.databind.JsonNode;
 import com.fasterxml.jackson.databind.ObjectMapper;
 import com.xpeho.spring_boot_java_random_user.domain.entities.UserRequest;
+import io.cucumber.datatable.DataTable;
 import io.cucumber.java.en.And;
 import io.cucumber.java.en.Given;
 import io.cucumber.java.en.Then;
 import io.cucumber.java.en.When;
 
+import java.util.List;
+
 import static org.junit.jupiter.api.Assertions.assertEquals;
 
 public class StepDefinition extends SpringIntegrationTest {
@@ -39,16 +42,13 @@ public void theResponseStatusShouldBe(int expectedStatus) {
         assertEquals(expectedStatus, latestResponse.getStatusCode().value());
     }
 
-    @And("the response should contain the created user id {long}")
-    public void theResponseShouldContainTheCreatedUserId(long expectedId) throws Exception {
-        JsonNode body = objectMapper.readTree(latestResponse.getBody());
-        assertEquals(expectedId, body.get("id").asLong());
-    }
-
-    @And("the response should contain the firstname {string}")
-    public void theResponseShouldContainTheFirstname(String expectedFirstname) throws Exception {
+    @And("the user profile")
+    public void theUserProfile(DataTable table) throws Exception{
         JsonNode body = objectMapper.readTree(latestResponse.getBody());
-        assertEquals(expectedFirstname, body.get("firstname").asText());
+        List<List<String>> rows = table.asLists(String.class);
+        for (List<String> row : rows) {
+            assertEquals(row.get(1), body.get(row.get(0)).asText());
+        }
     }
 
     @When("the client call to GET \\/random-users\\/{int}")

src/test/resources/features/create_user.feature

@@ -4,5 +4,6 @@ Feature: Create user endpoint
     Given a valid user payload for creation
     When the client call to POST /random-users
     Then the response status should be 201
-    And the response should contain the created user id 1
-    And the response should contain the firstname "Emma"
+    And the user profile
+      | id        | 1    |
+      | firstname | Emma |

src/test/resources/features/get_user.feature

@@ -6,7 +6,9 @@ Feature: Get user endpoint
     Then the response status should be 201
     When the client call to GET /random-users/1
     Then the response status should be 200
-    And the response should contain the firstname "Emma"
+    And the user profile
+      | id        | 1    |
+      | firstname | Emma |
 
   Scenario: Get a user that does not exist
     When the client call to GET /random-users/999