Project Number Date
ApolloFullRunnerReport 2021.AT1.23 28 lip 2021, 07:05

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 34s 282ms 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" 119ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 505ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 295ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 017ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 125ms
When Wait "15" seconds 15s
And Get updated transports in "15" time for api version "v1" and expect status "404" 079ms
And Check if the updated transports response is empty 012ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 421ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 091ms
And Check if the updated transports response contains created transport 014ms
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" 097ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 463ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 066ms
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
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 472ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 094ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 095ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 469ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 066ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 098ms
And Set token of apiUsername "super-admin-piast" 094ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 992ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 007ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 404ms
Then Login as "super-admin-piast" 2s 861ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 126ms
After Hooks.deleteTransportAfterApiTest() 057ms
After Hooks.rollbackSettings() 001ms
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
And Set token of apiUsername "super-admin-piast" 096ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 025ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_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" 383ms
Then Login as "super-admin-piast" 1s 003ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 128ms
After Hooks.deleteTransportAfterApiTest() 073ms
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" 094ms
And Set token of apiUsername "super-admin-piast" 099ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 023ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_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" 367ms
Then Login as "super-admin-piast" 985ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 122ms
After Hooks.deleteTransportAfterApiTest() 070ms
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" 092ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 425ms
And Find active transports for api version "v1" and expect status "200" 086ms
Then Check if active transports contains created transport 006ms
After Hooks.deleteTransportAfterApiTest() 076ms
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
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 365ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 684ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 067ms
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
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 395ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 293ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 077ms
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 Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 458ms
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() 068ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 002ms
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" 383ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 009ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 065ms
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
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 363ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 048ms
After Hooks.deleteTransportAfterApiTest() 059ms