Project Number Date
ApolloFullRunnerReport apollo-test-2.64 01 lip 2021, 04:35

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@deleteTransportAfterApiTest 55 1 0 0 0 56 12 1 13 48s 717ms Failed
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 444ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 2s 897ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 1s 176ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 293ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 607ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 728ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 239ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 602ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 722ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 274ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 478ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 711ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 242ms
And Set token of apiUsername "super-admin-piast" 254ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 248ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" 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" 1s 373ms
Then Login as "super-admin-piast" 10s 256ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 552ms
After Hooks.deleteTransportAfterApiTest() 1s 050ms
After Hooks.rollbackSettings() 002ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 246ms
And Set token of apiUsername "super-admin-piast" 232ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 204ms
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" 1s 412ms
Then Login as "super-admin-piast" 2s 560ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 379ms
After Hooks.deleteTransportAfterApiTest() 713ms
After Hooks.rollbackSettings() 000ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 245ms
And Set token of apiUsername "super-admin-piast" 229ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 164ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 023ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 306ms
Then Login as "super-admin-piast" 2s 647ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 350ms
After Hooks.deleteTransportAfterApiTest() 792ms
After Hooks.rollbackSettings() 000ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 230ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 350ms
And Find active transports for api version "v1" and expect status "200" 276ms
Then Check if active transports contains created transport 011ms
After Hooks.deleteTransportAfterApiTest() 887ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 231ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 269ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 2s 814ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 737ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 235ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 326ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 726ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 750ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 267ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 292ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 360ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 781ms
View Feature API Transport
Given Login by Api as "super-admin-piast" and get token and expect status "200" 254ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 265ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 072ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 754ms
View Feature API Transport
Scenario Outline Check if custom fields map is correct after creating a transport by Public API [A-7508]
Steps
Given Login by Api as "super-admin-piast" and get token and expect status "200" 286ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 380ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 242ms
java.lang.NullPointerException
	at Utils.JsonApiUtil.getMapOfNodeFromJSON(JsonApiUtil.java:478)
	at CucumberTests.Api.ApiTransportTest.checkIfAPICustomFieldsAreCorrect(ApiTransportTest.java:170)
	at ✽.Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast"(file:Features/Api/Transport.feature:144)
After Hooks.deleteTransportAfterApiTest() 719ms