Project Number Date
ApolloFullRunnerReport 2021.AT1.58 13 sie 2021, 02:50

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
API Transport 207 2 7 0 0 216 44 2 46 1m 17s 068ms Failed
Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 146ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 2s 324ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 337ms
@deleteTransportAfterApiTest
Scenario Outline Check if it is possible to create transport by Public API
Before Hooks.showScenarioName(Scenario) 009ms
Steps
Given Login by Api as "super-admin-semmelrock" and get token and expect status "200" 141ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 655ms
Error message 
java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <422>.

	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.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	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.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	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.post(RequestSpecificationImpl.groovy:175)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy)
	at CucumberTests.Api.ApiTransportTest.createTransportByJSONFileForAndExpectStatus(ApiTransportTest.java:43)
	at ✽.Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200"(file:Features/Api/Transport.feature:6)
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 000ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 004ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 132ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 086ms
And Check if the updated transports response is empty 014ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 517ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 121ms
And Check if the updated transports response contains created transport 013ms
After Hooks.deleteTransportAfterApiTest() 130ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 112ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 320ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Nieprawidłowe wartości w polu orderInTransport" 007ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 132ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 225ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Brak wartości w polu orderInTransport, pole jest obowiązkowe" 007ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 125ms
When Create transport by invalid JSON file "CREATE_LOAD_STEP_TYPE_NAME_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 221ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawna wartość w polu stepTypeName. Poprawne wartości to: load, unload" 006ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 112ms
When Create transport by invalid JSON file "CREATE_LOAD_STEP_TYPE_NAME_EMPTY" as "super-admin-piast" for api version "v1" 192ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Brak wartości w polu stepTypeName, pole jest obowiązkowe" 006ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 111ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 258ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Nieprawidłowe wartości w polu orderInTransport" 006ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 104ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 205ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Brak wartości w polu orderInTransport, pole jest obowiązkowe" 006ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 103ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_COUNTRY_CODE_INCORRECT" as "super-admin-piast" for api version "v1" 261ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny kod kraju" 005ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 101ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_EMPTY" as "super-admin-piast" for api version "v1" 206ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny adres" 006ms
Before Hooks.showScenarioName(Scenario) 014ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 101ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_RECIPIENT_EMPTY" as "super-admin-piast" for api version "v1" 196ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny adres" 006ms
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 109ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_POSTAL_EMPTY" as "super-admin-piast" for api version "v1" 209ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny adres" 007ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 119ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_CITY_EMPTY" as "super-admin-piast" for api version "v1" 198ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny adres" 004ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 098ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_STREET_EMPTY" as "super-admin-piast" for api version "v1" 201ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny adres" 006ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 105ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 228ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Nieprawidłowe wartości w polu orderInTransport" 006ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 102ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 214ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Brak wartości w polu orderInTransport, pole jest obowiązkowe" 004ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 101ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_EMPTY" as "super-admin-piast" for api version "v1" 208ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawne dane firmy" 005ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 104ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_EMPTY" as "super-admin-piast" for api version "v1" 170ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "W zleceniu wieloetapowym każdy etap musi mieć uzupełniony magazyn lub adres" 005ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 103ms
When Create transport by invalid JSON file "CREATE_LOAD_QUANTITY_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 164ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł quantity musi być poprawną liczbą" 004ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 107ms
When Create transport by invalid JSON file "CREATE_LOAD_VOLUME_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 175ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł volume musi być poprawną liczbą" 007ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 102ms
When Create transport by invalid JSON file "CREATE_LOAD_WEIGHT_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 173ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł weight musi być poprawną liczbą" 004ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 100ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 165ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł company.id musi być liczbą całkowitą" 005ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 102ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 166ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł warehouse.id musi być liczbą całkowitą" 005ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 103ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 169ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł warehouse.idx musi być liczbą całkowitą" 005ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 109ms
When Create transport by invalid JSON file "CREATE_LOAD_MIN_ADVICE_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 171ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł minAdviceDate musi być poprawną datą" 004ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 102ms
When Create transport by invalid JSON file "CREATE_LOAD_MAX_ADVICE_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 176ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł maxAdviceDate musi być poprawną datą" 006ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 104ms
When Create transport by invalid JSON file "CREATE_LOAD_ARRIVAL_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 163ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł arrivalDate musi być poprawną datą" 005ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 107ms
When Create transport by invalid JSON file "CREATE_LOAD_STEP_PACKAGE_TYPES_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 150ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł stepPackageType.id musi być liczbą całkowitą" 005ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 105ms
When Create transport by invalid JSON file "CREATE_LOAD_NO_ADDRESS_AND_WAREHOUSE_IN_ONE_STEP" as "super-admin-piast" for api version "v1" 172ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "W zleceniu wieloetapowym każdy etap musi mieć uzupełniony magazyn lub adres" 005ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 112ms
When Create transport by invalid JSON file "CREATE_DELIVERY_NO_WAREHOUSE_IN_ONLY_STEP" as "super-admin-piast" for api version "v1" 165ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Magazyn jest wymagany w zleceniu jednoetapowym" 005ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 100ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 408ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 095ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 107ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 469ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 110ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 100ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 362ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 097ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 102ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 403ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 103ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 102ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 362ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 083ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 102ms
And Set token of apiUsername "super-admin-piast" 100ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 1s 023ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 109ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 356ms
Then Login as "super-admin-piast" 2s 543ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 131ms
After Hooks.deleteTransportAfterApiTest() 096ms
After Hooks.rollbackSettings() 079ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 104ms
And Set token of apiUsername "super-admin-piast" 095ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 032ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 021ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 386ms
Then Login as "super-admin-piast" 1s 017ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 151ms
After Hooks.deleteTransportAfterApiTest() 107ms
After Hooks.rollbackSettings() 032ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 097ms
And Set token of apiUsername "super-admin-piast" 105ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 029ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 019ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 358ms
Then Login as "super-admin-piast" 1s 040ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 134ms
After Hooks.deleteTransportAfterApiTest() 095ms
After Hooks.rollbackSettings() 019ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 000ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 098ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 425ms
And Find active transports for api version "v1" and expect status "200" 059ms
Then Check if active transports contains created transport 007ms
After Hooks.deleteTransportAfterApiTest() 087ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 101ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 037ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 026ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 101ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 324ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 491ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 078ms
After Hooks.rollbackSettings() 026ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 098ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 033ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 022ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 103ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 332ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 178ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 076ms
After Hooks.rollbackSettings() 028ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 098ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 032ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 028ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 099ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 340ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 123ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 092ms
After Hooks.rollbackSettings() 024ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 111ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 030ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 025ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 094ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 321ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 007ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 069ms
After Hooks.rollbackSettings() 023ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 000ms
Given Set token of apiUsername "super-admin-piast" 095ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 030ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 024ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 097ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 320ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 049ms
After Hooks.deleteTransportAfterApiTest() 073ms
After Hooks.rollbackSettings() 031ms
@deleteTransportAfterApiTest @rollbackSettings
Scenario Outline Check if it possible to edit transport by API [A-4167]
Before Hooks.showScenarioName(Scenario) 001ms
Steps
Given Set token of apiUsername "super-admin-piast" 103ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 030ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 024ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 110ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 374ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 4s 628ms
And Show all transport types 1s 066ms
And Click button advice in transport table "DELIVERY" 101ms
And Set advice window in schedule 3s 005ms
And Fill advice form 10s 688ms
And Click advice save button and wait for advice form to disappear 10s 207ms
Error message 
org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='save'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.nMoPf6}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 8985c6aef34bc2ee84a41d67573a54de
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:215)
	at Pages.Transport.AdviceFormPage.confirm(AdviceFormPage.java:27)
	at CucumberTests.Transport.AdviceTransport.clickAdviceSaveButtonAndWaitForAdviceFormToDisappear(AdviceTransport.java:179)
	at ✽.Click advice save button and wait for advice form to disappear(file:Features/Api/Transport.feature:167)
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 000ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 000ms
And Go to transport details "DELIVERY" 000ms
And Expand advice panel 000ms
Then Check are transport values equals 000ms
After Hooks.deleteTransportAfterApiTest() 094ms
After Hooks.rollbackSettings() 026ms