Project Number Date
Kafka DB API Testing live(dev) a0b6f62e-3107-4d69-a080-7c50b94ec999 06 Mar 2022, 20:41

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
API-KAFKA-DB-Examples - Workflow 35 0 0 0 0 35 8 0 8 7.301 Passed
Feature API-KAFKA-DB-Examples - Workflow
0.000
Before io.virtualan.cucumblan.core.BaseStepDefinition.before(io.cucumber.java.Scenario) 0.270
Before io.virtualan.cucumblan.core.DBBaseStepDefinition.before(io.cucumber.java.Scenario) 0.009
Before io.virtualan.cucumblan.core.MsgBaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Given provided all the feature level parameters from file 0.000
Tags: @pet
5.325
Before io.virtualan.cucumblan.core.BaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Before io.virtualan.cucumblan.core.DBBaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Before io.virtualan.cucumblan.core.MsgBaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Given as a user perform message Validate pet Response action 0.000
When send inline message details for event TEST on pet with type JSON 0.175
{
"category": {
"id": 100,
"name": "string"
},
"id": 100,
"name": "doggie",
"photoUrls": [
"string"
],
"status": "available",
"tags": [
{
"id": 0,
"name": "string"
}
]
}

JSONMessage{type='JSON', id=100, body={"category": {"id": 100,"name": "string"},"id": 100,"name": "doggie","photoUrls": ["string"],"status": "available","tags": [{"id": 0,"name": "string"}]}}

Then verify-by-elements contains pet information for event TEST contains 100 on pet with type JSON 5.130
name doggie
id i~100
{"category": {"id": 100,"name": "string"},"id": 100,"name": "doggie","photoUrls": ["string"],"status": "available","tags": [{"id": 0,"name": "string"}]}
Then verify details for event TEST contains 100 on pet with type JSON 0.019
id,name, category/id:name,status
i~100,doggie,i~100:string,available
[{
    "id": 100,
    "name": "doggie",
    "category": {
        "id": 100,
        "name": "string"
    },
    "status": "available"
}]
{
    "photoUrls": ["string"],
    "name": "doggie",
    "id": 100,
    "category": {
        "name": "string",
        "id": 100
    },
    "status": "available",
    "tags": [{
        "name": "string",
        "id": 0
    }]
}
Tags: @pet
1.617
Before io.virtualan.cucumblan.core.BaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Before io.virtualan.cucumblan.core.DBBaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Before io.virtualan.cucumblan.core.MsgBaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Given a user perform a api action 0.000
And add the 1000 value of the key as petId 0.000
And add request with given header params 0.053
contentType application/json
When a user get application/json in /api/pets/[petId] resource on pet 0.965
{
    "AcceptContentType": "application/json",
    "resource": "https://live.virtualandemo.com/api/pets/1000",
    "context": {"petId": "1000"},
    "url": "https://live.virtualandemo.com"
}
Then the status code is 200 0.106
{
    "STATUS_CODE": "200",
    "petId": "1000"
}
And verify api response csvson includes in the response 0.001
id,name, category/id:name,status
i~1000,doggie,i~1000:Rocky,available
[{"id":1000,"name":"doggie","category":{"id":1000,"name":"Rocky"},"status":"available"}]
{"photoUrls":["null"],"name":"doggie","id":1000,"category":{"name":"Rocky","id":1000},"type":"DOGS","tags":[{"name":"Dogs","id":0}],"status":"available"}
And verify across response includes following in the response 0.487
name doggie
{
  "id": 1000,
  "category": {
    "id": 1000,
    "name": "Rocky"
  },
  "name": "doggie",
  "type": "DOGS",
  "photoUrls": [
    "null"
  ],
  "tags": [
    {
      "id": 0,
      "name": "Dogs"
    }
  ],
  "status": "available"
}
Tags: @pet
0.151
Before io.virtualan.cucumblan.core.BaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Before io.virtualan.cucumblan.core.DBBaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Before io.virtualan.cucumblan.core.MsgBaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Given a user perform a api action 0.000
And add the grey value of the key as tag 0.000
And add request with given query params 0.006
tags [tag]
And add request with given header params 0.000
contentType application/json
When a user get application/json in /api/pets/findByTags resource on pet 0.137
{
    "AcceptContentType": "application/json",
    "resource": "https://live.virtualandemo.com/api/pets/findByTags",
    "context": {
        "STATUS_CODE": "200",
        "petId": "1000",
        "tag": "grey"
    },
    "url": "https://live.virtualandemo.com"
}
Then the status code is 200 0.001
{
    "STATUS_CODE": "200",
    "petId": "1000",
    "tag": "grey"
}
And verify-all /api/pets/findByTags api includes following in the response 0.003
photoUrls[0] string
name Butch
id i~201
category.name Bulldog
category.id i~200
status available
tags[0].name grey
tags[0].id i~201
{
  "category": {
    "id": 200,
    "name": "Bulldog"
  },
  "id": 201,
  "name": "Butch",
  "photoUrls": [
    "string"
  ],
  "status": "available",
  "tags": [
    {
      "id": 201,
      "name": "grey"
    }
  ]
}
Tags: @pet
0.176
Before io.virtualan.cucumblan.core.BaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Before io.virtualan.cucumblan.core.DBBaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Before io.virtualan.cucumblan.core.MsgBaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Given a user perform a api action 0.000
And add request with given header params 0.001
contentType application/json
And create api with given input 0.000
photoUrls[0] string
name doggie
id i~100
category.name string
category.id i~100
status available
tags[0].name string
tags[0].id i~0
{
    "photoUrls": ["string"],
    "name": "doggie",
    "id": 100,
    "category": {
        "name": "string",
        "id": 100
    },
    "status": "available",
    "tags": [{
        "name": "string",
        "id": 0
    }]
}
When a user post application/json in /api/pets resource on pet 0.166
{
    "AcceptContentType": "application/json",
    "resource": "https://live.virtualandemo.com/api/pets",
    "context": {
        "STATUS_CODE": "200",
        "petId": "1000",
        "tag": "grey"
    },
    "url": "https://live.virtualandemo.com"
}
Then the status code is 200 0.000
{
    "STATUS_CODE": "200",
    "petId": "1000",
    "tag": "grey"
}
And verify-all /api/pets api includes following in the response 0.003
photoUrls[0] string
name doggie
id i~100
category.name string
category.id i~100
status available
tags[0].name string
tags[0].id i~0
{
  "category": {
    "id": 100,
    "name": "string"
  },
  "id": 100,
  "name": "doggie",
  "photoUrls": [
    "string"
  ],
  "status": "available",
  "tags": [
    {
      "id": 0,
      "name": "string"
    }
  ]
}
And verify-by-elements contains pet information for event TEST contains 100 on pet with type JSON 0.000
name doggie
id i~100
{"category": {"id": 100,"name": "string"},"id": 100,"name": "doggie","photoUrls": ["string"],"status": "available","tags": [{"id": 0,"name": "string"}]}
And verify details for event TEST contains 100 on pet with type JSON 0.000
id,name, category/id:name,status
i~100,doggie,i~100:string,available
[{
    "id": 100,
    "name": "doggie",
    "category": {
        "id": 100,
        "name": "string"
    },
    "status": "available"
}]
{
    "photoUrls": ["string"],
    "name": "doggie",
    "id": 100,
    "category": {
        "name": "string",
        "id": 100
    },
    "status": "available",
    "tags": [{
        "name": "string",
        "id": 0
    }]
}
Tags: @employee
0.019
Before io.virtualan.cucumblan.core.BaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Before io.virtualan.cucumblan.core.DBBaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Before io.virtualan.cucumblan.core.MsgBaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Given as a user perform sql query action 0.000
And create variable empId as key and 1 as value 0.000
When execute DDL for the given sql details on the on employee 0.019
create table employees (emp_no int, birth_date date,first_name VARCHAR(50),last_name VARCHAR(50), gender VARCHAR(50),hire_date date)
Tags: @employee
0.000
Before io.virtualan.cucumblan.core.BaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Before io.virtualan.cucumblan.core.DBBaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Before io.virtualan.cucumblan.core.MsgBaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Given as a user perform sql query action 0.000
When execute INSERT for the given sql details on the on employee 0.000
insert into employees (emp_no,birth_date,first_name,last_name, gender,hire_date) values ([empId], DATE '1983-11-17','Danny', 'Ray', 'Male',DATE '2012-03-24')
Tags: @employee
0.008
Before io.virtualan.cucumblan.core.BaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Before io.virtualan.cucumblan.core.DBBaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Before io.virtualan.cucumblan.core.MsgBaseStepDefinition.before(io.cucumber.java.Scenario) 0.000
Given as a user perform sql query action 0.000
When read details on the given query on employee 0.007
select emp_no, to_char(birth_date, 'YYYY-mm-DD') birth_date ,first_name,last_name, gender,to_char(hire_date , 'YYYY-mm-DD') hire_date from employees where emp_no = [empId]
{
    "resource": "employee",
    "sql": "select emp_no, to_char(birth_date, 'YYYY-mm-DD') birth_date ,first_name,last_name, gender,to_char(hire_date , 'YYYY-mm-DD') hire_date from employees where emp_no = 1"
}
[{"EMP_NO":1,"BIRTH_DATE":"1983-11-17","FIRST_NAME":"Danny","LAST_NAME":"Ray","GENDER":"Male","HIRE_DATE":"2012-03-24"}]
Then validate information on the given details on employee 0.000
EMP_NO,BIRTH_DATE,FIRST_NAME,LAST_NAME,GENDER,HIRE_DATE
i~[empId],1983-11-17,Danny,Ray,Male,2012-03-24
[{
    "HIRE_DATE": "2012-03-24",
    "BIRTH_DATE": "1983-11-17",
    "EMP_NO": 1,
    "GENDER": "Male",
    "LAST_NAME": "Ray",
    "FIRST_NAME": "Danny"
}]
[{
    "EMP_NO": 1,
    "BIRTH_DATE": "1983-11-17",
    "FIRST_NAME": "Danny",
    "LAST_NAME": "Ray",
    "GENDER": "Male",
    "HIRE_DATE": "2012-03-24"
}]