Cucumber-JVM Reports - Feature: API Transport

Project	Number	Date
ApolloFullRunnerReport	kapibary.45	18 cze 2021, 05:45

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

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

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

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

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

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

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

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

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

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

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]

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

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

When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_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 "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" 282ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_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 "Brak wartości w polu orderInTransport, pole jest obowiązkowe" 009ms

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

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 019ms

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 007ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 865ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 753ms

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 659ms

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 931ms	Passed

Feature Report