Project Number Date
ApolloFullRunnerReport apollo-test-2.137 29 sie 2021, 05:53

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 2m 28s 954ms 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" 296ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 4s 465ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s 106ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 004ms
Given Login by Api as "super-admin-semmelrock" and get token and expect status "200" 321ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 2s 638ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s 001ms
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" 258ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 186ms
And Check if the updated transports response is empty 013ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 962ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 281ms
And Check if the updated transports response contains created transport 019ms
After Hooks.deleteTransportAfterApiTest() 724ms
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" 226ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 821ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 593ms
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" 315ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 965ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 589ms
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" 254ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 821ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 568ms
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" 247ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 805ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 589ms
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" 243ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 871ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 563ms
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" 233ms
And Set token of apiUsername "super-admin-piast" 235ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 527ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 251ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 769ms
Then Login as "super-admin-piast" 5s 350ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 389ms
After Hooks.deleteTransportAfterApiTest() 715ms
After Hooks.rollbackSettings() 175ms
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" 256ms
And Set token of apiUsername "super-admin-piast" 261ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 193ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 193ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 772ms
Then Login as "super-admin-piast" 2s 540ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 387ms
After Hooks.deleteTransportAfterApiTest() 638ms
After Hooks.rollbackSettings() 134ms
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" 244ms
And Set token of apiUsername "super-admin-piast" 235ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 122ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 729ms
Then Login as "super-admin-piast" 2s 699ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 403ms
After Hooks.deleteTransportAfterApiTest() 678ms
After Hooks.rollbackSettings() 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" 238ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 727ms
And Find active transports for api version "v1" and expect status "200" 302ms
Then Check if active transports contains created transport 007ms
After Hooks.deleteTransportAfterApiTest() 654ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 243ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 155ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 158ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 246ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 717ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 957ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 756ms
After Hooks.rollbackSettings() 137ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 240ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 144ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 169ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 241ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 711ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 908ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 630ms
After Hooks.rollbackSettings() 137ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 240ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 135ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 161ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 219ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 683ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 339ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 670ms
After Hooks.rollbackSettings() 146ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 247ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 146ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 176ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 252ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 747ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 033ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 676ms
After Hooks.rollbackSettings() 133ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 237ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 145ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 161ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 241ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 729ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 317ms
After Hooks.deleteTransportAfterApiTest() 715ms
After Hooks.rollbackSettings() 127ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 242ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 148ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 140ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 3s 192ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 651ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 008ms
And Show all transport types 1s 159ms
And Click button advice in transport table "DELIVERY" 282ms
And Set advice window in schedule 3s 856ms
And Fill advice form 13s 351ms
And Click advice save button and wait for advice form to disappear 33s 864ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 3s 088ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 458ms
And Go to transport details "DELIVERY" 2s 943ms
And Expand advice panel 711ms
Then Check are transport values equals 2s 505ms
After Hooks.deleteTransportAfterApiTest() 869ms
After Hooks.rollbackSettings() 147ms