Cucumber-JVM Reports - Feature: API Transport

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.40	03 sie 2021, 06:22

	Steps	Scenarios	Features
API Transport	191	1	0	0	0	192	43	1	44	1m 47s 089ms	Failed

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-piast" and get token and expect status "200" 133ms

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

Then Check if the user has created a transport 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 350ms

@deleteTransportAfterApiTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 005ms

Steps

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

When Wait "15" seconds 15s 001ms

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

And Check if the updated transports response is empty 016ms

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 139ms

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

Steps

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

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

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

And Check if response message contains "Nieprawidłowe wartości w polu orderInTransport" 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" 114ms

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

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) 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_STEP_TYPE_NAME_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 388ms

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) 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_TYPE_NAME_EMPTY" as "super-admin-piast" for api version "v1" 411ms

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

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

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

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

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

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

And Check if response message contains "Brak wartości w polu orderInTransport, pole jest obowiązkowe" 007ms

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_COUNTRY_CODE_INCORRECT" as "super-admin-piast" for api version "v1" 383ms

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

And Check if response message contains "Niepoprawny kod kraju" 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" 113ms

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

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

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

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) 012ms

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_ADDRESS_POSTAL_EMPTY" as "super-admin-piast" for api version "v1" 346ms

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

And Check if response message contains "Niepoprawny 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) 002ms

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_ADDRESS_CITY_EMPTY" as "super-admin-piast" for api version "v1" 369ms

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) 001ms

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

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

And Check if response message contains "Niepoprawny 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) 002ms

Steps

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

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

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

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

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) 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_LOAD_COMPANY_EMPTY" as "super-admin-piast" for api version "v1" 394ms

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

And Check if response message contains "Niepoprawne dane firmy" 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" 103ms

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

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

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

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

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

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

And Check if response message contains "Węzeł volume musi być poprawną liczbą" 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" 104ms

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

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

And Check if response message contains "Węzeł weight 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" 100ms

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

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

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_WAREHOUSE_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 316ms

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

And Check if response message contains "Węzeł warehouse.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" 099ms

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

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

And Check if response message contains "Węzeł warehouse.idx 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" 097ms

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

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

And Check if response message contains "Węzeł minAdviceDate musi byd 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" 101ms

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

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

And Check if response message contains "Węzeł maxAdviceDate musi być poprawną datą" 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" 112ms

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

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

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

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

And Check if response message contains "Węzeł stepPackageType.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" 102ms

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

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

And Check if response message contains "Węzeł stepPackageType.step.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" 100ms

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

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

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

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

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

@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" 108ms

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 089ms

@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" 103ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 097ms

@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" 106ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 102ms

After Hooks.rollbackSettings() 001ms

@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" 102ms

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

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

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

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

Then Login as "super-admin-piast" 998ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 079ms

After Hooks.rollbackSettings() 000ms

@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" 097ms

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

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

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

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

Then Login as "super-admin-piast" 967ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 091ms

After Hooks.rollbackSettings() 000ms

@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" 101ms

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

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

Then Check if active transports contains created transport 007ms

Hooks

After Hooks.deleteTransportAfterApiTest() 118ms

@deleteTransportAfterApiTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 087ms

@deleteTransportAfterApiTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given 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" 425ms

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 094ms

@deleteTransportAfterApiTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given 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" 368ms

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 078ms

@deleteTransportAfterApiTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

@deleteTransportAfterApiTest

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 Login by Api as "super-admin-piast" and get token and expect status "200" 101ms

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 076ms

@deleteTransportAfterApiTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 493ms

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

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

And Show all transport types 1s 073ms

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

And Set advice window in schedule 2s 886ms

And Fill advice form 10s 754ms

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

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

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

And Go to "TRANSPORT_TABLE" 206ms

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

Then Check are transport values equals 2s 133ms

Error message

java.lang.AssertionError: Wartości w formularzu w polu phone-number-prefix są niepoprawne, wartość na stronie:  wartość poprawna: 48
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Transport.Transport.checkAreValuesEquals(Transport.java:136)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:258)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:239)
	at ✽.Check are transport values equals(file:Features/Api/Transport.feature:164)

Hooks

After Hooks.deleteTransportAfterApiTest() 123ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
API Transport	191	1	0	0	0	192	43	1	44	1m 47s 089ms	Failed

Feature Report