Cucumber-JVM Reports - Tag: @rollbackAllCustomFieldsSettings

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

	Steps	Scenarios	Features
@rollbackAllCustomFieldsSettings	570	2	1	0	0	573	36	2	38	51m 18s 990ms	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" 237ms

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

And Mark custom fields as not obligatory 006ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 481ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 2s 787ms

After Hooks.rollbackAllCustomFieldsSettings() 359ms

After Hooks.rollbackSettings() 123ms

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

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

And Mark custom fields as not obligatory 007ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 034ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 900ms

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

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

And Mark custom fields as not obligatory 005ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 970ms

After Hooks.rollbackAllCustomFieldsSettings() 393ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 701ms

After Hooks.rollbackAllCustomFieldsSettings() 376ms

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

And Mark custom fields as not obligatory 003ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 812ms

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

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

And Mark custom fields as not obligatory 004ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 843ms

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-keeeper" 241ms

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

And Mark custom fields as not obligatory 005ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 958ms

After Hooks.rollbackAllCustomFieldsSettings() 458ms

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

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

And Mark custom fields as not obligatory 005ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 949ms

After Hooks.rollbackAllCustomFieldsSettings() 605ms

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

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

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

And Mark custom fields as not obligatory 010ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 010ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 869ms

After Hooks.rollbackAddedActionAuthorities() 326ms

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

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

And Mark custom fields as not obligatory 007ms

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

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

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

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

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

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 906ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 934ms

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

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

And Mark custom fields as not obligatory 009ms

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

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

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

And Show all transport types 1s 150ms

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

And Set advice window in schedule 3s 288ms

And Fill advice form 10s 547ms

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

And Go to "TRANSPORT_TABLE" 480ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 907ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 805ms

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

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

And Mark custom fields as not obligatory 009ms

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

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

And Show all transport types 1s 156ms

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

And Set advice window in schedule 3s 341ms

And Fill advice form 10s 687ms

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

And Go to "TRANSPORT_TABLE" 448ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 871ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 302ms

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

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

And Mark custom fields as not obligatory 008ms

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

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

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

And Show all transport types 1s 153ms

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

And Set advice window in schedule 3s 277ms

And Fill advice form 10s 523ms

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

And Go to "TRANSPORT_TABLE" 451ms

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

When Add file to transport by API 1s 836ms

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

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 (f8cb78390cf3d7d1218d778b44af147e)] -> 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() 962ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 804ms

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

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

And Mark custom fields as not obligatory 011ms

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

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

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

And Show all transport types 1s 157ms

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

And Set advice window in schedule 3s 337ms

And Fill advice form 10s 776ms

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

And Go to "TRANSPORT_TABLE" 443ms

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

When Add file to transport by API 1s 514ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 981ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 441ms

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

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

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

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

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

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

And Show all transport types 1s 160ms

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

And Set advice window in schedule 7s 793ms

And Fill advice form 16s 469ms

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

And Go to "TRANSPORT_TABLE" 454ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 071ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 069ms

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

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

And Mark custom fields as not obligatory 005ms

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

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

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

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

And Show all transport types 1s 234ms

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

And Set advice window in schedule 3s 224ms

And Fill advice form 16s 560ms

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

And Go to "TRANSPORT_TABLE" 436ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 839ms

After Hooks.rollbackAllCustomFieldsSettings() 730ms

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

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

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

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

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

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

And Show all transport types 1s 173ms

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

And Set advice window in schedule 3s 261ms

And Fill advice form 16s 567ms

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

And Go to "TRANSPORT_TABLE" 403ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 906ms

After Hooks.rollbackAllCustomFieldsSettings() 764ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 384ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 950ms

After Hooks.rollbackAllCustomFieldsSettings() 482ms

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

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

And Mark custom fields as not obligatory 007ms

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

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

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

And Go to "TRANSPORT_TABLE" 426ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 013ms

After Hooks.rollbackAllCustomFieldsSettings() 623ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 482ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 183ms

After Hooks.rollbackAllCustomFieldsSettings() 3s

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

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

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

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

And Show all transport types 1s 248ms

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

And Set advice window in schedule 3s 231ms

And Fill advice form 16s 443ms

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

And Go to "TRANSPORT_TABLE" 443ms

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

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

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

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

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

And Click cancel in status confirmation modal 15s 350ms

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

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

And Fill transport form 28s 805ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 892ms

After Hooks.rollbackAllCustomFieldsSettings() 757ms

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

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

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

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

And Login as "keeeper-admin" 6s

And Show all transport types 1s 184ms

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

And Set advice window in schedule 3s 214ms

And Fill advice form 16s 407ms

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

And Go to "TRANSPORT_TABLE" 458ms

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

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

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

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

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

And Click cancel in status confirmation modal 15s 369ms

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

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

And Fill transport form 28s 767ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 978ms

After Hooks.rollbackAllCustomFieldsSettings() 763ms

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

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

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

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

And Show all transport types 1s 160ms

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

And Set advice window in schedule 7s 594ms

And Fill advice form 16s 366ms

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

And Go to "TRANSPORT_TABLE" 590ms

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

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

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

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

And Click cancel in status confirmation modal 15s 443ms

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

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

And Fill transport form 39s 904ms

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

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

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

And Fill "warehouseman-(u)" in transport form 18s 010ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 166ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 114ms

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

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

And Mark custom fields as not obligatory 004ms

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

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

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

And Go to "TRANSPORT_TABLE" 345ms

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

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

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

And Click cancel in status confirmation modal 15s 380ms

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

And Fill transport form 40s 954ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 999ms

After Hooks.rollbackAllCustomFieldsSettings() 493ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 398ms

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

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

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

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

And Click cancel in status confirmation modal 15s 371ms

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

And Fill transport form 40s 949ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 886ms

After Hooks.rollbackAllCustomFieldsSettings() 619ms

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

And Mark custom fields as not obligatory 007ms

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

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

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

And Go to "TRANSPORT_TABLE" 491ms

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

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

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

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

And Click cancel in status confirmation modal 15s 524ms

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

And Fill transport form 40s 486ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 025ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 923ms

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

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

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

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

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

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

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

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

And Click cancel in status confirmation modal 15s 317ms

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

And Fill transport form 40s 929ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 965ms

After Hooks.rollbackAllCustomFieldsSettings() 488ms

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

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

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

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

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

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

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

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

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

And Click cancel in status confirmation modal 15s 403ms

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

And Fill transport form 41s 006ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 932ms

After Hooks.rollbackAllCustomFieldsSettings() 662ms

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

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

And Mark custom fields as not obligatory 009ms

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

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

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

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

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

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

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

And Click cancel in status confirmation modal 15s 546ms

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

And Fill transport form 40s 640ms

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 094ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 959ms

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

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

And Mark custom fields as not obligatory 007ms

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

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 505ms

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

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

When Open statuses popup 146ms

And Toggle status date confirmation checkbox 402ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 052ms

After Hooks.rollbackAllCustomFieldsSettings() 1s 858ms

After Hooks.deleteModeOfTransportationAfterTest() 387ms

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

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

And Mark custom fields as not obligatory 009ms

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

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 462ms

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

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

And Open statuses popup 146ms

And Toggle status date confirmation checkbox 393ms

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

Then Verify that status cannot be confirmed 1s 232ms

Hooks

After Hooks.deleteTransportAfterTest() 927ms

After Hooks.rollbackAllCustomFieldsSettings() 1s 814ms

After Hooks.deleteModeOfTransportationAfterTest() 328ms

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

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

And Mark custom fields as not obligatory 006ms

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

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

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

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

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

And Login as "bausch-admin" 6s

And Go to "TRANSPORT_TABLE" 504ms

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

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

And Open statuses popup 150ms

And Toggle status date confirmation checkbox 426ms

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

Then Verify that status cannot be confirmed 1s 225ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 044ms

After Hooks.rollbackAllCustomFieldsSettings() 1s 857ms

After Hooks.deleteModeOfTransportationAfterTest() 325ms

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

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

And Mark custom fields as not obligatory 005ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 494ms

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

And Set actual confirmed transport status list 1s 969ms

And Disable task by API 278ms

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

And Edit transport hours and recalculate statuses 19s 089ms

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

Hooks

After Hooks.deleteTransportAfterTest() 782ms

After Hooks.rollbackAllCustomFieldsSettings() 347ms

After Hooks.rollbackTaskChanges() 194ms

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

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

And Mark custom fields as not obligatory 006ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 521ms

And Confirm statuses until reach "registered-katowice-przyjęcia" 11s 628ms

And Disable task by API 192ms

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

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

And Go to "TRANSPORT_TABLE" 466ms

Then Verify that "START_OF_UNLOADING" is not visible 406ms

Hooks

After Hooks.deleteTransportAfterTest() 872ms

After Hooks.rollbackAllCustomFieldsSettings() 343ms

After Hooks.rollbackTaskChanges() 186ms

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

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

And Mark custom fields as not obligatory 005ms

And Login as "dayco-admin" 2s 147ms

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

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

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

When Go to "TRANSPORT_TABLE" 397ms

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

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

And Go to "TRANSPORT_TABLE" 452ms

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

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

And Wait "12" seconds 12s

Then Go to "ARCHIVE_TAB" 503ms

And Show "OWN_COLLECTION" 169ms

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

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:120)
	at ✽.Verify that created transport is "true" in transport table(file:Features/Atom/Transport/Archive.feature:54)

Hooks

After Hooks.deleteTransportAfterTest() 1s 015ms

After Hooks.rollbackAllCustomFieldsSettings() 466ms

After Hooks.rollbackSettings() 154ms

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

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

And Mark custom fields as not obligatory 004ms

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

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

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

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

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 029ms

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

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

And Wait "90" seconds 1m 30s

And Go to "ARCHIVE_TAB" 534ms

And Show "DELIVERY" 182ms

And Go to transport details "DELIVERY" 30s 600ms

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

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

And Wait "7" seconds 7s

And Go to transport details "DELIVERY" 30s 594ms

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

Hooks

After Hooks.deleteTransportAfterTest() 872ms

After Hooks.rollbackAllCustomFieldsSettings() 004ms

After Hooks.rollbackAddedActionAuthorities() 258ms

After Hooks.rollbackRemovedActionAuthorities() 540ms

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

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

And Mark custom fields as not obligatory 004ms

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

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

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

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

And Set advice window in schedule 3s 277ms

And Fill advice form 9s 325ms

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

And Go to "TRANSPORT_TABLE" 434ms

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

And Confirm statuses until reach "on-the-area" 6s 275ms

And Go to transport details "OWN_COLLECTION" 2s 855ms

And Click create similar button 15s 268ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 7s 033ms

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

And Open similar transport details 439ms

Then Check if transport form modal is visible 104ms

Hooks

After Hooks.deleteTransportAfterTest() 823ms

After Hooks.deleteSimilarTransportAfterTest() 579ms

After Hooks.rollbackAllCustomFieldsSettings() 483ms

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

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

And Mark custom fields as not obligatory 005ms

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" 5s 012ms

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

And Set advice window in schedule 3s 228ms

And Fill advice form 9s 286ms

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

And Go to "TRANSPORT_TABLE" 460ms

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

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

And Go to transport details "OWN_COLLECTION" 2s 898ms

And Click create similar button 15s 266ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 7s 027ms

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

And Open similar transport details 472ms

Then Check if transport form modal is visible 087ms

Hooks

After Hooks.deleteTransportAfterTest() 968ms

After Hooks.deleteSimilarTransportAfterTest() 617ms

After Hooks.rollbackAllCustomFieldsSettings() 477ms

	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	51m 18s 990ms	Failed

Tag Report