Project Number Date
ApolloFullRunnerReport 2021.AT1.55 10 sie 2021, 05:37

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 1m 33s 427ms 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" 143ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 2s 468ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 357ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 005ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 122ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 071ms
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" 470ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 096ms
And Check if the updated transports response contains created transport 015ms
After Hooks.deleteTransportAfterApiTest() 129ms
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_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 407ms
Then Check if response status code equals "200" 000ms
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_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 408ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 101ms
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" 100ms
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() 093ms
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" 099ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 337ms
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" 104ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 336ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 075ms
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" 100ms
And Set token of apiUsername "super-admin-piast" 102ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 982ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 087ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 350ms
Then Login as "super-admin-piast" 1s 865ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 140ms
After Hooks.deleteTransportAfterApiTest() 099ms
After Hooks.rollbackSettings() 060ms
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" 126ms
And Set token of apiUsername "super-admin-piast" 102ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 036ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 025ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 394ms
Then Login as "super-admin-piast" 1s 046ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 139ms
After Hooks.deleteTransportAfterApiTest() 107ms
After Hooks.rollbackSettings() 035ms
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" 101ms
And Set token of apiUsername "super-admin-piast" 098ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 035ms
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" 318ms
Then Login as "super-admin-piast" 1s 088ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 140ms
After Hooks.deleteTransportAfterApiTest() 096ms
After Hooks.rollbackSettings() 024ms
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" 099ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 356ms
And Find active transports for api version "v1" and expect status "200" 064ms
Then Check if active transports contains created transport 006ms
After Hooks.deleteTransportAfterApiTest() 092ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 100ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 034ms
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" 101ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 301ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 489ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 080ms
After Hooks.rollbackSettings() 023ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 099ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 031ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 030ms
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" 342ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 165ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 078ms
After Hooks.rollbackSettings() 027ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 106ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 035ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 028ms
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" 312ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 116ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 071ms
After Hooks.rollbackSettings() 024ms
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" 032ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 022ms
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" 329ms
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() 093ms
After Hooks.rollbackSettings() 029ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 099ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 030ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 024ms
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" 310ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 074ms
After Hooks.deleteTransportAfterApiTest() 074ms
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" 028ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 028ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 136ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 302ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 4s 737ms
And Show all transport types 1s 070ms
And Click button advice in transport table "DELIVERY" 101ms
And Set advice window in schedule 3s 010ms
And Fill advice form 10s 711ms
And Click advice save button and wait for advice form to disappear 31s 297ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 509ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 232ms
And Go to transport details "DELIVERY" 2s 450ms
And Expand advice panel 232ms
Then Check are transport values equals 2s 135ms
After Hooks.deleteTransportAfterApiTest() 150ms
After Hooks.rollbackSettings() 024ms