Cucumber-JVM Reports - Feature: API Transport

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.12	25 Jul 2021, 06:02

	Steps	Scenarios	Features
API Transport	182	0	0	0	0	182	42	0	42	1m 26s 635ms	Passed

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 005ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 115ms

When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 2s 103ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Nieprawidłowe wartości w polu orderInTransport" 010ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 004ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 116ms

When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 434ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Brak wartości w polu orderInTransport, pole jest obowiązkowe" 007ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 003ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 121ms

When Create transport by invalid JSON file "CREATE_LOAD_STEP_TYPE_NAME_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 381ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Niepoprawna wartość w polu stepTypeName. Poprawne wartości to: load, unload" 008ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 128ms

When Create transport by invalid JSON file "CREATE_LOAD_STEP_TYPE_NAME_EMPTY" as "super-admin-piast" for api version "v1" 408ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Brak wartości w polu stepTypeName, pole jest obowiązkowe" 007ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 107ms

When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 392ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Nieprawidłowe wartości w polu orderInTransport" 008ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 111ms

When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 379ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Brak wartości w polu orderInTransport, pole jest obowiązkowe" 004ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 112ms

When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_COUNTRY_CODE_INCORRECT" as "super-admin-piast" for api version "v1" 436ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Niepoprawny kod kraju" 006ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 113ms

When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_EMPTY" as "super-admin-piast" for api version "v1" 402ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Niepoprawny adres" 010ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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_ADDRESS_RECIPIENT_EMPTY" as "super-admin-piast" for api version "v1" 389ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Niepoprawny adres" 007ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 111ms

When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_POSTAL_EMPTY" as "super-admin-piast" for api version "v1" 391ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Niepoprawny adres" 008ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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_ADDRESS_CITY_EMPTY" as "super-admin-piast" for api version "v1" 367ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Niepoprawny adres" 007ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 016ms

Steps

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_ADDRESS_STREET_EMPTY" as "super-admin-piast" for api version "v1" 382ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Niepoprawny adres" 006ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 004ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 111ms

When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 481ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Nieprawidłowe wartości w polu orderInTransport" 007ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 117ms

When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 369ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Brak wartości w polu orderInTransport, pole jest obowiązkowe" 007ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 098ms

When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_EMPTY" as "super-admin-piast" for api version "v1" 312ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Niepoprawne dane firmy" 006ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 098ms

When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_EMPTY" as "super-admin-piast" for api version "v1" 463ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Niepoprawne dane firmy" 009ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 003ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 165ms

When Create transport by invalid JSON file "CREATE_LOAD_QUANTITY_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 488ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł quantity musi być poprawną liczbą" 005ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 003ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 108ms

When Create transport by invalid JSON file "CREATE_LOAD_VOLUME_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 374ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł volume musi być poprawną liczbą" 004ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 103ms

When Create transport by invalid JSON file "CREATE_LOAD_WEIGHT_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 321ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł weight musi być poprawną liczbą" 005ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 382ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł company.id musi być liczbą całkowitą" 005ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 361ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł warehouse.id musi być liczbą całkowitą" 005ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 331ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł warehouse.idx musi być liczbą całkowitą" 004ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 104ms

When Create transport by invalid JSON file "CREATE_LOAD_MIN_ADVICE_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 379ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł minAdviceDate musi byd poprawną datą" 004ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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_MAX_ADVICE_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 352ms

Then Check if response status code equals "422" 001ms

And Check if response message contains "Węzeł maxAdviceDate musi być poprawną datą" 005ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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_ARRIVAL_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 355ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł arrivalDate musi być poprawną datą" 005ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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_STEP_PACKAGE_TYPES_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 359ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł stepPackageType.id musi być liczbą całkowitą" 006ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 111ms

When Create transport by invalid JSON file "CREATE_LOAD_STEP_PACKAGE_TYPES_PACKAGE_TYPE_STEP_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 363ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Węzeł stepPackageType.step.id musi być liczbą całkowitą" 007ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 104ms

When Create transport by invalid JSON file "CREATE_LOAD_NO_ADDRESS_AND_WAREHOUSE_IN_ONE_STEP" as "super-admin-piast" for api version "v1" 300ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "W zleceniu wieloetapowym każdy etap musi mieć uzupełniony magazyn lub adres" 006ms

Scenario Outline Check validation message when creating transport with incorrect data in node by Public API [A-7510] [A-7509] [A-7515] [A-7604] [A-7962]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 104ms

When Create transport by invalid JSON file "CREATE_DELIVERY_NO_WAREHOUSE_IN_ONLY_STEP" as "super-admin-piast" for api version "v1" 213ms

Then Check if response status code equals "422" 000ms

And Check if response message contains "Magazyn jest wymagany w zleceniu jednoetapowym" 005ms

@deleteTransportAfterApiTest

Scenario Outline Check if it is possible to create transport with only part of data in company node by Public API [A-7513]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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" 574ms

Then Check if response status code equals "200" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 213ms

@deleteTransportAfterApiTest

Scenario Outline Check if it is possible to create transport with only part of data in company node by Public API [A-7513]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 106ms

When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 492ms

Then Check if response status code equals "200" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 072ms

@deleteTransportAfterApiTest

Scenario Outline Check if it is possible to create transport with only part of data in company node by Public API [A-7513]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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" 472ms

Then Check if response status code equals "200" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 071ms

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it is possible to create transport with different transport identifier type by Public API [A-7523]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 099ms

And Set token of apiUsername "super-admin-piast" 103ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 111ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 009ms

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" 2s 711ms

And Check is transport "DELIVERY" created in transport table and set transport id 1s 149ms

Hooks

After Hooks.deleteTransportAfterApiTest() 076ms

After Hooks.rollbackSettings() 001ms

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it is possible to create transport with different transport identifier type by Public API [A-7523]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 107ms

And Set token of apiUsername "super-admin-piast" 109ms

And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 032ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 003ms

When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 479ms

Then Login as "super-admin-piast" 1s 048ms

And Check is transport "DELIVERY" created in transport table and set transport id 1s 141ms

Hooks

After Hooks.deleteTransportAfterApiTest() 106ms

After Hooks.rollbackSettings() 000ms

@deleteTransportAfterApiTest @rollbackSettings

Scenario Outline Check if it is possible to create transport with different transport identifier type by Public API [A-7523]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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" 024ms

And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_IDENTIFIER" with "super-admin-piast" 001ms

When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 374ms

Then Login as "super-admin-piast" 1s 003ms

And Check is transport "DELIVERY" created in transport table and set transport id 1s 122ms

Hooks

After Hooks.deleteTransportAfterApiTest() 066ms

After Hooks.rollbackSettings() 000ms

@deleteTransportAfterApiTest

Scenario Outline Check if it is possible to get transport list by API

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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" 392ms

And Find active transports for api version "v1" and expect status "200" 107ms

Then Check if active transports contains created transport 007ms

Hooks

After Hooks.deleteTransportAfterApiTest() 076ms

@deleteTransportAfterApiTest

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 108ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 365ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 807ms

Then Check if response status code equals "200" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 081ms

@deleteTransportAfterApiTest

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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" 397ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 069ms

@deleteTransportAfterApiTest

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 102ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 378ms

When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 124ms

Then Check if response status code equals "404" 000ms

Hooks

After Hooks.deleteTransportAfterApiTest() 081ms

@deleteTransportAfterApiTest

Scenario Outline Check if response code contains expected status after editing transport by Api[A-7521]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 098ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 390ms

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

Hooks

After Hooks.deleteTransportAfterApiTest() 109ms

@deleteTransportAfterApiTest

Scenario Outline Check if custom fields map is correct after creating a transport by Public API [A-7508]

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login by Api as "super-admin-piast" and get token and expect status "200" 102ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 411ms

And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 051ms

Hooks

After Hooks.deleteTransportAfterApiTest() 081ms

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by API [A-4167]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 461ms

And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 399ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 4s 810ms

And Show all transport types 1s 058ms

And Click button advice in transport table "DELIVERY" 084ms

And Set advice window in schedule 2s 948ms

And Fill advice form 8s 410ms

And Click advice save button and wait for advice form to disappear 31s 217ms

When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 871ms

And Check if response status code equals "200" 000ms

And Go to "TRANSPORT_TABLE" 234ms

And Go to transport details "DELIVERY" 2s 453ms

Then Check are transport values equals 202ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
API Transport	182	0	0	0	0	182	42	0	42	1m 26s 635ms	Passed

Feature Report