Cucumber-JVM Reports - Feature: API Transport

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.67	04 lip 2021, 06:29

	Steps	Scenarios	Features
API Transport	161	0	0	0	0	161	39	0	39	1m 15s 410ms	Passed

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

Steps

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

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

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]

Steps

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

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

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

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

Steps

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

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

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

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

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

Steps

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

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

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]

Steps

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

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

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

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

Steps

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

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

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]

Steps

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

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

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]

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

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]

Steps

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

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

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]

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

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]

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

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]

Steps

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

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

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]

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

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]

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

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]

Steps

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

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

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

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

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

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

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

Steps

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

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

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

And Check if response message contains "Węzeł quantity 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]

Steps

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

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

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

And Check if response message contains "Węzeł volume 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]

Steps

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

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

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]

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

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

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

Steps

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

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

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

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

Steps

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

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

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

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

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

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

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

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

Steps

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

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

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]

Steps

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

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

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]

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

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

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

Steps

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

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

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ą" 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]

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_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 2s 486ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 1s 021ms

@deleteTransportAfterApiTest

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

Steps

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 715ms

@deleteTransportAfterApiTest

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 709ms

@deleteTransportAfterApiTest @rollbackSettings

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

Steps

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 788ms

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]

Steps

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 820ms

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]

Steps

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 769ms

After Hooks.rollbackSettings() 000ms

@deleteTransportAfterApiTest

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

Steps

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

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

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

Then Check if active transports contains created transport 008ms

Hooks

After Hooks.deleteTransportAfterApiTest() 749ms

@deleteTransportAfterApiTest

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

Steps

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 749ms

@deleteTransportAfterApiTest

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

Steps

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 780ms

@deleteTransportAfterApiTest

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

Steps

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 731ms

@deleteTransportAfterApiTest

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

Steps

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 698ms

@deleteTransportAfterApiTest

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

Steps

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 730ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
API Transport	161	0	0	0	0	161	39	0	39	1m 15s 410ms	Passed

Feature Report