Project Number Date
ApolloFullRunnerReport apollo-test-2.105 04 sie 2021, 05:16

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@deleteTransportAfterApiTest 69 4 3 0 0 76 11 4 15 2m 7s 359ms Failed
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 004ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 266ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 4s 203ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s 060ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 020ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 295ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 155ms
And Check if the updated transports response is empty 013ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 641ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 322ms
And Check if the updated transports response contains created transport 017ms
After Hooks.deleteTransportAfterApiTest() 765ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 229ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 520ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 620ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 254ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 534ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 599ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 238ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 546ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 582ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 232ms
And Set token of apiUsername "super-admin-piast" 236ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 125ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 046ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 403ms
Then Login as "super-admin-piast" 6s 613ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 395ms
After Hooks.deleteTransportAfterApiTest() 698ms
After Hooks.rollbackSettings() 188ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 253ms
And Set token of apiUsername "super-admin-piast" 244ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 151ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 027ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 433ms
Then Login as "super-admin-piast" 2s 295ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 373ms
After Hooks.deleteTransportAfterApiTest() 603ms
After Hooks.rollbackSettings() 185ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 221ms
And Set token of apiUsername "super-admin-piast" 220ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 130ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 026ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 486ms
Then Login as "super-admin-piast" 2s 462ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 374ms
After Hooks.deleteTransportAfterApiTest() 625ms
After Hooks.rollbackSettings() 095ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 258ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 419ms
And Find active transports for api version "v1" and expect status "200" 268ms
Then Check if active transports contains created transport 008ms
After Hooks.deleteTransportAfterApiTest() 677ms
View Feature API Transport
Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login by Api as "super-admin-piast" and get token and expect status "200" 246ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 394ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 338ms
Then Check if response status code equals "200" 001ms
org.junit.ComparisonFailure: Odpowiedź zawiera kod 404 zamiast 200 expected:<[200]> but was:<[404]>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at CucumberTests.Api.ApiTransportTest.checkIfResponseStatusCodeEquals(ApiTransportTest.java:137)
	at ✽.Check if response status code equals "200"(file:Features/Api/Transport.feature:120)
After Hooks.deleteTransportAfterApiTest() 662ms
View Feature API Transport
Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]
Before Hooks.showScenarioName(Scenario) 002ms
Steps
Given Login by Api as "super-admin-piast" and get token and expect status "200" 243ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 374ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 334ms
Then Check if response status code equals "422" 000ms
org.junit.ComparisonFailure: Odpowiedź zawiera kod 404 zamiast 422 expected:<4[22]> but was:<4[04]>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at CucumberTests.Api.ApiTransportTest.checkIfResponseStatusCodeEquals(ApiTransportTest.java:137)
	at ✽.Check if response status code equals "422"(file:Features/Api/Transport.feature:120)
After Hooks.deleteTransportAfterApiTest() 642ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 271ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 417ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 351ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 706ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 240ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 407ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 035ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 637ms
View Feature API Transport
Scenario Outline Check if custom fields map is correct after creating a transport by Public API [A-7508]
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login by Api as "super-admin-piast" and get token and expect status "200" 252ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 479ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 150ms
java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <404>.

	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallConstructor(CallSiteArray.java:59)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:238)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor78.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.get(RequestSpecificationImpl.groovy:171)
	at io.restassured.internal.RequestSpecificationImpl.get(RequestSpecificationImpl.groovy)
	at CucumberTests.Api.ApiTransportTest.getCustomFieldsListByPublicApi(ApiTransportTest.java:202)
	at CucumberTests.Api.ApiTransportTest.checkIfAPICustomFieldsAreCorrect(ApiTransportTest.java:172)
	at ✽.Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast"(file:Features/Api/Transport.feature:145)
After Hooks.deleteTransportAfterApiTest() 662ms
View Feature API Transport
Scenario Outline Check if it possible to edit transport by API [A-4167]
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 5s 492ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 426ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 2s 564ms
And Show all transport types 1s 181ms
And Click button advice in transport table "DELIVERY" 264ms
And Set advice window in schedule 3s 865ms
And Fill advice form 13s 355ms
And Click advice save button and wait for advice form to disappear 34s 361ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 351ms
And Check if response status code equals "200" 000ms
org.junit.ComparisonFailure: Odpowiedź zawiera kod 404 zamiast 200 expected:<[200]> but was:<[404]>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at CucumberTests.Api.ApiTransportTest.checkIfResponseStatusCodeEquals(ApiTransportTest.java:137)
	at ✽.Check if response status code equals "200"(file:Features/Api/Transport.feature:161)
And Go to "TRANSPORT_TABLE" 000ms
And Go to transport details "DELIVERY" 000ms
Then Check are transport values equals 000ms
After Hooks.deleteTransportAfterApiTest() 801ms