Project Number Date
ApolloFullRunnerReport apollo-test-2.158 15 wrz 2021, 06:58

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 54s 852ms Passed
Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 008ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 358ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 3s 966ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 983ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 013ms
Given Login by Api as "super-admin-semmelrock" and get token and expect status "200" 333ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 2s 623ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 958ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 005ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 355ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 184ms
And Check if the updated transports response is empty 017ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 966ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 292ms
And Check if the updated transports response contains created transport 018ms
After Hooks.deleteTransportAfterApiTest() 674ms
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 292ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 1s 218ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Nieprawidłowe wartości w polu orderInTransport" 009ms
Before Hooks.showScenarioName(Scenario) 003ms
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" 915ms
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" 316ms
When Create transport by invalid JSON file "CREATE_LOAD_STEP_TYPE_NAME_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 863ms
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" 283ms
When Create transport by invalid JSON file "CREATE_LOAD_STEP_TYPE_NAME_EMPTY" as "super-admin-piast" for api version "v1" 877ms
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) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 286ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 1s 092ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Nieprawidłowe wartości w polu orderInTransport" 010ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 290ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_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 "Brak wartości w polu orderInTransport, pole jest obowiązkowe" 007ms
Before Hooks.showScenarioName(Scenario) 006ms
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_ADDRESS_COUNTRY_CODE_INCORRECT" as "super-admin-piast" for api version "v1" 1s 105ms
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" 285ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_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 "Niepoprawny adres" 008ms
Before Hooks.showScenarioName(Scenario) 011ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 273ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_RECIPIENT_EMPTY" as "super-admin-piast" for api version "v1" 851ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny adres" 007ms
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 295ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_POSTAL_EMPTY" as "super-admin-piast" for api version "v1" 898ms
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" 295ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_CITY_EMPTY" as "super-admin-piast" for api version "v1" 934ms
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" 328ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_STREET_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" 006ms
Before Hooks.showScenarioName(Scenario) 001ms
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_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 1s 094ms
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" 281ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 869ms
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) 001ms
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_COMPANY_EMPTY" as "super-admin-piast" for api version "v1" 1s 019ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawne dane firmy" 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_LOAD_WAREHOUSE_EMPTY" as "super-admin-piast" for api version "v1" 829ms
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" 289ms
When Create transport by invalid JSON file "CREATE_LOAD_QUANTITY_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 877ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł quantity 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" 278ms
When Create transport by invalid JSON file "CREATE_LOAD_VOLUME_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 880ms
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) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 287ms
When Create transport by invalid JSON file "CREATE_LOAD_WEIGHT_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 873ms
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" 293ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 814ms
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" 277ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 828ms
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" 288ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 823ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł warehouse.idx musi być liczbą całkowitą" 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_MIN_ADVICE_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 849ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł minAdviceDate 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" 292ms
When Create transport by invalid JSON file "CREATE_LOAD_MAX_ADVICE_DATE_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ł maxAdviceDate musi być poprawną datą" 009ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 286ms
When Create transport by invalid JSON file "CREATE_LOAD_ARRIVAL_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 826ms
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" 279ms
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" 832ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Nie znaleźliśmy opakowania o nazwie" 006ms
Before Hooks.showScenarioName(Scenario) 001ms
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_NO_ADDRESS_AND_WAREHOUSE_IN_ONE_STEP" as "super-admin-piast" for api version "v1" 798ms
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) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 284ms
When Create transport by invalid JSON file "CREATE_DELIVERY_NO_WAREHOUSE_IN_ONLY_STEP" as "super-admin-piast" for api version "v1" 697ms
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" 294ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 843ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 560ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 287ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 899ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 551ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 291ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 783ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 554ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
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_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 806ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 541ms
@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_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 783ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 505ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 296ms
And Set token of apiUsername "super-admin-piast" 320ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 305ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 251ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 662ms
Then Login as "super-admin-piast" 6s 655ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 360ms
After Hooks.deleteTransportAfterApiTest() 641ms
After Hooks.rollbackSettings() 172ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 306ms
And Set token of apiUsername "super-admin-piast" 280ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 167ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 782ms
Then Login as "super-admin-piast" 2s 529ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 401ms
After Hooks.deleteTransportAfterApiTest() 602ms
After Hooks.rollbackSettings() 144ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 288ms
And Set token of apiUsername "super-admin-piast" 275ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 116ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 678ms
Then Login as "super-admin-piast" 2s 540ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 376ms
After Hooks.deleteTransportAfterApiTest() 625ms
After Hooks.rollbackSettings() 100ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 291ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 692ms
And Find active transports for api version "v1" and expect status "200" 278ms
Then Check if active transports contains created transport 006ms
After Hooks.deleteTransportAfterApiTest() 591ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 297ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 165ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 279ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 702ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 996ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 618ms
After Hooks.rollbackSettings() 124ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 282ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 146ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 157ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 286ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 802ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 905ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 597ms
After Hooks.rollbackSettings() 133ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 290ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 137ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 148ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 289ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 699ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 399ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 626ms
After Hooks.rollbackSettings() 128ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 281ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 150ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 157ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 290ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 688ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 029ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 584ms
After Hooks.rollbackSettings() 139ms
@deleteApiTransportsAfterTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 932ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 145ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 130ms
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 759ms
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 687ms
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" 375ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 236ms
After Hooks.rollbackSettings() 092ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 293ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 147ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 155ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 302ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 675ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 240ms
After Hooks.deleteTransportAfterApiTest() 607ms
After Hooks.rollbackSettings() 126ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 285ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 155ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 397ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 654ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 008ms
And Show all transport types 1s 174ms
And Click button advice in transport table "DELIVERY" 286ms
And Set advice window in schedule 3s 771ms
And Fill advice form 13s 327ms
And Click advice save button and wait for advice form to disappear 33s 287ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 802ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 454ms
And Go to transport details "DELIVERY" 2s 914ms
And Expand advice panel 560ms
Then Check are transport values equals 2s 389ms
After Hooks.deleteTransportAfterApiTest() 832ms
After Hooks.rollbackSettings() 133ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 002ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 5s 120ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 603ms
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 067ms
After Hooks.deleteTransportAfterApiTest() 779ms
After Hooks.deleteCustomFieldAfterTest() 2s 497ms
@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 118ms
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 075ms
After Hooks.deleteTransportAfterApiTest() 789ms
After Hooks.deleteCustomFieldAfterTest() 2s 495ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 002ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 4s 114ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 403ms
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 068ms
After Hooks.deleteTransportAfterApiTest() 805ms
After Hooks.deleteCustomFieldAfterTest() 2s 471ms
@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 880ms
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 "yolo" with expect status "422" 827ms
After Hooks.deleteTransportAfterApiTest() 000ms
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" 3s 977ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 473ms
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" 622ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 472ms
@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 927ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 378ms
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 442ms
@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 944ms
And Create custom field with "CREATE_LOADING_SELECT_CFD" by "super-admin-semmelrock" 2s 567ms
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 397ms
After Hooks.deleteTransportAfterApiTest() 747ms
After Hooks.deleteCustomFieldAfterTest() 2s 501ms
@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 992ms
And Create custom field with "CREATE_LOADING_SELECT_CFD" by "super-admin-semmelrock" 2s 529ms
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 030ms
After Hooks.deleteTransportAfterApiTest() 775ms
After Hooks.deleteCustomFieldAfterTest() 2s 474ms
@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 953ms
And Create custom field with "CREATE_LOADING_SELECT_CFD" by "super-admin-semmelrock" 2s 497ms
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" 626ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 483ms
@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 011ms
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 "21.12.2026 12:00" with expect status "200" 2s 069ms
After Hooks.deleteTransportAfterApiTest() 768ms
After Hooks.deleteCustomFieldAfterTest() 2s 434ms
@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 872ms
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 "13.04.2023" with expect status "200" 2s 034ms
After Hooks.deleteTransportAfterApiTest() 771ms
After Hooks.deleteCustomFieldAfterTest() 2s 485ms
@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 079ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 401ms
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" 1s 991ms
After Hooks.deleteTransportAfterApiTest() 757ms
After Hooks.deleteCustomFieldAfterTest() 2s 404ms
@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 089ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 339ms
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" 617ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 445ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 11s 114ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 301ms
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" 614ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 422ms
@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 917ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 279ms
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" 629ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 368ms
@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 906ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 318ms
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 021ms
After Hooks.deleteTransportAfterApiTest() 783ms
After Hooks.deleteCustomFieldAfterTest() 2s 346ms
@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 876ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 298ms
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 946ms
After Hooks.deleteTransportAfterApiTest() 798ms
After Hooks.deleteCustomFieldAfterTest() 2s 391ms
@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 911ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 284ms
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" 621ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 369ms
@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 820ms
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 "13:31" with expect status "422" 608ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 382ms
@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 929ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 257ms
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" 604ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 369ms