Project Number Date
ApolloFullRunnerReport 2021.AT1.66 19 sie 2021, 05:10

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 30s 768ms Passed
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 006ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 126ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 2s 286ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 347ms
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" 128ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 1s 050ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 216ms
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" 133ms
When Wait "15" seconds 15s
And Get updated transports in "15" time for api version "v1" and expect status "404" 048ms
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" 462ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 084ms
And Check if the updated transports response contains created transport 012ms
After Hooks.deleteTransportAfterApiTest() 109ms
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_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 341ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 086ms
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" 104ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 381ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 079ms
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" 334ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 081ms
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" 318ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 087ms
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
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 347ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 086ms
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" 102ms
And Set token of apiUsername "super-admin-piast" 110ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 924ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 097ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 320ms
Then Login as "super-admin-piast" 2s 690ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 165ms
After Hooks.deleteTransportAfterApiTest() 123ms
After Hooks.rollbackSettings() 063ms
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" 102ms
And Set token of apiUsername "super-admin-piast" 104ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 040ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 028ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 382ms
Then Login as "super-admin-piast" 1s 173ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 141ms
After Hooks.deleteTransportAfterApiTest() 101ms
After Hooks.rollbackSettings() 028ms
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" 099ms
And 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: "ERP_IDENTIFIER" with "super-admin-piast" 022ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 385ms
Then Login as "super-admin-piast" 1s 058ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 138ms
After Hooks.deleteTransportAfterApiTest() 113ms
After Hooks.rollbackSettings() 025ms
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" 105ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 327ms
And Find active transports for api version "v1" and expect status "200" 061ms
Then Check if active transports contains created transport 006ms
After Hooks.deleteTransportAfterApiTest() 073ms
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" 024ms
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" 317ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 553ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 076ms
After Hooks.rollbackSettings() 026ms
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" 030ms
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" 101ms
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_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 171ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 081ms
After Hooks.rollbackSettings() 028ms
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" 033ms
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" 105ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 302ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 128ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 071ms
After Hooks.rollbackSettings() 022ms
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" 035ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 023ms
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" 288ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 006ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 061ms
After Hooks.rollbackSettings() 025ms
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" 028ms
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" 096ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 294ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 044ms
After Hooks.deleteTransportAfterApiTest() 067ms
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" 030ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 023ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 513ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 319ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 014ms
And Show all transport types 1s 067ms
And Click button advice in transport table "DELIVERY" 095ms
And Set advice window in schedule 2s 896ms
And Fill advice form 10s 759ms
And Click advice save button and wait for advice form to disappear 31s 286ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 517ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 254ms
And Go to transport details "DELIVERY" 2s 630ms
And Expand advice panel 113ms
Then Check are transport values equals 2s 140ms
After Hooks.deleteTransportAfterApiTest() 139ms
After Hooks.rollbackSettings() 026ms