Project Number Date
ApolloFullRunnerReport 2021.AT1.60 15 sie 2021, 05:37

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 947ms Passed
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" 129ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 2s 334ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 349ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 007ms
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" 884ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 223ms
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" 120ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 072ms
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" 463ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 083ms
And Check if the updated transports response contains created transport 013ms
After Hooks.deleteTransportAfterApiTest() 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" 102ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 405ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 086ms
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" 103ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 422ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 096ms
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_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 359ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 085ms
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" 102ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 360ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 082ms
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" 112ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 393ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 101ms
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" 104ms
And Set token of apiUsername "super-admin-piast" 098ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 991ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 086ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 346ms
Then Login as "super-admin-piast" 3s 345ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 189ms
After Hooks.deleteTransportAfterApiTest() 103ms
After Hooks.rollbackSettings() 072ms
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" 106ms
And Set token of apiUsername "super-admin-piast" 106ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 032ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 026ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 341ms
Then Login as "super-admin-piast" 1s 071ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 130ms
After Hooks.deleteTransportAfterApiTest() 075ms
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" 110ms
And 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: "ERP_IDENTIFIER" with "super-admin-piast" 018ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 325ms
Then Login as "super-admin-piast" 1s 059ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 137ms
After Hooks.deleteTransportAfterApiTest() 092ms
After Hooks.rollbackSettings() 023ms
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" 341ms
And Find active transports for api version "v1" and expect status "200" 089ms
Then Check if active transports contains created transport 005ms
After Hooks.deleteTransportAfterApiTest() 076ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 114ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 037ms
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" 108ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 328ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 464ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 071ms
After Hooks.rollbackSettings() 025ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 100ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 046ms
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" 097ms
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" 169ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 078ms
After Hooks.rollbackSettings() 026ms
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" 025ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 097ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 330ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 123ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 057ms
After Hooks.rollbackSettings() 024ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 095ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 029ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 020ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 097ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 315ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 007ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 066ms
After Hooks.rollbackSettings() 027ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 095ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 032ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 021ms
And 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" 299ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 037ms
After Hooks.deleteTransportAfterApiTest() 065ms
After Hooks.rollbackSettings() 026ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 111ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 031ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 024ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 478ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 295ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 4s 655ms
And Show all transport types 1s 075ms
And Click button advice in transport table "DELIVERY" 090ms
And Set advice window in schedule 2s 972ms
And Fill advice form 10s 640ms
And Click advice save button and wait for advice form to disappear 31s 276ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 504ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 268ms
And Go to transport details "DELIVERY" 2s 455ms
And Expand advice panel 225ms
Then Check are transport values equals 2s 145ms
After Hooks.deleteTransportAfterApiTest() 115ms
After Hooks.rollbackSettings() 026ms