Cucumber-JVM Reports - Feature: API Transport

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.57	12 sie 2021, 05:48

	Steps	Scenarios	Features
API Transport	216	0	0	0	0	216	46	0	46	1m 44s 072ms	Passed

Scenario Outline Check if it is possible to create transport by Public API

Hooks

Before Hooks.showScenarioName(Scenario) 004ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 155ms

When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 2s 167ms

Then Check if the user has created a transport 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 379ms

@deleteTransportAfterApiTest

Scenario Outline Check if it is possible to create transport by Public API

Hooks

Before Hooks.showScenarioName(Scenario) 003ms

Steps

Given Login by Api as "super-admin-semmelrock" and get token and expect status "200" 113ms

When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 842ms

Then Check if the user has created a transport 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 237ms

@deleteTransportAfterApiTest

Scenario Outline Check if it is possible to get correct last updates transport list by Public API

Hooks

Before Hooks.showScenarioName(Scenario) 003ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 112ms

When Wait "15" seconds 15s 001ms

And Get updated transports in "15" time for api version "v1" and expect status "404" 066ms

And Check if the updated transports response is empty 012ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 438ms

Then Get updated transports in "15" time for api version "v1" and expect status "200" 105ms

And Check if the updated transports response contains created transport 013ms

Hooks

After Hooks.deleteTransportAfterApiTest() 113ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 003ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 102ms

When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 291ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Nieprawidłowe wartości w polu orderInTransport" 005ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 112ms

When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 243ms

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

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 106ms

When Create transport by invalid JSON file "CREATE_LOAD_STEP_TYPE_NAME_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 205ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Niepoprawna wartość w polu stepTypeName. Poprawne wartości to: load, unload" 005ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 105ms

When Create transport by invalid JSON file "CREATE_LOAD_STEP_TYPE_NAME_EMPTY" as "super-admin-piast" for api version "v1" 212ms

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

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 102ms

When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 243ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Nieprawidłowe wartości w polu orderInTransport" 005ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 103ms

When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 203ms

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" 004ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 099ms

When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_COUNTRY_CODE_INCORRECT" as "super-admin-piast" for api version "v1" 244ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Niepoprawny kod kraju" 006ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 102ms

When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_EMPTY" as "super-admin-piast" for api version "v1" 182ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Niepoprawny adres" 006ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 015ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 102ms

When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_RECIPIENT_EMPTY" as "super-admin-piast" for api version "v1" 220ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Niepoprawny adres" 006ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 099ms

When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_POSTAL_EMPTY" as "super-admin-piast" for api version "v1" 219ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Niepoprawny adres" 006ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 120ms

When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_CITY_EMPTY" as "super-admin-piast" for api version "v1" 213ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Niepoprawny adres" 006ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 108ms

When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_STREET_EMPTY" as "super-admin-piast" for api version "v1" 180ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Niepoprawny adres" 005ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 097ms

When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 211ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Nieprawidłowe wartości w polu orderInTransport" 005ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 093ms

When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 175ms

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

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 097ms

When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_EMPTY" as "super-admin-piast" for api version "v1" 188ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Niepoprawne dane firmy" 004ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 104ms

When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_EMPTY" as "super-admin-piast" for api version "v1" 159ms

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" 005ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 099ms

When Create transport by invalid JSON file "CREATE_LOAD_QUANTITY_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 172ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł quantity musi być poprawną liczbą" 004ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 098ms

When Create transport by invalid JSON file "CREATE_LOAD_VOLUME_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 156ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł volume musi być poprawną liczbą" 004ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 098ms

When Create transport by invalid JSON file "CREATE_LOAD_WEIGHT_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 152ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł weight musi być poprawną liczbą" 007ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 102ms

When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 189ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł company.id musi być liczbą całkowitą" 004ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 109ms

When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 186ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł warehouse.id musi być liczbą całkowitą" 005ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 118ms

When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 144ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł warehouse.idx musi być liczbą całkowitą" 004ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 096ms

When Create transport by invalid JSON file "CREATE_LOAD_MIN_ADVICE_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 152ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł minAdviceDate musi być poprawną datą" 005ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 114ms

When Create transport by invalid JSON file "CREATE_LOAD_MAX_ADVICE_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 164ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł maxAdviceDate musi być poprawną datą" 005ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 112ms

When Create transport by invalid JSON file "CREATE_LOAD_ARRIVAL_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 159ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł arrivalDate musi być poprawną datą" 005ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 103ms

When Create transport by invalid JSON file "CREATE_LOAD_STEP_PACKAGE_TYPES_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 152ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł stepPackageType.id musi być liczbą całkowitą" 006ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 109ms

When Create transport by invalid JSON file "CREATE_LOAD_NO_ADDRESS_AND_WAREHOUSE_IN_ONE_STEP" as "super-admin-piast" for api version "v1" 151ms

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" 004ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 100ms

When Create transport by invalid JSON file "CREATE_DELIVERY_NO_WAREHOUSE_IN_ONLY_STEP" as "super-admin-piast" for api version "v1" 163ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Magazyn jest wymagany w zleceniu jednoetapowym" 005ms

@deleteTransportAfterApiTest

Scenario Outline Check if it is possible to create transport with only part of data in company node by Public API [A-7513]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 097ms

When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 389ms

Then Check if response status code equals "200" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 091ms

@deleteTransportAfterApiTest

Scenario Outline Check if it is possible to create transport with only part of data in company node by Public API [A-7513]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 104ms

When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 410ms

Then Check if response status code equals "200" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 088ms

@deleteTransportAfterApiTest

Scenario Outline Check if it is possible to create transport with only part of data in company node by Public API [A-7513]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 101ms

When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 362ms

Then Check if response status code equals "200" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 075ms

@deleteTransportAfterApiTest

Scenario Outline Check if it is possible to create transport with only part of data in company node by Public API [A-7513]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 102ms

When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 350ms

Then Check if response status code equals "200" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 077ms

@deleteTransportAfterApiTest

Scenario Outline Check if it is possible to create transport with only part of data in company node by Public API [A-7513]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 100ms

When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 348ms

Then Check if response status code equals "200" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 076ms

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it is possible to create transport with different transport identifier type by Public API [A-7523]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 104ms

And Set token of apiUsername "super-admin-piast" 099ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 965ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 100ms

When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 351ms

Then Login as "super-admin-piast" 2s 897ms

And Check is transport "DELIVERY" created in transport table and set transport id 1s 174ms

Hooks

After Hooks.deleteTransportAfterApiTest() 113ms

After Hooks.rollbackSettings() 077ms

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it is possible to create transport with different transport identifier type by Public API [A-7523]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 136ms

And Set token of apiUsername "super-admin-piast" 101ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 036ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 034ms

When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 398ms

Then Login as "super-admin-piast" 1s 046ms

And Check is transport "DELIVERY" created in transport table and set transport id 1s 135ms

Hooks

After Hooks.deleteTransportAfterApiTest() 121ms

After Hooks.rollbackSettings() 030ms

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it is possible to create transport with different transport identifier type by Public API [A-7523]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 103ms

And Set token of apiUsername "super-admin-piast" 107ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 038ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 019ms

When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 392ms

Then Login as "super-admin-piast" 1s 002ms

And Check is transport "DELIVERY" created in transport table and set transport id 1s 144ms

Hooks

After Hooks.deleteTransportAfterApiTest() 092ms

After Hooks.rollbackSettings() 021ms

@deleteTransportAfterApiTest

Scenario Outline Check if it is possible to get transport list by API

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 100ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 344ms

And Find active transports for api version "v1" and expect status "200" 069ms

Then Check if active transports contains created transport 005ms

Hooks

After Hooks.deleteTransportAfterApiTest() 083ms

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 115ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 036ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 027ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 113ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 333ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 523ms

Then Check if response status code equals "200" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 077ms

After Hooks.rollbackSettings() 029ms

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 105ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 038ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 025ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 099ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 322ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 188ms

Then Check if response status code equals "422" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 107ms

After Hooks.rollbackSettings() 029ms

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 101ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 035ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 026ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 102ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 321ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 114ms

Then Check if response status code equals "404" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 078ms

After Hooks.rollbackSettings() 028ms

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 098ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 031ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 029ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 095ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 318ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 008ms

Then Check if response status code equals "401" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 083ms

After Hooks.rollbackSettings() 050ms

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if custom fields map is correct after creating a transport by Public API [A-7508]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 097ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 039ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 027ms

And Login by Api as "super-admin-piast" and get token and expect status "200" 103ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 325ms

And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 050ms

Hooks

After Hooks.deleteTransportAfterApiTest() 086ms

After Hooks.rollbackSettings() 030ms

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it possible to edit transport by API [A-4167]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 098ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 029ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 026ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 707ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 303ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 4s 716ms

And Show all transport types 1s 080ms

And Click button advice in transport table "DELIVERY" 089ms

And Set advice window in schedule 2s 926ms

And Fill advice form 10s 711ms

And Click advice save button and wait for advice form to disappear 31s 206ms

When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 488ms

And Check if response status code equals "200" 000ms

And Go to "TRANSPORT_TABLE" 241ms

And Go to transport details "DELIVERY" 2s 509ms

And Expand advice panel 202ms

Then Check are transport values equals 2s 139ms

Hooks

After Hooks.deleteTransportAfterApiTest() 116ms

After Hooks.rollbackSettings() 026ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
API Transport	216	0	0	0	0	216	46	0	46	1m 44s 072ms	Passed

Feature Report