Project Number Date
ApolloFullRunnerReport apollo-test-2.78 13 lip 2021, 05:31

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 20s 115ms Passed
View Feature API Transport
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_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 503ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 126ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 123ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 483ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 099ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 123ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 466ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 112ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 120ms
And Set token of apiUsername "super-admin-piast" 125ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 102ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 032ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 399ms
Then Login as "super-admin-piast" 3s 425ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 410ms
After Hooks.deleteTransportAfterApiTest() 107ms
After Hooks.rollbackSettings() 002ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 131ms
And Set token of apiUsername "super-admin-piast" 118ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 074ms
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" 433ms
Then Login as "super-admin-piast" 1s 996ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 377ms
After Hooks.deleteTransportAfterApiTest() 136ms
After Hooks.rollbackSettings() 000ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 122ms
And Set token of apiUsername "super-admin-piast" 122ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 067ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 029ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 434ms
Then Login as "super-admin-piast" 2s 070ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 357ms
After Hooks.deleteTransportAfterApiTest() 104ms
After Hooks.rollbackSettings() 000ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 121ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 457ms
And Find active transports for api version "v1" and expect status "200" 064ms
Then Check if active transports contains created transport 006ms
After Hooks.deleteTransportAfterApiTest() 098ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 124ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 402ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 455ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 102ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 121ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 381ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 310ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 091ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 123ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 450ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 165ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 120ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 117ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 411ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 029ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 092ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 121ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 385ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 061ms
After Hooks.deleteTransportAfterApiTest() 101ms