Project Number Date
ApolloFullRunnerReport 2021.AT1.64 17 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 204ms Passed
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 007ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 138ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 2s 405ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 386ms
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" 118ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 984ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 275ms
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" 126ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 063ms
And Check if the updated transports response is empty 014ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 497ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 093ms
And Check if the updated transports response contains created transport 013ms
After Hooks.deleteTransportAfterApiTest() 132ms
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_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 353ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 093ms
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" 097ms
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() 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" 099ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 367ms
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" 100ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 342ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 094ms
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" 355ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 088ms
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" 101ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 979ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 079ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 347ms
Then Login as "super-admin-piast" 2s 669ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 141ms
After Hooks.deleteTransportAfterApiTest() 080ms
After Hooks.rollbackSettings() 054ms
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" 118ms
And Set token of apiUsername "super-admin-piast" 101ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 031ms
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" 311ms
Then Login as "super-admin-piast" 1s 054ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 140ms
After Hooks.deleteTransportAfterApiTest() 091ms
After Hooks.rollbackSettings() 033ms
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" 108ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 042ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 020ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 310ms
Then Login as "super-admin-piast" 1s 084ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 145ms
After Hooks.deleteTransportAfterApiTest() 103ms
After Hooks.rollbackSettings() 018ms
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" 360ms
And Find active transports for api version "v1" and expect status "200" 065ms
Then Check if active transports contains created transport 007ms
After Hooks.deleteTransportAfterApiTest() 078ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 104ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 034ms
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" 098ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 314ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 467ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 076ms
After Hooks.rollbackSettings() 027ms
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" 031ms
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" 102ms
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_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 176ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 073ms
After Hooks.rollbackSettings() 023ms
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" 033ms
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" 098ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 331ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 124ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 078ms
After Hooks.rollbackSettings() 023ms
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" 031ms
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" 095ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 297ms
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() 074ms
After Hooks.rollbackSettings() 023ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 104ms
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" 097ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 304ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 042ms
After Hooks.deleteTransportAfterApiTest() 070ms
After Hooks.rollbackSettings() 023ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 094ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 026ms
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 483ms
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 623ms
And Show all transport types 1s 075ms
And Click button advice in transport table "DELIVERY" 090ms
And Set advice window in schedule 2s 929ms
And Fill advice form 10s 704ms
And Click advice save button and wait for advice form to disappear 31s 250ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 552ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 259ms
And Go to transport details "DELIVERY" 2s 459ms
And Expand advice panel 220ms
Then Check are transport values equals 2s 128ms
After Hooks.deleteTransportAfterApiTest() 099ms
After Hooks.rollbackSettings() 025ms