Cucumber-JVM Reports - Feature: Status confirmation

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.81	15 lip 2021, 06:54

	Steps	Scenarios	Features
Status confirmation	532	1	5	0	0	538	35	1	36	47m 41s 411ms	Failed

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Steps

Given Set token of apiUsername "super-admin-hochland" 233ms

And Get custom field settings for "DELIVERY" transport type and "hochland" company 204ms

And Mark custom fields as not obligatory 2s 833ms

And Login as "hochland-admin" 10s 372ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 039ms

When Find transport in table with status "advice-added" 3s 680ms

And Confirm statuses until reach "process-ended" 21s 928ms

Then Check if transport has "process-ended" 066ms

Hooks

After Hooks.deleteTransportAfterTest() 860ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 495ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Steps

Given Set token of apiUsername "super-admin-pgf" 232ms

And Get custom field settings for "UNLOAD" transport type and "pgf" company 115ms

And Mark custom fields as not obligatory 006ms

And Login as "pgf-admin" 4s 802ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 17s 931ms

When Find transport in table with status "planned" 17s 574ms

And Confirm statuses until reach "process-ended" 13s 544ms

Then Check if transport has "process-ended" 059ms

Hooks

After Hooks.deleteTransportAfterTest() 807ms

After Hooks.rollbackAllCustomFieldsSettings() 449ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Steps

Given Set token of apiUsername "super-admin-adama" 230ms

And Get custom field settings for "DELIVERY" transport type and "adama" company 122ms

And Mark custom fields as not obligatory 005ms

And Login as "adama-admin" 5s 457ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 2s 671ms

When Find transport in table with status "planned" 3s 611ms

And Confirm statuses until reach "process-ended" 11s 455ms

Then Check if transport has "process-ended" 063ms

Hooks

After Hooks.deleteTransportAfterTest() 691ms

After Hooks.rollbackAllCustomFieldsSettings() 401ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Steps

Given Set token of apiUsername "super-admin-lantmannen" 237ms

And Get custom field settings for "DELIVERY" transport type and "lantmannen" company 098ms

And Mark custom fields as not obligatory 004ms

And Login as "lantmannen-admin" 4s 780ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 2s 939ms

When Find transport in table with status "potwierdzony" 3s 605ms

And Confirm statuses until reach "process-ended" 21s 861ms

Then Check if transport has "process-ended" 064ms

Hooks

After Hooks.deleteTransportAfterTest() 746ms

After Hooks.rollbackAllCustomFieldsSettings() 004ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Steps

Given Set token of apiUsername "super-admin-lantmannen" 246ms

And Get custom field settings for "LOAD" transport type and "lantmannen" company 097ms

And Mark custom fields as not obligatory 004ms

And Login as "lantmannen-admin" 2s 196ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 954ms

When Find transport in table with status "created" 3s 671ms

And Confirm statuses until reach "process-ended" 26s 985ms

Then Check if transport has "process-ended" 064ms

Hooks

After Hooks.deleteTransportAfterTest() 867ms

After Hooks.rollbackAllCustomFieldsSettings() 005ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Steps

Given Set token of apiUsername "super-admin-keeeper" 239ms

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 106ms

And Mark custom fields as not obligatory 584ms

And Login as "keeeper-admin" 5s 967ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 830ms

When Find transport in table with status "planned" 3s 609ms

And Confirm statuses until reach "process-ended" 21s 823ms

Then Check if transport has "process-ended" 066ms

Hooks

After Hooks.deleteTransportAfterTest() 833ms

After Hooks.rollbackAllCustomFieldsSettings() 641ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses by user

Steps

Given Set token of apiUsername "super-admin-keeeper" 239ms

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 110ms

And Mark custom fields as not obligatory 580ms

And Login as "keeeper-admin" 5s 776ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 875ms

When Find transport in table with status "planned" 3s 591ms

And Confirm statuses until reach "process-ended" 21s 885ms

Then Check if transport has "process-ended" 065ms

Hooks

After Hooks.deleteTransportAfterTest() 862ms

After Hooks.rollbackAllCustomFieldsSettings() 715ms

@deleteTransportAfterTest

Scenario Outline Check if transport has ended status after adding advice by user

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 9s 074ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 445ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 663ms

When Accept or reject "accept" transferred transport 19s 607ms

And Get inputs from database "ADVICE_SMALLS" "super-admin-skz" 020ms

And Click button advice in transport table "SMALLS_IMPORT" 228ms

And Set advice window in schedule 3s 694ms

And Fill advice form 17s 469ms

And Click advice save button and wait for advice form to disappear 33s 871ms

And Check if window is "silver" 4s 067ms

And Go to "TRANSPORT_TABLE" 414ms

Then Check if transport has "process-ended" 897ms

Hooks

After Hooks.deleteTransportAfterTest() 878ms

@deleteTransportAfterTest

Scenario Outline Check if transport has ended status after adding advice by user

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 686ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 535ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 625ms

When Accept or reject "accept" transferred transport 19s 901ms

And Get inputs from database "ADVICE_SMALLS" "super-admin-skz" 020ms

And Click button advice in transport table "SMALLS_EXPORT" 226ms

And Set advice window in schedule 3s 410ms

And Fill advice form 17s 479ms

And Click advice save button and wait for advice form to disappear 33s 823ms

And Check if window is "silver" 4s 067ms

And Go to "TRANSPORT_TABLE" 466ms

Then Check if transport has "process-ended" 1s 116ms

Hooks

After Hooks.deleteTransportAfterTest() 852ms

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to edit advice after reach specific status

Steps

Given Set token of apiUsername "super-admin-hochland" 247ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_ADVICE" "CHECKPOINT_BASED" "ARRIVAL" 468ms

And Get custom field settings for "DELIVERY" transport type and "hochland" company 204ms

And Mark custom fields as not obligatory 2s 720ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 059ms

When Login as "hochland-admin" 10s 328ms

And Find transport in table with status "advice-added" 3s 731ms

And Confirm statuses until reach "arrived" 6s 305ms

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

Then Check if it is not possible to edit advice 1s 123ms

Hooks

After Hooks.deleteTransportAfterTest() 902ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 388ms

After Hooks.rollbackAddedActionAuthorities() 307ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check is transport color changed after confirm status

Steps

Given Set token of apiUsername "super-admin-hochland" 227ms

And Get custom field settings for "DELIVERY" transport type and "hochland" company 190ms

And Mark custom fields as not obligatory 2s 764ms

And Login as "hochland-admin" 9s 704ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 121ms

When Find transport in table with status "advice-added" 3s 714ms

And Check if transport row is "blue" 3s 215ms

And Confirm statuses until reach "arrived" 6s 314ms

And Check if transport row is "green" 3s 193ms

And Confirm statuses until reach "during-unload" 6s 193ms

Then Check if transport row is "orange" 3s 184ms

And Confirm statuses until reach "unloaded" 6s 208ms

Then Check if transport row is "darkgoldenrod" 3s 208ms

And Confirm statuses until reach "process-ended" 6s 245ms

Then Check if transport row is "silver" 3s 196ms

Hooks

After Hooks.deleteTransportAfterTest() 811ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 417ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses before add file to transport

Steps

Given Set token of apiUsername "super-admin-piast" 220ms

And Get custom field settings for "DELIVERY" transport type and "piast" company 242ms

And Mark custom fields as not obligatory 007ms

And Login as "piast-admin" 5s 923ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 980ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 018ms

And Show all transport types 1s 132ms

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

And Set advice window in schedule 3s 386ms

And Fill advice form 10s 300ms

And Click advice save button and wait for advice form to disappear 33s 287ms

And Go to "TRANSPORT_TABLE" 493ms

And Find transport in table with status "advice-added" 3s 581ms

And Confirm statuses until reach "left-the-area" 32s 294ms

Then Check if next status is not possible to confirm 318ms

Hooks

After Hooks.deleteTransportAfterTest() 846ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 826ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses before add file to transport

Steps

Given Set token of apiUsername "super-admin-piast" 241ms

And Get custom field settings for "LOAD" transport type and "piast" company 255ms

And Mark custom fields as not obligatory 012ms

And Login as "piast-admin" 6s 083ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 921ms

And Get inputs from database "ADVICE_LOAD" "super-admin-piast" 022ms

And Show all transport types 1s 140ms

And Click button advice in transport table "LOAD" 234ms

And Set advice window in schedule 3s 326ms

And Fill advice form 10s 492ms

And Click advice save button and wait for advice form to disappear 33s 256ms

And Go to "TRANSPORT_TABLE" 407ms

And Find transport in table with status "advice-added" 3s 616ms

And Confirm statuses until reach "left-the-area" 31s 207ms

Then Check if next status is not possible to confirm 274ms

Hooks

After Hooks.deleteTransportAfterTest() 879ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 491ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses after add file to transport

Steps

Given Set token of apiUsername "super-admin-piast" 250ms

And Get custom field settings for "DELIVERY" transport type and "piast" company 228ms

And Mark custom fields as not obligatory 007ms

And Login as "piast-admin" 6s 043ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 948ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 018ms

And Show all transport types 1s 142ms

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

And Set advice window in schedule 3s 400ms

And Fill advice form 10s 424ms

And Click advice save button and wait for advice form to disappear 33s 269ms

And Go to "TRANSPORT_TABLE" 444ms

And Find transport in table with status "advice-added" 3s 593ms

When Add file to transport by API 2s 002ms

And Confirm statuses until reach "process-ended" 37s 508ms

Then Check if transport has "process-ended" 062ms

Hooks

After Hooks.deleteTransportAfterTest() 817ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 814ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses after add file to transport

Steps

Given Set token of apiUsername "super-admin-piast" 249ms

And Get custom field settings for "LOAD" transport type and "piast" company 247ms

And Mark custom fields as not obligatory 009ms

And Login as "piast-admin" 6s 054ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 942ms

And Get inputs from database "ADVICE_LOAD" "super-admin-piast" 020ms

And Show all transport types 1s 121ms

And Click button advice in transport table "LOAD" 247ms

And Set advice window in schedule 3s 374ms

And Fill advice form 10s 385ms

And Click advice save button and wait for advice form to disappear 33s 274ms

And Go to "TRANSPORT_TABLE" 422ms

And Find transport in table with status "advice-added" 3s 625ms

When Add file to transport by API 1s 686ms

And Confirm statuses until reach "process-ended" 37s 600ms

Then Check if transport has "process-ended" 065ms

Hooks

After Hooks.deleteTransportAfterTest() 875ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 496ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - with advice step

Steps

Given Set token of apiUsername "super-admin-hochland" 229ms

And Get custom field settings for "TRANSFER_BETWEEN_WAREHOUSES" transport type and "hochland" company 250ms

And Mark custom fields as not obligatory 4s 979ms

And Set custom field "Magazynier (R)" with "EDIT_TRANSFER_BETWEEN_WAREHOUSES_WAREHOUSEMAN_U_CFD" in "TRANSFER_BETWEEN_WAREHOUSES" - "hochland" by "super-admin-hochland" 523ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 925ms

And Set "advice" inputs from JSON file "ADVICE_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

And Login as "hochland-admin" 10s 404ms

And Show all transport types 1s 149ms

And Click button advice in transport table "TRANSFER_BETWEEN_WAREHOUSES" 1s 126ms

And Set advice window in schedule 7s 464ms

And Fill advice form 15s 968ms

And Click advice save button and wait for advice form to disappear 33s 844ms

And Go to "TRANSPORT_TABLE" 408ms

And Find transport in table with status "advice-added" 3s 613ms

And Confirm statuses until reach "during-load" 11s 528ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 590ms

And Check if next status is not possible to confirm in status confirmation modal 347ms

Hooks

After Hooks.deleteTransportAfterTest() 891ms

After Hooks.rollbackAllCustomFieldsSettings() 5s 206ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - with advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 270ms

And Get custom field settings for "LOAD" transport type and "keeeper" company 131ms

And Mark custom fields as not obligatory 801ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_LOAD_SANITARY_CONDITIONS_CFD" in "LOAD" - "keeeper" by "super-admin-keeeper" 241ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 921ms

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper" 001ms

And Login as "keeeper-admin" 6s 128ms

And Show all transport types 1s 155ms

And Click button advice in transport table "LOAD" 229ms

And Set advice window in schedule 3s 172ms

And Fill advice form 16s 186ms

And Click advice save button and wait for advice form to disappear 33s 229ms

And Go to "TRANSPORT_TABLE" 448ms

And Find transport in table with status "advice-added" 3s 662ms

And Confirm statuses until reach "arrived" 6s 291ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 589ms

And Check if next status is not possible to confirm in status confirmation modal 231ms

Hooks

After Hooks.deleteTransportAfterTest() 765ms

After Hooks.rollbackAllCustomFieldsSettings() 868ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - with advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 224ms

And Get custom field settings for "CONTAINER" transport type and "keeeper" company 120ms

And Mark custom fields as not obligatory 766ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_CONTAINER_SANITARY_CONDITIONS_CFD" in "CONTAINER" - "keeeper" by "super-admin-keeeper" 228ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 899ms

And Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-keeeper" 001ms

And Login as "keeeper-admin" 5s 941ms

And Show all transport types 1s 179ms

And Click button advice in transport table "CONTAINER" 246ms

And Set advice window in schedule 3s 175ms

And Fill advice form 16s 153ms

And Click advice save button and wait for advice form to disappear 33s 222ms

And Go to "TRANSPORT_TABLE" 434ms

And Find transport in table with status "advice-added" 3s 660ms

And Confirm statuses until reach "arrived" 6s 302ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 528ms

And Check if next status is not possible to confirm in status confirmation modal 231ms

Hooks

After Hooks.deleteTransportAfterTest() 757ms

After Hooks.rollbackAllCustomFieldsSettings() 907ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - without advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 236ms

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 122ms

And Mark custom fields as not obligatory 576ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 227ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 812ms

And Login as "keeeper-admin" 6s 060ms

And Go to "TRANSPORT_TABLE" 382ms

And Find transport in table with status "planned" 3s 562ms

And Confirm statuses until reach "arrived" 6s 305ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 693ms

And Check if next status is not possible to confirm in status confirmation modal 243ms

Hooks

After Hooks.deleteTransportAfterTest() 879ms

After Hooks.rollbackAllCustomFieldsSettings() 572ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - without advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 240ms

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 118ms

And Mark custom fields as not obligatory 615ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_TANKER_GRANULATE_DELIVERY_SANITARY_CONDITIONS_CFD" in "TANKER_GRANULATE_DELIVERY" - "keeeper" by "super-admin-keeeper" 251ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 922ms

And Login as "keeeper-admin" 5s 873ms

And Go to "TRANSPORT_TABLE" 375ms

And Find transport in table with status "planned" 3s 590ms

And Confirm statuses until reach "arrived" 6s 259ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 620ms

And Check if next status is not possible to confirm in status confirmation modal 256ms

Hooks

After Hooks.deleteTransportAfterTest() 995ms

After Hooks.rollbackAllCustomFieldsSettings() 720ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - without advice step

Steps

Given Set token of apiUsername "super-admin-hochland" 222ms

And Get custom field settings for "DELIVERY" transport type and "hochland" company 199ms

And Mark custom fields as not obligatory 2s 774ms

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 1s 214ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 090ms

And Login as "hochland-admin" 10s 390ms

And Go to "TRANSPORT_TABLE" 478ms

And Find transport in table with status "advice-added" 3s 614ms

And Confirm statuses until reach "during-unload" 11s 493ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 665ms

And Check if next status is not possible to confirm in status confirmation modal 390ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 065ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 355ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 230ms

And Get custom field settings for "LOAD" transport type and "keeeper" company 149ms

And Mark custom fields as not obligatory 750ms

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper" 001ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_LOAD_SANITARY_CONDITIONS_CFD" in "LOAD" - "keeeper" by "super-admin-keeeper" 217ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 921ms

And Login as "keeeper-admin" 5s 921ms

And Show all transport types 1s 251ms

And Click button advice in transport table "LOAD" 234ms

And Set advice window in schedule 3s 184ms

And Fill advice form 15s 973ms

And Click advice save button and wait for advice form to disappear 33s 251ms

And Go to "TRANSPORT_TABLE" 413ms

And Find transport in table with status "advice-added" 3s 674ms

When Confirm statuses until reach "arrived" 6s 286ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 511ms

And Check if next status is not possible to confirm in status confirmation modal 255ms

And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper" 001ms

And Click cancel in status confirmation modal 15s 380ms

And Go to transport details "LOAD" 2s 832ms

And Open section: "advice-panel" 1s 141ms

And Fill transport form 28s 396ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 194ms

And Go to transport details "LOAD" 2s 857ms

And Open section: "advice-panel" 1s 146ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 30s 577ms

And Confirm statuses until reach "process-ended" 16s 617ms

Then Check if transport has "process-ended" 067ms

Hooks

After Hooks.deleteTransportAfterTest() 894ms

After Hooks.rollbackAllCustomFieldsSettings() 814ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 223ms

And Get custom field settings for "CONTAINER" transport type and "keeeper" company 143ms

And Mark custom fields as not obligatory 743ms

And Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-keeeper" 001ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_CONTAINER_SANITARY_CONDITIONS_CFD" in "CONTAINER" - "keeeper" by "super-admin-keeeper" 260ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 883ms

And Login as "keeeper-admin" 6s 188ms

And Show all transport types 1s 156ms

And Click button advice in transport table "CONTAINER" 239ms

And Set advice window in schedule 3s 199ms

And Fill advice form 16s 055ms

And Click advice save button and wait for advice form to disappear 33s 225ms

And Go to "TRANSPORT_TABLE" 405ms

And Find transport in table with status "advice-added" 3s 625ms

When Confirm statuses until reach "arrived" 10s 434ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 599ms

And Check if next status is not possible to confirm in status confirmation modal 248ms

And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-keeeper" 001ms

And Click cancel in status confirmation modal 15s 337ms

And Go to transport details "CONTAINER" 2s 816ms

And Open section: "advice-panel" 1s 149ms

And Fill transport form 28s 393ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 170ms

And Go to transport details "CONTAINER" 2s 760ms

And Open section: "advice-panel" 1s 192ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 30s 591ms

And Confirm statuses until reach "process-ended" 16s 591ms

Then Check if transport has "process-ended" 059ms

Hooks

After Hooks.deleteTransportAfterTest() 821ms

After Hooks.rollbackAllCustomFieldsSettings() 889ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Steps

Given Set token of apiUsername "super-admin-hochland" 227ms

And Get custom field settings for "TRANSFER_BETWEEN_WAREHOUSES" transport type and "hochland" company 250ms

And Mark custom fields as not obligatory 4s 899ms

And Set "advice" inputs from JSON file "ADVICE_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 002ms

And Set custom field "Magazynier (R)" with "EDIT_TRANSFER_BETWEEN_WAREHOUSES_WAREHOUSEMAN_U_CFD" in "TRANSFER_BETWEEN_WAREHOUSES" - "hochland" by "super-admin-hochland" 396ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 935ms

And Login as "hochland-admin" 10s 662ms

And Show all transport types 1s 155ms

And Click button advice in transport table "TRANSFER_BETWEEN_WAREHOUSES" 1s 079ms

And Set advice window in schedule 7s 464ms

And Fill advice form 16s 104ms

And Click advice save button and wait for advice form to disappear 33s 807ms

And Go to "TRANSPORT_TABLE" 423ms

And Find transport in table with status "advice-added" 3s 588ms

When Confirm statuses until reach "during-load" 11s 808ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 585ms

And Check if next status is not possible to confirm in status confirmation modal 296ms

And Set "transport" inputs from JSON file "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

And Click cancel in status confirmation modal 15s 366ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 3s 042ms

And Open section: "advice-panel" 1s 169ms

And Fill transport form 39s 386ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 235ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 989ms

And Open section: "advice-panel" 1s 470ms

And Fill "warehouseman-(u)" in transport form 30s 660ms

And Confirm statuses until reach "process-ended" 32s 258ms

Then Check if transport has "process-ended" 063ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 166ms

After Hooks.rollbackAllCustomFieldsSettings() 5s 169ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 256ms

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 114ms

And Mark custom fields as not obligatory 575ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-keeeper" 001ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 236ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 887ms

And Login as "keeeper-admin" 6s 422ms

And Go to "TRANSPORT_TABLE" 391ms

And Find transport in table with status "planned" 3s 598ms

When Confirm statuses until reach "arrived" 6s 357ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 605ms

And Check if next status is not possible to confirm in status confirmation modal 236ms

And Click cancel in status confirmation modal 15s 348ms

And Go to transport details "UNLOAD" 2s 894ms

And Fill transport form 40s 420ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 190ms

And Confirm statuses until reach "process-ended" 16s 560ms

Then Check if transport has "process-ended" 065ms

Hooks

After Hooks.deleteTransportAfterTest() 870ms

After Hooks.rollbackAllCustomFieldsSettings() 578ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 250ms

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 115ms

And Mark custom fields as not obligatory 565ms

And Set "transport" inputs from JSON file "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 001ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_TANKER_GRANULATE_DELIVERY_SANITARY_CONDITIONS_CFD" in "TANKER_GRANULATE_DELIVERY" - "keeeper" by "super-admin-keeeper" 240ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 922ms

And Login as "keeeper-admin" 6s 198ms

And Go to "TRANSPORT_TABLE" 392ms

And Find transport in table with status "planned" 3s 584ms

When Confirm statuses until reach "arrived" 6s 270ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 645ms

And Check if next status is not possible to confirm in status confirmation modal 257ms

And Click cancel in status confirmation modal 15s 358ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 917ms

And Fill transport form 40s 502ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 214ms

And Confirm statuses until reach "process-ended" 16s 776ms

Then Check if transport has "process-ended" 060ms

Hooks

After Hooks.deleteTransportAfterTest() 896ms

After Hooks.rollbackAllCustomFieldsSettings() 723ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Steps

Given Set token of apiUsername "super-admin-hochland" 274ms

And Get custom field settings for "DELIVERY" transport type and "hochland" company 208ms

And Mark custom fields as not obligatory 2s 685ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 732ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 130ms

And Login as "hochland-admin" 10s 739ms

And Go to "TRANSPORT_TABLE" 533ms

And Find transport in table with status "advice-added" 3s 598ms

When Confirm statuses until reach "during-unload" 11s 620ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 817ms

And Check if next status is not possible to confirm in status confirmation modal 697ms

And Click cancel in status confirmation modal 10s 743ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //div[contains(@class,'modal-content')]//button[contains(@data-dismiss, 'modal')] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=91.0.4472.101 (af52a90bf87030dd1523486a1cd3ae25c5d76c9b-refs/branch-heads/4472@{#1462}), userDataDir=/home/teamcity/build-agent/temp/buildTmp/.com.google.Chrome.lTPSR1}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=91.0.4472.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: f758a2f28e68e2c4d26d83f38049210a
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:219)
	at CucumberTests.StatusTests.ConfirmStatuses.clickCancelInStatusConfirmationModal(ConfirmStatuses.java:131)
	at ✽.Click cancel in status confirmation modal(file:Features/Atom/Statuses/ConfirmStatuses.feature:219)

And Go to transport details "DELIVERY" 000ms

And Fill transport form 000ms

And Click "save-transport-and-close" save button and wait for form to disappear 000ms

And Confirm statuses until reach "process-ended" 000ms

Then Check if transport has "process-ended" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 868ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 356ms

@deleteTransportAfterTest

Scenario Outline Check if it is possible to confirm status by guard without confirming earlier statuses

Steps

Given Set token of apiUsername "super-admin-skd" 234ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 2s 641ms

And Confirm status "REPORTING" by Public API "v1" 468ms

And Confirm status "ARRIVAL" by Public API "v1" 721ms

And Login as "swiss-krono-delivery-guard" 4s 705ms

And Go to "TRANSPORT_TABLE" 459ms

When Confirm "Departure" status in transport row 162ms

Then Verify that "Departure" has been confirmed 1s 243ms

Hooks

After Hooks.deleteTransportAfterTest() 839ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm next status in transport details on transport details reopen after filling blockade customfields and not saving changes - without advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 258ms

And Get custom field settings for "UNLOAD" transport type and "keeeper" company 115ms

And Mark custom fields as not obligatory 609ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-keeeper" 001ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 252ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 16s 743ms

When Login as "keeeper-admin" 5s 882ms

And Find transport in table with status "planned" 3s 622ms

And Confirm statuses until reach "arrived" 6s 275ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 586ms

And Check if next status is not possible to confirm in status confirmation modal 264ms

And Click cancel in status confirmation modal 15s 364ms

And Go to transport details "UNLOAD" 2s 849ms

And Fill transport form 40s 470ms

Then Check if confirm status modal appeared on confirming next status in transport "details" 306ms

And Check if next status is not possible to confirm in status confirmation modal 205ms

Hooks

After Hooks.deleteTransportAfterTest() 777ms

After Hooks.rollbackAllCustomFieldsSettings() 576ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm next status in transport details on transport details reopen after filling blockade customfields and not saving changes - without advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 223ms

And Get custom field settings for "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 120ms

And Mark custom fields as not obligatory 596ms

And Set "transport" inputs from JSON file "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 001ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_TANKER_GRANULATE_DELIVERY_SANITARY_CONDITIONS_CFD" in "TANKER_GRANULATE_DELIVERY" - "keeeper" by "super-admin-keeeper" 248ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 2s 861ms

When Login as "keeeper-admin" 6s 083ms

And Find transport in table with status "planned" 3s 618ms

And Confirm statuses until reach "arrived" 6s 285ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 635ms

And Check if next status is not possible to confirm in status confirmation modal 262ms

And Click cancel in status confirmation modal 15s 341ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 871ms

And Fill transport form 40s 436ms

Then Check if confirm status modal appeared on confirming next status in transport "details" 276ms

And Check if next status is not possible to confirm in status confirmation modal 244ms

Hooks

After Hooks.deleteTransportAfterTest() 863ms

After Hooks.rollbackAllCustomFieldsSettings() 687ms

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm next status in transport details on transport details reopen after filling blockade customfields and not saving changes - without advice step

Steps

Given Set token of apiUsername "super-admin-hochland" 217ms

And Get custom field settings for "DELIVERY" transport type and "hochland" company 208ms

And Mark custom fields as not obligatory 2s 698ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 002ms

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 741ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 159ms

When Login as "hochland-admin" 9s 981ms

And Find transport in table with status "advice-added" 3s 768ms

And Confirm statuses until reach "during-unload" 11s 467ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 697ms

And Check if next status is not possible to confirm in status confirmation modal 417ms

And Click cancel in status confirmation modal 15s 660ms

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

And Fill transport form 40s 390ms

Then Check if confirm status modal appeared on confirming next status in transport "details" 303ms

And Check if next status is not possible to confirm in status confirmation modal 255ms

Hooks

After Hooks.deleteTransportAfterTest() 822ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 549ms

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm status with given confirmation date [A-7159]

Steps

Given Set token of apiUsername "super-admin-bausch" 266ms

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 172ms

And Mark custom fields as not obligatory 733ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 718ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 280ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 636ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 372ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" 4s 666ms

And Login as "bausch-admin" 6s 625ms

And Go to "TRANSPORT_TABLE" 501ms

And Find transport in table with status "advice-added" 3s 609ms

And Confirm statuses until reach "on-the-way" 17s 114ms

When Open statuses popup 128ms

And Toggle status date confirmation checkbox 397ms

And Confirm statuses until reach "process-ended" 6s 169ms

Then Check if transport has "process-ended" 066ms

Hooks

After Hooks.deleteTransportAfterTest() 880ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 112ms

After Hooks.deleteModeOfTransportationAfterTest() 323ms

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm status with invalid confirmation date [A-7159]

Steps

Given Set token of apiUsername "super-admin-bausch" 230ms

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 175ms

And Mark custom fields as not obligatory 737ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 702ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 202ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 653ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 392ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" 4s 605ms

And Login as "bausch-admin" 6s 444ms

And Go to "TRANSPORT_TABLE" 489ms

And Find transport in table with status "advice-added" 3s 623ms

And Confirm statuses until reach "on-the-way" 15s 821ms

And Open statuses popup 129ms

And Toggle status date confirmation checkbox 391ms

And Change status execution date to "1" days from today 2s 437ms

Then Verify that status cannot be confirmed 1s 188ms

Hooks

After Hooks.deleteTransportAfterTest() 862ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 119ms

After Hooks.deleteModeOfTransportationAfterTest() 324ms

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm status with invalid confirmation date [A-7159]

Steps

Given Set token of apiUsername "super-admin-bausch" 231ms

And Get custom field settings for "LOAD_EXPORT" transport type and "bausch" company 170ms

And Mark custom fields as not obligatory 726ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 695ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 2s 192ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 640ms

And Confirm status "ORDER_COMPLETNESS" by Public API "v1" 403ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" 4s 461ms

And Login as "bausch-admin" 6s 323ms

And Go to "TRANSPORT_TABLE" 492ms

And Find transport in table with status "advice-added" 3s 588ms

And Confirm statuses until reach "on-the-way" 16s 731ms

And Open statuses popup 141ms

And Toggle status date confirmation checkbox 392ms

And Change status execution date to "-1" days from today 2s 454ms

Then Verify that status cannot be confirmed 1s 202ms

Hooks

After Hooks.deleteTransportAfterTest() 872ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 116ms

After Hooks.deleteModeOfTransportationAfterTest() 333ms

@deleteAllTransportsAfterTest @deleteAllAddedStatus

Scenario Outline Check if statuses in new orders are created based on current status scheme [A-6867]

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 7s 372ms

And Create task with new status by JSON file "NEW_STATUS_SMALLS_IMPORT" as "super-admin-skz" 508ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 371ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 647ms

When Accept or reject "accept" transferred transport 19s 749ms

And Get inputs from database "ADVICE_SMALLS" "super-admin-skz" 016ms

And Click button advice in transport table "SMALLS_IMPORT" 243ms

And Set advice window in schedule 3s 422ms

And Fill advice form 17s 451ms

And Click advice save button and wait for advice form to disappear 33s 872ms

And If user is login then logout 263ms

And Login as "swisskrono-admin" 8s 373ms

And Show all transport types 1s 192ms

Then Check if transport has "testowy-różoffy-statusik" 205ms

And Go to "SETTINGS_TAB" 800ms

When Disable status "testowy-różoffy-statusik" for transport "SMALLS_IMPORT" 2s 183ms

And Delete created transport by API 1s 478ms

Then If user is login then logout 281ms

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 3s 637ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 722ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 654ms

When Accept or reject "accept" transferred transport 19s 694ms

And Get inputs from database "ADVICE_SMALLS" "super-admin-skz" 018ms

And Click button advice in transport table "SMALLS_IMPORT" 236ms

And Set advice window in schedule 3s 561ms

And Fill advice form 17s 459ms

And Click advice save button and wait for advice form to disappear 18s 371ms

And If user is login then logout 727ms

And Login as "swisskrono-admin" 3s 160ms

And Show all transport types 1s 175ms

Then Check if transport has disabled status "testowy-różoffy-statusik" 15s 051ms

Hooks

After Hooks.deleteAllTransports() 1m 16s 927ms

After Hooks.deleteAllAddedStatus() 2s 530ms

@deleteTransportAfterTest @rollbackTaskChanges @rollbackAllCustomFieldsSettings

Scenario Outline Confirmed statuses of existing orders should not be deleted - even after editing the order [A-6874]

Steps

Given Set token of apiUsername "super-admin-farmacol" 357ms

And Get custom field settings for "EXTERNAL_DELIVERY" transport type and "farmacol" company 109ms

And Mark custom fields as not obligatory 005ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 962ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 3s 865ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 113ms

When Login as "farmacol-admin" 7s 609ms

And Go to "TRANSPORT_TABLE" 493ms

And Confirm statuses until reach "during-unload" 16s 891ms

And Set actual confirmed transport status list 2s 007ms

And Disable task by API 303ms

And Go to transport details "EXTERNAL_DELIVERY" 2s 973ms

And Edit transport hours and recalculate statuses 30s 628ms

Then Verify that all confirmed statuses are still on transport status list 417ms

Hooks

After Hooks.deleteTransportAfterTest() 848ms

After Hooks.rollbackAllCustomFieldsSettings() 341ms

After Hooks.rollbackTaskChanges() 178ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Status confirmation	532	1	5	0	0	538	35	1	36	47m 41s 411ms	Failed

Feature Report