Project Number Date
ApolloFullRunnerReport 2021.AT1.56 11 sie 2021, 05:39

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@deleteTransportAfterApiTest 101 0 0 0 0 101 17 0 17 1m 34s 848ms Passed
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" 122ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 2s 239ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 346ms
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" 118ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 108ms
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" 486ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 132ms
And Check if the updated transports response contains created transport 012ms
After Hooks.deleteTransportAfterApiTest() 159ms
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" 100ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 405ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 098ms
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" 102ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 433ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 090ms
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" 103ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 343ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 086ms
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" 102ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 411ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 091ms
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" 101ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 357ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 081ms
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" 104ms
And Set token of apiUsername "super-admin-piast" 099ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 925ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 083ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 351ms
Then Login as "super-admin-piast" 2s 832ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 147ms
After Hooks.deleteTransportAfterApiTest() 090ms
After Hooks.rollbackSettings() 064ms
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" 102ms
And Set token of apiUsername "super-admin-piast" 097ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 034ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 026ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 332ms
Then Login as "super-admin-piast" 1s 118ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 134ms
After Hooks.deleteTransportAfterApiTest() 107ms
After Hooks.rollbackSettings() 029ms
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" 100ms
And Set token of apiUsername "super-admin-piast" 105ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 031ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 022ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 379ms
Then Login as "super-admin-piast" 1s 031ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 140ms
After Hooks.deleteTransportAfterApiTest() 103ms
After Hooks.rollbackSettings() 028ms
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" 100ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 343ms
And Find active transports for api version "v1" and expect status "200" 065ms
Then Check if active transports contains created transport 007ms
After Hooks.deleteTransportAfterApiTest() 073ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 097ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 038ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 025ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 101ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 338ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 535ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 082ms
After Hooks.rollbackSettings() 043ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 107ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 031ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 025ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 097ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 316ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 165ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 088ms
After Hooks.rollbackSettings() 027ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 097ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 038ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 030ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 096ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 317ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 115ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 087ms
After Hooks.rollbackSettings() 023ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 091ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 032ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 020ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 092ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 307ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 008ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 072ms
After Hooks.rollbackSettings() 026ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 098ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 034ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 024ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 100ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 342ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 050ms
After Hooks.deleteTransportAfterApiTest() 086ms
After Hooks.rollbackSettings() 030ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 102ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 030ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 025ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 727ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 293ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 4s 692ms
And Show all transport types 1s 066ms
And Click button advice in transport table "DELIVERY" 104ms
And Set advice window in schedule 3s 017ms
And Fill advice form 10s 748ms
And Click advice save button and wait for advice form to disappear 31s 266ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 549ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 225ms
And Go to transport details "DELIVERY" 2s 440ms
And Expand advice panel 226ms
Then Check are transport values equals 2s 128ms
After Hooks.deleteTransportAfterApiTest() 116ms
After Hooks.rollbackSettings() 026ms