Project Number Date
ApolloFullRunnerReport 2021.AT1.14 26 Jul 2021, 08:50

Tag Report

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 17s 202ms Passed
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 108ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 486ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 292ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 116ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 615ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 101ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 097ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 501ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 113ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 101ms
And Set token of apiUsername "super-admin-piast" 105ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 096ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 008ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 455ms
Then Login as "super-admin-piast" 2s 437ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 149ms
After Hooks.deleteTransportAfterApiTest() 137ms
After Hooks.rollbackSettings() 001ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 114ms
And Set token of apiUsername "super-admin-piast" 100ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 030ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 001ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 425ms
Then Login as "super-admin-piast" 1s 011ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 137ms
After Hooks.deleteTransportAfterApiTest() 116ms
After Hooks.rollbackSettings() 000ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 100ms
And Set token of apiUsername "super-admin-piast" 099ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 030ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 002ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 370ms
Then Login as "super-admin-piast" 1s 031ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 129ms
After Hooks.deleteTransportAfterApiTest() 110ms
After Hooks.rollbackSettings() 000ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 102ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 400ms
And Find active transports for api version "v1" and expect status "200" 106ms
Then Check if active transports contains created transport 008ms
After Hooks.deleteTransportAfterApiTest() 088ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 099ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 420ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 779ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 086ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 098ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 376ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 263ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 113ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 101ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 401ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 118ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 089ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 096ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 403ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 008ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 073ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 101ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 396ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 049ms
After Hooks.deleteTransportAfterApiTest() 093ms