Project Number Date
ApolloFullRunnerReport 2021.AT1.59 14 sie 2021, 05:45

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 1m 35s 770ms 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" 142ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 2s 137ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 359ms
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" 124ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 850ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 212ms
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" 113ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 068ms
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" 473ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 087ms
And Check if the updated transports response contains created transport 013ms
After Hooks.deleteTransportAfterApiTest() 107ms
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_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 356ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 122ms
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" 114ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 386ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 081ms
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" 101ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 359ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 077ms
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_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 334ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 078ms
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" 120ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 350ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 075ms
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" 1s 024ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 086ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 329ms
Then Login as "super-admin-piast" 3s 104ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 172ms
After Hooks.deleteTransportAfterApiTest() 108ms
After Hooks.rollbackSettings() 112ms
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" 108ms
And Set token of apiUsername "super-admin-piast" 099ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 036ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 027ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 333ms
Then Login as "super-admin-piast" 1s 129ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 151ms
After Hooks.deleteTransportAfterApiTest() 088ms
After Hooks.rollbackSettings() 030ms
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" 096ms
And Set token of apiUsername "super-admin-piast" 102ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 032ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 021ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 338ms
Then Login as "super-admin-piast" 1s 042ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 143ms
After Hooks.deleteTransportAfterApiTest() 097ms
After Hooks.rollbackSettings() 020ms
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" 106ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 327ms
And Find active transports for api version "v1" and expect status "200" 064ms
Then Check if active transports contains created transport 005ms
After Hooks.deleteTransportAfterApiTest() 076ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 101ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 031ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 028ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 111ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 322ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 505ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 074ms
After Hooks.rollbackSettings() 031ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 103ms
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" 104ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 313ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 173ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 075ms
After Hooks.rollbackSettings() 024ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 101ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 032ms
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" 394ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 116ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 081ms
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" 045ms
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" 096ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 298ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 007ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 073ms
After Hooks.rollbackSettings() 024ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given Set token of apiUsername "super-admin-piast" 098ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 032ms
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" 096ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 344ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 079ms
After Hooks.deleteTransportAfterApiTest() 087ms
After Hooks.rollbackSettings() 030ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 108ms
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 as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 595ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 324ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 4s 658ms
And Show all transport types 1s 079ms
And Click button advice in transport table "DELIVERY" 101ms
And Set advice window in schedule 2s 940ms
And Fill advice form 10s 763ms
And Click advice save button and wait for advice form to disappear 31s 257ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 435ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 259ms
And Go to transport details "DELIVERY" 2s 510ms
And Expand advice panel 214ms
Then Check are transport values equals 2s 146ms
After Hooks.deleteTransportAfterApiTest() 149ms
After Hooks.rollbackSettings() 031ms