Project Number Date
ApolloFullRunnerReport apollo-test-2.151 09 wrz 2021, 06:10

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 740ms 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" 296ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 4s 217ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s 198ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 024ms
Given Login by Api as "super-admin-semmelrock" and get token and expect status "200" 352ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 2s 561ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 1s 075ms
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" 308ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 163ms
And Check if the updated transports response is empty 015ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 948ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 284ms
And Check if the updated transports response contains created transport 017ms
After Hooks.deleteTransportAfterApiTest() 704ms
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" 248ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 844ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 588ms
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" 254ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 921ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 577ms
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" 257ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 873ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 616ms
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" 239ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 791ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 556ms
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" 244ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 825ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 586ms
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" 238ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 4s 242ms
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 718ms
Then Login as "super-admin-piast" 7s 520ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 435ms
After Hooks.deleteTransportAfterApiTest() 557ms
After Hooks.rollbackSettings() 166ms
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" 239ms
And Set token of apiUsername "super-admin-piast" 258ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 163ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 711ms
Then Login as "super-admin-piast" 2s 612ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 410ms
After Hooks.deleteTransportAfterApiTest() 677ms
After Hooks.rollbackSettings() 137ms
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" 232ms
And Set token of apiUsername "super-admin-piast" 255ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 136ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 117ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 748ms
Then Login as "super-admin-piast" 2s 450ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 406ms
After Hooks.deleteTransportAfterApiTest() 658ms
After Hooks.rollbackSettings() 100ms
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
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 713ms
And Find active transports for api version "v1" and expect status "200" 296ms
Then Check if active transports contains created transport 008ms
After Hooks.deleteTransportAfterApiTest() 632ms
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" 144ms
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" 242ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 768ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 1s 847ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 664ms
After Hooks.rollbackSettings() 154ms
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" 147ms
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" 235ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 733ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 887ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 666ms
After Hooks.rollbackSettings() 129ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 238ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 141ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 160ms
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 719ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 342ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 635ms
After Hooks.rollbackSettings() 138ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 280ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 158ms
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" 249ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 666ms
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() 661ms
After Hooks.rollbackSettings() 142ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 223ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 133ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 151ms
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 656ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 254ms
After Hooks.deleteTransportAfterApiTest() 628ms
After Hooks.rollbackSettings() 140ms
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" 133ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 168ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 533ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 690ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 008ms
And Show all transport types 1s 158ms
And Click button advice in transport table "DELIVERY" 228ms
And Set advice window in schedule 3s 900ms
And Fill advice form 13s 348ms
And Click advice save button and wait for advice form to disappear 33s 888ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 2s 688ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 486ms
And Go to transport details "DELIVERY" 2s 965ms
And Expand advice panel 598ms
Then Check are transport values equals 2s 367ms
After Hooks.deleteTransportAfterApiTest() 818ms
After Hooks.rollbackSettings() 134ms