Project Number Date
ApolloFullRunnerReport apollo-test-2.1 17 Jul 2021, 02:42

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@deleteTransportAfterApiTest 53 0 0 0 0 53 12 0 12 16s 899ms Passed
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" 096ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 437ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 093ms
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_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 456ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 093ms
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_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 434ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 074ms
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" 062ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 007ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 380ms
Then Login as "super-admin-piast" 2s 242ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 514ms
After Hooks.deleteTransportAfterApiTest() 087ms
After Hooks.rollbackSettings() 002ms
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" 002ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 425ms
Then Login as "super-admin-piast" 996ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 573ms
After Hooks.deleteTransportAfterApiTest() 078ms
After Hooks.rollbackSettings() 000ms
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" 101ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 031ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 002ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 357ms
Then Login as "super-admin-piast" 982ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 491ms
After Hooks.deleteTransportAfterApiTest() 073ms
After Hooks.rollbackSettings() 000ms
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" 099ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 388ms
And Find active transports for api version "v1" and expect status "200" 878ms
Then Check if active transports contains created transport 086ms
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" 097ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 348ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 414ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 072ms
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" 104ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 370ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 256ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 065ms
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" 344ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 109ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 064ms
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
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 367ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 009ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 073ms
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" 097ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 364ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 030ms
After Hooks.deleteTransportAfterApiTest() 060ms