Cucumber-JVM Reports - Feature: API Transport

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.141	02 wrz 2021, 02:51

	Steps	Scenarios	Features
API Transport	209	1	13	0	0	223	46	1	47	2m 39s 306ms	Failed

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

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

Then Check if the user has created a transport 001ms

Hooks

After Hooks.deleteTransportAfterApiTest() 1s 074ms

@deleteTransportAfterApiTest

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

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

Then Check if the user has created a transport 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 1s 088ms

@deleteTransportAfterApiTest

Scenario Outline Check if it is possible to get correct last updates transport list 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" 281ms

When Wait "15" seconds 15s 001ms

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

And Check if the updated transports response is empty 011ms

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 874ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Steps

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_ADDRESS_COUNTRY_CODE_INCORRECT" as "super-admin-piast" for api version "v1" 1s 124ms

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

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

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

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

Steps

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

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

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

Steps

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

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

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

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

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

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

Steps

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

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

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

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

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

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

Steps

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

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

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

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

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

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

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

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

And Check if response message contains "W zleceniu wieloetapowym każdy etap musi mieć uzupełniony magazyn lub adres" 006ms

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

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

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

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

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

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

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

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

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

Steps

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

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

And Check if response message contains "Węzeł company.id musi być liczbą całkowitą" 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) 001ms

Steps

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

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

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

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

Steps

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

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

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

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

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

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

Steps

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_ARRIVAL_DATE_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ł arrivalDate 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" 236ms

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

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

And Check if response message contains "Nie znaleźliśmy opakowania o nazwie" 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" 245ms

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

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

And Check if response message contains "W zleceniu wieloetapowym każdy etap musi mieć uzupełniony magazyn lub adres" 006ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 591ms

@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) 003ms

Steps

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 680ms

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 627ms

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 548ms

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 558ms

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

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

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 549ms

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

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

Then Login as "super-admin-piast" 8s 961ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 677ms

After Hooks.rollbackSettings() 189ms

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

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

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

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 749ms

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 717ms

After Hooks.rollbackSettings() 154ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 652ms

After Hooks.rollbackSettings() 108ms

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

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

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

Then Check if active transports contains created transport 008ms

Hooks

After Hooks.deleteTransportAfterApiTest() 687ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 704ms

After Hooks.rollbackSettings() 134ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 670ms

After Hooks.rollbackSettings() 137ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 696ms

After Hooks.rollbackSettings() 142ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 696ms

After Hooks.rollbackSettings() 156ms

@deleteApiTransportsAfterTest @rollbackSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-piast" and set token of apiUsername "super-admin-piast" 2s 967ms

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

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

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 684ms

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 664ms

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

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

Hooks

After Hooks.deleteApiTransportsAfterTest() 1s 348ms

After Hooks.rollbackSettings() 097ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 629ms

After Hooks.rollbackSettings() 130ms

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

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 as "piast-admin" and set token of apiUsername "super-admin-piast" 32s 293ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: Nie udalo sie poprawnie zalogowac piast-admin (tried for 20 second(s) with 500 MILLISECONDS interval)
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.checkElementIsVisible(BasePage.java:185)
	at Pages.LoginPage.loginAs(LoginPage.java:42)
	at CucumberTests.BaseTest.loginAs(BaseTest.java:100)
	at CucumberTests.LoginTest.loginAsAndSetTokenOfApiUsername(LoginTest.java:83)
	at ✽.Login as "piast-admin" and set token of apiUsername "super-admin-piast"(file:Features/Api/Transport.feature:158)
Caused by: org.openqa.selenium.NoSuchElementException: Cannot locate an element using By.xpath: //a[text()='Logout'] | //a[text()='Wyloguj']
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: driver.version: unknown
	at org.openqa.selenium.support.ui.ExpectedConditions.lambda$findElement$0(ExpectedConditions.java:882)
	at java.util.Optional.orElseThrow(Optional.java:290)
	at org.openqa.selenium.support.ui.ExpectedConditions.findElement(ExpectedConditions.java:881)
	at org.openqa.selenium.support.ui.ExpectedConditions.access$000(ExpectedConditions.java:43)
	at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:205)
	at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:201)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208)
	at Pages.BasePage.checkElementIsVisible(BasePage.java:185)
	at Pages.LoginPage.loginAs(LoginPage.java:42)
	at CucumberTests.BaseTest.loginAs(BaseTest.java:100)
	at CucumberTests.LoginTest.loginAsAndSetTokenOfApiUsername(LoginTest.java:83)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaStepDefinition.execute(JavaStepDefinition.java:57)
	at cucumber.runner.PickleStepDefinitionMatch.runStep(PickleStepDefinitionMatch.java:50)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.PickleStepTestStep.run(PickleStepTestStep.java:43)
	at cucumber.runner.TestCase.run(TestCase.java:45)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

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

And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 000ms

And Show all transport types 000ms

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

And Set advice window in schedule 000ms

And Fill advice form 000ms

And Click advice save button and wait for advice form to disappear 000ms

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

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

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "DELIVERY" 000ms

And Expand advice panel 000ms

Then Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 000ms

After Hooks.rollbackSettings() 136ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
API Transport	209	1	13	0	0	223	46	1	47	2m 39s 306ms	Failed

Feature Report