Cucumber-JVM Reports - Tag: @deleteTransportAfterApiTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.66	03 lip 2021, 06:35

	Steps	Scenarios	Features
@deleteTransportAfterApiTest	53	0	0	0	0	53	12	0	12	44s 099ms	Passed

View Feature API Transport

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 1s 043ms

View Feature API Transport

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 706ms

View Feature API Transport

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 724ms

View Feature API Transport

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 791ms

After Hooks.rollbackSettings() 002ms

View Feature API Transport

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 877ms

After Hooks.rollbackSettings() 000ms

View Feature API Transport

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 700ms

After Hooks.rollbackSettings() 000ms

View Feature API Transport

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

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

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

Then Check if active transports contains created transport 006ms

Hooks

After Hooks.deleteTransportAfterApiTest() 742ms

View Feature API Transport

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 687ms

View Feature API Transport

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 786ms

View Feature API Transport

@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 388ms

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 761ms

View Feature API Transport

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 750ms

View Feature API Transport

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 696ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@deleteTransportAfterApiTest	53	0	0	0	0	53	12	0	12	44s 099ms	Passed

Tag Report