Project Number Date
ApolloFullRunnerReport apollo-test-2.132 25 sie 2021, 05:54

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 123ms 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" 295ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 4s 726ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s 068ms
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" 287ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 2s 610ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s 042ms
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" 272ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 150ms
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" 1s 873ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 300ms
And Check if the updated transports response contains created transport 011ms
After Hooks.deleteTransportAfterApiTest() 694ms
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" 236ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 903ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 630ms
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" 248ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 960ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 600ms
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" 240ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 799ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 587ms
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" 241ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 827ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 588ms
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" 235ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 843ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 575ms
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" 239ms
And Set token of apiUsername "super-admin-piast" 240ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 118ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 234ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 750ms
Then Login as "super-admin-piast" 5s 293ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 438ms
After Hooks.deleteTransportAfterApiTest() 683ms
After Hooks.rollbackSettings() 186ms
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" 237ms
And Set token of apiUsername "super-admin-piast" 245ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 156ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 807ms
Then Login as "super-admin-piast" 2s 550ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 359ms
After Hooks.deleteTransportAfterApiTest() 658ms
After Hooks.rollbackSettings() 139ms
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" 236ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 162ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 119ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 725ms
Then Login as "super-admin-piast" 2s 524ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 394ms
After Hooks.deleteTransportAfterApiTest() 662ms
After Hooks.rollbackSettings() 099ms
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" 259ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 685ms
And Find active transports for api version "v1" and expect status "200" 281ms
Then Check if active transports contains created transport 008ms
After Hooks.deleteTransportAfterApiTest() 655ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 244ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 138ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 165ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 243ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 705ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 946ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 653ms
After Hooks.rollbackSettings() 146ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 257ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 137ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 184ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 244ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 678ms
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() 619ms
After Hooks.rollbackSettings() 137ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 246ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 140ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 163ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 242ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 718ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 346ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 625ms
After Hooks.rollbackSettings() 135ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 282ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 159ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 171ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 253ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 763ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 028ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 683ms
After Hooks.rollbackSettings() 123ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 268ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 149ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 258ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 716ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 281ms
After Hooks.deleteTransportAfterApiTest() 574ms
After Hooks.rollbackSettings() 116ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 228ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 151ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 3s 081ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 627ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 009ms
And Show all transport types 1s 171ms
And Click button advice in transport table "DELIVERY" 221ms
And Set advice window in schedule 4s 002ms
And Fill advice form 13s 465ms
And Click advice save button and wait for advice form to disappear 34s 014ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 741ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 481ms
And Go to transport details "DELIVERY" 2s 968ms
And Expand advice panel 694ms
Then Check are transport values equals 2s 409ms
After Hooks.deleteTransportAfterApiTest() 920ms
After Hooks.rollbackSettings() 131ms