Cucumber-JVM Reports - Feature: API Transport

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.51	22 cze 2021, 10:35

	Steps	Scenarios	Features
API Transport	91	0	0	0	0	91	21	0	21	44s 141ms	Passed

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

Steps

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

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

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

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

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

Steps

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

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

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

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

Steps

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

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

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

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

Steps

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

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

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

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

Steps

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

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

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

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

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

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

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

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

Steps

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

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

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

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

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

Steps

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

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

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

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

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

Steps

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

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

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

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

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

Steps

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

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

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

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

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

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

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

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

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

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

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

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

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

Steps

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

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

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

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

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

Steps

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

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

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

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

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

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

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

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

Steps

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

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

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

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

@deleteTransportAfterApiTest

Scenario Outline Check if it is possible to create transport with 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" 255ms

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 018ms

@deleteTransportAfterApiTest

Scenario Outline Check if it is possible to create transport with 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" 326ms

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 004ms

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

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

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

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

Then Login as "super-admin-piast" 3s 223ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 1s 062ms

After Hooks.rollbackSettings() 002ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 822ms

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

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

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

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" 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 284ms

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 816ms

After Hooks.rollbackSettings() 000ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
API Transport	91	0	0	0	0	91	21	0	21	44s 141ms	Passed

Feature Report