Project Number Date
ApolloFullRunnerReport 2021.AT1.19 27 Jul 2021, 06:07

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@deleteTransportAfterApiTest 63 0 0 0 0 63 14 0 14 33s 694ms Passed
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 004ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 145ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 596ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 278ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 096ms
When Wait "15" seconds 15s
And Get updated transports in "15" time for api version "v1" and expect status "404" 065ms
And Check if the updated transports response is empty 013ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 413ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 088ms
And Check if the updated transports response contains created transport 018ms
After Hooks.deleteTransportAfterApiTest() 086ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 096ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 454ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 121ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 094ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 510ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 081ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 098ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 452ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 071ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 092ms
And Set token of apiUsername "super-admin-piast" 105ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 1s 012ms
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" 376ms
Then Login as "super-admin-piast" 2s 378ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 148ms
After Hooks.deleteTransportAfterApiTest() 066ms
After Hooks.rollbackSettings() 002ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 103ms
And Set token of apiUsername "super-admin-piast" 097ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 034ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 003ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 368ms
Then Login as "super-admin-piast" 978ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 123ms
After Hooks.deleteTransportAfterApiTest() 078ms
After Hooks.rollbackSettings() 000ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 095ms
And Set token of apiUsername "super-admin-piast" 096ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 027ms
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" 394ms
Then Login as "super-admin-piast" 950ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 121ms
After Hooks.deleteTransportAfterApiTest() 079ms
After Hooks.rollbackSettings() 000ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 002ms
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" 397ms
And Find active transports for api version "v1" and expect status "200" 052ms
Then Check if active transports contains created transport 007ms
After Hooks.deleteTransportAfterApiTest() 078ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 097ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 327ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 727ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 069ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 093ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 426ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 266ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 129ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 090ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 392ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 108ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 060ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 088ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 339ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 007ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 067ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 094ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 364ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 045ms
After Hooks.deleteTransportAfterApiTest() 114ms