Project Number Date
ApolloFullRunnerReport 2021.AT1.61 16 sie 2021, 05:45

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 996ms Passed
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" 141ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 2s 316ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 320ms
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" 116ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 917ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 220ms
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" 114ms
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 010ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 434ms
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 012ms
After Hooks.deleteTransportAfterApiTest() 123ms
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" 349ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 089ms
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" 098ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 399ms
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" 097ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 341ms
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" 112ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 340ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 084ms
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" 132ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 381ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 078ms
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" 096ms
And Set token of apiUsername "super-admin-piast" 099ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 993ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 082ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 343ms
Then Login as "super-admin-piast" 3s 205ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 143ms
After Hooks.deleteTransportAfterApiTest() 091ms
After Hooks.rollbackSettings() 053ms
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" 096ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 035ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 030ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 344ms
Then Login as "super-admin-piast" 1s 065ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 137ms
After Hooks.deleteTransportAfterApiTest() 083ms
After Hooks.rollbackSettings() 034ms
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" 034ms
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" 327ms
Then Login as "super-admin-piast" 1s 317ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 131ms
After Hooks.deleteTransportAfterApiTest() 076ms
After Hooks.rollbackSettings() 019ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 000ms
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" 399ms
And Find active transports for api version "v1" and expect status "200" 078ms
Then Check if active transports contains created transport 006ms
After Hooks.deleteTransportAfterApiTest() 091ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 093ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 027ms
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" 306ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 479ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 076ms
After Hooks.rollbackSettings() 029ms
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" 025ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 111ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 341ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 175ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 081ms
After Hooks.rollbackSettings() 026ms
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" 037ms
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" 096ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 320ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 132ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 077ms
After Hooks.rollbackSettings() 031ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given 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: "ID" with "super-admin-piast" 046ms
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" 308ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 011ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 086ms
After Hooks.rollbackSettings() 025ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 109ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 032ms
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" 099ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 315ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 047ms
After Hooks.deleteTransportAfterApiTest() 080ms
After Hooks.rollbackSettings() 027ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 096ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 025ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 030ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 426ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 312ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 4s 673ms
And Show all transport types 1s 076ms
And Click button advice in transport table "DELIVERY" 100ms
And Set advice window in schedule 2s 920ms
And Fill advice form 10s 693ms
And Click advice save button and wait for advice form to disappear 31s 210ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 576ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 291ms
And Go to transport details "DELIVERY" 2s 602ms
And Expand advice panel 097ms
Then Check are transport values equals 2s 134ms
After Hooks.deleteTransportAfterApiTest() 136ms
After Hooks.rollbackSettings() 029ms