Project Number Date
ApolloFullRunnerReport apollo-test-2.90 22 lip 2021, 06:11

Feature Report

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 2m 29s 795ms Passed
Feature API Transport
Before Hooks.showScenarioName(Scenario) 005ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 283ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 6s 512ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Nieprawidłowe wartości w polu orderInTransport" 018ms
Before Hooks.showScenarioName(Scenario) 006ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 327ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 861ms
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" 010ms
Before Hooks.showScenarioName(Scenario) 005ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 271ms
When Create transport by invalid JSON file "CREATE_LOAD_STEP_TYPE_NAME_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 775ms
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" 009ms
Before Hooks.showScenarioName(Scenario) 005ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 254ms
When Create transport by invalid JSON file "CREATE_LOAD_STEP_TYPE_NAME_EMPTY" as "super-admin-piast" for api version "v1" 783ms
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" 006ms
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 260ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 772ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Nieprawidłowe wartości w polu orderInTransport" 008ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 260ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 764ms
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" 009ms
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 257ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_COUNTRY_CODE_INCORRECT" as "super-admin-piast" for api version "v1" 791ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny kod kraju" 008ms
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 290ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_EMPTY" as "super-admin-piast" for api version "v1" 788ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny adres" 010ms
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 254ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_RECIPIENT_EMPTY" as "super-admin-piast" for api version "v1" 680ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny adres" 007ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 230ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_POSTAL_EMPTY" as "super-admin-piast" for api version "v1" 752ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny adres" 007ms
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 292ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_CITY_EMPTY" as "super-admin-piast" for api version "v1" 741ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny adres" 008ms
Before Hooks.showScenarioName(Scenario) 014ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 241ms
When Create transport by invalid JSON file "CREATE_LOAD_ADDRESS_STREET_EMPTY" as "super-admin-piast" for api version "v1" 734ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawny adres" 007ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 246ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_INCORRECT_VALUES" as "super-admin-piast" for api version "v1" 758ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Nieprawidłowe wartości w polu orderInTransport" 007ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 232ms
When Create transport by invalid JSON file "CREATE_LOAD_ORDER_IN_TRANSPORT_EMPTY" as "super-admin-piast" for api version "v1" 696ms
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" 006ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 248ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_EMPTY" as "super-admin-piast" for api version "v1" 790ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawne dane firmy" 008ms
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 244ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_EMPTY" as "super-admin-piast" for api version "v1" 897ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Niepoprawne dane firmy" 008ms
Before Hooks.showScenarioName(Scenario) 003ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 279ms
When Create transport by invalid JSON file "CREATE_LOAD_QUANTITY_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 806ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł quantity musi być poprawną liczbą" 006ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 256ms
When Create transport by invalid JSON file "CREATE_LOAD_VOLUME_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 714ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł volume musi być poprawną liczbą" 007ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 238ms
When Create transport by invalid JSON file "CREATE_LOAD_WEIGHT_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 720ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł weight musi być poprawną liczbą" 006ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 263ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 818ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł company.id musi być liczbą całkowitą" 007ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 252ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 710ms
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
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 244ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_IDX_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 714ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł warehouse.idx musi być liczbą całkowitą" 006ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 350ms
When Create transport by invalid JSON file "CREATE_LOAD_MIN_ADVICE_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 721ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł minAdviceDate musi byd poprawną datą" 005ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 245ms
When Create transport by invalid JSON file "CREATE_LOAD_MAX_ADVICE_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 689ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł maxAdviceDate musi być poprawną datą" 006ms
Before Hooks.showScenarioName(Scenario) 002ms
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_ARRIVAL_DATE_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 800ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł arrivalDate musi być poprawną datą" 007ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 249ms
When Create transport by invalid JSON file "CREATE_LOAD_STEP_PACKAGE_TYPES_ID_INCORRECT_DATA_TYPE" as "super-admin-piast" for api version "v1" 751ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Węzeł stepPackageType.id musi być liczbą całkowitą" 007ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 272ms
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" 712ms
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
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 237ms
When Create transport by invalid JSON file "CREATE_LOAD_NO_ADDRESS_AND_WAREHOUSE_IN_ONE_STEP" as "super-admin-piast" for api version "v1" 671ms
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" 005ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 253ms
When Create transport by invalid JSON file "CREATE_DELIVERY_NO_WAREHOUSE_IN_ONLY_STEP" as "super-admin-piast" for api version "v1" 553ms
Then Check if response status code equals "422" 000ms
And Check if response message contains "Magazyn jest wymagany w zleceniu jednoetapowym" 006ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 241ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_ID_FILLED_ONLY" as "super-admin-piast" for api version "v1" 2s 720ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 932ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 257ms
When Create transport by invalid JSON file "CREATE_LOAD_COMPANY_SHORTNAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 573ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 616ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 251ms
When Create transport by invalid JSON file "CREATE_LOAD_WAREHOUSE_NAME_FILLED_ONLY" as "super-admin-piast" for api version "v1" 1s 554ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 614ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 258ms
And Set token of apiUsername "super-admin-piast" 234ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 234ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ID" with "super-admin-piast" 028ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 539ms
Then Login as "super-admin-piast" 7s 969ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 388ms
After Hooks.deleteTransportAfterApiTest() 658ms
After Hooks.rollbackSettings() 001ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 252ms
And Set token of apiUsername "super-admin-piast" 235ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 166ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ALT_IDENTIFIER" with "super-admin-piast" 030ms
When Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 445ms
Then Login as "super-admin-piast" 2s 285ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 367ms
After Hooks.deleteTransportAfterApiTest() 704ms
After Hooks.rollbackSettings() 000ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 258ms
And Set token of apiUsername "super-admin-piast" 233ms
And Get setting "TRANSPORT_IDENTIFIER_TYPE" for "piast" 156ms
And Prepare setting: "TRANSPORT_IDENTIFIER_TYPE" with value: "ERP_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" 1s 492ms
Then Login as "super-admin-piast" 2s 238ms
And Check is transport "DELIVERY" created in transport table and set transport id 1s 358ms
After Hooks.deleteTransportAfterApiTest() 588ms
After Hooks.rollbackSettings() 000ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 237ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 411ms
And Find active transports for api version "v1" and expect status "200" 317ms
Then Check if active transports contains created transport 010ms
After Hooks.deleteTransportAfterApiTest() 643ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 239ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 498ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "none" for api version "v1" 2s 795ms
Then Check if response status code equals "200" 000ms
After Hooks.deleteTransportAfterApiTest() 670ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 272ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 466ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY_EMPTY_STEP_TYPE_NAME" as "super-admin-piast" with "none" for api version "v1" 844ms
Then Check if response status code equals "422" 000ms
After Hooks.deleteTransportAfterApiTest() 761ms
Before Hooks.showScenarioName(Scenario) 002ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 263ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 553ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidTransportId" for api version "v1" 355ms
Then Check if response status code equals "404" 000ms
After Hooks.deleteTransportAfterApiTest() 675ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 249ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 446ms
When Edit transport by API-validation JSON file "EDIT_DELIVERY" as "super-admin-piast" with "invalidToken" for api version "v1" 033ms
Then Check if response status code equals "401" 000ms
After Hooks.deleteTransportAfterApiTest() 660ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login by Api as "super-admin-piast" and get token and expect status "200" 261ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 415ms
And Verify that custom fields from API are equivalent to custom fields from "CREATE_DELIVERY" as "super-admin-piast" 246ms
After Hooks.deleteTransportAfterApiTest() 649ms
Before Hooks.showScenarioName(Scenario) 001ms
Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 6s 373ms
And Create transport by JSON file "CREATE_DELIVERY" as "super-admin-piast" for api version "v1" and expect status "200" 1s 517ms
And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 2s 793ms
And Show all transport types 1s 154ms
And Click button advice in transport table "DELIVERY" 217ms
And Set advice window in schedule 3s 853ms
And Fill advice form 10s 725ms
And Click advice save button and wait for advice form to disappear 33s 844ms
When Edit transport by JSON file "EDIT_DELIVERY" as "super-admin-piast" for api version "v1" 5s 377ms
And Check if response status code equals "200" 000ms
And Go to "TRANSPORT_TABLE" 473ms
And Go to transport details "DELIVERY" 2s 938ms
Then Check are transport values equals 505ms
After Hooks.deleteTransportAfterTest() 1s 099ms