Cucumber-JVM Reports - Tag: @deleteTransportAfterApiTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.95	26 lip 2021, 05:36

	Steps	Scenarios	Features
@deleteTransportAfterApiTest	53	0	0	0	0	53	12	0	12	44s 775ms	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" 235ms

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 859ms

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 629ms

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 606ms

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

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

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

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

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" 8s 060ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 699ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 714ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 708ms

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

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

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

Then Check if active transports contains created transport 006ms

Hooks

After Hooks.deleteTransportAfterApiTest() 645ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 595ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 708ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 680ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 655ms

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

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

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

Hooks

After Hooks.deleteTransportAfterApiTest() 671ms

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

Tag Report