Cucumber-JVM Reports - Tag: @rollbackAllCustomFieldsSettings

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.57	27 cze 2021, 06:33

	Steps	Scenarios	Features
@rollbackAllCustomFieldsSettings	570	2	1	0	0	573	36	2	38	50m 7s 910ms	Failed

View Feature Filters

@deleteTransportsAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings

Scenario Outline Check if sorting by "Finished" status is working correctly [A-7517]

Steps

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

And Get custom field settings for "DELIVERY" transport type and "neuca" company 175ms

And Mark custom fields as not obligatory 006ms

And Get setting "SORT_TABLE_BY_TRANSPORT_COMPLETED" for "neuca" 138ms

And Prepare setting: "SORT_TABLE_BY_TRANSPORT_COMPLETED" with value: "true" with "super-admin-neuca" 031ms

When Create 3 transports "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 21s 152ms

Then Login as "neuca-admin" 2s 230ms

And Go to "TRANSPORT_TABLE" 482ms

And Confirm statuses until reach "process-ended" 17s 171ms

Then Check if sorting by 'Finished' status is working correctly 295ms

Hooks

After Hooks.deleteTransportsAfterTest() 2s 762ms

After Hooks.rollbackAllCustomFieldsSettings() 390ms

After Hooks.rollbackSettings() 122ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Steps

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

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

And Mark custom fields as not obligatory 007ms

And Login as "hochland-admin" 2s 780ms

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

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

And Confirm statuses until reach "process-ended" 18s 967ms

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

Hooks

After Hooks.deleteTransportAfterTest() 973ms

After Hooks.rollbackAllCustomFieldsSettings() 24s 045ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Steps

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

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

And Mark custom fields as not obligatory 005ms

And Login as "pgf-admin" 5s 156ms

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

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

And Confirm statuses until reach "process-ended" 10s 477ms

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

Hooks

After Hooks.deleteTransportAfterTest() 936ms

After Hooks.rollbackAllCustomFieldsSettings() 430ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Steps

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

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

And Mark custom fields as not obligatory 005ms

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

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

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

And Confirm statuses until reach "process-ended" 9s 482ms

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

Hooks

After Hooks.deleteTransportAfterTest() 791ms

After Hooks.rollbackAllCustomFieldsSettings() 403ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Steps

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

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

And Mark custom fields as not obligatory 004ms

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

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

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

And Confirm statuses until reach "process-ended" 17s 890ms

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

Hooks

After Hooks.deleteTransportAfterTest() 935ms

After Hooks.rollbackAllCustomFieldsSettings() 005ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Steps

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

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

And Mark custom fields as not obligatory 004ms

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 3s 008ms

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

And Confirm statuses until reach "process-ended" 22s 079ms

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

Hooks

After Hooks.deleteTransportAfterTest() 841ms

After Hooks.rollbackAllCustomFieldsSettings() 004ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Steps

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

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

And Mark custom fields as not obligatory 005ms

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

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

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

And Confirm statuses until reach "process-ended" 17s 976ms

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

Hooks

After Hooks.deleteTransportAfterTest() 794ms

After Hooks.rollbackAllCustomFieldsSettings() 431ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Steps

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

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

And Mark custom fields as not obligatory 006ms

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

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

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

And Confirm statuses until reach "process-ended" 17s 992ms

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

Hooks

After Hooks.deleteTransportAfterTest() 928ms

After Hooks.rollbackAllCustomFieldsSettings() 577ms

View Feature Status confirmation

@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" 251ms

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

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

And Mark custom fields as not obligatory 008ms

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

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

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

And Confirm statuses until reach "arrived" 5s 269ms

And Go to transport details "DELIVERY" 4s 860ms

Then Check if it is not possible to edit advice 580ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 016ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 863ms

After Hooks.rollbackAddedActionAuthorities() 332ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check is transport color changed after confirm status

Steps

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

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

And Mark custom fields as not obligatory 008ms

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

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

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

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

And Confirm statuses until reach "arrived" 5s 289ms

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

And Confirm statuses until reach "during-unload" 5s 208ms

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

And Confirm statuses until reach "unloaded" 5s 223ms

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

And Confirm statuses until reach "process-ended" 5s 204ms

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

Hooks

After Hooks.deleteTransportAfterTest() 849ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 836ms

View Feature Status confirmation

@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" 226ms

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

And Mark custom fields as not obligatory 008ms

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 018ms

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

And Show all transport types 1s 150ms

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

And Set advice window in schedule 3s 526ms

And Fill advice form 10s 637ms

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

And Go to "TRANSPORT_TABLE" 474ms

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

And Confirm statuses until reach "left-the-area" 26s 380ms

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

Hooks

After Hooks.deleteTransportAfterTest() 946ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 777ms

View Feature Status confirmation

@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" 230ms

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

And Mark custom fields as not obligatory 008ms

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

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

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

And Show all transport types 1s 160ms

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

And Set advice window in schedule 3s 382ms

And Fill advice form 10s 476ms

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

And Go to "TRANSPORT_TABLE" 420ms

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

And Confirm statuses until reach "left-the-area" 25s 363ms

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

Hooks

After Hooks.deleteTransportAfterTest() 867ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 386ms

View Feature Status confirmation

@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" 229ms

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

And Mark custom fields as not obligatory 009ms

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 074ms

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

And Show all transport types 1s 153ms

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

And Set advice window in schedule 3s 403ms

And Fill advice form 10s 585ms

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

And Go to "TRANSPORT_TABLE" 479ms

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

When Add file to transport by API 1s 755ms

And Confirm statuses until reach "process-ended" 33s 139ms

Error message

java.lang.AssertionError: Wartość advice-added-magazyn-hala-a atrybutu data-status-name nie zmieniła się w webelemencie [[ChromeDriver: chrome on LINUX (5a5499d3085df027d32946dd6250004a)] -> xpath: //td[contains(@data-status-name, 'advice-added')]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.StatusUtil.waitUntilAttributeOfWebElementChangeValue(StatusUtil.java:43)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:303)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:290)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:84)
	at ✽.Confirm statuses until reach "process-ended"(file:Features/Atom/Statuses/ConfirmStatuses.feature:117)

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

Hooks

After Hooks.deleteTransportAfterTest() 909ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 822ms

View Feature Status confirmation

@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" 278ms

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

And Mark custom fields as not obligatory 011ms

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

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

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

And Show all transport types 1s 117ms

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

And Set advice window in schedule 3s 411ms

And Fill advice form 10s 307ms

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

And Go to "TRANSPORT_TABLE" 451ms

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

When Add file to transport by API 1s 387ms

And Confirm statuses until reach "process-ended" 30s 530ms

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

Hooks

After Hooks.deleteTransportAfterTest() 980ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 417ms

View Feature Status confirmation

@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" 228ms

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

And Mark custom fields as not obligatory 009ms

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

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

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

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

And Show all transport types 1s 135ms

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

And Set advice window in schedule 7s 538ms

And Fill advice form 16s 371ms

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

And Go to "TRANSPORT_TABLE" 435ms

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

And Confirm statuses until reach "during-load" 9s 602ms

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 318ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 039ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 902ms

View Feature Status confirmation

@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" 237ms

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

And Mark custom fields as not obligatory 007ms

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

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

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

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

And Show all transport types 1s 257ms

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

And Set advice window in schedule 3s 261ms

And Fill advice form 16s 522ms

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

And Go to "TRANSPORT_TABLE" 456ms

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

And Confirm statuses until reach "arrived" 5s 298ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 917ms

After Hooks.rollbackAllCustomFieldsSettings() 717ms

View Feature Status confirmation

@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" 225ms

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

And Mark custom fields as not obligatory 006ms

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

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

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

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

And Show all transport types 1s 174ms

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

And Set advice window in schedule 3s 271ms

And Fill advice form 16s 483ms

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

And Go to "TRANSPORT_TABLE" 467ms

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

And Confirm statuses until reach "arrived" 5s 281ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 818ms

After Hooks.rollbackAllCustomFieldsSettings() 767ms

View Feature Status confirmation

@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" 225ms

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

And Mark custom fields as not obligatory 005ms

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

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

And Go to "TRANSPORT_TABLE" 414ms

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

And Confirm statuses until reach "arrived" 5s 293ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 974ms

After Hooks.rollbackAllCustomFieldsSettings() 481ms

View Feature Status confirmation

@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 "TANKER_GRANULATE_DELIVERY" transport type and "keeeper" company 116ms

And Mark custom fields as not obligatory 006ms

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

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 3s 069ms

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

And Go to "TRANSPORT_TABLE" 353ms

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

And Confirm statuses until reach "arrived" 5s 276ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 084ms

After Hooks.rollbackAllCustomFieldsSettings() 624ms

View Feature Status confirmation

@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 190ms

And Mark custom fields as not obligatory 007ms

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

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

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

And Go to "TRANSPORT_TABLE" 476ms

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

And Confirm statuses until reach "during-unload" 9s 510ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 121ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 864ms

View Feature Status confirmation

@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" 211ms

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

And Mark custom fields as not obligatory 006ms

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

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

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

And Show all transport types 1s 251ms

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

And Set advice window in schedule 3s 217ms

And Fill advice form 16s 334ms

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

And Go to "TRANSPORT_TABLE" 444ms

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

When Confirm statuses until reach "arrived" 5s 285ms

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

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

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

And Click cancel in status confirmation modal 15s 327ms

And Go to transport details "LOAD" 4s 809ms

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

And Fill transport form 28s 587ms

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

And Go to transport details "LOAD" 4s 893ms

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

And Fill "meeting-sanitary-and-technical-conditions" in transport form 17s 427ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 889ms

After Hooks.rollbackAllCustomFieldsSettings() 746ms

View Feature Status confirmation

@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" 224ms

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

And Mark custom fields as not obligatory 005ms

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

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

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

And Show all transport types 1s 175ms

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

And Set advice window in schedule 3s 240ms

And Fill advice form 16s 204ms

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

And Go to "TRANSPORT_TABLE" 367ms

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

When Confirm statuses until reach "arrived" 5s 233ms

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

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

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

And Click cancel in status confirmation modal 15s 376ms

And Go to transport details "CONTAINER" 4s 870ms

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

And Fill transport form 28s 663ms

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

And Go to transport details "CONTAINER" 4s 842ms

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

And Fill "meeting-sanitary-and-technical-conditions" in transport form 17s 481ms

And Confirm statuses until reach "process-ended" 12s 671ms

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

Hooks

After Hooks.deleteTransportAfterTest() 946ms

After Hooks.rollbackAllCustomFieldsSettings() 750ms

View Feature Status confirmation

@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" 240ms

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

And Mark custom fields as not obligatory 008ms

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

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

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

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

And Show all transport types 1s 165ms

And Click button advice in transport table "TRANSFER_BETWEEN_WAREHOUSES" 987ms

And Set advice window in schedule 7s 465ms

And Fill advice form 16s 516ms

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

And Go to "TRANSPORT_TABLE" 494ms

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

When Confirm statuses until reach "during-load" 9s 468ms

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

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

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

And Click cancel in status confirmation modal 15s 440ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 994ms

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

And Fill transport form 39s 587ms

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

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 896ms

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

And Fill "warehouseman-(u)" in transport form 17s 964ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 239ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 120ms

View Feature Status confirmation

@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" 229ms

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

And Mark custom fields as not obligatory 005ms

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

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

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

And Go to "TRANSPORT_TABLE" 417ms

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

When Confirm statuses until reach "arrived" 5s 240ms

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

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

And Click cancel in status confirmation modal 15s 409ms

And Go to transport details "UNLOAD" 4s 923ms

And Fill transport form 40s 978ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 895ms

After Hooks.rollbackAllCustomFieldsSettings() 488ms

View Feature Status confirmation

@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" 218ms

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

And Mark custom fields as not obligatory 005ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 430ms

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

When Confirm statuses until reach "arrived" 5s 285ms

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 276ms

And Click cancel in status confirmation modal 15s 387ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 976ms

And Fill transport form 40s 801ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 889ms

After Hooks.rollbackAllCustomFieldsSettings() 611ms

View Feature Status confirmation

@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" 230ms

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

And Mark custom fields as not obligatory 006ms

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

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

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

And Go to "TRANSPORT_TABLE" 471ms

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

When Confirm statuses until reach "during-unload" 9s 455ms

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

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

And Click cancel in status confirmation modal 15s 728ms

And Go to transport details "DELIVERY" 4s 949ms

And Fill transport form 40s 777ms

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

And Confirm statuses until reach "process-ended" 9s 448ms

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

Hooks

After Hooks.deleteTransportAfterTest() 952ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 959ms

View Feature Status confirmation

@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" 233ms

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

And Mark custom fields as not obligatory 005ms

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 858ms

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

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

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

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

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

And Click cancel in status confirmation modal 15s 344ms

And Go to transport details "UNLOAD" 4s 887ms

And Fill transport form 40s 809ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 893ms

After Hooks.rollbackAllCustomFieldsSettings() 519ms

View Feature Status confirmation

@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 005ms

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

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 3s 028ms

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

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

And Confirm statuses until reach "arrived" 5s 280ms

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

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

And Click cancel in status confirmation modal 15s 381ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 994ms

And Fill transport form 40s 912ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 888ms

After Hooks.rollbackAllCustomFieldsSettings() 638ms

View Feature Status confirmation

@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" 222ms

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

And Mark custom fields as not obligatory 010ms

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

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

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

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

And Confirm statuses until reach "during-unload" 9s 521ms

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

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

And Click cancel in status confirmation modal 15s 433ms

And Go to transport details "DELIVERY" 4s 988ms

And Fill transport form 40s 749ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 903ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 739ms

View Feature Status confirmation

@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" 221ms

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

And Mark custom fields as not obligatory 009ms

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

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

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

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

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

And Login as "bausch-admin" 5s 785ms

And Go to "TRANSPORT_TABLE" 513ms

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

And Confirm statuses until reach "on-the-way" 13s 835ms

When Open statuses popup 157ms

And Toggle status date confirmation checkbox 396ms

And Confirm statuses until reach "process-ended" 5s 220ms

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 102ms

After Hooks.rollbackAllCustomFieldsSettings() 1s 838ms

After Hooks.deleteModeOfTransportationAfterTest() 319ms

View Feature Status confirmation

@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" 236ms

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

And Mark custom fields as not obligatory 006ms

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

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 456ms

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

And Confirm statuses until reach "on-the-way" 13s 794ms

And Open statuses popup 156ms

And Toggle status date confirmation checkbox 394ms

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

Then Verify that status cannot be confirmed 1s 229ms

Hooks

After Hooks.deleteTransportAfterTest() 935ms

After Hooks.rollbackAllCustomFieldsSettings() 1s 868ms

After Hooks.deleteModeOfTransportationAfterTest() 323ms

View Feature Status confirmation

@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 173ms

And Mark custom fields as not obligatory 008ms

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

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

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

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

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

And Login as "bausch-admin" 5s 964ms

And Go to "TRANSPORT_TABLE" 515ms

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

And Confirm statuses until reach "on-the-way" 13s 802ms

And Open statuses popup 125ms

And Toggle status date confirmation checkbox 384ms

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

Then Verify that status cannot be confirmed 1s 177ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 030ms

After Hooks.rollbackAllCustomFieldsSettings() 1s 866ms

After Hooks.deleteModeOfTransportationAfterTest() 329ms

View Feature Status confirmation

@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" 341ms

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

And Mark custom fields as not obligatory 005ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 2s 052ms

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

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

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

And Go to "TRANSPORT_TABLE" 456ms

And Confirm statuses until reach "during-unload" 13s 775ms

And Set actual confirmed transport status list 2s 070ms

And Disable task by API 214ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 955ms

And Edit transport hours and recalculate statuses 19s 115ms

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

Hooks

After Hooks.deleteTransportAfterTest() 896ms

After Hooks.rollbackAllCustomFieldsSettings() 366ms

After Hooks.rollbackTaskChanges() 201ms

View Feature Status

@deleteTransportAfterTest @rollbackTaskChanges @rollbackAllCustomFieldsSettings

Scenario Outline Check if deleted task is not in new transports' workflow @A-6875

Steps

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

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

And Mark custom fields as not obligatory 005ms

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

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

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

When Login as "farmacol-admin" 2s 356ms

And Go to "TRANSPORT_TABLE" 479ms

And Confirm statuses until reach "registered-katowice-przyjęcia" 9s 593ms

And Disable task by API 191ms

And Find transport pencil button in transports table 1s 846ms

And Click pencil and move transport to next day in schedule 22s 951ms

And Go to "TRANSPORT_TABLE" 432ms

Then Verify that "START_OF_UNLOADING" is not visible 410ms

Hooks

After Hooks.deleteTransportAfterTest() 957ms

After Hooks.rollbackAllCustomFieldsSettings() 356ms

After Hooks.rollbackTaskChanges() 210ms

View Feature Move transport to archive

@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings

Scenario Outline Check if confirming transport status removed it to the archive

Steps

Given Set token of apiUsername "super-admin-dayco" 219ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 109ms

And Mark custom fields as not obligatory 005ms

And Login as "dayco-admin" 1s 960ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 093ms

And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 127ms

And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 033ms

When Go to "TRANSPORT_TABLE" 402ms

And Click button advice in transport table "OWN_COLLECTION" 1s 397ms

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 45s 990ms

And Go to "TRANSPORT_TABLE" 456ms

And Find transport in table with status "planned-magazyn-tychy" 3s 688ms

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

And Wait "12" seconds 12s

Then Go to "ARCHIVE_TAB" 528ms

And Show "OWN_COLLECTION" 173ms

And Verify that created transport is "true" in transport table 1m 32s 270ms

Error message

java.lang.AssertionError: expected: but was:
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failNotEquals(Assert.java:834)
	at org.junit.Assert.assertEquals(Assert.java:118)
	at org.junit.Assert.assertEquals(Assert.java:144)
	at CucumberTests._PerformanceTests.TransportTableTest.verifyThatCreatedTransportIsInTransportTable(TransportTableTest.java:116)
	at ✽.Verify that created transport is "true" in transport table(file:Features/Atom/Transport/Archive.feature:54)

Hooks

After Hooks.deleteTransportAfterTest() 997ms

After Hooks.rollbackAllCustomFieldsSettings() 468ms

After Hooks.rollbackSettings() 143ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if user can add description to archived transport

Steps

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

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

And Mark custom fields as not obligatory 004ms

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

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_MAIN_DATA_SECTION" "UNLIMITED" 321ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_ADVICE" "UNLIMITED" 338ms

And Add action authority with: "adama" "adama-admin" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 314ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 947ms

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

And Confirm statuses until reach "process-ended" 9s 445ms

And Wait "90" seconds 1m 30s

And Go to "ARCHIVE_TAB" 516ms

And Show "DELIVERY" 178ms

And Go to transport details "DELIVERY" 32s 669ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 525ms

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

And Wait "7" seconds 7s

And Go to transport details "DELIVERY" 32s 606ms

Then Verify that "transport-description" in transport has value "opis" 085ms

Hooks

After Hooks.deleteTransportAfterTest() 849ms

After Hooks.rollbackAllCustomFieldsSettings() 004ms

After Hooks.rollbackAddedActionAuthorities() 255ms

After Hooks.rollbackRemovedActionAuthorities() 537ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if similar transport can be created based on transport with confirmed statuses [A-7322]

Steps

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

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 128ms

And Mark custom fields as not obligatory 004ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 087ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 001ms

When Login as "dayco-admin" 4s 781ms

And Click button advice in transport table "OWN_COLLECTION" 917ms

And Set advice window in schedule 3s 284ms

And Fill advice form 9s 155ms

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

And Go to "TRANSPORT_TABLE" 456ms

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

And Confirm statuses until reach "on-the-area" 5s 244ms

And Go to transport details "OWN_COLLECTION" 4s 800ms

And Click create similar button 15s 245ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 6s 994ms

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

And Open similar transport details 457ms

Then Check if transport form modal is visible 090ms

Hooks

After Hooks.deleteTransportAfterTest() 934ms

After Hooks.deleteSimilarTransportAfterTest() 560ms

After Hooks.rollbackAllCustomFieldsSettings() 498ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if similar transport can be created based on transport with confirmed statuses [A-7322]

Steps

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

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 113ms

And Mark custom fields as not obligatory 005ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 2s 050ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 001ms

When Login as "dayco-admin" 5s 033ms

And Click button advice in transport table "OWN_COLLECTION" 867ms

And Set advice window in schedule 3s 302ms

And Fill advice form 9s 265ms

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

And Go to "TRANSPORT_TABLE" 452ms

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

And Confirm statuses until reach "during-load" 9s 430ms

And Go to transport details "OWN_COLLECTION" 4s 832ms

And Click create similar button 15s 267ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 6s 994ms

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

And Open similar transport details 574ms

Then Check if transport form modal is visible 099ms

Hooks

After Hooks.deleteTransportAfterTest() 973ms

After Hooks.deleteSimilarTransportAfterTest() 615ms

After Hooks.rollbackAllCustomFieldsSettings() 478ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@rollbackAllCustomFieldsSettings	570	2	1	0	0	573	36	2	38	50m 7s 910ms	Failed

Tag Report