Cucumber-JVM Reports - Feature: Status confirmation

Project	Number	Date
ApolloFullRunnerReport	develop.437	26 maj 2021, 09:53

	Steps	Scenarios	Features
Status confirmation	471	2	3	0	0	476	35	2	37	39m 27s 088ms	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 418ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 16s 025ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 108ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 154ms

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

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

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

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

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/temp/buildTmp/.com.google.Chrome.x7scRn}, 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: f61f6420f9a12e09488e06998535d39b
*** Element info: {Using=xpath, value=//button[@class='btn btn-sm btn-primary btn-wide']}
	at sun.reflect.GeneratedConstructorAccessor202.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() 144ms

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

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

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

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/temp/buildTmp/.com.google.Chrome.x7scRn}, 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: f61f6420f9a12e09488e06998535d39b
*** Element info: {Using=xpath, value=//td[contains(@data-status-name, 'created')]}
	at sun.reflect.GeneratedConstructorAccessor202.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() 114ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 136ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 102ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 144ms

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

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

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

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

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

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

And Set advice window in schedule 2s 902ms

And Fill advice form 14s 603ms

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

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

And Go to "TRANSPORT_TABLE" 207ms

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

Hooks

After Hooks.deleteTransportAfterTest() 150ms

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

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

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

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

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

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

And Set advice window in schedule 2s 767ms

And Fill advice form 14s 569ms

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

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

And Go to "TRANSPORT_TABLE" 179ms

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

Hooks

After Hooks.deleteTransportAfterTest() 143ms

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

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 145ms

After Hooks.rollbackAddedActionAuthorities() 087ms

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

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

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

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

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

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 142ms

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

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

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

And Show all transport types 1s 047ms

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

And Set advice window in schedule 2s 660ms

And Fill advice form 8s 384ms

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

And Go to "TRANSPORT_TABLE" 245ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 127ms

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

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

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

And Set advice window in schedule 2s 655ms

And Fill advice form 8s 375ms

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

And Go to "TRANSPORT_TABLE" 193ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 144ms

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

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

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

And Show all transport types 1s 037ms

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

And Set advice window in schedule 2s 662ms

And Fill advice form 8s 418ms

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

And Go to "TRANSPORT_TABLE" 230ms

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

When Add file to transport by API 1s 068ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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

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

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

And Show all transport types 1s 044ms

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

And Set advice window in schedule 2s 651ms

And Fill advice form 8s 291ms

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

And Go to "TRANSPORT_TABLE" 197ms

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

When Add file to transport by API 367ms

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

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

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

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

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

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

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

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

And Show all transport types 1s 044ms

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

And Set advice window in schedule 6s 545ms

And Fill advice form 13s 361ms

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

And Go to "TRANSPORT_TABLE" 178ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 128ms

After Hooks.rollbackCustomFieldSettings() 100ms

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

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

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

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

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

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

And Show all transport types 1s 054ms

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

And Set advice window in schedule 2s 508ms

And Fill advice form 13s 200ms

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

And Go to "TRANSPORT_TABLE" 218ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 147ms

After Hooks.rollbackCustomFieldSettings() 048ms

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

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

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

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

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

And Show all transport types 1s 048ms

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

And Set advice window in schedule 2s 546ms

And Fill advice form 13s 170ms

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

And Go to "TRANSPORT_TABLE" 205ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 144ms

After Hooks.rollbackCustomFieldSettings() 059ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 109ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 136ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 108ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 148ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 215ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 142ms

After Hooks.rollbackCustomFieldSettings() 118ms

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

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

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

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

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

And Show all transport types 1s 048ms

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

And Set advice window in schedule 2s 483ms

And Fill advice form 13s 192ms

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

And Go to "TRANSPORT_TABLE" 199ms

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

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

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

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

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

And Click cancel in status confirmation modal 15s 156ms

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

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

And Fill transport form 24s 720ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 125ms

After Hooks.rollbackCustomFieldSettings() 066ms

@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 "CONTAINER" 039ms

And Set "advice" inputs from JSON file "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" 049ms

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

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

And Show all transport types 1s 062ms

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

And Set advice window in schedule 2s 528ms

And Fill advice form 13s 207ms

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

And Go to "TRANSPORT_TABLE" 209ms

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

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

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

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

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

And Click cancel in status confirmation modal 15s 148ms

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

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

And Fill transport form 24s 626ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 109ms

After Hooks.rollbackCustomFieldSettings() 071ms

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

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

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

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

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

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

And Show all transport types 1s 044ms

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

And Set advice window in schedule 6s 551ms

And Fill advice form 13s 250ms

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

And Go to "TRANSPORT_TABLE" 184ms

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

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

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

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

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

And Click cancel in status confirmation modal 15s 183ms

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

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

And Fill transport form 36s 122ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 191ms

After Hooks.rollbackCustomFieldSettings() 089ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 134ms

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

When Confirm statuses until reach "arrived" 4s 287ms

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

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

And Click cancel in status confirmation modal 15s 174ms

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

And Fill transport form 36s 375ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 127ms

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

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

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

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

And Click cancel in status confirmation modal 15s 157ms

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

And Fill transport form 36s 341ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 109ms

After Hooks.rollbackCustomFieldSettings() 048ms

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

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 241ms

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

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

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

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

And Click cancel in status confirmation modal 15s 170ms

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

And Fill transport form 35s 720ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 139ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 205ms

When Confirm "Departure" status in transport row 057ms

Then Verify that "Departure" has been confirmed 255ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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

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

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

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

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

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

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

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

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

And Click cancel in status confirmation modal 15s 130ms

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

And Fill transport form 36s 416ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 116ms

After Hooks.rollbackCustomFieldSettings() 046ms

@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 "TANKER_GRANULATE_DELIVERY" 041ms

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

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

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

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

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

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

And Click cancel in status confirmation modal 15s 168ms

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

And Fill transport form 36s 372ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 118ms

After Hooks.rollbackCustomFieldSettings() 058ms

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

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

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

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

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

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

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

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

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

And Click cancel in status confirmation modal 15s 150ms

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

And Fill transport form 35s 805ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 143ms

After Hooks.rollbackCustomFieldSettings() 120ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 209ms

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

When Open statuses popup 109ms

And Toggle status date confirmation checkbox 327ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 182ms

After Hooks.deleteModeOfTransportationAfterTest() 139ms

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

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 216ms

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

And Open statuses popup 097ms

And Toggle status date confirmation checkbox 296ms

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

Then Verify that status cannot be confirmed 1s 084ms

Hooks

After Hooks.deleteTransportAfterTest() 152ms

After Hooks.deleteModeOfTransportationAfterTest() 118ms

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

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

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

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

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

And Login as "bausch-admin" 971ms

And Go to "TRANSPORT_TABLE" 173ms

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

And Open statuses popup 116ms

And Toggle status date confirmation checkbox 274ms

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

Then Verify that status cannot be confirmed 1s 080ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

After Hooks.deleteModeOfTransportationAfterTest() 106ms

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

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

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

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

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

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

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

And Set advice window in schedule 2s 951ms

And Fill advice form 14s 551ms

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

And If user is login then logout 124ms

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

And Show all transport types 1s 054ms

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

And Go to "SETTINGS_TAB" 322ms

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

And Delete created transport by API 170ms

Then If user is login then logout 091ms

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

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

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

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

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

And Fill advice form 14s 576ms

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

And If user is login then logout 103ms

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

And Show all transport types 1s 048ms

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

Hooks

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

After Hooks.deleteAllAddedStatus() 2s 234ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 194ms

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

And Set actual confirmed transport status list 1s 369ms

And Disable task by API 063ms

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

And Edit transport hours and recalculate statuses 16s 301ms

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

Hooks

After Hooks.deleteTransportAfterTest() 139ms

After Hooks.rollbackTaskChanges() 055ms

	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	39m 27s 088ms	Failed

Feature Report