Project Number Date
ApolloFullRunnerReport apollo-test-2.155 12 wrz 2021, 06:40

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
API Transport 283 0 0 0 0 283 67 0 67 5m 43s 085ms Passed
Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 005ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 268ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 4s 269ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s 052ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-semmelrock" and get token and expect status "200" 254ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 2s 645ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 971ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 256ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 196ms
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" 1s 910ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 280ms
And Check if the updated transports response contains created transport 015ms
After Hooks.deleteTransportAfterApiTest() 694ms
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 247ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 1s 147ms
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" 242ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 864ms
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) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 249ms
When Create transport by invalid JSON file "CREATE_LOAD_STEP_TYPE_NAME_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 843ms
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" 008ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 241ms
When Create transport by invalid JSON file "CREATE_LOAD_STEP_TYPE_NAME_EMPTY" as "super-admin-piast" for api version "v1" 826ms
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" 007ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 237ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 1s 029ms
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) 003ms
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_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 824ms
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" 005ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 234ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_COUNTRY_CODE_INCORRECT" as "super-admin-piast" for api version "v1" 1s 107ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny kod kraju" 006ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 281ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_EMPTY" as "super-admin-piast" for api version "v1" 870ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny adres" 006ms
Before Hooks.showScenarioName(Scenario) 011ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 234ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_RECIPIENT_EMPTY" as "super-admin-piast" for api version "v1" 812ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny adres" 005ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 226ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_POSTAL_EMPTY" as "super-admin-piast" for api version "v1" 815ms
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" 247ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_CITY_EMPTY" as "super-admin-piast" for api version "v1" 833ms
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" 247ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_STREET_EMPTY" as "super-admin-piast" for api version "v1" 800ms
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" 274ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 1s 044ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Nieprawidłowe wartości w polu orderInTransport" 008ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 242ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 805ms
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" 243ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_EMPTY" as "super-admin-piast" for api version "v1" 1s 040ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawne dane firmy" 007ms
Before Hooks.showScenarioName(Scenario) 002ms
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_WAREHOUSE_EMPTY" 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 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" 239ms
When Create transport by invalid JSON file "CREATE_LOAD_QUANTITY_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 817ms
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) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 232ms
When Create transport by invalid JSON file "CREATE_LOAD_VOLUME_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 796ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł volume 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" 235ms
When Create transport by invalid JSON file "CREATE_LOAD_WEIGHT_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 824ms
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) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 240ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 796ms
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" 239ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 766ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł warehouse.id musi być liczbą całkowitą" 007ms
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_IDX_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 770ms
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" 241ms
When Create transport by invalid JSON file "CREATE_LOAD_MIN_ADVICE_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 802ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł minAdviceDate 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" 262ms
When Create transport by invalid JSON file "CREATE_LOAD_MAX_ADVICE_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 865ms
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" 230ms
When Create transport by invalid JSON file "CREATE_LOAD_ARRIVAL_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 790ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł arrivalDate musi być poprawną datą" 006ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 241ms
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" 762ms
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" 238ms
When Create transport by invalid JSON file "CREATE_LOAD_NO_ADDRESS_AND_WAREHOUSE_IN_ONE_STEP" as "super-admin-piast" for api version "v1" 764ms
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" 286ms
When Create transport by invalid JSON file "CREATE_DELIVERY_NO_WAREHOUSE_IN_ONLY_STEP" as "super-admin-piast" for api version "v1" 639ms
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" 233ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 876ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 632ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 259ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 2s 039ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 644ms
@deleteTransportAfterApiTest
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_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 863ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 614ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 235ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 785ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 610ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 002ms
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_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 839ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 589ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 240ms
And Set token of apiUsername "super-admin-piast" 236ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 330ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 249ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 731ms
Then Login as "super-admin-piast" 7s 030ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 513ms
After Hooks.deleteTransportAfterApiTest() 674ms
After Hooks.rollbackSettings() 189ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 243ms
And Set token of apiUsername "super-admin-piast" 230ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 161ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 174ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 774ms
Then Login as "super-admin-piast" 2s 553ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 371ms
After Hooks.deleteTransportAfterApiTest() 685ms
After Hooks.rollbackSettings() 147ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 245ms
And Set token of apiUsername "super-admin-piast" 237ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 140ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 129ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 693ms
Then Login as "super-admin-piast" 2s 466ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 350ms
After Hooks.deleteTransportAfterApiTest() 660ms
After Hooks.rollbackSettings() 104ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 254ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 774ms
And Find active transports for api version "v1" and expect status "200" 285ms
Then Check if active transports contains created transport 008ms
After Hooks.deleteTransportAfterApiTest() 636ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 241ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 139ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 168ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 237ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 678ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 933ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 654ms
After Hooks.rollbackSettings() 132ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 241ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 144ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 168ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 238ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 654ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 896ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 627ms
After Hooks.rollbackSettings() 134ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 234ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 138ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 175ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 250ms
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 "invalidTransportId" for api version "v1" 335ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 632ms
After Hooks.rollbackSettings() 131ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 240ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 137ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 194ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 272ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 706ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 030ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 664ms
After Hooks.rollbackSettings() 121ms
@deleteApiTransportsAfterTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 899ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 154ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 127ms
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 636ms
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 634ms
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" 332ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 284ms
After Hooks.rollbackSettings() 105ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 246ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 134ms
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" 247ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 649ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 297ms
After Hooks.deleteTransportAfterApiTest() 724ms
After Hooks.rollbackSettings() 133ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 244ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 139ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 160ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 5s 343ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 769ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 008ms
And Show all transport types 1s 185ms
And Click button advice in transport table "DELIVERY" 262ms
And Set advice window in schedule 3s 919ms
And Fill advice form 13s 299ms
And Click advice save button and wait for advice form to disappear 34s 011ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 757ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 459ms
And Go to transport details "DELIVERY" 2s 932ms
And Expand advice panel 542ms
Then Check are transport values equals 2s 416ms
After Hooks.deleteTransportAfterApiTest() 855ms
After Hooks.rollbackSettings() 135ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 5s 115ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 610ms
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 122ms
After Hooks.deleteTransportAfterApiTest() 848ms
After Hooks.deleteCustomFieldAfterTest() 2s 302ms
@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 939ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 463ms
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 073ms
After Hooks.deleteTransportAfterApiTest() 852ms
After Hooks.deleteCustomFieldAfterTest() 2s 180ms
@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 887ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 494ms
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 037ms
After Hooks.deleteTransportAfterApiTest() 839ms
After Hooks.deleteCustomFieldAfterTest() 2s 128ms
@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 965ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 380ms
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" 837ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 157ms
@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 087ms
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 "dd.MM.yyyy HH:mm" with expect status "422" 596ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 082ms
@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 752ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 425ms
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" 627ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 067ms
@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 783ms
And Create custom field with "CREATE_LOADING_SELECT_CFD" by "super-admin-semmelrock" 2s 632ms
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 035ms
After Hooks.deleteTransportAfterApiTest() 821ms
After Hooks.deleteCustomFieldAfterTest() 2s 093ms
@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 887ms
And Create custom field with "CREATE_LOADING_SELECT_CFD" by "super-admin-semmelrock" 2s 562ms
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 049ms
After Hooks.deleteTransportAfterApiTest() 818ms
After Hooks.deleteCustomFieldAfterTest() 2s 080ms
@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 965ms
And Create custom field with "CREATE_LOADING_SELECT_CFD" by "super-admin-semmelrock" 2s 544ms
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" 588ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 536ms
@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 961ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 329ms
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 064ms
After Hooks.deleteTransportAfterApiTest() 809ms
After Hooks.deleteCustomFieldAfterTest() 2s 106ms
@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 044ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 369ms
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 049ms
After Hooks.deleteTransportAfterApiTest() 824ms
After Hooks.deleteCustomFieldAfterTest() 2s 135ms
@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 852ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 426ms
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 003ms
After Hooks.deleteTransportAfterApiTest() 816ms
After Hooks.deleteCustomFieldAfterTest() 2s 133ms
@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 138ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 327ms
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" 570ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 003ms
@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 736ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 343ms
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" 568ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 1s 956ms
@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 815ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 299ms
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" 588ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 1s 978ms
@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 915ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 366ms
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
After Hooks.deleteTransportAfterApiTest() 790ms
After Hooks.deleteCustomFieldAfterTest() 2s 049ms
@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 864ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 265ms
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" 1s 944ms
After Hooks.deleteTransportAfterApiTest() 789ms
After Hooks.deleteCustomFieldAfterTest() 1s 990ms
@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 971ms
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 "12.12.2022" with expect status "422" 568ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 1s 979ms
@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 756ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 234ms
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" 556ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 110ms
@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 865ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 366ms
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" 569ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 1s 972ms