Cucumber-JVM Reports - Feature: API Transport

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.46	19 cze 2021, 05:43

	Steps	Scenarios	Features
API Transport	91	0	0	0	0	91	21	0	21	47s 005ms	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" 293ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 015ms

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 005ms

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

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

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

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

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

Then Login as "super-admin-piast" 7s 834ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 968ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 687ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 692ms

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	47s 005ms	Passed

Feature Report