Project Number Date
ApolloFullRunnerReport apollo-test-2.162 18 wrz 2021, 06:45

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
API Transport 308 0 0 0 0 308 69 0 69 6m 48s 832ms Passed
Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 313ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 2s 445ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 676ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-semmelrock" and get token and expect status "200" 380ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 2s 103ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 864ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 280ms
When Wait "15" seconds 15s
And Get updated transports in "15" time for api version "v1" and expect status "404" 176ms
And Check if the updated transports response is empty 011ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 840ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 229ms
And Check if the updated transports response contains created transport 007ms
After Hooks.deleteTransportAfterApiTest() 646ms
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 288ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 1s 136ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Nieprawidłowe wartości w polu orderInTransport" 005ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 279ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 903ms
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) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 307ms
When Create transport by invalid JSON file "CREATE_LOAD_STEP_TYPE_NAME_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 860ms
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" 005ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 274ms
When Create transport by invalid JSON file "CREATE_LOAD_STEP_TYPE_NAME_EMPTY" as "super-admin-piast" for api version "v1" 863ms
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) 012ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 285ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 1s 073ms
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) 004ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 305ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 852ms
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" 289ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_COUNTRY_CODE_INCORRECT" as "super-admin-piast" for api version "v1" 1s 125ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny kod kraju" 006ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 278ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_EMPTY" as "super-admin-piast" for api version "v1" 852ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny adres" 006ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 271ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_RECIPIENT_EMPTY" as "super-admin-piast" for api version "v1" 860ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny adres" 008ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 275ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_POSTAL_EMPTY" as "super-admin-piast" for api version "v1" 906ms
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" 310ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_CITY_EMPTY" as "super-admin-piast" for api version "v1" 888ms
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" 280ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_STREET_EMPTY" as "super-admin-piast" for api version "v1" 850ms
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" 276ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 1s 072ms
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" 301ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 876ms
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) 009ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 304ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_EMPTY" as "super-admin-piast" for api version "v1" 1s 061ms
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" 300ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_EMPTY" as "super-admin-piast" for api version "v1" 784ms
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" 007ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 266ms
When Create transport by invalid JSON file "CREATE_LOAD_QUANTITY_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 853ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł quantity musi być poprawną liczbą" 005ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 282ms
When Create transport by invalid JSON file "CREATE_LOAD_VOLUME_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 878ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł volume musi być poprawną liczbą" 006ms
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 329ms
When Create transport by invalid JSON file "CREATE_LOAD_WEIGHT_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 847ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł weight musi być poprawną liczbą" 006ms
Before Hooks.showScenarioName(Scenario) 011ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 282ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 831ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł company.id musi być liczbą całkowitą" 006ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 275ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 801ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł warehouse.id musi być liczbą całkowitą" 006ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 272ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 803ms
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) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 263ms
When Create transport by invalid JSON file "CREATE_LOAD_MIN_ADVICE_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 904ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł minAdviceDate musi być poprawną datą" 032ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 299ms
When Create transport by invalid JSON file "CREATE_LOAD_MAX_ADVICE_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 874ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł maxAdviceDate musi być poprawną datą" 005ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 268ms
When Create transport by invalid JSON file "CREATE_LOAD_ARRIVAL_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 803ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł arrivalDate musi być poprawną datą" 007ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 277ms
When Create transport by invalid JSON file "CREATE_LOAD_STEP_PACKAGE_TYPES_PACKAGE_TYPE_NAME_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 805ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Nie znaleźliśmy opakowania o nazwie" 005ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 267ms
When Create transport by invalid JSON file "CREATE_LOAD_NO_ADDRESS_AND_WAREHOUSE_IN_ONE_STEP" as "super-admin-piast" for api version "v1" 799ms
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" 006ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 295ms
When Create transport by invalid JSON file "CREATE_DELIVERY_NO_WAREHOUSE_IN_ONLY_STEP" as "super-admin-piast" for api version "v1" 669ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Magazyn jest wymagany w zleceniu jednoetapowym" 004ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 305ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 833ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 586ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 297ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 946ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 558ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 284ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 824ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 547ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 296ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 822ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 557ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 275ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 812ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 563ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 285ms
And Set token of apiUsername "super-admin-piast" 294ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 159ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 716ms
Then Login as "super-admin-piast" 6s 699ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 411ms
After Hooks.deleteTransportAfterApiTest() 643ms
After Hooks.rollbackSettings() 135ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 283ms
And Set token of apiUsername "super-admin-piast" 286ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 147ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 778ms
Then Login as "super-admin-piast" 2s 445ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 410ms
After Hooks.deleteTransportAfterApiTest() 652ms
After Hooks.rollbackSettings() 136ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 295ms
And Set token of apiUsername "super-admin-piast" 296ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 128ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 729ms
Then Login as "super-admin-piast" 2s 520ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 376ms
After Hooks.deleteTransportAfterApiTest() 671ms
After Hooks.rollbackSettings() 104ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 294ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 766ms
And Find active transports for api version "v1" and expect status "200" 290ms
Then Check if active transports contains created transport 006ms
After Hooks.deleteTransportAfterApiTest() 616ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 310ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 140ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 185ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 305ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 923ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 755ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 662ms
After Hooks.rollbackSettings() 133ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 295ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 149ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 145ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 296ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 764ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 911ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 635ms
After Hooks.rollbackSettings() 127ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 290ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 143ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 152ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 294ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 724ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 383ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 637ms
After Hooks.rollbackSettings() 136ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 297ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 135ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 173ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 281ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 694ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 033ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 640ms
After Hooks.rollbackSettings() 137ms
@deleteApiTransportsAfterTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 869ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 145ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 136ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" with erp identifier "5345467712" 1s 700ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" with erp identifier "5345467712" 1s 814ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_WITH_FILLED_ERP_IDENTIFIER" as "super-admin-piast" for api version "v1" by identifier "5345467712" 390ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 353ms
After Hooks.rollbackSettings() 098ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 286ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 161ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 303ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 776ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 227ms
After Hooks.deleteTransportAfterApiTest() 615ms
After Hooks.rollbackSettings() 134ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 277ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 152ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 5s 338ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 745ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 009ms
And Show all transport types 1s 173ms
And Click button advice in transport table "DELIVERY" 203ms
And Set advice window in schedule 3s 613ms
And Fill advice form 13s 588ms
And Click advice save button and wait for advice form to disappear 33s 912ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 826ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 466ms
And Go to transport details "DELIVERY" 2s 931ms
And Expand advice panel 561ms
Then Check are transport values equals 2s 379ms
After Hooks.deleteTransportAfterApiTest() 875ms
After Hooks.rollbackSettings() 139ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 4s 101ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 576ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "liczbowy CF" value "213" with expect status "200" 2s 118ms
After Hooks.deleteTransportAfterApiTest() 853ms
After Hooks.deleteCustomFieldAfterTest() 2s 499ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 4s 324ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 448ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "liczbowy CF" value "-3" with expect status "200" 2s 052ms
After Hooks.deleteTransportAfterApiTest() 870ms
After Hooks.deleteCustomFieldAfterTest() 2s 512ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 4s 047ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 385ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "liczbowy CF" value "4.5" with expect status "200" 2s 066ms
After Hooks.deleteTransportAfterApiTest() 831ms
After Hooks.deleteCustomFieldAfterTest() 2s 454ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 3s 930ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 367ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "liczbowy CF" value "yolo" with expect status "422" 642ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 384ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 3s 919ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 422ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "liczbowy CF" value "dd.MM.yyyy HH:mm" with expect status "422" 616ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 428ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 3s 892ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 359ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "liczbowy CF" value "11:00" with expect status "422" 605ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 398ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 3s 923ms
And Create custom field with "CREATE_LOADING_SELECT_CFD" by "super-admin-semmelrock" 2s 659ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "selektowy CF" value "opcja 1" with expect status "200" 2s 108ms
After Hooks.deleteTransportAfterApiTest() 890ms
After Hooks.deleteCustomFieldAfterTest() 2s 399ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 002ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 3s 978ms
And Create custom field with "CREATE_LOADING_SELECT_CFD" by "super-admin-semmelrock" 2s 589ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "selektowy CF" value "opcja 2" with expect status "200" 2s 056ms
After Hooks.deleteTransportAfterApiTest() 811ms
After Hooks.deleteCustomFieldAfterTest() 2s 388ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 3s 940ms
And Create custom field with "CREATE_LOADING_SELECT_CFD" by "super-admin-semmelrock" 2s 512ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "selektowy CF" value "opcja ktorej nie ma" with expect status "422" 629ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 394ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 3s 937ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 347ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "datowy CF" value "21.12.2026 12:00" with expect status "200" 2s 102ms
After Hooks.deleteTransportAfterApiTest() 820ms
After Hooks.deleteCustomFieldAfterTest() 2s 381ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 4s 084ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 346ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "datowy CF" value "13.04.2023" with expect status "200" 2s 156ms
After Hooks.deleteTransportAfterApiTest() 854ms
After Hooks.deleteCustomFieldAfterTest() 2s 448ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 4s 014ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 306ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "datowy CF" value "2023-09-29T18:46:19Z" with expect status "200" 2s 027ms
After Hooks.deleteTransportAfterApiTest() 833ms
After Hooks.deleteCustomFieldAfterTest() 2s 389ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 4s 086ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 294ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "datowy CF" value "41.12.2026 12:00" with expect status "422" 614ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 409ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 3s 932ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 324ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "datowy CF" value "11:56" with expect status "422" 617ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 322ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 3s 814ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 269ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "datowy CF" value "elo mordeczko" with expect status "422" 627ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 443ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 3s 853ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 335ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "data i godz CF" value "21.12.2026 12:00" with expect status "200" 2s 135ms
After Hooks.deleteTransportAfterApiTest() 840ms
After Hooks.deleteCustomFieldAfterTest() 2s 560ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 4s 139ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 288ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "data i godz CF" value "2023-09-29T18:46:19Z" with expect status "200" 2s 046ms
After Hooks.deleteTransportAfterApiTest() 817ms
After Hooks.deleteCustomFieldAfterTest() 2s 309ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 3s 903ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 274ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "data i godz CF" value "12.12.2022" with expect status "422" 598ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 352ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 3s 901ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 268ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "data i godz CF" value "13:31" with expect status "422" 643ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 360ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 3s 832ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 276ms
When Create transport by JSON file "CREATE_LOADING_WITH_CF" as "super-admin-semmelrock" for api version "v1" and edit CF "data i godz CF" value "kitku" with expect status "422" 603ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 301ms
@deleteTransportAfterApiTest @TmsLink=A-8215
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-semmelrock" 258ms
And Get free time windows on tomorrow with "super-admin-semmelrock" "semmelrock" "LOADING" "Magazyn Gdynia" by API 1s 067ms
And Create transport "CREATE_LOADING" by JSON file as "super-admin-semmelrock" on first free time window slot 1s 902ms
When Login as "super-admin-semmelrock" 3s 763ms
And Go to "TRANSPORT_TABLE" 533ms
And Show all transport types 1s 184ms
And Go to transport details "LOADING" 2s 778ms
And Check are transport values equals 000ms
And Close transport details 15s 223ms
And Go to "WAREHOUSE_TAB" 820ms
And Go to next day in schedule 1s 137ms
And Select warehouse "Magazyn Gdynia" 1s 375ms
And Check if time window is "visible" in selected warehouse 085ms
Then Check if time window is visible on proper ramp in schedule 080ms
Then Check if time window starts on proper hour in schedule 327ms
After Hooks.deleteTransportAfterApiTest() 823ms
@deleteTransportAfterTest @TmsLink=A-8208
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-semmelrock" 266ms
And Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" with time window start at "12":"30" 629ms
And Check if response status code equals "422" 000ms
And Check if response message contains "Wybrany początek okna czasowego nie jest zgodny z ustawieniami magazynu. Błąd w węźle timeWindow.start." 005ms
When Login as "semmelrock-admin" 3s 997ms
And Show all transport types 1s 175ms
And Check if transport is "not visible" in table of transports 15s 059ms
And Go to "WAREHOUSE_TAB" 833ms
And Select warehouse "Magazyn Gdynia" 1s 347ms
Then Check if time window is "not visible" in selected warehouse 15s 036ms
After Hooks.deleteTransportAfterTest() 000ms