Cucumber-JVM Reports - Tag: @rollbackAllCustomFieldsSettings

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.82	16 lip 2021, 06:58

	Steps	Scenarios	Features
@rollbackAllCustomFieldsSettings	570	2	1	0	0	573	36	2	38	55m 814ms	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" 227ms

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

And Mark custom fields as not obligatory 005ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 525ms

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

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

Hooks

After Hooks.deleteTransportsAfterTest() 2s 526ms

After Hooks.rollbackAllCustomFieldsSettings() 353ms

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

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

And Mark custom fields as not obligatory 2s 896ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 899ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 553ms

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

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

And Mark custom fields as not obligatory 006ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 834ms

After Hooks.rollbackAllCustomFieldsSettings() 443ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 695ms

After Hooks.rollbackAllCustomFieldsSettings() 421ms

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

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

And Mark custom fields as not obligatory 005ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 739ms

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

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

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

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

And Confirm statuses until reach "process-ended" 27s 053ms

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

Hooks

After Hooks.deleteTransportAfterTest() 762ms

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

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

And Mark custom fields as not obligatory 577ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 803ms

After Hooks.rollbackAllCustomFieldsSettings() 596ms

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

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

And Mark custom fields as not obligatory 618ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 741ms

After Hooks.rollbackAllCustomFieldsSettings() 748ms

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

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

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

And Mark custom fields as not obligatory 2s 799ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 024ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 436ms

After Hooks.rollbackAddedActionAuthorities() 334ms

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

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

And Mark custom fields as not obligatory 2s 746ms

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

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

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

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

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

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 895ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 455ms

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 "DELIVERY" transport type and "piast" company 224ms

And Mark custom fields as not obligatory 008ms

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

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

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

And Show all transport types 1s 154ms

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

And Set advice window in schedule 3s 283ms

And Fill advice form 10s 508ms

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

And Go to "TRANSPORT_TABLE" 456ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 852ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 866ms

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

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

And Mark custom fields as not obligatory 009ms

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

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 2s 062ms

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

And Show all transport types 1s 141ms

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

And Set advice window in schedule 3s 338ms

And Fill advice form 10s 447ms

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

And Go to "TRANSPORT_TABLE" 459ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 864ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 404ms

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

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

And Mark custom fields as not obligatory 007ms

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

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

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

And Show all transport types 1s 135ms

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

And Set advice window in schedule 3s 304ms

And Fill advice form 10s 597ms

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

And Go to "TRANSPORT_TABLE" 447ms

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

When Add file to transport by API 1s 771ms

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

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 (ce0cfe6e091c8f8aa74b3a11b177404f)] -> 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() 847ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 860ms

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

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

And Mark custom fields as not obligatory 012ms

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

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

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

And Show all transport types 1s 142ms

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

And Set advice window in schedule 3s 306ms

And Fill advice form 10s 463ms

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

And Go to "TRANSPORT_TABLE" 429ms

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

When Add file to transport by API 1s 710ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 822ms

After Hooks.rollbackAllCustomFieldsSettings() 4s 431ms

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

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

And Mark custom fields as not obligatory 4s 927ms

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

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

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

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

And Show all transport types 1s 145ms

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

And Set advice window in schedule 7s 490ms

And Fill advice form 16s 296ms

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

And Go to "TRANSPORT_TABLE" 420ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 027ms

After Hooks.rollbackAllCustomFieldsSettings() 5s 289ms

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

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

And Mark custom fields as not obligatory 788ms

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

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

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

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

And Show all transport types 1s 159ms

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

And Set advice window in schedule 3s 258ms

And Fill advice form 16s 463ms

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

And Go to "TRANSPORT_TABLE" 447ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 779ms

After Hooks.rollbackAllCustomFieldsSettings() 909ms

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

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

And Mark custom fields as not obligatory 700ms

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

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

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

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

And Show all transport types 1s 172ms

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

And Set advice window in schedule 3s 225ms

And Fill advice form 16s 366ms

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

And Go to "TRANSPORT_TABLE" 429ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 834ms

After Hooks.rollbackAllCustomFieldsSettings() 858ms

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

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

And Mark custom fields as not obligatory 582ms

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

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

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

And Go to "TRANSPORT_TABLE" 394ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 868ms

After Hooks.rollbackAllCustomFieldsSettings() 591ms

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

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

And Mark custom fields as not obligatory 599ms

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

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

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

And Go to "TRANSPORT_TABLE" 428ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 984ms

After Hooks.rollbackAllCustomFieldsSettings() 723ms

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

And Mark custom fields as not obligatory 2s 678ms

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

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

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

And Go to "TRANSPORT_TABLE" 474ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 165ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 344ms

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

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

And Mark custom fields as not obligatory 755ms

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

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

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

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

And Show all transport types 1s 292ms

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

And Set advice window in schedule 3s 228ms

And Fill advice form 16s 297ms

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

And Go to "TRANSPORT_TABLE" 451ms

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

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

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

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

And Click cancel in status confirmation modal 15s 349ms

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

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

And Fill transport form 28s 572ms

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

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

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

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

And Confirm statuses until reach "process-ended" 15s 641ms

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

Hooks

After Hooks.deleteTransportAfterTest() 906ms

After Hooks.rollbackAllCustomFieldsSettings() 837ms

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

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

And Mark custom fields as not obligatory 777ms

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

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

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

And Show all transport types 1s 168ms

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

And Set advice window in schedule 3s 228ms

And Fill advice form 16s 337ms

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

And Go to "TRANSPORT_TABLE" 454ms

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

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

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

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

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

And Click cancel in status confirmation modal 15s 379ms

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

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

And Fill transport form 28s 685ms

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

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

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

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

And Confirm statuses until reach "process-ended" 15s 624ms

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

Hooks

After Hooks.deleteTransportAfterTest() 836ms

After Hooks.rollbackAllCustomFieldsSettings() 852ms

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

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

And Mark custom fields as not obligatory 4s 809ms

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

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

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

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

And Show all transport types 1s 158ms

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

And Set advice window in schedule 7s 482ms

And Fill advice form 16s 370ms

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

And Go to "TRANSPORT_TABLE" 450ms

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

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

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

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

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

And Click cancel in status confirmation modal 15s 335ms

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

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

And Fill transport form 39s 699ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 164ms

After Hooks.rollbackAllCustomFieldsSettings() 5s 116ms

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

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

And Mark custom fields as not obligatory 558ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 408ms

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

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

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

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

And Click cancel in status confirmation modal 15s 420ms

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

And Fill transport form 40s 848ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 812ms

After Hooks.rollbackAllCustomFieldsSettings() 584ms

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

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

And Mark custom fields as not obligatory 589ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 420ms

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

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

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

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

And Click cancel in status confirmation modal 15s 435ms

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

And Fill transport form 40s 833ms

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

And Confirm statuses until reach "process-ended" 15s 685ms

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

Hooks

After Hooks.deleteTransportAfterTest() 888ms

After Hooks.rollbackAllCustomFieldsSettings() 674ms

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

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

And Mark custom fields as not obligatory 2s 785ms

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

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

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

And Go to "TRANSPORT_TABLE" 476ms

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

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

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

And Click cancel in status confirmation modal 15s 646ms

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

And Fill transport form 40s 516ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 870ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 457ms

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

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

And Mark custom fields as not obligatory 589ms

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

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

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

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

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

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

And Click cancel in status confirmation modal 15s 336ms

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

And Fill transport form 40s 820ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 865ms

After Hooks.rollbackAllCustomFieldsSettings() 593ms

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

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

And Mark custom fields as not obligatory 576ms

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

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

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

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

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

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

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

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

And Click cancel in status confirmation modal 15s 376ms

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

And Fill transport form 40s 789ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 857ms

After Hooks.rollbackAllCustomFieldsSettings() 710ms

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

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

And Mark custom fields as not obligatory 2s 752ms

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

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

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

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

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

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

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

And Click cancel in status confirmation modal 15s 568ms

And Go to transport details "DELIVERY" 3s 012ms

And Fill transport form 40s 683ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 875ms

After Hooks.rollbackAllCustomFieldsSettings() 3s 352ms

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

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

And Mark custom fields as not obligatory 755ms

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

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 512ms

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

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

When Open statuses popup 143ms

And Toggle status date confirmation checkbox 385ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 1s 007ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 106ms

After Hooks.deleteModeOfTransportationAfterTest() 333ms

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

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

And Mark custom fields as not obligatory 724ms

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

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 505ms

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

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

And Open statuses popup 154ms

And Toggle status date confirmation checkbox 396ms

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

Then Verify that status cannot be confirmed 1s 229ms

Hooks

After Hooks.deleteTransportAfterTest() 895ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 174ms

After Hooks.deleteModeOfTransportationAfterTest() 315ms

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

And Mark custom fields as not obligatory 750ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 509ms

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

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

And Open statuses popup 142ms

And Toggle status date confirmation checkbox 400ms

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

Then Verify that status cannot be confirmed 1s 232ms

Hooks

After Hooks.deleteTransportAfterTest() 966ms

After Hooks.rollbackAllCustomFieldsSettings() 2s 161ms

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

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

And Mark custom fields as not obligatory 007ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 494ms

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

And Set actual confirmed transport status list 2s 030ms

And Disable task by API 300ms

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

And Edit transport hours and recalculate statuses 30s 627ms

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

Hooks

After Hooks.deleteTransportAfterTest() 788ms

After Hooks.rollbackAllCustomFieldsSettings() 347ms

After Hooks.rollbackTaskChanges() 187ms

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

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

And Mark custom fields as not obligatory 006ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 512ms

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

And Disable task by API 205ms

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

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

And Go to "TRANSPORT_TABLE" 492ms

Then Verify that "START_OF_UNLOADING" is not visible 382ms

Hooks

After Hooks.deleteTransportAfterTest() 898ms

After Hooks.rollbackAllCustomFieldsSettings() 342ms

After Hooks.rollbackTaskChanges() 192ms

View Feature Move transport to archive

@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings @FLAKY

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

Steps

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

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

And Mark custom fields as not obligatory 005ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 409ms

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

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

And Go to "TRANSPORT_TABLE" 454ms

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

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

And Wait "12" seconds 12s

Then Go to "ARCHIVE_TAB" 526ms

And Show "OWN_COLLECTION" 165ms

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

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() 737ms

After Hooks.rollbackAllCustomFieldsSettings() 486ms

After Hooks.rollbackSettings() 148ms

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

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

And Mark custom fields as not obligatory 004ms

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

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

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

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

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

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

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

And Wait "90" seconds 1m 30s

And Go to "ARCHIVE_TAB" 480ms

And Show "DELIVERY" 153ms

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

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

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

And Wait "7" seconds 7s

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

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

Hooks

After Hooks.deleteTransportAfterTest() 643ms

After Hooks.rollbackAllCustomFieldsSettings() 004ms

After Hooks.rollbackAddedActionAuthorities() 279ms

After Hooks.rollbackRemovedActionAuthorities() 554ms

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

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

And Mark custom fields as not obligatory 004ms

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

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

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

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

And Set advice window in schedule 3s 237ms

And Fill advice form 9s 266ms

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

And Go to "TRANSPORT_TABLE" 402ms

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

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

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

And Click create similar button 15s 264ms

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

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

And Open similar transport details 472ms

Then Check if transport form modal is visible 071ms

Hooks

After Hooks.deleteSimilarTransportAfterTest() 659ms

After Hooks.deleteTransportAfterTest() 807ms

After Hooks.rollbackAllCustomFieldsSettings() 488ms

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

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

And Mark custom fields as not obligatory 004ms

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

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

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

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

And Set advice window in schedule 3s 250ms

And Fill advice form 9s 192ms

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

And Go to "TRANSPORT_TABLE" 381ms

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

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

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

And Click create similar button 15s 214ms

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

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

And Open similar transport details 474ms

Then Check if transport form modal is visible 080ms

Hooks

After Hooks.deleteSimilarTransportAfterTest() 578ms

After Hooks.deleteTransportAfterTest() 771ms

After Hooks.rollbackAllCustomFieldsSettings() 492ms

	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	55m 814ms	Failed

Tag Report