Project Number Date
ApolloFullRunnerReport apollo-test-2.136 28 sie 2021, 05:52

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 27s 030ms Passed
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 008ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 271ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 4s 390ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 921ms
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" 301ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 2s 709ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s 015ms
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" 247ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 144ms
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" 1s 827ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 277ms
And Check if the updated transports response contains created transport 016ms
After Hooks.deleteTransportAfterApiTest() 689ms
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" 233ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 898ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 628ms
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" 243ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 929ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 620ms
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" 231ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 766ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 601ms
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 838ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 590ms
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" 227ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 730ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 583ms
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" 242ms
And Set token of apiUsername "super-admin-piast" 240ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 177ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 289ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 782ms
Then Login as "super-admin-piast" 5s 326ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 428ms
After Hooks.deleteTransportAfterApiTest() 672ms
After Hooks.rollbackSettings() 171ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 236ms
And Set token of apiUsername "super-admin-piast" 268ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 123ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 173ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 699ms
Then Login as "super-admin-piast" 2s 503ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 378ms
After Hooks.deleteTransportAfterApiTest() 674ms
After Hooks.rollbackSettings() 137ms
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" 229ms
And Set token of apiUsername "super-admin-piast" 236ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 147ms
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 700ms
Then Login as "super-admin-piast" 2s 526ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 403ms
After Hooks.deleteTransportAfterApiTest() 727ms
After Hooks.rollbackSettings() 106ms
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" 251ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 707ms
And Find active transports for api version "v1" and expect status "200" 276ms
Then Check if active transports contains created transport 006ms
After Hooks.deleteTransportAfterApiTest() 661ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 246ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 137ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 154ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 234ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 623ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 897ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 663ms
After Hooks.rollbackSettings() 151ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 231ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 144ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 166ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 235ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 694ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 877ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 626ms
After Hooks.rollbackSettings() 144ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 239ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 165ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 168ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 237ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 715ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 331ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 641ms
After Hooks.rollbackSettings() 132ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 253ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 131ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 155ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 247ms
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" as "super-admin-piast" with "invalidToken" for api version "v1" 030ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 644ms
After Hooks.rollbackSettings() 133ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 245ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 132ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 173ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 234ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 627ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 273ms
After Hooks.deleteTransportAfterApiTest() 641ms
After Hooks.rollbackSettings() 127ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 233ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 138ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 163ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 3s 033ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 638ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 009ms
And Show all transport types 1s 179ms
And Click button advice in transport table "DELIVERY" 246ms
And Set advice window in schedule 4s 194ms
And Fill advice form 13s 305ms
And Click advice save button and wait for advice form to disappear 33s 944ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 780ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 477ms
And Go to transport details "DELIVERY" 2s 933ms
And Expand advice panel 603ms
Then Check are transport values equals 2s 436ms
After Hooks.deleteTransportAfterApiTest() 904ms
After Hooks.rollbackSettings() 163ms