Cucumber-JVM Reports - Feature: Status confirmation

Project	Number	Date
ApolloFullRunnerReport	develop.359	26 mar 2021, 05:52

	Steps	Scenarios	Features
Status confirmation	408	5	9	0	0	422	29	6	35	36m 49s 862ms	Failed

@deleteTransportAfterTest

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

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 474ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 401ms

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

And Confirm statuses until reach "process-ended" 28s 065ms

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

Hooks

After Hooks.deleteTransportAfterTest() 099ms

@deleteTransportAfterTest

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

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 2s 347ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 608ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 118ms

@deleteTransportAfterTest

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

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 165ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 308ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 095ms

@deleteTransportAfterTest

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

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 1s 111ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 318ms

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

And Confirm statuses until reach "departed" 24s 394ms

Then Check if transport has "departed" 027ms

Hooks

After Hooks.deleteTransportAfterTest() 169ms

@deleteTransportAfterTest

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

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 123ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 332ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 110ms

@deleteTransportAfterTest

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

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 107ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 312ms

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

And Confirm statuses until reach "process-ended" 29s 783ms

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

Hooks

After Hooks.deleteTransportAfterTest() 126ms

@deleteTransportAfterTest

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

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 199ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 307ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 104ms

@deleteTransportAfterTest

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

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 171ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 330ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 108ms

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 275ms

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

When Accept or reject "accept" transferred transport 18s 070ms

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

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

And Set advice window in schedule 2s 724ms

And Fill advice form 14s 686ms

And Click advice save button and wait for advice form to disappear 30s 769ms

And Check if window is "gray" 2s 029ms

Error message

java.lang.AssertionError
	at org.junit.Assert.fail(Assert.java:86)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.junit.Assert.assertTrue(Assert.java:52)
	at CucumberTests.Schedule.ScheduleTest.checkIfWindowIs(ScheduleTest.java:53)
	at ✽.Check if window is "gray"(file:Features/Atom/Statuses/ConfirmStatuses.feature:32)

And Go to "TRANSPORT_TABLE" 000ms

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

Hooks

After Hooks.deleteTransportAfterTest() 143ms

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 248ms

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

When Accept or reject "accept" transferred transport 18s 113ms

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

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

And Set advice window in schedule 2s 644ms

And Fill advice form 14s 712ms

And Click advice save button and wait for advice form to disappear 30s 747ms

And Check if window is "gray" 2s 033ms

Error message

java.lang.AssertionError
	at org.junit.Assert.fail(Assert.java:86)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.junit.Assert.assertTrue(Assert.java:52)
	at CucumberTests.Schedule.ScheduleTest.checkIfWindowIs(ScheduleTest.java:53)
	at ✽.Check if window is "gray"(file:Features/Atom/Statuses/ConfirmStatuses.feature:32)

And Go to "TRANSPORT_TABLE" 000ms

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

Hooks

After Hooks.deleteTransportAfterTest() 167ms

@deleteTransportAfterTest @rollbackAddedActionAuthorities

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

Steps

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 15s 353ms

When Login as "hochland-admin" 2s 826ms

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

And Confirm statuses until reach "arrived" 3s 819ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 138ms

After Hooks.rollbackAddedActionAuthorities() 049ms

@deleteTransportAfterTest

Scenario Outline Check is transport color changed after confirm status

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 215ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 338ms

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

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

And Confirm statuses until reach "arrived" 3s 815ms

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

And Confirm statuses until reach "during-unload" 3s 752ms

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

And Confirm statuses until reach "unloaded" 3s 775ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 120ms

@deleteTransportAfterTest

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

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 004ms

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

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

And Show all transport types 1s 053ms

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

And Set advice window in schedule 2s 554ms

And Fill advice form 8s 449ms

And Click advice save button and wait for advice form to disappear 30s 742ms

And Go to "TRANSPORT_TABLE" 265ms

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

And Confirm statuses until reach "left-the-area" 17s 522ms

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

Hooks

After Hooks.deleteTransportAfterTest() 104ms

@deleteTransportAfterTest

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

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 190ms

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

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

And Show all transport types 1s 042ms

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

And Set advice window in schedule 2s 586ms

And Fill advice form 8s 469ms

And Click advice save button and wait for advice form to disappear 30s 714ms

And Go to "TRANSPORT_TABLE" 200ms

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

And Confirm statuses until reach "left-the-area" 17s 527ms

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

Hooks

After Hooks.deleteTransportAfterTest() 116ms

@deleteTransportAfterTest

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

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 155ms

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

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

And Show all transport types 1s 048ms

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

And Set advice window in schedule 2s 578ms

And Fill advice form 8s 452ms

And Click advice save button and wait for advice form to disappear 30s 773ms

And Go to "TRANSPORT_TABLE" 243ms

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

When Add file to transport by API 619ms

And Confirm statuses until reach "process-ended" 35s 278ms

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

Hooks

After Hooks.deleteTransportAfterTest() 119ms

@deleteTransportAfterTest

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

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 220ms

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

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

And Show all transport types 1s 048ms

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

And Set advice window in schedule 2s 555ms

And Fill advice form 8s 444ms

And Click advice save button and wait for advice form to disappear 30s 768ms

And Go to "TRANSPORT_TABLE" 202ms

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

When Add file to transport by API 294ms

And Confirm statuses until reach "process-ended" 35s 237ms

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

Hooks

After Hooks.deleteTransportAfterTest() 125ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

And Get "Magazynier (R)" settings from "hochland" in "TRANSFER_BETWEEN_WAREHOUSES" 292ms

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

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

And Get inputs from database "ADVICE_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 003ms

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

And Show all transport types 1s 072ms

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

And Set advice window in schedule 6s 439ms

And Fill advice form 11s 937ms

And Click advice save button and wait for advice form to disappear 30s 741ms

And Go to "TRANSPORT_TABLE" 213ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 121ms

After Hooks.rollbackCustomFieldSettings() 077ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "LOAD" 024ms

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

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

And Get inputs from database "ADVICE_LOAD" "super-admin-keeeper" 002ms

And Login as "keeeper-admin" 1s 850ms

And Show all transport types 1s 140ms

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

And Set advice window in schedule 2s 385ms

And Fill advice form 13s 274ms

And Click advice save button and wait for advice form to disappear 30s 740ms

And Go to "TRANSPORT_TABLE" 208ms

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

And Confirm statuses until reach "arrived" 3s 783ms

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

Hooks

After Hooks.deleteTransportAfterTest() 130ms

After Hooks.rollbackCustomFieldSettings() 037ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "CONTAINER" 025ms

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

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

And Get inputs from database "ADVICE_CONTAINER" "super-admin-keeeper" 003ms

And Login as "keeeper-admin" 1s 968ms

And Show all transport types 1s 060ms

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

And Set advice window in schedule 2s 469ms

And Fill advice form 13s 269ms

And Click advice save button and wait for advice form to disappear 30s 718ms

And Go to "TRANSPORT_TABLE" 202ms

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

And Confirm statuses until reach "arrived" 3s 818ms

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

Hooks

After Hooks.deleteTransportAfterTest() 106ms

After Hooks.rollbackCustomFieldSettings() 036ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "UNLOAD" 014ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 333ms

And Login as "keeeper-admin" 1s 906ms

And Go to "TRANSPORT_TABLE" 123ms

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

And Confirm statuses until reach "arrived" 3s 833ms

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

Hooks

After Hooks.deleteTransportAfterTest() 109ms

After Hooks.rollbackCustomFieldSettings() 041ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "TANKER_GRANULATE_DELIVERY" 024ms

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

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 347ms

And Login as "keeeper-admin" 1s 823ms

And Go to "TRANSPORT_TABLE" 103ms

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

And Confirm statuses until reach "arrived" 3s 824ms

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

Hooks

After Hooks.deleteTransportAfterTest() 093ms

After Hooks.rollbackCustomFieldSettings() 034ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

And Get "Magazynier" settings from "hochland" in "DELIVERY" 021ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 391ms

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

And Go to "TRANSPORT_TABLE" 219ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 127ms

After Hooks.rollbackCustomFieldSettings() 100ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "LOAD" 025ms

And Get inputs from database "ADVICE_LOAD" "super-admin-keeeper" 003ms

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

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

And Login as "keeeper-admin" 1s 723ms

And Show all transport types 1s 138ms

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

And Set advice window in schedule 2s 393ms

And Fill advice form 13s 311ms

And Click advice save button and wait for advice form to disappear 30s 708ms

And Go to "TRANSPORT_TABLE" 191ms

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

When Confirm statuses until reach "arrived" 3s 828ms

And Check if next status is not possible to confirm 111ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 002ms

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

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

And Fill transport form 24s 767ms

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

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

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

And Fill "meeting-sanitary-and-technical-conditions" in transport form 15s 816ms

And Confirm statuses until reach "process-ended" 24s 251ms

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

After Hooks.rollbackCustomFieldSettings() 030ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "CONTAINER" 021ms

And Get inputs from database "ADVICE_CONTAINER" "super-admin-keeeper" 002ms

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

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

And Login as "keeeper-admin" 2s 328ms

And Show all transport types 1s 058ms

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

And Set advice window in schedule 2s 395ms

And Fill advice form 13s 226ms

And Click advice save button and wait for advice form to disappear 30s 738ms

And Go to "TRANSPORT_TABLE" 208ms

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

When Confirm statuses until reach "arrived" 3s 824ms

And Check if next status is not possible to confirm 103ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 002ms

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

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

And Fill transport form 24s 757ms

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

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

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

And Fill "meeting-sanitary-and-technical-conditions" in transport form 15s 792ms

And Confirm statuses until reach "process-ended" 24s 286ms

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

Hooks

After Hooks.deleteTransportAfterTest() 112ms

After Hooks.rollbackCustomFieldSettings() 050ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

And Get "Magazynier (R)" settings from "hochland" in "TRANSFER_BETWEEN_WAREHOUSES" 023ms

And Get inputs from database "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" 055ms

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

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

And Show all transport types 1s 058ms

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

And Set advice window in schedule 6s 445ms

And Fill advice form 11s 943ms

And Click advice save button and wait for advice form to disappear 30s 773ms

And Go to "TRANSPORT_TABLE" 219ms

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

When Confirm statuses until reach "during-load" 6s 610ms

And Check if next status is not possible to confirm 114ms

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 002ms

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

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

And Fill transport form 36s 332ms

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

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

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

And Fill "warehouseman-(u)" in transport form 15s 855ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 152ms

After Hooks.rollbackCustomFieldSettings() 060ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "UNLOAD" 025ms

And Get inputs from database "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" 034ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 339ms

And Login as "keeeper-admin" 2s 535ms

And Go to "TRANSPORT_TABLE" 137ms

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

When Confirm statuses until reach "arrived" 3s 795ms

And Check if next status is not possible to confirm 112ms

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

And Fill transport form 37s 884ms

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

And Confirm statuses until reach "process-ended" 24s 251ms

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

Hooks

After Hooks.deleteTransportAfterTest() 120ms

After Hooks.rollbackCustomFieldSettings() 035ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "TANKER_GRANULATE_DELIVERY" 023ms

And Get inputs from database "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" 041ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 384ms

And Login as "keeeper-admin" 1s 937ms

And Go to "TRANSPORT_TABLE" 150ms

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

When Confirm statuses until reach "arrived" 3s 800ms

And Check if next status is not possible to confirm 113ms

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

And Fill transport form 36s 378ms

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

And Confirm statuses until reach "process-ended" 24s 298ms

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

Hooks

After Hooks.deleteTransportAfterTest() 128ms

After Hooks.rollbackCustomFieldSettings() 033ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

And Get "Magazynier" settings from "hochland" in "DELIVERY" 024ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 002ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 397ms

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

And Go to "TRANSPORT_TABLE" 201ms

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

When Confirm statuses until reach "during-unload" 6s 582ms

And Check if next status is not possible to confirm 119ms

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

And Fill transport form 36s 113ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 129ms

After Hooks.rollbackCustomFieldSettings() 101ms

@deleteTransportAfterTest

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

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 1s 347ms

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

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

And Login as "swiss-krono-delivery-guard" 1s 849ms

And Go to "TRANSPORT_TABLE" 162ms

When Confirm "Departure" status in transport row 3s 085ms

Then Verify that "Departure" has been confirmed 15s 032ms

Error message

java.lang.AssertionError: Status nie został potwierdzony!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.verifyThatHasBeenConfirmed(ConfirmStatuses.java:118)
	at ✽.Verify that "Departure" has been confirmed(file:Features/Atom/Statuses/ConfirmStatuses.feature:219)

Hooks

After Hooks.deleteTransportAfterTest() 128ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

Steps

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

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "UNLOAD" 020ms

And Get inputs from database "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" 035ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 15s 285ms

When Login as "keeeper-admin" 2s 039ms

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

And Confirm statuses until reach "arrived" 3s 823ms

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

And Fill transport form 38s 057ms

Then Check if next status is not possible to confirm in transport details 070ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.rollbackCustomFieldSettings() 034ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

Steps

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

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "TANKER_GRANULATE_DELIVERY" 014ms

And Get inputs from database "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" 033ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 333ms

When Login as "keeeper-admin" 1s 978ms

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

And Confirm statuses until reach "arrived" 3s 823ms

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

And Fill transport form 36s 467ms

Then Check if next status is not possible to confirm in transport details 064ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

After Hooks.rollbackCustomFieldSettings() 032ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

Steps

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

And Get "Magazynier" settings from "hochland" in "DELIVERY" 026ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 002ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 392ms

When Login as "hochland-admin" 2s 479ms

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

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

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

And Fill transport form 36s 082ms

Then Check if next status is not possible to confirm in transport details 055ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

After Hooks.rollbackCustomFieldSettings() 099ms

@deleteAllTransportsAfterTest @rollbackAddedActionAuthorities

Scenario Outline Check if unload step status is visible for specific users [A-6868]

Steps

Given Set token of apiUsername "super-admin-skz" 095ms

And Add action authority with: "swisskrono" "swisskrono-admin" "SMALLS_EXPORT" "MOVE_UNLOAD_STEPS" "ACTIVE" 042ms

And Add action authority with: "swisskrono" "pskza1-carrier@qa.qa-test" "SMALLS_EXPORT" "MOVE_UNLOAD_STEPS" "ACTIVE" 053ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 221ms

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

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 287ms

And Show all transport types 1s 070ms

Then Check if transport has "Potwierdzenie kolejności rozładunków" 15s 008ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//td[contains(@data-status-name, 'Potwierdzenie kolejności rozładunków')]"}
  (Session info: headless chrome=88.0.4324.182)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.ZUoRZl}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=88.0.4324.182, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 423f60b2023fdfe4d7313f5fd928fd53
*** Element info: {Using=xpath, value=//td[contains(@data-status-name, 'Potwierdzenie kolejności rozładunków')]}
	at sun.reflect.GeneratedConstructorAccessor204.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at CucumberTests.StatusTests.StatusUtils.checkIfTransportHasStatus(StatusUtils.java:20)
	at ✽.Check if transport has "Potwierdzenie kolejności rozładunków"(file:Features/Atom/Statuses/ConfirmStatuses.feature:252)

And If user is login then logout 000ms

And Login as "pskza1-carrier@qa.qa-test" 000ms

When Accept or reject "accept" transferred transport 000ms

And Show all transport types 000ms

Then Check if transport has "Potwierdzenie kolejności rozładunków" 000ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 090ms

After Hooks.deleteAllTransports() 46s 543ms

@deleteAllTransportsAfterTest @deleteAllAddedStatus

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

Steps

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

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 262ms

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

When Accept or reject "accept" transferred transport 18s 107ms

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

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

And Set advice window in schedule 2s 683ms

And Fill advice form 14s 727ms

And Click advice save button and wait for advice form to disappear 30s 745ms

And If user is login then logout 116ms

And Login as "swisskrono-admin" 2s 344ms

And Show all transport types 1s 064ms

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

And Go to "SETTINGS_TAB" 314ms

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

And Delete created transport by API 104ms

Then If user is login then logout 325ms

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 268ms

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

When Accept or reject "accept" transferred transport 17s 984ms

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

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

And Set advice window in schedule 2s 663ms

And Fill advice form 14s 789ms

And Click advice save button and wait for advice form to disappear 30s 761ms

And If user is login then logout 115ms

And Login as "swisskrono-admin" 1s 339ms

And Show all transport types 1s 083ms

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

Hooks

After Hooks.deleteAllTransports() 1m 1s 341ms

After Hooks.deleteAllAddedStatus() 15s 034ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div/a[text()='Drobnica import']"}
  (Session info: headless chrome=88.0.4324.182)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.ZUoRZl}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=88.0.4324.182, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 423f60b2023fdfe4d7313f5fd928fd53
*** Element info: {Using=xpath, value=//div/a[text()='Drobnica import']}
	at sun.reflect.GeneratedConstructorAccessor204.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at Pages.Settings.SettingsPage.goToTransportTypeSettings(SettingsPage.java:35)
	at CucumberTests.Hooks.deleteAllAddedStatus(Hooks.java:568)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

@deleteTransportAfterTest @rollbackTaskChanges

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

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

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 668ms

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

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

And Go to "TRANSPORT_TABLE" 222ms

And Set actual confirmed transport status list 1s 383ms

And Disable task by API 047ms

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

And Edit transport hours and recalculate statuses 16s 345ms

Then Verify that confirmed statuses is still the same 133ms

Error message

java.lang.AssertionError: Wyłączony task jest niewidoczny na liście potwierdzonych statusów!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.verifyThatConfirmedStatusesIsStillTheSame(ConfirmStatuses.java:226)
	at ✽.Verify that confirmed statuses is still the same(file:Features/Atom/Statuses/ConfirmStatuses.feature:317)

Hooks

After Hooks.deleteTransportAfterTest() 129ms

After Hooks.rollbackTaskChanges() 043ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Status confirmation	408	5	9	0	0	422	29	6	35	36m 49s 862ms	Failed

Feature Report