Project Number Date
ApolloFullRunnerReport 2021.AT1.57 12 sie 2021, 05:48

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 1m 35s 644ms Passed
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" 155ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 2s 167ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 379ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-semmelrock" and get token and expect status "200" 113ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 842ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 237ms
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" 112ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 066ms
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" 438ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 105ms
And Check if the updated transports response contains created transport 013ms
After Hooks.deleteTransportAfterApiTest() 113ms
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" 097ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 389ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 091ms
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" 104ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 410ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 088ms
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" 101ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 362ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 075ms
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" 102ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 350ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 077ms
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" 100ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 348ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 076ms
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" 104ms
And Set token of apiUsername "super-admin-piast" 099ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 965ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 100ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 351ms
Then Login as "super-admin-piast" 2s 897ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 174ms
After Hooks.deleteTransportAfterApiTest() 113ms
After Hooks.rollbackSettings() 077ms
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" 136ms
And Set token of apiUsername "super-admin-piast" 101ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 036ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 034ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 398ms
Then Login as "super-admin-piast" 1s 046ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 135ms
After Hooks.deleteTransportAfterApiTest() 121ms
After Hooks.rollbackSettings() 030ms
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" 103ms
And Set token of apiUsername "super-admin-piast" 107ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 038ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 019ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 392ms
Then Login as "super-admin-piast" 1s 002ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 144ms
After Hooks.deleteTransportAfterApiTest() 092ms
After Hooks.rollbackSettings() 021ms
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" 100ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 344ms
And Find active transports for api version "v1" and expect status "200" 069ms
Then Check if active transports contains created transport 005ms
After Hooks.deleteTransportAfterApiTest() 083ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 115ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 036ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 027ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 113ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 333ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 523ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 077ms
After Hooks.rollbackSettings() 029ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 105ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 038ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 025ms
And 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" 322ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 188ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 107ms
After Hooks.rollbackSettings() 029ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 101ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 035ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 026ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 102ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 321ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 114ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 078ms
After Hooks.rollbackSettings() 028ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 098ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 031ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 029ms
And 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" 318ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 008ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 083ms
After Hooks.rollbackSettings() 050ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 097ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 039ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 027ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 103ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 325ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 050ms
After Hooks.deleteTransportAfterApiTest() 086ms
After Hooks.rollbackSettings() 030ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 098ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 029ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 026ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 707ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 303ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 4s 716ms
And Show all transport types 1s 080ms
And Click button advice in transport table "DELIVERY" 089ms
And Set advice window in schedule 2s 926ms
And Fill advice form 10s 711ms
And Click advice save button and wait for advice form to disappear 31s 206ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 488ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 241ms
And Go to transport details "DELIVERY" 2s 509ms
And Expand advice panel 202ms
Then Check are transport values equals 2s 139ms
After Hooks.deleteTransportAfterApiTest() 116ms
After Hooks.rollbackSettings() 026ms