Cucumber-JVM Reports - Feature: Status confirmation

Project	Number	Date
ApolloFullRunnerReport	A-7146.436	26 maj 2021, 01:01

	Steps	Scenarios	Features
Status confirmation	471	2	3	0	0	476	35	2	37	38m 55s 911ms	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 368ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 137ms

@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" 1s 144ms

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

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

And Confirm statuses until reach "process-ended" 8s 632ms

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

Hooks

After Hooks.deleteTransportAfterTest() 146ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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

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

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

And Confirm statuses until reach "departed" 50s 750ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//button[@class='btn btn-sm btn-primary btn-wide']"}
  (Session info: headless chrome=90.0.4430.212)
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=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.rWS44N}, 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=90.0.4430.212, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 9a0b5d3fd5f7c180699bb810740e4442
*** Element info: {Using=xpath, value=//button[@class='btn btn-sm btn-primary btn-wide']}
	at sun.reflect.GeneratedConstructorAccessor213.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.BasePage.getWebElementByXpath(BasePage.java:323)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:297)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:287)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:84)
	at ✽.Confirm statuses until reach "departed"(file:Features/Atom/Statuses/ConfirmStatuses.feature:8)

Then Check if transport has "departed" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 168ms

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

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

When Find transport in table with status "created" 18s 211ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//td[contains(@data-status-name, 'created')]"}
  (Session info: headless chrome=90.0.4430.212)
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=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.rWS44N}, 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=90.0.4430.212, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 9a0b5d3fd5f7c180699bb810740e4442
*** Element info: {Using=xpath, value=//td[contains(@data-status-name, 'created')]}
	at sun.reflect.GeneratedConstructorAccessor213.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.ConfirmStatuses.findTransportInTableWith(ConfirmStatuses.java:68)
	at ✽.Find transport in table with status "created"(file:Features/Atom/Statuses/ConfirmStatuses.feature:7)

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

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

Hooks

After Hooks.deleteTransportAfterTest() 146ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 127ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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

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

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

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

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

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

And Set advice window in schedule 2s 781ms

And Fill advice form 14s 768ms

And Click advice save button and wait for advice form to disappear 31s 266ms

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

And Go to "TRANSPORT_TABLE" 192ms

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

Hooks

After Hooks.deleteTransportAfterTest() 135ms

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

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

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

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

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

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

And Set advice window in schedule 2s 725ms

And Fill advice form 14s 640ms

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

And Check if window is "silver" 2s 026ms

And Go to "TRANSPORT_TABLE" 155ms

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 129ms

After Hooks.rollbackAddedActionAuthorities() 071ms

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

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

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

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

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

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 145ms

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

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

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

And Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 635ms

And Fill advice form 8s 413ms

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

And Go to "TRANSPORT_TABLE" 242ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 129ms

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

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

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

And Show all transport types 1s 045ms

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

And Set advice window in schedule 2s 621ms

And Fill advice form 8s 359ms

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

And Go to "TRANSPORT_TABLE" 180ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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

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

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

And Show all transport types 1s 044ms

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

And Set advice window in schedule 2s 656ms

And Fill advice form 8s 408ms

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

And Go to "TRANSPORT_TABLE" 234ms

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

When Add file to transport by API 577ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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

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

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

And Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 643ms

And Fill advice form 8s 294ms

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

And Go to "TRANSPORT_TABLE" 203ms

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

When Add file to transport by API 294ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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

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

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

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

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

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

And Show all transport types 1s 048ms

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

And Set advice window in schedule 6s 538ms

And Fill advice form 13s 245ms

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

And Go to "TRANSPORT_TABLE" 203ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 153ms

After Hooks.rollbackCustomFieldSettings() 103ms

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

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

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

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

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

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

And Show all transport types 1s 051ms

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

And Set advice window in schedule 2s 518ms

And Fill advice form 13s 255ms

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

And Go to "TRANSPORT_TABLE" 210ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 137ms

After Hooks.rollbackCustomFieldSettings() 053ms

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

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

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

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

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

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

And Show all transport types 1s 054ms

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

And Set advice window in schedule 2s 542ms

And Fill advice form 13s 248ms

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

And Go to "TRANSPORT_TABLE" 196ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 125ms

After Hooks.rollbackCustomFieldSettings() 058ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 123ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

After Hooks.rollbackCustomFieldSettings() 051ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 134ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 218ms

After Hooks.rollbackCustomFieldSettings() 082ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 210ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 172ms

After Hooks.rollbackCustomFieldSettings() 121ms

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

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

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

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

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

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

And Show all transport types 1s 052ms

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

And Set advice window in schedule 2s 571ms

And Fill advice form 13s 144ms

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

And Go to "TRANSPORT_TABLE" 171ms

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

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

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

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

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

And Click cancel in status confirmation modal 15s 130ms

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

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

And Fill transport form 24s 710ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 128ms

After Hooks.rollbackCustomFieldSettings() 052ms

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

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

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

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

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

And Show all transport types 1s 047ms

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

And Set advice window in schedule 2s 514ms

And Fill advice form 13s 195ms

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

And Go to "TRANSPORT_TABLE" 209ms

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

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

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

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

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

And Click cancel in status confirmation modal 15s 144ms

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

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

And Fill transport form 24s 713ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 118ms

After Hooks.rollbackCustomFieldSettings() 074ms

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

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

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

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

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

And Show all transport types 1s 046ms

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

And Set advice window in schedule 6s 529ms

And Fill advice form 13s 307ms

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

And Go to "TRANSPORT_TABLE" 160ms

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

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

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

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

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

And Click cancel in status confirmation modal 15s 132ms

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

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

And Fill transport form 36s 123ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 150ms

After Hooks.rollbackCustomFieldSettings() 063ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 111ms

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

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

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

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

And Click cancel in status confirmation modal 15s 146ms

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

And Fill transport form 36s 374ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 116ms

After Hooks.rollbackCustomFieldSettings() 042ms

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

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 135ms

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

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

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

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

And Click cancel in status confirmation modal 15s 145ms

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

And Fill transport form 36s 315ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 132ms

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 - without advice step

Steps

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 196ms

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

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

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

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

And Click cancel in status confirmation modal 15s 192ms

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

And Fill transport form 35s 856ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 144ms

After Hooks.rollbackCustomFieldSettings() 112ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 199ms

When Confirm "Departure" status in transport row 061ms

Then Verify that "Departure" has been confirmed 259ms

Hooks

After Hooks.deleteTransportAfterTest() 134ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

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

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

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

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

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

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

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

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

And Click cancel in status confirmation modal 15s 180ms

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

And Fill transport form 36s 396ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 104ms

After Hooks.rollbackCustomFieldSettings() 059ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

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

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

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

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

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

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

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

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

And Click cancel in status confirmation modal 15s 151ms

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

And Fill transport form 36s 427ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 118ms

After Hooks.rollbackCustomFieldSettings() 055ms

@deleteTransportAfterTest @rollbackCustomFieldSettings

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

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

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

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

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

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

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

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

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

And Click cancel in status confirmation modal 15s 167ms

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

And Fill transport form 35s 711ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

After Hooks.rollbackCustomFieldSettings() 118ms

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

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

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

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 254ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 869ms

And Login as "bausch-admin" 1s 581ms

And Go to "TRANSPORT_TABLE" 230ms

And Find transport in table with status "on-the-way" 3s 206ms

When Open statuses popup 103ms

And Toggle status date confirmation checkbox 296ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 146ms

After Hooks.deleteModeOfTransportationAfterTest() 145ms

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

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

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

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 281ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 827ms

And Login as "bausch-admin" 1s 119ms

And Go to "TRANSPORT_TABLE" 213ms

And Find transport in table with status "on-the-way" 3s 229ms

And Open statuses popup 103ms

And Toggle status date confirmation checkbox 316ms

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

Then Verify that status cannot be confirmed 1s 101ms

Hooks

After Hooks.deleteTransportAfterTest() 145ms

After Hooks.deleteModeOfTransportationAfterTest() 114ms

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

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

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

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 205ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 837ms

And Login as "bausch-admin" 1s 152ms

And Go to "TRANSPORT_TABLE" 229ms

And Find transport in table with status "on-the-way" 3s 187ms

And Open statuses popup 144ms

And Toggle status date confirmation checkbox 281ms

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

Then Verify that status cannot be confirmed 1s 063ms

Hooks

After Hooks.deleteTransportAfterTest() 144ms

After Hooks.deleteModeOfTransportationAfterTest() 114ms

@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" 1s 697ms

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

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

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

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

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

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

And Set advice window in schedule 2s 761ms

And Fill advice form 14s 615ms

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

And If user is login then logout 110ms

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

And Show all transport types 1s 079ms

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

And Go to "SETTINGS_TAB" 339ms

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

And Delete created transport by API 134ms

Then If user is login then logout 408ms

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

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

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

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

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

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

And Set advice window in schedule 2s 721ms

And Fill advice form 14s 498ms

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

And If user is login then logout 108ms

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

And Show all transport types 1s 047ms

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

Hooks

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

After Hooks.deleteAllAddedStatus() 2s 257ms

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

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

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

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

When Login as "farmacol-admin" 1s 697ms

And Go to "TRANSPORT_TABLE" 214ms

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

And Set actual confirmed transport status list 1s 374ms

And Disable task by API 063ms

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

And Edit transport hours and recalculate statuses 16s 340ms

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

Hooks

After Hooks.deleteTransportAfterTest() 147ms

After Hooks.rollbackTaskChanges() 058ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Status confirmation	471	2	3	0	0	476	35	2	37	38m 55s 911ms	Failed

Feature Report