Project Number Date
ApolloFullRunnerReport 2021.AT1.65 18 sie 2021, 03:49

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 30s 610ms 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" 135ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 2s 153ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 334ms
View Feature API Transport
@deleteTransportAfterApiTest
Before Hooks.showScenarioName(Scenario) 005ms
Given Login by Api as "super-admin-semmelrock" and get token and expect status "200" 130ms
When Create transport by JSON file "CREATE_LOADING" as "super-admin-semmelrock" for api version "v1" and expect status "200" 939ms
Then Check if the user has created a transport 000ms
After Hooks.deleteTransportAfterApiTest() 258ms
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" 111ms
When Wait "15" seconds 15s 001ms
And Get updated transports in "15" time for api version "v1" and expect status "404" 079ms
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" 412ms
Then Get updated transports in "15" time for api version "v1" and expect status "200" 146ms
And Check if the updated transports response contains created transport 019ms
After Hooks.deleteTransportAfterApiTest() 114ms
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" 095ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 359ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 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" 105ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 431ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 088ms
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" 100ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 381ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 077ms
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" 097ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 325ms
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" 099ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_FILLED_ONLY" as "super-admin-piast" for api version "v1" 374ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 094ms
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" 099ms
And Set token of apiUsername "super-admin-piast" 098ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 935ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 079ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 339ms
Then Login as "super-admin-piast" 2s 658ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 139ms
After Hooks.deleteTransportAfterApiTest() 095ms
After Hooks.rollbackSettings() 061ms
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" 100ms
And Set token of apiUsername "super-admin-piast" 099ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 039ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 025ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 348ms
Then Login as "super-admin-piast" 1s 161ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 146ms
After Hooks.deleteTransportAfterApiTest() 106ms
After Hooks.rollbackSettings() 028ms
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" 095ms
And Set token of apiUsername "super-admin-piast" 090ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 034ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 024ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 375ms
Then Login as "super-admin-piast" 1s 101ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 135ms
After Hooks.deleteTransportAfterApiTest() 093ms
After Hooks.rollbackSettings() 021ms
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" 127ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 361ms
And Find active transports for api version "v1" and expect status "200" 056ms
Then Check if active transports contains created transport 005ms
After Hooks.deleteTransportAfterApiTest() 077ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 002ms
Given 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: "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" 328ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 440ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 064ms
After Hooks.rollbackSettings() 027ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 095ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 033ms
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" 111ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 314ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 166ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 087ms
After Hooks.rollbackSettings() 028ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 116ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 033ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 029ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 095ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 293ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 133ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 067ms
After Hooks.rollbackSettings() 025ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 087ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 033ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 029ms
And Login by Api as "super-admin-piast" and get token and expect status "200" 094ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 333ms
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() 081ms
After Hooks.rollbackSettings() 024ms
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" 032ms
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" 093ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 353ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 045ms
After Hooks.deleteTransportAfterApiTest() 069ms
After Hooks.rollbackSettings() 027ms
View Feature API Transport
@deleteTransportAfterApiTest @rollbackSettings
Before Hooks.showScenarioName(Scenario) 001ms
Given Set token of apiUsername "super-admin-piast" 092ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 029ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 022ms
And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 516ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 299ms
And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 017ms
And Show all transport types 1s 058ms
And Click button advice in transport table "DELIVERY" 102ms
And Set advice window in schedule 2s 948ms
And Fill advice form 10s 745ms
And Click advice save button and wait for advice form to disappear 31s 276ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 523ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 237ms
And Go to transport details "DELIVERY" 2s 586ms
And Expand advice panel 105ms
Then Check are transport values equals 2s 139ms
After Hooks.deleteTransportAfterApiTest() 135ms
After Hooks.rollbackSettings() 028ms