Project Number Date
ApolloFullRunnerReport apollo-test-2.124 19 sie 2021, 06:07

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 31s 868ms Passed
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 005ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 252ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 3s 981ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s
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 728ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 968ms
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" 271ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 139ms
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 888ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 287ms
And Check if the updated transports response contains created transport 018ms
After Hooks.deleteTransportAfterApiTest() 731ms
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" 234ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 698ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 596ms
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" 258ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 895ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 620ms
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" 237ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 689ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 595ms
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" 234ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 663ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 586ms
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_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 714ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 593ms
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" 228ms
And Set token of apiUsername "super-admin-piast" 232ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 236ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 230ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 563ms
Then Login as "super-admin-piast" 7s 311ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 467ms
After Hooks.deleteTransportAfterApiTest() 653ms
After Hooks.rollbackSettings() 187ms
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" 245ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 143ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 147ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 592ms
Then Login as "super-admin-piast" 2s 482ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 383ms
After Hooks.deleteTransportAfterApiTest() 650ms
After Hooks.rollbackSettings() 139ms
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" 228ms
And Set token of apiUsername "super-admin-piast" 249ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 125ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 129ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 584ms
Then Login as "super-admin-piast" 2s 450ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 379ms
After Hooks.deleteTransportAfterApiTest() 659ms
After Hooks.rollbackSettings() 109ms
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" 249ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 577ms
And Find active transports for api version "v1" and expect status "200" 271ms
Then Check if active transports contains created transport 006ms
After Hooks.deleteTransportAfterApiTest() 630ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 241ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 145ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 153ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 245ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 603ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 791ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 668ms
After Hooks.rollbackSettings() 140ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 267ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 146ms
And 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 588ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 832ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 637ms
After Hooks.rollbackSettings() 133ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 262ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 152ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 164ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 236ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 587ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 337ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 645ms
After Hooks.rollbackSettings() 132ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 251ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 170ms
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 578ms
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() 638ms
After Hooks.rollbackSettings() 143ms
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" 156ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 144ms
And 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 569ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 264ms
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" 248ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 134ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 156ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 040ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 581ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 2s 746ms
And Show all transport types 1s 163ms
And Click button advice in transport table "DELIVERY" 237ms
And Set advice window in schedule 3s 776ms
And Fill advice form 13s 370ms
And Click advice save button and wait for advice form to disappear 33s 891ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 518ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 456ms
And Go to transport details "DELIVERY" 2s 900ms
And Expand advice panel 591ms
Then Check are transport values equals 2s 402ms
After Hooks.deleteTransportAfterApiTest() 916ms
After Hooks.rollbackSettings() 145ms