Project Number Date
ApolloFullRunnerReport apollo-test-2.146 05 wrz 2021, 06:14

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 32s 609ms 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" 279ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 4s 249ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s 060ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 005ms
Given Login by Api as "super-admin-semmelrock" and get token and expect status "200" 265ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 2s 621ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 999ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 262ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 138ms
And Check if the updated transports response is empty 015ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 839ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 279ms
And Check if the updated transports response contains created transport 016ms
After Hooks.deleteTransportAfterApiTest() 708ms
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" 251ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 805ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 625ms
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" 259ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 990ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 640ms
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_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 827ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 574ms
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" 244ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 816ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 559ms
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_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 815ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 590ms
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" 250ms
And Set token of apiUsername "super-admin-piast" 245ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 159ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 246ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 706ms
Then Login as "super-admin-piast" 8s 320ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 377ms
After Hooks.deleteTransportAfterApiTest() 554ms
After Hooks.rollbackSettings() 167ms
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" 259ms
And Set token of apiUsername "super-admin-piast" 250ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 156ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 160ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 719ms
Then Login as "super-admin-piast" 2s 483ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 401ms
After Hooks.deleteTransportAfterApiTest() 676ms
After Hooks.rollbackSettings() 140ms
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" 232ms
And Set token of apiUsername "super-admin-piast" 243ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 151ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 125ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 724ms
Then Login as "super-admin-piast" 2s 491ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 383ms
After Hooks.deleteTransportAfterApiTest() 647ms
After Hooks.rollbackSettings() 097ms
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" 255ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 656ms
And Find active transports for api version "v1" and expect status "200" 296ms
Then Check if active transports contains created transport 007ms
After Hooks.deleteTransportAfterApiTest() 623ms
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" 138ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 170ms
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 "none" for api version "v1" 1s 832ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 645ms
After Hooks.rollbackSettings() 147ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 260ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 152ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 170ms
And 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 751ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 867ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 630ms
After Hooks.rollbackSettings() 132ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 237ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 144ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 164ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 241ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 756ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 339ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 649ms
After Hooks.rollbackSettings() 125ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 255ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 132ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 180ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 257ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 688ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 031ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 642ms
After Hooks.rollbackSettings() 131ms
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" 135ms
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" 242ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 677ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 258ms
After Hooks.deleteTransportAfterApiTest() 633ms
After Hooks.rollbackSettings() 131ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 243ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 137ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 171ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 273ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 674ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 009ms
And Show all transport types 1s 172ms
And Click button advice in transport table "DELIVERY" 273ms
And Set advice window in schedule 3s 736ms
And Fill advice form 13s 313ms
And Click advice save button and wait for advice form to disappear 33s 921ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 646ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 497ms
And Go to transport details "DELIVERY" 2s 921ms
And Expand advice panel 529ms
Then Check are transport values equals 2s 410ms
After Hooks.deleteTransportAfterApiTest() 839ms
After Hooks.rollbackSettings() 160ms