Cucumber-JVM Reports - Tag: @deleteTransportAfterApiTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.85	19 lip 2021, 03:57

	Steps	Scenarios	Features
@deleteTransportAfterApiTest	53	0	0	0	0	53	12	0	12	44s 112ms	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]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 874ms

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]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 639ms

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]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 599ms

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]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 721ms

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]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 800ms

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]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 690ms

After Hooks.rollbackSettings() 000ms

View Feature API Transport

@deleteTransportAfterApiTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

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

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

Then Check if active transports contains created transport 009ms

Hooks

After Hooks.deleteTransportAfterApiTest() 663ms

View Feature API Transport

@deleteTransportAfterApiTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 597ms

View Feature API Transport

@deleteTransportAfterApiTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 693ms

View Feature API Transport

@deleteTransportAfterApiTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

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

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() 654ms

View Feature API Transport

@deleteTransportAfterApiTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 666ms

View Feature API Transport

@deleteTransportAfterApiTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 642ms

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

Tag Report