Project Number Date
ApolloFullRunnerReport apollo-test-2.157 14 wrz 2021, 06:50

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 46s 746ms Passed
Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 004ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 373ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 4s 219ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s 013ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 004ms
Given Login by Api as "super-admin-semmelrock" and get token and expect status "200" 419ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 2s 935ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s 086ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 293ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 138ms
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 927ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 297ms
And Check if the updated transports response contains created transport 014ms
After Hooks.deleteTransportAfterApiTest() 659ms
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 298ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 1s 294ms
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" 316ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 948ms
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" 009ms
Before Hooks.showScenarioName(Scenario) 001ms
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_STEP_TYPE_NAME_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 894ms
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" 007ms
Before Hooks.showScenarioName(Scenario) 002ms
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_STEP_TYPE_NAME_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 "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" 285ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 1s 080ms
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" 276ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 837ms
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" 298ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_COUNTRY_CODE_INCORRECT" as "super-admin-piast" for api version "v1" 1s 103ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny kod kraju" 005ms
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" 869ms
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" 285ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_RECIPIENT_EMPTY" as "super-admin-piast" for api version "v1" 845ms
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" 284ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_POSTAL_EMPTY" as "super-admin-piast" for api version "v1" 892ms
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" 316ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_CITY_EMPTY" as "super-admin-piast" for api version "v1" 892ms
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" 305ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_STREET_EMPTY" as "super-admin-piast" for api version "v1" 920ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny adres" 005ms
Before Hooks.showScenarioName(Scenario) 001ms
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_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 1s 098ms
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) 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_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 853ms
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" 277ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_EMPTY" as "super-admin-piast" for api version "v1" 1s 032ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawne dane firmy" 007ms
Before Hooks.showScenarioName(Scenario) 001ms
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_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" 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_QUANTITY_INCORRECT_DATA_TYPE" 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ę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" 280ms
When Create transport by invalid JSON file "CREATE_LOAD_VOLUME_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 844ms
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) 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_WEIGHT_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 887ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł weight musi być poprawną liczbą" 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_COMPANY_ID_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ł company.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" 288ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_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.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" 280ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 793ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł warehouse.idx 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" 299ms
When Create transport by invalid JSON file "CREATE_LOAD_MIN_ADVICE_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 836ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł minAdviceDate musi być poprawną datą" 008ms
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_MAX_ADVICE_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 836ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł maxAdviceDate musi być poprawną datą" 006ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 271ms
When Create transport by invalid JSON file "CREATE_LOAD_ARRIVAL_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 808ms
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" 289ms
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" 815ms
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" 282ms
When Create transport by invalid JSON file "CREATE_LOAD_NO_ADDRESS_AND_WAREHOUSE_IN_ONE_STEP" as "super-admin-piast" for api version "v1" 819ms
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" 290ms
When Create transport by invalid JSON file "CREATE_DELIVERY_NO_WAREHOUSE_IN_ONLY_STEP" as "super-admin-piast" for api version "v1" 667ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Magazyn jest wymagany w zleceniu jednoetapowym" 006ms
@deleteTransportAfterApiTest
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_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 882ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 564ms
@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 962ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 580ms
@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_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 818ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 539ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
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_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 778ms
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" 300ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 903ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 531ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 318ms
And Set token of apiUsername "super-admin-piast" 290ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 249ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 253ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 738ms
Then Login as "super-admin-piast" 7s 248ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 369ms
After Hooks.deleteTransportAfterApiTest() 631ms
After Hooks.rollbackSettings() 165ms
@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" 299ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 163ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 169ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 735ms
Then Login as "super-admin-piast" 2s 594ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 394ms
After Hooks.deleteTransportAfterApiTest() 622ms
After Hooks.rollbackSettings() 136ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 284ms
And 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: "ERP_IDENTIFIER" with "super-admin-piast" 123ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 784ms
Then Login as "super-admin-piast" 2s 524ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 365ms
After Hooks.deleteTransportAfterApiTest() 635ms
After Hooks.rollbackSettings() 095ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 284ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 705ms
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() 596ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 281ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 140ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 167ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 282ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 695ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 939ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 633ms
After Hooks.rollbackSettings() 133ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 279ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 162ms
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 733ms
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() 592ms
After Hooks.rollbackSettings() 128ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 283ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 149ms
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" 286ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 761ms
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() 616ms
After Hooks.rollbackSettings() 136ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 296ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 157ms
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" 303ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 667ms
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() 609ms
After Hooks.rollbackSettings() 127ms
@deleteApiTransportsAfterTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 906ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 145ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 128ms
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 675ms
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 730ms
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" 389ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 319ms
After Hooks.rollbackSettings() 093ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 288ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 156ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 288ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 709ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 241ms
After Hooks.deleteTransportAfterApiTest() 613ms
After Hooks.rollbackSettings() 130ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 279ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 144ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 151ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 5s 947ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 667ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 010ms
And Show all transport types 1s 177ms
And Click button advice in transport table "DELIVERY" 276ms
And Set advice window in schedule 3s 672ms
And Fill advice form 13s 363ms
And Click advice save button and wait for advice form to disappear 33s 345ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 750ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 449ms
And Go to transport details "DELIVERY" 2s 899ms
And Expand advice panel 465ms
Then Check are transport values equals 2s 391ms
After Hooks.deleteTransportAfterApiTest() 814ms
After Hooks.rollbackSettings() 131ms
@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 159ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 598ms
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 150ms
After Hooks.deleteTransportAfterApiTest() 847ms
After Hooks.deleteCustomFieldAfterTest() 2s 579ms
@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 822ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 420ms
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 058ms
After Hooks.deleteTransportAfterApiTest() 735ms
After Hooks.deleteCustomFieldAfterTest() 2s 488ms
@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 975ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 349ms
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 042ms
After Hooks.deleteTransportAfterApiTest() 796ms
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 024ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 353ms
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" 836ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 446ms
@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 042ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 336ms
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" 594ms
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 966ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 381ms
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" 633ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 468ms
@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 973ms
And Create custom field with "CREATE_LOADING_SELECT_CFD" by "super-admin-semmelrock" 2s 627ms
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 022ms
After Hooks.deleteTransportAfterApiTest() 793ms
After Hooks.deleteCustomFieldAfterTest() 2s 463ms
@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 948ms
And Create custom field with "CREATE_LOADING_SELECT_CFD" by "super-admin-semmelrock" 2s 555ms
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 046ms
After Hooks.deleteTransportAfterApiTest() 757ms
After Hooks.deleteCustomFieldAfterTest() 2s 539ms
@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 812ms
And Create custom field with "CREATE_LOADING_SELECT_CFD" by "super-admin-semmelrock" 2s 531ms
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" 633ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 477ms
@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 879ms
And Create custom field with "CREATE_LOADING_DATE_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 "datowy CF" value "21.12.2026 12:00" with expect status "200" 2s 125ms
After Hooks.deleteTransportAfterApiTest() 783ms
After Hooks.deleteCustomFieldAfterTest() 2s 427ms
@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 976ms
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 005ms
After Hooks.deleteTransportAfterApiTest() 776ms
After Hooks.deleteCustomFieldAfterTest() 2s 482ms
@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 250ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 338ms
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() 795ms
After Hooks.deleteCustomFieldAfterTest() 2s 407ms
@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 775ms
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 "41.12.2026 12:00" with expect status "422" 610ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 396ms
@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 894ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 302ms
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" 628ms
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 984ms
And Create custom field with "CREATE_LOADING_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 "datowy CF" value "elo mordeczko" with expect status "422" 607ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 385ms
@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 337ms
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 086ms
After Hooks.deleteTransportAfterApiTest() 752ms
After Hooks.deleteCustomFieldAfterTest() 2s 364ms
@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 936ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 238ms
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 991ms
After Hooks.deleteTransportAfterApiTest() 755ms
After Hooks.deleteCustomFieldAfterTest() 2s 405ms
@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 791ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 280ms
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" 590ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 340ms
@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 870ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 271ms
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" 622ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 362ms
@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 122ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 253ms
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 288ms