Project Number Date
ApolloFullRunnerReport apollo-test-2.148 07 wrz 2021, 06:21

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 32s 734ms Passed
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 009ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 277ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 4s 416ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s 123ms
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" 357ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 2s 649ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s 012ms
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" 250ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 155ms
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 934ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 283ms
And Check if the updated transports response contains created transport 013ms
After Hooks.deleteTransportAfterApiTest() 709ms
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" 252ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 852ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 598ms
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
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 945ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 604ms
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_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 881ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 599ms
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_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 799ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 583ms
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 807ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 584ms
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" 248ms
And Set token of apiUsername "super-admin-piast" 242ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 289ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 247ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 695ms
Then Login as "super-admin-piast" 7s 043ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 423ms
After Hooks.deleteTransportAfterApiTest() 568ms
After Hooks.rollbackSettings() 178ms
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" 241ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 138ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 161ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 716ms
Then Login as "super-admin-piast" 2s 482ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 359ms
After Hooks.deleteTransportAfterApiTest() 681ms
After Hooks.rollbackSettings() 128ms
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" 241ms
And Set token of apiUsername "super-admin-piast" 243ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 163ms
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 721ms
Then Login as "super-admin-piast" 2s 515ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 382ms
After Hooks.deleteTransportAfterApiTest() 672ms
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" 248ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 757ms
And Find active transports for api version "v1" and expect status "200" 306ms
Then Check if active transports contains created transport 007ms
After Hooks.deleteTransportAfterApiTest() 644ms
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" 142ms
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" 250ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 714ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 2s 038ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 662ms
After Hooks.rollbackSettings() 157ms
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" 140ms
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" 244ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 744ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 892ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 655ms
After Hooks.rollbackSettings() 134ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 257ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 142ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 157ms
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 682ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 340ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 639ms
After Hooks.rollbackSettings() 141ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 263ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 146ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 195ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 230ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 742ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 027ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 657ms
After Hooks.rollbackSettings() 140ms
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" 137ms
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" 248ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 645ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 258ms
After Hooks.deleteTransportAfterApiTest() 615ms
After Hooks.rollbackSettings() 127ms
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" 127ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 158ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 536ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 740ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 008ms
And Show all transport types 1s 191ms
And Click button advice in transport table "DELIVERY" 268ms
And Set advice window in schedule 3s 897ms
And Fill advice form 13s 335ms
And Click advice save button and wait for advice form to disappear 33s 854ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 692ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 557ms
And Go to transport details "DELIVERY" 3s
And Expand advice panel 561ms
Then Check are transport values equals 2s 363ms
After Hooks.deleteTransportAfterApiTest() 829ms
After Hooks.rollbackSettings() 138ms