Project Number Date
ApolloFullRunnerReport apollo-test-2.130 24 sie 2021, 05:52

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@deleteTransportAfterApiTest 104 0 0 0 0 104 18 0 18 2m 30s 906ms Passed
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 007ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 315ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 4s 309ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s 157ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 017ms
Given Login by Api as "super-admin-semmelrock" and get token and expect status "200" 314ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 2s 708ms
Then Check if the user has created a transport 001ms
After Hooks.deleteTransportAfterApiTest() 1s 102ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 004ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 256ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 157ms
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" 1s 895ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 286ms
And Check if the updated transports response contains created transport 013ms
After Hooks.deleteTransportAfterApiTest() 719ms
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" 225ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 871ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 610ms
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" 239ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 970ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 590ms
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" 255ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 844ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 573ms
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" 250ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 783ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 627ms
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" 231ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 790ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 576ms
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" 239ms
And Set token of apiUsername "super-admin-piast" 233ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 147ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 226ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 748ms
Then Login as "super-admin-piast" 5s 493ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 389ms
After Hooks.deleteTransportAfterApiTest() 688ms
After Hooks.rollbackSettings() 195ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 253ms
And Set token of apiUsername "super-admin-piast" 259ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 150ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 172ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 779ms
Then Login as "super-admin-piast" 2s 536ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 414ms
After Hooks.deleteTransportAfterApiTest() 666ms
After Hooks.rollbackSettings() 146ms
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" 257ms
And Set token of apiUsername "super-admin-piast" 251ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 159ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 126ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 703ms
Then Login as "super-admin-piast" 2s 576ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 391ms
After Hooks.deleteTransportAfterApiTest() 667ms
After Hooks.rollbackSettings() 111ms
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" 248ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 711ms
And Find active transports for api version "v1" and expect status "200" 323ms
Then Check if active transports contains created transport 007ms
After Hooks.deleteTransportAfterApiTest() 641ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 255ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 161ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 239ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 663ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 878ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 666ms
After Hooks.rollbackSettings() 129ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 235ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 156ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 169ms
And 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 767ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 851ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 645ms
After Hooks.rollbackSettings() 131ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 262ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 164ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 160ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 236ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 698ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 331ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 634ms
After Hooks.rollbackSettings() 124ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 235ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 166ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 239ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 663ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 036ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 684ms
After Hooks.rollbackSettings() 125ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 240ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 137ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 157ms
And 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 697ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 264ms
After Hooks.deleteTransportAfterApiTest() 619ms
After Hooks.rollbackSettings() 139ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 230ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 137ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 167ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 630ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 682ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 019ms
And Show all transport types 1s 164ms
And Click button advice in transport table "DELIVERY" 267ms
And Set advice window in schedule 3s 781ms
And Fill advice form 13s 278ms
And Click advice save button and wait for advice form to disappear 33s 907ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 689ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 489ms
And Go to transport details "DELIVERY" 3s 103ms
And Expand advice panel 603ms
Then Check are transport values equals 2s 369ms
After Hooks.deleteTransportAfterApiTest() 812ms
After Hooks.rollbackSettings() 135ms