Project Number Date
ApolloFullRunnerReport apollo-test-2.112 10 sie 2021, 05:53

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@deleteTransportAfterApiTest 101 0 0 0 0 101 17 0 17 2m 22s 876ms Passed
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 005ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 282ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 4s 022ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s 125ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 004ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 305ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 148ms
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 723ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 299ms
And Check if the updated transports response contains created transport 015ms
After Hooks.deleteTransportAfterApiTest() 754ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 252ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 734ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 614ms
View Feature API Transport
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 784ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 623ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 236ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 672ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 617ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 251ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 693ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 600ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 252ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 686ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 587ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 246ms
And Set token of apiUsername "super-admin-piast" 235ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 184ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 253ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 575ms
Then Login as "super-admin-piast" 4s 356ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 424ms
After Hooks.deleteTransportAfterApiTest() 681ms
After Hooks.rollbackSettings() 189ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 388ms
And Set token of apiUsername "super-admin-piast" 241ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 169ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 174ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 553ms
Then Login as "super-admin-piast" 2s 431ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 385ms
After Hooks.deleteTransportAfterApiTest() 677ms
After Hooks.rollbackSettings() 149ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 233ms
And Set token of apiUsername "super-admin-piast" 217ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 132ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 649ms
Then Login as "super-admin-piast" 2s 496ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 358ms
After Hooks.deleteTransportAfterApiTest() 676ms
After Hooks.rollbackSettings() 106ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 002ms
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 560ms
And Find active transports for api version "v1" and expect status "200" 255ms
Then Check if active transports contains created transport 008ms
After Hooks.deleteTransportAfterApiTest() 616ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 232ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 133ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 176ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 235ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 579ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 723ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 668ms
After Hooks.rollbackSettings() 143ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 252ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 155ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 140ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 229ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 513ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 770ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 671ms
After Hooks.rollbackSettings() 135ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 237ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 139ms
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 538ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 360ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 661ms
After Hooks.rollbackSettings() 129ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 238ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 153ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 163ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 234ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 547ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 032ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 653ms
After Hooks.rollbackSettings() 144ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 242ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 126ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 153ms
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 526ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 290ms
After Hooks.deleteTransportAfterApiTest() 659ms
After Hooks.rollbackSettings() 133ms
View Feature API Transport
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 230ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 149ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 257ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 663ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 522ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 2s 802ms
And Show all transport types 1s 162ms
And Click button advice in transport table "DELIVERY" 269ms
And Set advice window in schedule 3s 949ms
And Fill advice form 13s 446ms
And Click advice save button and wait for advice form to disappear 33s 895ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 732ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 488ms
And Go to transport details "DELIVERY" 2s 936ms
And Expand advice panel 675ms
Then Check are transport values equals 2s 389ms
After Hooks.deleteTransportAfterApiTest() 864ms
After Hooks.rollbackSettings() 134ms