Project Number Date
ApolloFullRunnerReport apollo-test-2.156 13 wrz 2021, 06:47

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 40s 953ms Passed
Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 007ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 271ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 4s 105ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s 082ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 004ms
Given Login by Api as "super-admin-semmelrock" and get token and expect status "200" 261ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 2s 616ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s 049ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 263ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 163ms
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 872ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 300ms
And Check if the updated transports response contains created transport 014ms
After Hooks.deleteTransportAfterApiTest() 700ms
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_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 1s 170ms
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) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 244ms
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" 006ms
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_STEP_TYPE_NAME_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 835ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawna wartość w polu stepTypeName. Poprawne wartości to: load, unload" 006ms
Before Hooks.showScenarioName(Scenario) 002ms
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_STEP_TYPE_NAME_EMPTY" as "super-admin-piast" for api version "v1" 861ms
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) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 246ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 1s 116ms
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" 252ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 839ms
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) 002ms
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_ADDRESS_COUNTRY_CODE_INCORRECT" as "super-admin-piast" for api version "v1" 1s 057ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny kod kraju" 007ms
Before Hooks.showScenarioName(Scenario) 003ms
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_ADDRESS_EMPTY" as "super-admin-piast" for api version "v1" 846ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny adres" 006ms
Before Hooks.showScenarioName(Scenario) 014ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 218ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_RECIPIENT_EMPTY" as "super-admin-piast" for api version "v1" 871ms
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" 225ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_POSTAL_EMPTY" as "super-admin-piast" for api version "v1" 778ms
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" 261ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_CITY_EMPTY" as "super-admin-piast" for api version "v1" 813ms
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" 270ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_STREET_EMPTY" as "super-admin-piast" for api version "v1" 799ms
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" 225ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 1s 059ms
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) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 248ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 780ms
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" 235ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_EMPTY" as "super-admin-piast" for api version "v1" 978ms
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" 241ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_EMPTY" as "super-admin-piast" for api version "v1" 811ms
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) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 236ms
When Create transport by invalid JSON file "CREATE_LOAD_QUANTITY_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 866ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł quantity 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" 249ms
When Create transport by invalid JSON file "CREATE_LOAD_VOLUME_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 857ms
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" 232ms
When Create transport by invalid JSON file "CREATE_LOAD_WEIGHT_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 803ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł weight 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_COMPANY_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 783ms
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) 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_WAREHOUSE_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 785ms
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) 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_WAREHOUSE_IDX_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 791ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł warehouse.idx musi być liczbą całkowitą" 005ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 247ms
When Create transport by invalid JSON file "CREATE_LOAD_MIN_ADVICE_DATE_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ł minAdviceDate 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" 237ms
When Create transport by invalid JSON file "CREATE_LOAD_MAX_ADVICE_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 803ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł maxAdviceDate musi być poprawną datą" 006ms
Before Hooks.showScenarioName(Scenario) 003ms
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_ARRIVAL_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 761ms
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" 231ms
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" 786ms
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) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 220ms
When Create transport by invalid JSON file "CREATE_LOAD_NO_ADDRESS_AND_WAREHOUSE_IN_ONE_STEP" as "super-admin-piast" for api version "v1" 761ms
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" 010ms
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_DELIVERY_NO_WAREHOUSE_IN_ONLY_STEP" as "super-admin-piast" for api version "v1" 636ms
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" 236ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 892ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 606ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 244ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 961ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 576ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 002ms
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_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 800ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 1s 187ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 002ms
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_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 836ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 588ms
@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_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 863ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 588ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 265ms
And Set token of apiUsername "super-admin-piast" 245ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 290ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 268ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 733ms
Then Login as "super-admin-piast" 6s 621ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 361ms
After Hooks.deleteTransportAfterApiTest() 660ms
After Hooks.rollbackSettings() 199ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 247ms
And Set token of apiUsername "super-admin-piast" 245ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 139ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 173ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 736ms
Then Login as "super-admin-piast" 2s 613ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 400ms
After Hooks.deleteTransportAfterApiTest() 640ms
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" 235ms
And Set token of apiUsername "super-admin-piast" 237ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 147ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 124ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 770ms
Then Login as "super-admin-piast" 2s 554ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 375ms
After Hooks.deleteTransportAfterApiTest() 656ms
After Hooks.rollbackSettings() 104ms
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 241ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 740ms
And Find active transports for api version "v1" and expect status "200" 298ms
Then Check if active transports contains created transport 006ms
After Hooks.deleteTransportAfterApiTest() 642ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 238ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 166ms
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 753ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 827ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 709ms
After Hooks.rollbackSettings() 144ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 246ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
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" 233ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 693ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 862ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 647ms
After Hooks.rollbackSettings() 132ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 231ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 137ms
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" 240ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 752ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 333ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 622ms
After Hooks.rollbackSettings() 129ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 232ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 135ms
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" 247ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 697ms
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() 708ms
After Hooks.rollbackSettings() 145ms
@deleteApiTransportsAfterTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 820ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 156ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 129ms
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 642ms
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 658ms
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" 351ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteApiTransportsAfterTest() 1s 267ms
After Hooks.rollbackSettings() 098ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 244ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 119ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 144ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 225ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 656ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 264ms
After Hooks.deleteTransportAfterApiTest() 664ms
After Hooks.rollbackSettings() 128ms
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 232ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 140ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 161ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 5s 345ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 719ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 009ms
And Show all transport types 1s 184ms
And Click button advice in transport table "DELIVERY" 246ms
And Set advice window in schedule 3s 766ms
And Fill advice form 13s 370ms
And Click advice save button and wait for advice form to disappear 33s 864ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 674ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 556ms
And Go to transport details "DELIVERY" 2s 914ms
And Expand advice panel 501ms
Then Check are transport values equals 2s 395ms
After Hooks.deleteTransportAfterApiTest() 879ms
After Hooks.rollbackSettings() 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" 5s 064ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 611ms
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 015ms
After Hooks.deleteTransportAfterApiTest() 831ms
After Hooks.deleteCustomFieldAfterTest() 2s 210ms
@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 835ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 458ms
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() 820ms
After Hooks.deleteCustomFieldAfterTest() 2s 163ms
@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 946ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 417ms
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 021ms
After Hooks.deleteTransportAfterApiTest() 813ms
After Hooks.deleteCustomFieldAfterTest() 2s 112ms
@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 023ms
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 "yolo" with expect status "422" 808ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 068ms
@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 849ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 427ms
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" 547ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 084ms
@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 900ms
And Create custom field with "CREATE_LOADING_NUMERIC_CFD" by "super-admin-semmelrock" 2s 383ms
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" 598ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 056ms
@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 762ms
And Create custom field with "CREATE_LOADING_SELECT_CFD" by "super-admin-semmelrock" 2s 631ms
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 249ms
After Hooks.deleteTransportAfterApiTest() 779ms
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" 4s 011ms
And Create custom field with "CREATE_LOADING_SELECT_CFD" by "super-admin-semmelrock" 2s 551ms
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 011ms
After Hooks.deleteTransportAfterApiTest() 848ms
After Hooks.deleteCustomFieldAfterTest() 2s 094ms
@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 850ms
And Create custom field with "CREATE_LOADING_SELECT_CFD" by "super-admin-semmelrock" 2s 521ms
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" 579ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 055ms
@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 910ms
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 "21.12.2026 12:00" with expect status "200" 2s 063ms
After Hooks.deleteTransportAfterApiTest() 795ms
After Hooks.deleteCustomFieldAfterTest() 2s 086ms
@deleteTransportAfterApiTest @deleteCustomFieldAfterTest @TmsLink=A-8211
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "super-admin-semmelrock" and set token of apiUsername "super-admin-semmelrock" 3s 853ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 370ms
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" 1s 988ms
After Hooks.deleteTransportAfterApiTest() 837ms
After Hooks.deleteCustomFieldAfterTest() 2s 066ms
@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 874ms
And Create custom field with "CREATE_LOADING_DATE_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 "datowy CF" value "2023-09-29T18:46:19Z" with expect status "200" 1s 986ms
After Hooks.deleteTransportAfterApiTest() 820ms
After Hooks.deleteCustomFieldAfterTest() 2s 161ms
@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 365ms
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" 574ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 036ms
@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 830ms
And Create custom field with "CREATE_LOADING_DATE_CFD" by "super-admin-semmelrock" 2s 351ms
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" 561ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 1s 969ms
@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 900ms
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 "elo mordeczko" with expect status "422" 558ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 2s 009ms
@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 802ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 316ms
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 039ms
After Hooks.deleteTransportAfterApiTest() 782ms
After Hooks.deleteCustomFieldAfterTest() 2s 001ms
@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 251ms
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 968ms
After Hooks.deleteTransportAfterApiTest() 788ms
After Hooks.deleteCustomFieldAfterTest() 2s 041ms
@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 954ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 278ms
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" 585ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 1s 975ms
@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 807ms
And Create custom field with "CREATE_LOADING_TIME_AND_DATE_CFD" by "super-admin-semmelrock" 2s 278ms
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" 561ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 1s 994ms
@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 846ms
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 "kitku" with expect status "422" 561ms
After Hooks.deleteTransportAfterApiTest() 000ms
After Hooks.deleteCustomFieldAfterTest() 1s 967ms