Cucumber-JVM Reports - Tag: @deleteTransportAfterTest

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.68	21 sie 2021, 05:16

	Steps	Scenarios	Features
@deleteTransportAfterTest	3891	34	118	0	0	4043	375	34	409	5h 28m 47s 225ms	Failed

View Feature Advice transport

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 251ms

And Set "advice" inputs from JSON file "CREATE_ADVICE_CONTAINER" "super-admin-adama" 007ms

And Check is transport "CONTAINER" created in transport table and set transport id 1s 111ms

When Click button advice in transport table "CONTAINER" 094ms

And Set advice window in schedule in the past 2s 469ms

And Fill advice form 18s 078ms

And Click advice save button to check error message 088ms

Then Check if possible advice alert is displayed 020ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 003ms

And Check is transport "DELIVERY" created in transport table and set transport id 1s 116ms

When Click button advice in transport table "DELIVERY" 077ms

And Set advice window in schedule in the past 2s 612ms

And Fill advice form 10s 643ms

And Click advice save button to check error message 085ms

Then Check if possible advice alert is displayed 022ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-piast" 004ms

And Check is transport "LOAD" created in transport table and set transport id 1s 123ms

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

And Set advice window in schedule in the past 2s 635ms

And Fill advice form 10s 571ms

And Click advice save button to check error message 082ms

Then Check if possible advice alert is displayed 023ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

And Check is transport "LOAD" created in transport table and set transport id 1s 104ms

When Click button advice in transport table "LOAD" 070ms

And Set advice window in schedule in the past 2s 456ms

And Fill advice form 15s 395ms

And Click advice save button to check error message 104ms

Then Check if possible advice alert is displayed 020ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to advice transport in the past when advice is created from transports table.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Check is transport "CONTAINER" created in transport table and set transport id 1s 121ms

When Click button advice in transport table "CONTAINER" 106ms

And Set advice window in schedule in the past 2s 478ms

And Fill advice form 15s 392ms

And Click advice save button to check error message 083ms

Then Check if possible advice alert is displayed 015ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to edit advice in transport details.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 179ms

And Show all transport types 1s 046ms

And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama" 656ms

And Go to "TRANSPORT_TABLE" 128ms

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

When Go to transport details "CONTAINER" 2s 425ms

And Fill transport form 4s 708ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_CONTAINER" "super-admin-adama" 002ms

And Expand advice panel 117ms

And Edit advice in transport details 14s 661ms

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

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

And Expand advice panel 098ms

Then Check are advice values equals after edition 2s 284ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to edit advice in transport details.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Show all transport types 1s 043ms

And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 633ms

And Go to "TRANSPORT_TABLE" 124ms

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

When Go to transport details "DELIVERY" 2s 557ms

And Fill transport form 1m 2s 462ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_DELIVERY" "super-admin-piast" 001ms

And Expand advice panel 15s 026ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[@id='advice-panel']"}
  (Session info: headless chrome=92.0.4515.131)
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: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.2KxY4c}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 27f8686fbbe216e38127d63861020cbd
*** Element info: {Using=xpath, value=//div[@id='advice-panel']}
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	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:325)
	at CucumberTests.Transport.AdviceTransport.expandAdvicePanel(AdviceTransport.java:142)
	at ✽.Expand advice panel(file:Features/Atom/Advice/AdviceTransport.feature:34)

And Edit advice in transport details 000ms

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

And Go to transport details "DELIVERY" 000ms

And Expand advice panel 000ms

Then Check are advice values equals after edition 000ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to edit advice in transport details.

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

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

And Show all transport types 1s 053ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-piast" 574ms

And Go to "TRANSPORT_TABLE" 139ms

And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-piast" 003ms

When Go to transport details "LOAD" 2s 807ms

And Fill transport form 57s 334ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_DELIVERY" "super-admin-piast" 002ms

And Expand advice panel 104ms

And Edit advice in transport details 6s 632ms

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

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

And Expand advice panel 107ms

Then Check are advice values equals after edition 105ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to edit advice in transport details.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Show all transport types 1s 045ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper" 576ms

And Go to "TRANSPORT_TABLE" 112ms

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

When Go to transport details "LOAD" 2s 430ms

And Fill transport form 26s 032ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_LOAD" "super-admin-keeeper" 004ms

And Expand advice panel 116ms

And Edit advice in transport details 20s 455ms

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

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

And Expand advice panel 087ms

Then Check are advice values equals after edition 8s 335ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to edit advice in transport details.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Show all transport types 1s 048ms

And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-keeeper" 582ms

And Go to "TRANSPORT_TABLE" 128ms

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

When Go to transport details "CONTAINER" 2s 391ms

And Fill transport form 26s 107ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_CONTAINER" "super-admin-keeeper" 003ms

And Expand advice panel 118ms

And Edit advice in transport details 20s 530ms

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

Error message

java.lang.AssertionError: Nie udało się zapisać zmian! Pojawił się komunikat walidacyjny w polu:
[od]
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at Pages.Transport.TransportFormPage.clickSaveButtonAndWaitForFormToDisappear(TransportFormPage.java:195)
	at CucumberTests.Transport.CreateTransport.clickSaveButtonAndWaitForFormToDisappear(CreateTransport.java:202)
	at ✽.Click "save-transport-and-close" save button and wait for form to disappear(file:Features/Atom/Advice/AdviceTransport.feature:36)

And Go to transport details "CONTAINER" 000ms

And Expand advice panel 000ms

Then Check are advice values equals after edition 000ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to edit advice in transport details.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-skz" 1s 469ms

And Show all transport types 1s 044ms

And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-skz" 1s 112ms

And Go to "TRANSPORT_TABLE" 174ms

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

When Go to transport details "CONTAINER" 2s 575ms

And Fill transport form 7s 465ms

And Set "advice" inputs from JSON file "EDIT_ADVICE" "super-admin-skz" 002ms

And Expand advice panel 101ms

And Edit advice in transport details 16s 482ms

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

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

And Expand advice panel 100ms

Then Check are advice values equals after edition 4s 265ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 199ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_CONTAINER" "super-admin-adama" 003ms

When Show all transport types 1s 049ms

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

And Set advice window in schedule 2s 445ms

And Fill advice form 14s 542ms

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

And Go to "TRANSPORT_TABLE" 196ms

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

Then Check are advice values equals 2s 353ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When Show all transport types 1s 040ms

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

And Set advice window in schedule 6s 484ms

And Fill advice form 15s 370ms

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

And Go to "TRANSPORT_TABLE" 196ms

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

Then Check are advice values equals 4s 343ms

Hooks

After Hooks.deleteTransportAfterTest() 144ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 002ms

When Show all transport types 1s 036ms

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

And Set advice window in schedule 2s 655ms

And Fill advice form 10s 635ms

And Click advice save button and wait for advice form to disappear 10s 176ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='save'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.2KxY4c}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 27f8686fbbe216e38127d63861020cbd
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:217)
	at Pages.Transport.AdviceFormPage.confirm(AdviceFormPage.java:27)
	at CucumberTests.Transport.AdviceTransport.clickAdviceSaveButtonAndWaitForAdviceFormToDisappear(AdviceTransport.java:179)
	at ✽.Click advice save button and wait for advice form to disappear(file:Features/Atom/Advice/AdviceTransport.feature:58)

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "DELIVERY" 000ms

Then Check are advice values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When Show all transport types 1s 042ms

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

And Set advice window in schedule 2s 620ms

And Fill advice form 10s 573ms

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

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='save'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.2KxY4c}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 27f8686fbbe216e38127d63861020cbd
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:217)
	at Pages.Transport.AdviceFormPage.confirm(AdviceFormPage.java:27)
	at CucumberTests.Transport.AdviceTransport.clickAdviceSaveButtonAndWaitForAdviceFormToDisappear(AdviceTransport.java:179)
	at ✽.Click advice save button and wait for advice form to disappear(file:Features/Atom/Advice/AdviceTransport.feature:58)

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "LOAD" 000ms

Then Check are advice values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

When Show all transport types 1s 046ms

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

And Set advice window in schedule 2s 452ms

And Fill advice form 15s 378ms

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

And Go to "TRANSPORT_TABLE" 199ms

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

Then Check are advice values equals 4s 323ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

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

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

When Show all transport types 1s 042ms

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

And Set advice window in schedule 2s 458ms

And Fill advice form 15s 346ms

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

And Go to "TRANSPORT_TABLE" 197ms

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

Then Check are advice values equals 4s 327ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to change warehouse during advice creation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-neuca" 002ms

And Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 1s 637ms

And Go to new transport "DELIVERY" 433ms

And Fill transport form 43s 093ms

And Select warehouse "Katowice" in step section "1" 553ms

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

When Change warehouse in schedule to: "Ołtarzew" 992ms

Then Set advice window in schedule 2s 200ms

And Check is transport created in schedule and set transport id 651ms

And Go to "TRANSPORT_TABLE" 244ms

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

And Check if transport has warehouse "Ołtarzew" in step section "1" 028ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table after passing it on to the carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 092ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 195ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 182ms

And Set token of apiUsername "paa1-carrier@qa.qa-test" 093ms

And Accept transferred transport by Api 163ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 877ms

And Set "advice" inputs from JSON file "ADVICE_TRANSPORT" "super-admin-adama" 001ms

When Show all transport types 1s 149ms

And Click button advice in transport table "TRANSPORT" 095ms

And Set advice window in schedule 2s 467ms

And Fill advice form 13s 990ms

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

And Go to "TRANSPORT_TABLE" 194ms

And Go to transport details "TRANSPORT" 2s 455ms

Then Check are advice values equals 4s 293ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table after passing it on to the carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Set token of apiUsername "pskza1-carrier@qa.qa-test" 095ms

And Accept transferred transport by Api 178ms

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

And Set "advice" inputs from JSON file "ADVICE_SMALLS" "super-admin-skz" 002ms

When Show all transport types 1s 051ms

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

And Set advice window in schedule 2s 630ms

And Fill advice form 16s 704ms

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

And Go to "TRANSPORT_TABLE" 182ms

And Go to transport details "SMALLS_IMPORT" 2s 508ms

Then Check are advice values equals 4s 346ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice by advice button in transport table after passing it on to the carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Set token of apiUsername "pskza1-carrier@qa.qa-test" 097ms

And Accept transferred transport by Api 094ms

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

And Set "advice" inputs from JSON file "ADVICE_SMALLS" "super-admin-skz" 002ms

When Show all transport types 1s 078ms

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

And Set advice window in schedule 2s 633ms

And Fill advice form 16s 700ms

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

And Go to "TRANSPORT_TABLE" 186ms

And Go to transport details "SMALLS_EXPORT" 2s 494ms

Then Check are advice values equals 4s 339ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if the advice restriction blockade windows are visible during advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 096ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 207ms

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

And Accept transferred transport by Api 101ms

And Login as "paa1-carrier@qa.qa-test" 1s 423ms

When Show all transport types 1s 086ms

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

And Set week view 1s 570ms

And Show yesterday 1s 076ms

Then Check if advice restriction blockade windows are visible 022ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if the advice restriction blockade windows are visible during advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 15s 226ms

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

And Accept transferred transport by Api 092ms

And Login as "pskza1-carrier@qa.qa-test" 1s 244ms

When Show all transport types 1s 068ms

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

And Set week view 2s 087ms

And Show yesterday 1s 118ms

Then Check if advice restriction blockade windows are visible 028ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if the advice restriction blockade windows are visible during advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 15s 228ms

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

And Accept transferred transport by Api 104ms

And Login as "pskza1-carrier@qa.qa-test" 1s 387ms

When Show all transport types 1s 065ms

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

And Set week view 2s 079ms

And Show yesterday 1s 144ms

Then Check if advice restriction blockade windows are visible 032ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to move advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Show all transport "false" 4s 805ms

And Click on time window date 1s 292ms

And Select view "DAYS_4" 2s 063ms

And Move advice window "3" 1s 325ms

Then Check if advice window is in new location 024ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to move advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 1s 510ms

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

And Show all transport "false" 191ms

And Click on time window date 15s 740ms

And Select view "DAYS_4" 2s 070ms

And Move advice window "3" 1s 478ms

Then Check if advice window is in new location 028ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to move advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Show all transport "false" 171ms

And Click on time window date 15s 538ms

And Select view "DAYS_4" 2s 070ms

And Move advice window "3" 1s 390ms

Then Check if advice window is in new location 026ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to move advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Show all transport "false" 236ms

And Click on time window date 1s 465ms

And Select view "DAYS_4" 2s 059ms

And Move advice window "3" 1s 373ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to move advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Show all transport "false" 165ms

And Click on time window date 1s 307ms

And Select view "DAYS_4" 2s 063ms

And Move advice window "3" 1s 305ms

Then Check if advice window is in new location 021ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to move advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 318ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 323ms

And Show all transport "true" 247ms

And Click on time window date 1s 351ms

And Select view "DAYS_4" 2s 062ms

And Move advice window "3" 1s 331ms

Then Check if advice window is in new location 024ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add advice and move advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 001ms

When Show all transport types 1s 039ms

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

And Set advice window in schedule 2s 644ms

And Fill advice form 10s 548ms

And Click advice save button and wait for advice form to disappear 10s 182ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='save'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.2KxY4c}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 27f8686fbbe216e38127d63861020cbd
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:217)
	at Pages.Transport.AdviceFormPage.confirm(AdviceFormPage.java:27)
	at CucumberTests.Transport.AdviceTransport.clickAdviceSaveButtonAndWaitForAdviceFormToDisappear(AdviceTransport.java:179)
	at ✽.Click advice save button and wait for advice form to disappear(file:Features/Atom/Advice/AdviceTransport.feature:158)

And Go to "TRANSPORT_TABLE" 000ms

And Click on time window date 000ms

And Select view "DAYS_4" 000ms

And Move advice window "3" 000ms

Then Check if advice window is in new location 000ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if late advice is red

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_LATE_DELIVERY" by JSON file as "super-admin-hochland" in "0" days 1s 346ms

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

Hooks

After Hooks.deleteTransportAfterTest() 118ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to resize advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Go to "TRANSPORT_TABLE" 128ms

And Show all transport types 1s 034ms

And Click on time window date 1s 313ms

And Scroll to time window "adviceWindow" 037ms

And Set time window height "2" "adviceWindow" 5s 403ms

Then Check height of the time window after expanding by "2" in "adviceWindow" 025ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to resize advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 992ms

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

And Go to "TRANSPORT_TABLE" 122ms

And Show all transport types 1s 035ms

And Click on time window date 1s 446ms

And Scroll to time window "adviceWindow" 035ms

And Set time window height "4" "adviceWindow" 5s 395ms

Then Check height of the time window after expanding by "4" in "adviceWindow" 023ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to resize advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Go to "TRANSPORT_TABLE" 128ms

And Show all transport types 1s 031ms

And Click on time window date 1s 281ms

And Scroll to time window "adviceWindow" 033ms

And Set time window height "3" "adviceWindow" 5s 387ms

Then Check height of the time window after expanding by "3" in "adviceWindow" 023ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to resize advice window in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 985ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 15s 290ms

And Go to "TRANSPORT_TABLE" 308ms

And Show all transport types 1s 197ms

And Click on time window date 1s 805ms

And Scroll to time window "adviceWindow" 046ms

And Set time window height "1" "adviceWindow" 5s 430ms

Then Check height of the time window after expanding by "1" in "adviceWindow" 024ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to resize advice window in schedule after add advice by advice button in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 002ms

When Show all transport types 1s 038ms

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

And Set advice window in schedule 2s 664ms

And Fill advice form 10s 581ms

And Click advice save button and wait for advice form to disappear 10s 190ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='save'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.2KxY4c}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 27f8686fbbe216e38127d63861020cbd
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:217)
	at Pages.Transport.AdviceFormPage.confirm(AdviceFormPage.java:27)
	at CucumberTests.Transport.AdviceTransport.clickAdviceSaveButtonAndWaitForAdviceFormToDisappear(AdviceTransport.java:179)
	at ✽.Click advice save button and wait for advice form to disappear(file:Features/Atom/Advice/AdviceTransport.feature:203)

And Go to "TRANSPORT_TABLE" 000ms

And Click on time window date 000ms

And Set time window height "2" "adviceWindow" 000ms

Then Check height of the time window after expanding by "2" in "adviceWindow" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 064ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice after clicking back button in browser

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Go to "WAREHOUSE_TAB" 827ms

And Select warehouse "Twarożkarnia wyrób gotowy" 1s 937ms

When Go to new transport "DELIVERY" 341ms

And Fill transport form 41s 796ms

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

And Click previous page button in browser 037ms

Then Check if advice window can't be created 2s 766ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to advice after modifing warehouse id in browser url

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

And Go to "WAREHOUSE_TAB" 798ms

And Select warehouse "Twarożkarnia wyrób gotowy" 1s 905ms

When Go to new transport "DELIVERY" 399ms

And Fill transport form 42s 117ms

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

And Replace warehouse id in browser url with "Twarożkarnia wyrób gotowy" id 045ms

Then Check if advice window can't be created 2s 347ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if transport without warehouse after carrier add advice has checkpoint steps

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 382ms

And Create transport "CREATE_TRANSPORT_WITHOUT_WAREHOUSES" by JSON file as "super-admin-adama" 1s 234ms

And Transfer transport to carrier by JSON file "super-admin-adama" "false" confirmation 178ms

And Set "advice" inputs from JSON file "ADVICE_TRANSPORT" "super-admin-adama" 001ms

When Show all transport types 1s 034ms

And Click button advice in transport table "TRANSPORT" 783ms

And Fill advice form 13s 842ms

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

When Find transport in table with status "no-advice-undefined" 3s 249ms

And Open statuses popup 111ms

And Wait "2" seconds 2s

Then Check if transport has checkpoints from list "Zgłoszenie się kierowcy,Zakończenie załadunku,Dostarczenie do klienta" in "1" 059ms

Hooks

After Hooks.deleteTransportAfterTest() 062ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if time window details preview displays correctly

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 087ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 172ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 729ms

And Login as "farmacol-admin" 1s 674ms

And Go to "WAREHOUSE_TAB" 763ms

And Select warehouse "Katowice Przyjęcia" 1s 201ms

And Set week view 2s 539ms

And Move cursor over time window element 403ms

Then Check if "Zaawizowany" "31415" "06:00" "GDA12345" are visible on time window popup details 133ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

View Feature Advice transport

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline Check if it is possible to advice transport after splitting advice data from advice window

- order: advice data => advice window [A-7478]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pba1-carrier" and set token of apiUsername "super-admin-bausch" 1s 745ms

And Create default accepted mode of transportation by API with "pba1-carrier" 280ms

And Create transport "CREATE_EXW_DELIVERY" by JSON file as "super-admin-bausch" 1s 280ms

And Set "advice" inputs from JSON file "ADVICE_EXW_DELIVERY" "super-admin-bausch" 001ms

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

When Go to "TRANSPORT_TABLE" 120ms

And Show all transport types 1s 040ms

And Click button advice in transport table "EXW_DELIVERY" 1s 050ms

And Fill advice form 11s 113ms

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

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

And Set advice window in schedule 2s 552ms

And Change filled value in details "rodo-acceptance" "checkbox" "true" "0" 1s 482ms

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

And Go to "TRANSPORT_TABLE" 204ms

And Show all transport types 1s 055ms

And Go to transport details "EXW_DELIVERY" 2s 439ms

Then Check are advice values equals 4s 259ms

Hooks

After Hooks.deleteTransportAfterTest() 151ms

After Hooks.deleteModeOfTransportationAfterTest() 069ms

View Feature Company Resources

@deleteTransportAfterTest

Scenario Outline Check if it possible to save resource to company from transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY_CONTRACTOR" "super-admin-neuca" 001ms

And Login as "pna1-carrier" and set token of apiUsername "super-admin-neuca" 1s 003ms

And Go to new transport "DELIVERY" 15s 283ms

And Fill transport form 36s 555ms

And Select "save-as-resource" checkbox 262ms

When Click "save-transport" save button and wait for form to disappear 30s 096ms

And Set advice window in schedule 2s 178ms

And Check is transport created in schedule and set transport id 976ms

Then Go to "OWN_COMPANY_TAB" 242ms

And Check if advice values are visible in company resources 137ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

View Feature Company Resources

@deleteTransportAfterTest

Scenario Outline Check if it possible to save resource to company from transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY_SUPPLIER" "super-admin-alrec" 001ms

And Login as "daa1-supplier-3" and set token of apiUsername "super-admin-alrec" 1s 524ms

And Go to new transport "DELIVERY" 15s 265ms

And Fill transport form 18s 506ms

And Select "save-as-resource" checkbox 262ms

When Click "save-transport" save button and wait for form to disappear 30s 054ms

And Set advice window in schedule 2s 149ms

And Check is transport created in schedule and set transport id 596ms

Then Go to "OWN_COMPANY_TAB" 278ms

And Check if advice values are visible in company resources 141ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

View Feature Custom fields

@deleteTransportAfterTest @deleteCustomFieldAfterTest @TmsLink=A-7060

Scenario Outline Check if it is possible to create new custom field [A-7060]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-skz" and set token of apiUsername "super-admin-skz" 1s 971ms

And Set "custom-field" inputs from JSON file "CREATE_CUSTOM_FIELD" "super-admin-skz" 001ms

And Go to "SETTINGS_TAB" 442ms

When Go to "CONTAINER" transport type settings 425ms

And Go to custom fields settings 192ms

And Click add new custom field 172ms

And Fill custom field form 6s 039ms

And Click save button 076ms

And Click back to custom field settings button 142ms

And Set custom field id 288ms

And Refresh page 2s 132ms

Then Go to new transport "CONTAINER" 397ms

And Verify if created custom field appeared in transport form 030ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteCustomFieldAfterTest() 263ms

View Feature Custom fields

@deleteTransportAfterTest @deleteCustomFieldAfterTest @TmsLink=A-7060

Scenario Outline Check if it is possible to create new custom field [A-7060]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "custom-field" inputs from JSON file "CREATE_CUSTOM_FIELD" "super-admin-piast" 001ms

And Go to "SETTINGS_TAB" 327ms

When Go to "LOAD" transport type settings 408ms

And Go to custom fields settings 179ms

And Click add new custom field 163ms

And Fill custom field form 6s 009ms

And Click save button 058ms

And Click back to custom field settings button 161ms

And Set custom field id 221ms

And Refresh page 2s 134ms

Then Go to new transport "LOAD" 348ms

And Verify if created custom field appeared in transport form 025ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteCustomFieldAfterTest() 263ms

View Feature Custom fields

@deleteTransportAfterTest @deleteCustomFieldAfterTest @TmsLink=A-7060

Scenario Outline Check if it is possible to create new custom field [A-7060]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "super-admin-hochland" and set token of apiUsername "super-admin-hochland" 3s 179ms

And Set "custom-field" inputs from JSON file "CREATE_CUSTOM_FIELD" "super-admin-hochland" 001ms

And Go to "SETTINGS_TAB" 330ms

When Go to "DELIVERY" transport type settings 327ms

And Go to custom fields settings 142ms

And Click add new custom field 164ms

And Fill custom field form 6s 015ms

And Click save button 056ms

And Click back to custom field settings button 131ms

And Set custom field id 508ms

And Refresh page 2s 134ms

Then Go to new transport "DELIVERY" 705ms

And Verify if created custom field appeared in transport form 023ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteCustomFieldAfterTest() 449ms

View Feature Custom fields

@deleteTransportAfterTest @deleteCustomFieldAfterTest @TmsLink=A-7061

Scenario Outline Check if it is possible to edit custom field [A-7061]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create custom field with "CREATE_CONTAINER_TEXT_CFD" by "super-admin-skz" 235ms

And Go to "SETTINGS_TAB" 343ms

When Go to "CONTAINER" transport type settings 481ms

And Go to custom fields settings 168ms

And Click edit button of "Testowy CFD" custom field 178ms

And Change filled value in details "definition-name" "text" "Edytowany CFD" "0" 1s 387ms

And Click save button 046ms

And Refresh page 2s 116ms

Then Go to new transport "CONTAINER" 343ms

And Verify that edited "Edytowany CFD" is visible in transport form 026ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteCustomFieldAfterTest() 203ms

View Feature Custom fields

@deleteTransportAfterTest @deleteCustomFieldAfterTest @TmsLink=A-7061

Scenario Outline Check if it is possible to edit custom field [A-7061]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create custom field with "CREATE_LOAD_TEXT_CFD" by "super-admin-piast" 311ms

And Go to "SETTINGS_TAB" 288ms

When Go to "LOAD" transport type settings 413ms

And Go to custom fields settings 194ms

And Click edit button of "Testowy CFD" custom field 183ms

And Change filled value in details "definition-name" "text" "Edytowany CFD" "0" 1s 341ms

And Click save button 054ms

And Refresh page 2s 123ms

Then Go to new transport "LOAD" 363ms

And Verify that edited "Edytowany CFD" is visible in transport form 025ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteCustomFieldAfterTest() 245ms

View Feature Custom fields

@deleteTransportAfterTest @deleteCustomFieldAfterTest @TmsLink=A-7061

Scenario Outline Check if it is possible to edit custom field [A-7061]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create custom field with "CREATE_DELIVERY_TEXT_CFD" by "super-admin-hochland" 531ms

And Go to "SETTINGS_TAB" 344ms

When Go to "DELIVERY" transport type settings 324ms

And Go to custom fields settings 157ms

And Click edit button of "Testowy CFD" custom field 197ms

And Change filled value in details "definition-name" "text" "Edytowany CFD" "0" 1s 444ms

And Click save button 054ms

And Refresh page 2s 127ms

Then Go to new transport "DELIVERY" 669ms

And Verify that edited "Edytowany CFD" is visible in transport form 024ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteCustomFieldAfterTest() 441ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport is marked based on the creating user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "swisskrono-purchasing-department" 097ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 1s 285ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 2s 105ms

When Go to "TRANSPORT_TABLE" 199ms

And Sort transports by "show-mine" 1s 067ms

And Show all transport types 1s 081ms

Then Verify that created transport is "true" in transport table 1s 073ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport is marked based on the creating user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "swisskrono-purchasing-department" 100ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 1s 203ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 1s 258ms

When Go to "TRANSPORT_TABLE" 206ms

And Sort transports by "show-all" 1s 062ms

And Show all transport types 1s 074ms

Then Verify that created transport is "true" in transport table 1s 087ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport is marked based on the creating user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "swisskrono-admin" 097ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 1s 219ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 1s 113ms

When Go to "TRANSPORT_TABLE" 137ms

And Sort transports by "show-mine" 1s 059ms

And Show all transport types 1s 063ms

Then Verify that created transport is "false" in transport table 31s 590ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport is marked based on the creating user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "swisskrono-admin" 101ms

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

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 1s 259ms

When Go to "TRANSPORT_TABLE" 127ms

And Sort transports by "show-all" 1s 056ms

And Show all transport types 1s 089ms

Then Verify that created transport is "true" in transport table 1s 075ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport in archive is marked based on the creating user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "swisskrono-purchasing-department" 097ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 1s 221ms

And Delete created transport by API 085ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 1s 110ms

When Go to "ARCHIVE_TAB" 232ms

And Sort transports by "show-mine" 1s 058ms

And Show "SMALLS_IMPORT" 082ms

Then Verify that created transport is "true" in transport table 15s 052ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport in archive is marked based on the creating user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "swisskrono-purchasing-department" 096ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-purchasing-department" 15s 201ms

And Delete created transport by API 075ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 1s 256ms

When Go to "ARCHIVE_TAB" 217ms

And Sort transports by "show-all" 1s 069ms

And Show "SMALLS_IMPORT" 075ms

Then Verify that created transport is "true" in transport table 15s 080ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport in archive is marked based on the creating user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "swisskrono-admin" 095ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 15s 224ms

And Delete created transport by API 085ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 1s 306ms

When Go to "ARCHIVE_TAB" 238ms

And Sort transports by "show-mine" 1s 069ms

And Show "SMALLS_IMPORT" 086ms

Then Verify that created transport is "false" in transport table 45s 625ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport in archive is marked based on the creating user

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "swisskrono-admin" 095ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "swisskrono-admin" 15s 229ms

And Delete created transport by API 118ms

And Login as "swisskrono-purchasing-department" and set token of apiUsername "super-admin-skz" 1s 277ms

When Go to "ARCHIVE_TAB" 210ms

And Sort transports by "show-all" 1s 063ms

And Show "SMALLS_IMPORT" 087ms

Then Verify that created transport is "true" in transport table 15s 045ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if order is visible after filter load or unload time column in specific time range

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-alrec" 094ms

And Create transport "CREATE_TRANSPORT_FIRST_SUPPLIER" by JSON file as "super-admin-alrec" 1s 237ms

When Login as "alrec-admin" 1s 079ms

And Go to "TRANSPORT_TABLE" 149ms

And Show all transport "true" 240ms

And Select transportType "TRANSPORT_ORDER" 1s 141ms

Then Check if load and unload time filters work properly "LOAD_TIME_WINDOW" 36s 620ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if it is possible to choose what the search in the archive applies to

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Accept transferred transport by Api 084ms

And Create advice by JSON file "CREATE_ADVICE_FOR_SMALLS" as "super-admin-skz" 841ms

And Delete created transport by API 121ms

When Go to "ARCHIVE_TAB" 228ms

And Show "SMALLS_IMPORT" 097ms

Then Check if it is possible to search with different date property selects 23s 658ms

Error message

org.junit.ComparisonFailure: Data jest inna niż wybrana w filtrze! Problem wystąpił przy TIME_WINDOW_START expected:<2[2].08.2021> but was:<2[1].08.2021>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at Pages.Filters.FiltersPage.checkDateFilterPropertySelect(FiltersPage.java:263)
	at CucumberTests.Filters.FilterTransportTest.searchWithDifferentArchiveFilters(FilterTransportTest.java:98)
	at ✽.Check if it is possible to search with different date property selects(file:Features/Atom/Filters/Filter.feature:141)

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if it is possible to choose what the search in the archive applies to

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Accept transferred transport by Api 081ms

And Create advice by JSON file "CREATE_ADVICE_FOR_SMALLS" as "super-admin-skz" 682ms

And Delete created transport by API 089ms

When Go to "ARCHIVE_TAB" 209ms

And Show "SMALLS_EXPORT" 083ms

Then Check if it is possible to search with different date property selects 23s 653ms

Error message

org.junit.ComparisonFailure: Data jest inna niż wybrana w filtrze! Problem wystąpił przy TIME_WINDOW_START expected:<2[2].08.2021> but was:<2[1].08.2021>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at Pages.Filters.FiltersPage.checkDateFilterPropertySelect(FiltersPage.java:263)
	at CucumberTests.Filters.FilterTransportTest.searchWithDifferentArchiveFilters(FilterTransportTest.java:98)
	at ✽.Check if it is possible to search with different date property selects(file:Features/Atom/Filters/Filter.feature:141)

Hooks

After Hooks.deleteTransportAfterTest() 119ms

View Feature Filters

@deleteTransportAfterTest

Scenario Outline Check if transport table days limit filter displays correct transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare setting: "TRANSPORT_TABLE_DAYS_LIMIT" with value: "7d" with "super-admin-neuca" 019ms

When Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" in "8" days 15s 404ms

And Login as "neuca-admin" 1s 636ms

And Go to "TRANSPORT_TABLE" 254ms

Then Verify that created transport is "false" in transport table 31s 660ms

And Toggle transport table days limit filter 078ms

And Verify that created transport is "true" in transport table 1s 090ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

View Feature Grouping of carriers

@deleteTransportAfterTest @removeContractorsGroup

Scenario Outline Check if company is selected in inquiry after adding company to contractors group and selecting contractors group

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Add carrier "Przewoźnik SKZ Automat 1" to carriers group "Kraj" by Api as "super-admin-skz" 249ms

When Go to "TRANSPORT_TABLE" 118ms

And Go to auction form 1s 221ms

And Select contractors group "Kraj" 097ms

Then Verify that carrier "PSKZA1" is selected 026ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

After Hooks.removeContractorsGroup() 053ms

View Feature Grouping of carriers

@deleteTransportAfterTest

Scenario Outline Check if all contractors group are selected in inquiry after click in all contractors group checkbox

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Go to "TRANSPORT_TABLE" 120ms

And Go to auction form 1s 215ms

And Select contractors group "Wybierz grupę firm transportowych" 101ms

Then Verify that all companies are selected after choose "data-group-name" 124ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature Grouping of carriers

@deleteTransportAfterTest

Scenario Outline Check if all companies are selected in inquiry after selecting all companies

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Go to "TRANSPORT_TABLE" 125ms

And Go to auction form 1s 185ms

And Select contractors group "Wybierz uczestników zapytania" 094ms

Then Verify that all companies are selected after choose "data-carrier-name" 101ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if it possible to add new index to transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 199ms

And Show all transport "false" 171ms

And Set "index" inputs from JSON file "ADD_INDEX" "super-admin-adama" 002ms

And Create product if needed "false" by api for principal "adama" 108ms

When Go to transport details "TRANSPORT" 2s 451ms

And Expand index panel 103ms

And Click add index button 141ms

And Fill index form 10s 507ms

And Click ok button in index form 15s 127ms

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

And Go to transport details "TRANSPORT" 2s 439ms

And Expand index panel 121ms

Then Check are transport values equals 084ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

After Hooks.deleteProductAfterTest() 074ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if it possible to add new index to transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 465ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 238ms

And Show all transport "true" 231ms

And Set "index" inputs from JSON file "ADD_INDEX" "super-admin-alrec" 001ms

And Create product if needed "true" by api for principal "alrec" 000ms

When Go to transport details "TRANSPORT_ORDER" 2s 470ms

And Expand index panel 091ms

And Click add index button 117ms

And Fill index form 7s 438ms

And Click ok button in index form 15s 147ms

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

And Go to transport details "TRANSPORT_ORDER" 2s 445ms

And Expand index panel 121ms

Then Check are transport values equals 2s 119ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

After Hooks.deleteProductAfterTest() 000ms

View Feature Crud index

@deleteTransportAfterTest @deleteProductAfterTest

Scenario Outline Check if it possible to edit index in index form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 217ms

And Show all transport "false" 163ms

And Set "index" inputs from JSON file "ADD_INDEX" "super-admin-adama" 001ms

And Create product if needed "false" by api for principal "adama" 025ms

When Go to transport details "TRANSPORT" 2s 451ms

And Expand index panel 089ms

And Click add index button 140ms

And Fill index form 10s 497ms

And Click ok button in index form 15s 118ms

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

When Go to transport details "TRANSPORT" 2s 447ms

And Expand index panel 114ms

And Click edit index button 142ms

And Edit index quantity to "999" 131ms

And Click ok button in index form 15s 099ms

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

And Go to transport details "TRANSPORT" 2s 417ms

And Expand index panel 127ms

And Verify if index quantity equals "999" 019ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

After Hooks.deleteProductAfterTest() 024ms

View Feature Crud index

@deleteTransportAfterTest @deleteProductAfterTest

Scenario Outline Check if it possible to edit index in index form

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 156ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 241ms

And Show all transport "true" 221ms

And Set "index" inputs from JSON file "ADD_INDEX" "super-admin-alrec" 001ms

And Create product if needed "true" by api for principal "alrec" 000ms

When Go to transport details "TRANSPORT_ORDER" 2s 470ms

And Expand index panel 099ms

And Click add index button 125ms

And Fill index form 7s 482ms

And Click ok button in index form 15s 098ms

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

When Go to transport details "TRANSPORT_ORDER" 2s 452ms

And Expand index panel 107ms

And Click edit index button 133ms

And Edit index quantity to "999" 129ms

And Click ok button in index form 15s 093ms

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

And Go to transport details "TRANSPORT_ORDER" 2s 399ms

And Expand index panel 105ms

And Verify if index quantity equals "999" 021ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

After Hooks.deleteProductAfterTest() 000ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if it possible to delete index in transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 206ms

And Show all transport "false" 161ms

And Set "index" inputs from JSON file "ADD_INDEX" "super-admin-adama" 001ms

And Create product if needed "false" by api for principal "adama" 025ms

When Go to transport details "TRANSPORT" 2s 442ms

And Add index to transport 25s 791ms

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

When Go to transport details "TRANSPORT" 2s 432ms

And Expand index panel 106ms

And Click delete index button 070ms

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

And Go to transport details "TRANSPORT" 2s 377ms

And Expand index panel 094ms

Then Verify that transport has no indexes 15s 037ms

Hooks

After Hooks.deleteTransportAfterTest() 062ms

After Hooks.deleteProductAfterTest() 024ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if it possible to delete index in transport

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 146ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 228ms

And Show all transport "true" 223ms

And Set "index" inputs from JSON file "ADD_INDEX" "super-admin-alrec" 001ms

And Create product if needed "true" by api for principal "alrec" 000ms

When Go to transport details "TRANSPORT_ORDER" 2s 486ms

And Add index to transport 22s 785ms

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

When Go to transport details "TRANSPORT_ORDER" 2s 467ms

And Expand index panel 123ms

And Click delete index button 084ms

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

And Go to transport details "TRANSPORT_ORDER" 2s 353ms

And Expand index panel 090ms

Then Verify that transport has no indexes 15s 036ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

After Hooks.deleteProductAfterTest() 000ms

View Feature Index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if indexes displayed after click indexes details icon on time window

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "dayco-admin" and set token of apiUsername "super-admin-dayco" 1s 785ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 202ms

And Set "index" inputs from JSON file "ADD_INDEX" "super-admin-dayco" 002ms

And Create product if needed "false" by api for principal "dayco" 024ms

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

And Add index to transport 24s 552ms

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

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

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

And Set advice window in schedule 2s 547ms

And Fill advice form 9s 193ms

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

When Click on index details icon 119ms

Then Verify that indexes display in window "product-index;quantity-of-Planned quantity;quantity-of-Quantity sent" 001ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.deleteProductAfterTest() 029ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after creating advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 170ms

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

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

And Show all transport types 1s 038ms

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

And Set advice window in schedule 2s 459ms

And Fill advice form 13s 927ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 5s 577ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

After Hooks.cleanUserDetailsAfterTest() 183ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after creating advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 135ms

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

And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 001ms

And Show all transport types 1s 037ms

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

And Set advice window in schedule 2s 721ms

And Fill advice form 10s 516ms

And Click advice save button and wait for advice form to disappear 10s 190ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='save'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.2KxY4c}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 27f8686fbbe216e38127d63861020cbd
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:217)
	at Pages.Transport.AdviceFormPage.confirm(AdviceFormPage.java:27)
	at CucumberTests.Transport.AdviceTransport.clickAdviceSaveButtonAndWaitForAdviceFormToDisappear(AdviceTransport.java:179)
	at ✽.Click advice save button and wait for advice form to disappear(file:Features/Atom/Mail/AdviceMail.feature:13)

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 000ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

After Hooks.cleanUserDetailsAfterTest() 151ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after creating advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 274ms

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

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

And Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 462ms

And Fill advice form 15s 386ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Time window has been saved!" 5s 481ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 139ms

After Hooks.cleanUserDetailsAfterTest() 237ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 233ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 193ms

And Show all transport types 1s 040ms

And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama" 560ms

And Go to "TRANSPORT_TABLE" 114ms

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

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

When Go to transport details "CONTAINER" 3s 168ms

And Fill transport form 4s 700ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_CONTAINER" "super-admin-adama" 001ms

And Expand advice panel 112ms

And Edit advice in transport details 14s 644ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 5s 460ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

After Hooks.cleanUserDetailsAfterTest() 168ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 161ms

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

And Show all transport types 1s 045ms

And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 600ms

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania PUT pod adresem /transports/228270600 - status odpowiedzi: 422 , komunikat:  [errors:[Operacja nie powiodła się. Prosimy spróbować ponownie a, jeśli problem się powtarza, o kontakt z info@logintegra.com.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.putObjectToApolloApi(RestUtil.java:194)
	at CucumberTests.Transport.AdviceTransport.createAdviceByJSONFile(AdviceTransport.java:345)
	at ✽.Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast"(file:Features/Atom/Mail/AdviceMail.feature:28)

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "DELIVERY" 000ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-piast" 000ms

When Go to transport details "DELIVERY" 000ms

And Fill transport form 000ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_DELIVERY" "super-admin-piast" 000ms

And Expand advice panel 000ms

And Edit advice in transport details 000ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 000ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

After Hooks.cleanUserDetailsAfterTest() 169ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 233ms

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

And Show all transport types 1s 044ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper" 589ms

And Go to "TRANSPORT_TABLE" 158ms

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

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

When Go to transport details "LOAD" 3s 159ms

And Fill transport form 26s 053ms

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

And Expand advice panel 112ms

And Edit advice in transport details 20s 482ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 3m 377ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 156ms

After Hooks.cleanUserDetailsAfterTest() 251ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after status confirmation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 232ms

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

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu" 5s 269ms

Then Check if user got a mail 000ms

And Confirm status "DEPARTURE" by Public API "v1" 252ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wyjazd" 35s 322ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 154ms

After Hooks.cleanUserDetailsAfterTest() 161ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackVerificationEmailSettingAfterTest

Scenario Outline Check if verification mail was sent to transport creator

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Prepare company "Dostawca Hochland Automat 1" verification email setting "48h" 031ms

And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 196ms

And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "dha1-supplier-2@qa.qa-test" 2s 418ms

And Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2@qa.qa-test" 15s 285ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Weryfikacja danych awizacji" 58s 180ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

After Hooks.cleanUserDetailsAfterTest() 213ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 132ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating a new auction

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 233ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 255ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 585ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowa aukcja" 5s 254ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

After Hooks.cleanUserDetailsAfterTest() 305ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 346ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 197ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 120ms

And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 511ms

And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 398ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 5s 187ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

After Hooks.cleanUserDetailsAfterTest() 262ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after bid has been added to auction

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Prepare user "swisskrono-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file 379ms

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

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 113ms

And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 187ms

And Wait till auction end 1m 58s 018ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę" 2m 47s 438ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

After Hooks.cleanUserDetailsAfterTest() 303ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after auction without bids

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 223ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 269ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 137ms

And Wait till auction end 1m 58s 017ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Aukcja zakończona bez ofert" 5s 484ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

After Hooks.cleanUserDetailsAfterTest() 187ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing first place in auction

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 324ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 250ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 137ms

And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 184ms

And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 283ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Oferta przelicytowana" 15s 678ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.cleanUserDetailsAfterTest() 295ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after winning an auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 343ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 230ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 112ms

And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 185ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 2m 15s 634ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

After Hooks.cleanUserDetailsAfterTest() 285ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after accepting minimal price

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 318ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 213ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 120ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 289ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 5s 192ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

After Hooks.cleanUserDetailsAfterTest() 265ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail two hours before auction ends

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 637ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 320ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 194ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes 2s 174ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji" 15s 691ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

After Hooks.cleanUserDetailsAfterTest() 260ms

View Feature Discrepancy Report Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after discrepancy report generation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "hochland-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 619ms

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

And Go to "TRANSPORT_TABLE" 147ms

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

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

And Fill transport form 37s 930ms

And Open section: "discrepancy-report-panel" 1s 069ms

And Fill discrepancy report section 49s 556ms

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

And Change filled value in details "rodo-acceptance" "checkbox" "true" "0" 1s 289ms

And Generate discrepancy report 18s 811ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Utworzono protokół niezgodności" 5s 947ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

After Hooks.cleanUserDetailsAfterTest() 430ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackAddedAuthorities

Scenario Outline Check if mail was sent to after transport delay

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "pha2-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 380ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 022ms

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

And Go to "WAREHOUSE_TAB" 818ms

And Select warehouse "Serownia" 1s 397ms

And Set week view 1s 094ms

And Show yesterday 1s 054ms

And Move window into the past 305ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 53s 407ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

After Hooks.cleanUserDetailsAfterTest() 326ms

After Hooks.rollbackAddedAuthorities() 018ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 344ms

And Wait "60" seconds 1m

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import" 32s 909ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

After Hooks.cleanUserDetailsAfterTest() 313ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "swisskrono-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 359ms

And Wait "60" seconds 1m

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport" 36s 866ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

After Hooks.cleanUserDetailsAfterTest() 328ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to carrier after transport transfer

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 368ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 207ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 33s 752ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację" 5s 456ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

After Hooks.cleanUserDetailsAfterTest() 248ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to carrier after transport transfer with no confirmation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 342ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 234ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 33s 835ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zostało przekazane nowe zlecenie" 5s 901ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

After Hooks.cleanUserDetailsAfterTest() 250ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 394ms

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

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 164ms

And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 201ms

And Add a bid "500" to an auction by JSON file as "pskza2-carrier-2@qa.qa-test" for "pskza2-carrier-2@qa.qa-test" 210ms

Then If user is login then logout 332ms

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

And Go to auction details 1s 215ms

And Pass transport to carrier from auction details 1s 280ms

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 10s 896ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.cleanUserDetailsAfterTest() 386ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating new inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 440ms

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

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 130ms

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowe zapytanie ofertowe" 5s 320ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

After Hooks.cleanUserDetailsAfterTest() 348ms

View Feature Pallet limit

@deleteTransportAfterTest

Scenario Outline Verify that the error is visible after exceeding the pallet limit during create transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-neuca" 001ms

And Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 974ms

When Go to new transport "DELIVERY" 368ms

And Fill transport form 43s 041ms

And Change filled value in details "number-of-pallets-step-0" "number" "1000000" "0" 1s 353ms

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

And Set advice window in schedule 2s 190ms

Then Verify that the error is visible after exceeding the pallet limit 235ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

View Feature Pallet limit

@deleteTransportAfterTest

Scenario Outline Verify that the error is visible after exceeding the pallet limit during edit transport [A-7071]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 1s 111ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 15s 280ms

And Go to "TRANSPORT_TABLE" 260ms

And Show all transport "false" 161ms

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

And Change filled value in details "number-of-pallets-step-0" "number" "1000000" "0" 1s 387ms

And Click "save-transport" save button 703ms

Then Verify that the error is visible after exceeding the pallet limit 013ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

View Feature Pallet limit

@deleteTransportAfterTest @rollbackMaxPalletLimit @TmsLink=A-7073

Scenario Outline Check if it is possible to create advice when pallet limit equals 1 [A-7073]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-pgf" 094ms

And Prepare max pallet limit "1" in "Magazyn Łódź" 002ms

Error message

java.lang.AssertionError: Nie znaleziono szukanego zasobu w Apollo!
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.getStringResult(ApolloSelectDbService.java:132)
	at Utils.JpaUtils.Apollo.SelectService.ApolloSelectDbService.findWarehouseMaxPalletLimit(ApolloSelectDbService.java:454)
	at CucumberTests.MaxPallet.MaxPalletTest.prepareMaxPalletLimitInWarehouse(MaxPalletTest.java:37)
	at ✽.Prepare max pallet limit "1" in "Magazyn Łódź"(file:Features/Atom/MaxPallet/MaxPallet.feature:34)

And Set "transport" inputs from JSON file "CREATE_UNLOAD" "super-admin-pgf" 000ms

When Login as "pgf-admin" 000ms

And Go to new transport "UNLOAD" 000ms

And Fill transport form 000ms

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

And Set advice window in schedule 000ms

And Check is transport created in schedule and set transport id 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "UNLOAD" 000ms

Then Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.rollbackMaxPalletLimit() 001ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

Scenario Outline Check that the appropriate means of transport are not visible during the advice [A-6256]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 100ms

And Create default mode of transportation by API with "pba1-carrier" 062ms

And Set status of MOT to "AWAITING_VERIFICATION" 046ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 15s 289ms

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

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

When Login as "super-admin-bausch" 1s 827ms

And Go to "TRANSPORT_TABLE" 230ms

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

And Set advice window in schedule 2s 581ms

Then Check if "AAAA0000" MOT is NOT visible in advice form 15s 368ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

After Hooks.deleteModeOfTransportationAfterTest() 053ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

Scenario Outline Check that the appropriate means of transport are not visible during the advice [A-6256]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 094ms

And Create default mode of transportation by API with "pba1-carrier" 064ms

And Set status of MOT to "DISABLED" 047ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 15s 218ms

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

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

When Login as "super-admin-bausch" 1s 192ms

And Go to "TRANSPORT_TABLE" 238ms

And Click button advice in transport table "LOAD_EXPORT" 089ms

And Set advice window in schedule 2s 582ms

Then Check if "AAAA0000" MOT is NOT visible in advice form 15s 374ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

After Hooks.deleteModeOfTransportationAfterTest() 054ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

Scenario Outline Check that the appropriate means of transport are visible during the advice [A-6256]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 097ms

And Create default mode of transportation by API with "pba1-carrier" 073ms

And Set status of MOT to "ACCEPTED" 060ms

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

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

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

When Login as "super-admin-bausch" 1s 225ms

And Go to "TRANSPORT_TABLE" 224ms

And Click button advice in transport table "LOAD_EXPORT" 094ms

And Set advice window in schedule 2s 587ms

Then Check if "AAAA0000" MOT can be selected in advice form 380ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

After Hooks.deleteModeOfTransportationAfterTest() 055ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

Scenario Outline Check that the appropriate means of transport are visible during the advice [A-6256]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 094ms

And Create default mode of transportation by API with "pba1-carrier" 070ms

And Set status of MOT to "UPDATED" 054ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 15s 243ms

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

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

When Login as "super-admin-bausch" 1s 151ms

And Go to "TRANSPORT_TABLE" 232ms

And Click button advice in transport table "LOAD_EXPORT" 081ms

And Set advice window in schedule 2s 598ms

Then Check if "AAAA0000" MOT can be selected in advice form 397ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

After Hooks.deleteModeOfTransportationAfterTest() 064ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

Scenario Outline Check that the appropriate means of transport are visible but not available during the advice [A-6256]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 092ms

And Create default mode of transportation by API with "pba1-carrier" 065ms

And Set status of MOT to "REJECTED" 056ms

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

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

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

When Login as "super-admin-bausch" 1s 179ms

And Go to "TRANSPORT_TABLE" 222ms

And Click button advice in transport table "LOAD_EXPORT" 084ms

And Set advice window in schedule 2s 564ms

Then Check if "AAAA0000" MOT is visible in advice form 362ms

And Check if "AAAA0000" MOT cannot be selected in advice form 15s 209ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

After Hooks.deleteModeOfTransportationAfterTest() 054ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

Scenario Outline Check that the appropriate means of transport are visible but not available during the advice [A-6256]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 097ms

And Create default mode of transportation by API with "pba1-carrier" 068ms

And Set status of MOT to "BLOCKED" 052ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 15s 237ms

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

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

When Login as "super-admin-bausch" 1s 236ms

And Go to "TRANSPORT_TABLE" 221ms

And Click button advice in transport table "LOAD_EXPORT" 090ms

And Set advice window in schedule 2s 570ms

Then Check if "AAAA0000" MOT is visible in advice form 362ms

And Check if "AAAA0000" MOT cannot be selected in advice form 15s 213ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

After Hooks.deleteModeOfTransportationAfterTest() 061ms

View Feature SK Api - Statuses confirmation

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

And Add transport by SKApi in "MGW" assigned to "" 175ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 086ms

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

And Set advice window in schedule 2s 553ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Fill advice form 16s 722ms

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

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

And Confirm statuses until reach "left-the-factory" through SKAPI 28s 347ms

Then Check if transport has "left-the-factory" 025ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

When Add transport by SKApi in "MGW" assigned to "" 004ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 193ms

And Go to "TRANSPORT_TABLE" 133ms

And Go to transport details "TRANSPORT_ORDER" 2s 429ms

Then Check are transport values equals 127ms

Error message

org.junit.ComparisonFailure: Wartości w formularzu w polu company-step-1 są niepoprawne, wartość na stronie: DSKZA1 wartość poprawna: Dostawca SKZ Automat 1 expected: but was:
	at org.junit.Assert.assertEquals(Assert.java:115)
	at CucumberTests.Transport.Transport.checkAreValuesEquals(Transport.java:123)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:263)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:239)
	at ✽.Check are transport values equals(file:Features/Atom/SK_API/SkApiTransport.feature:11)

Hooks

After Hooks.deleteTransportAfterTest() 070ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms

When Add transport by SKApi in "MGW" assigned to "" 002ms

Then Check is transport "CONTAINER" created in transport table and set transport id 6s 307ms

And Go to "TRANSPORT_TABLE" 126ms

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

Then Check are transport values equals 15s 341ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[@data-field-name='country-step-1']//input | //div[@data-field-name='country-step-1']//textarea"}
  (Session info: headless chrome=92.0.4515.131)
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: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.2KxY4c}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 27f8686fbbe216e38127d63861020cbd
*** Element info: {Using=xpath, value=//div[@data-field-name='country-step-1']//input | //div[@data-field-name='country-step-1']//textarea}
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	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.Transport.Transport.checkAreValuesEquals(Transport.java:121)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:263)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:239)
	at ✽.Check are transport values equals(file:Features/Atom/SK_API/SkApiTransport.feature:11)

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 001ms

When Add transport by SKApi in "MGW" assigned to "" 002ms

Then Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 377ms

And Go to "TRANSPORT_TABLE" 132ms

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

Then Check are transport values equals 15s 375ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[@data-field-name='country-step-1']//input | //div[@data-field-name='country-step-1']//textarea"}
  (Session info: headless chrome=92.0.4515.131)
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: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.2KxY4c}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 27f8686fbbe216e38127d63861020cbd
*** Element info: {Using=xpath, value=//div[@data-field-name='country-step-1']//input | //div[@data-field-name='country-step-1']//textarea}
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	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.Transport.Transport.checkAreValuesEquals(Transport.java:121)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:263)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:239)
	at ✽.Check are transport values equals(file:Features/Atom/SK_API/SkApiTransport.feature:11)

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

When Add transport by SKApi in "HRL" assigned to "" 002ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 1m 33s 301ms

Error message

java.lang.AssertionError: Dodane zlecenie nie pojawiło się na stronie
	at org.junit.Assert.fail(Assert.java:88)
	at CucumberTests.Transport.CreateTransport.checkIsTransportCreatedInTransportTable(CreateTransport.java:163)
	at ✽.Check is transport "TRANSPORT_ORDER" created in transport table and set transport id(file:Features/Atom/SK_API/SkApiTransport.feature:8)

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "TRANSPORT_ORDER" 000ms

Then Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms

When Add transport by SKApi in "HRL" assigned to "" 002ms

Then Check is transport "CONTAINER" created in transport table and set transport id 1m 33s 324ms

Error message

java.lang.AssertionError: Dodane zlecenie nie pojawiło się na stronie
	at org.junit.Assert.fail(Assert.java:88)
	at CucumberTests.Transport.CreateTransport.checkIsTransportCreatedInTransportTable(CreateTransport.java:163)
	at ✽.Check is transport "CONTAINER" created in transport table and set transport id(file:Features/Atom/SK_API/SkApiTransport.feature:8)

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "CONTAINER" 000ms

Then Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin-10" and set token of apiUsername "super-admin-skz" 1s 265ms

And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 001ms

When Add transport by SKApi in "HRL" assigned to "" 002ms

Then Check is transport "OWN_COLLECTION" created in transport table and set transport id 1m 33s 310ms

Error message

java.lang.AssertionError: Dodane zlecenie nie pojawiło się na stronie
	at org.junit.Assert.fail(Assert.java:88)
	at CucumberTests.Transport.CreateTransport.checkIsTransportCreatedInTransportTable(CreateTransport.java:163)
	at ✽.Check is transport "OWN_COLLECTION" created in transport table and set transport id(file:Features/Atom/SK_API/SkApiTransport.feature:8)

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "OWN_COLLECTION" 000ms

Then Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi with specific client name

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

And Set another client name "Pepsi" 000ms

When Add transport by SKApi in "MGW" assigned to "" 003ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 1s 139ms

And Check client name in database "Pepsi" "TRANSPORT_ORDER" 037ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it transport created by SKApi without `warehouse_alias` field is in default warehouse

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin-10" and set token of apiUsername "super-admin-skz" 1s 136ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

When Add transport by SKApi in "" assigned to "" 002ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 796ms

And Go to "TRANSPORT_TABLE" 112ms

And Go to transport details "TRANSPORT_ORDER" 2s 422ms

Then Check if transport has warehouse "MGW" in step section "0" 030ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it possible to advice transport when transport is created by sk API

The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 407ms

And Add transport by SKApi in "MGW" assigned to "" 003ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "CONTAINER" created in transport table and set transport id 6s 297ms

When Click button advice in transport table "CONTAINER" 089ms

And Set advice window in schedule 2s 565ms

And Fill advice form 16s 761ms

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

And Go to "TRANSPORT_TABLE" 194ms

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

Then Check are advice values equals 4s 340ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

After Hooks.cleanUserDetailsAfterTest() 275ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it possible to advice transport when transport is created by sk API

The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 001ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 353ms

And Add transport by SKApi in "MGW" assigned to "" 002ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 6s 372ms

When Click button advice in transport table "OWN_COLLECTION" 088ms

And Set advice window in schedule 2s 549ms

And Fill advice form 16s 800ms

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

And Go to "TRANSPORT_TABLE" 159ms

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

Then Check are advice values equals 4s 311ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

After Hooks.cleanUserDetailsAfterTest() 312ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it possible to advice transport when transport is created by sk API

The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 326ms

And Add transport by SKApi in "MGW" assigned to "" 002ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 790ms

When Click button advice in transport table "TRANSPORT_ORDER" 086ms

And Set advice window in schedule 2s 582ms

And Fill advice form 16s 720ms

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

And Go to "TRANSPORT_TABLE" 223ms

And Go to transport details "TRANSPORT_ORDER" 2s 467ms

Then Check are advice values equals 4s 341ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

After Hooks.cleanUserDetailsAfterTest() 270ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it possible to advice transport when transport is created by sk API

The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms

And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 479ms

And Add transport by SKApi in "MGW" assigned to "" 002ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 876ms

When Click button advice in transport table "TRANSPORT_ORDER" 088ms

And Set advice window in schedule 2s 549ms

And Fill advice form 16s 733ms

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

And Go to "TRANSPORT_TABLE" 233ms

And Go to transport details "TRANSPORT_ORDER" 2s 443ms

Then Check are advice values equals 4s 327ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

After Hooks.cleanUserDetailsAfterTest() 381ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it possible to advice transport when transport is created by sk API

The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 844ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 230ms

And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 002ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 807ms

When Click button advice in transport table "TRANSPORT_ORDER" 075ms

And Set advice window in schedule 30s 110ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//button[@data-button-name='SHIFT_RIGHT_DAY']"}
  (Session info: headless chrome=92.0.4515.131)
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: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.2KxY4c}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 27f8686fbbe216e38127d63861020cbd
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.GeneratedConstructorAccessor215.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:325)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:91)
	at ✽.Set advice window in schedule(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:13)

And Fill advice form 000ms

And Click advice save button and wait for advice form to disappear 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "TRANSPORT_ORDER" 000ms

Then Check are advice values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

After Hooks.cleanUserDetailsAfterTest() 229ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 001ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 352ms

And Add transport by SKApi in "MGW" assigned to "" 002ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 389ms

When Click button advice in transport table "OWN_COLLECTION" 094ms

And Set advice window in schedule 2s 547ms

And Fill advice form 16s 741ms

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

And Go to "TRANSPORT_TABLE" 196ms

Then Check advice data in SK API database "OWN_COLLECTION" 128ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

After Hooks.cleanUserDetailsAfterTest() 268ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 000ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 343ms

And Add transport by SKApi in "MGW" assigned to "" 003ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "CONTAINER" created in transport table and set transport id 3s 323ms

When Click button advice in transport table "CONTAINER" 072ms

And Set advice window in schedule 2s 562ms

And Fill advice form 16s 780ms

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

And Go to "TRANSPORT_TABLE" 207ms

Then Check advice data in SK API database "CONTAINER" 086ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

After Hooks.cleanUserDetailsAfterTest() 289ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 331ms

And Add transport by SKApi in "MGW" assigned to "" 004ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 002ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 916ms

When Click button advice in transport table "TRANSPORT_ORDER" 088ms

And Set advice window in schedule 2s 569ms

And Fill advice form 16s 822ms

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

And Go to "TRANSPORT_TABLE" 225ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 029ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

After Hooks.cleanUserDetailsAfterTest() 289ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 479ms

And Add transport by SKApi in "MGW" assigned to "" 002ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 869ms

When Click button advice in transport table "TRANSPORT_ORDER" 090ms

And Set advice window in schedule 2s 549ms

And Fill advice form 16s 814ms

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

And Go to "TRANSPORT_TABLE" 228ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 035ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

After Hooks.cleanUserDetailsAfterTest() 345ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 030ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms

And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 292ms

And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 003ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 2s 934ms

When Click button advice in transport table "TRANSPORT_ORDER" 082ms

And Set advice window in schedule 2s 595ms

And Fill advice form 16s 677ms

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

And Go to "TRANSPORT_TABLE" 207ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 094ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

After Hooks.cleanUserDetailsAfterTest() 205ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Check if not possible to advice transport in the past when advice is created from transports table and transport is created by sk API

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 001ms

And Add transport by SKApi in "MGW" assigned to "" 002ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "CONTAINER" created in transport table and set transport id 3s 342ms

When Click button advice in transport table "CONTAINER" 104ms

And Set advice window in schedule in the past 2s 587ms

And Fill advice form 16s 671ms

And Click advice save button to check error message 079ms

Then Check if possible advice alert is displayed 019ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Check if advice data saved in SK API database after edition

The scenario checks if you can correctly edit an advice. After that the correctness of the data that has been sent to the SK API microservice database is also verified.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 001ms

And Add transport by SKApi in "MGW" assigned to "" 005ms

And Set "advice" inputs from JSON file "EDIT_ADVICE" "super-admin-skz" 000ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 377ms

And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-skz" 453ms

Error message

java.lang.AssertionError: Nieoczekiwany błąd podczas żądania PUT pod adresem /transports/228285875 - status odpowiedzi: 422 , komunikat:  [errors:[Operacja nie powiodła się. Prosimy spróbować ponownie a, jeśli problem się powtarza, o kontakt z info@logintegra.com.]]
	at org.junit.Assert.fail(Assert.java:88)
	at Utils.RestUtils.RestUtil.putObjectToApolloApi(RestUtil.java:194)
	at CucumberTests.Transport.AdviceTransport.createAdviceByJSONFile(AdviceTransport.java:345)
	at ✽.Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-skz"(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:74)

And Go to "TRANSPORT_TABLE" 000ms

When Go to transport details "OWN_COLLECTION" 000ms

And Expand advice panel 000ms

And Edit advice in transport details 000ms

And Fill arrival date field 000ms

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

Then Check advice data in database after edition "OWN_COLLECTION" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 059ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Check if advice data saved in SK API database after edition

The scenario checks if you can correctly edit an advice. After that the correctness of the data that has been sent to the SK API microservice database is also verified.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 000ms

And Add transport by SKApi in "MGW" assigned to "" 005ms

And Set "advice" inputs from JSON file "EDIT_ADVICE" "super-admin-skz" 001ms

And Check is transport "CONTAINER" created in transport table and set transport id 3s 332ms

And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-skz" 852ms

And Go to "TRANSPORT_TABLE" 112ms

When Go to transport details "CONTAINER" 2s 519ms

And Expand advice panel 089ms

And Edit advice in transport details 16s 493ms

And Fill arrival date field 2s 284ms

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

Then Check advice data in database after edition "CONTAINER" 50s 109ms

Error message

java.lang.NullPointerException
	at CucumberTests.Transport.AdviceTransport.assertAdviceFields(AdviceTransport.java:210)
	at CucumberTests.Transport.AdviceTransport.checkAreAdviceValuesSavedInSKAPI(AdviceTransport.java:205)
	at ✽.Check advice data in database after edition "CONTAINER"(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:81)

Hooks

After Hooks.deleteTransportAfterTest() 133ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Check if advice data saved in SK API database after edition

The scenario checks if you can correctly edit an advice. After that the correctness of the data that has been sent to the SK API microservice database is also verified.

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

And Add transport by SKApi in "MGW" assigned to "" 002ms

And Set "advice" inputs from JSON file "EDIT_ADVICE" "super-admin-skz" 001ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 6s 820ms

And Create advice by JSON file "CREATE_ADVICE_FOR_TRANSPORT_ORDER" as "super-admin-skz" 884ms

And Go to "TRANSPORT_TABLE" 127ms

When Go to transport details "TRANSPORT_ORDER" 2s 495ms

And Expand advice panel 091ms

And Edit advice in transport details 16s 536ms

And Fill arrival date field 2s 269ms

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

Then Check advice data in database after edition "TRANSPORT_ORDER" 50s 094ms

Error message

java.lang.NullPointerException
	at CucumberTests.Transport.AdviceTransport.assertAdviceFields(AdviceTransport.java:210)
	at CucumberTests.Transport.AdviceTransport.checkAreAdviceValuesSavedInSKAPI(AdviceTransport.java:205)
	at ✽.Check advice data in database after edition "TRANSPORT_ORDER"(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:81)

Hooks

After Hooks.deleteTransportAfterTest() 120ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create "CREATE_GRAY_WINDOW_TWG" window by JSON file for test as "super-admin-hochland" 033ms

And Create "CREATE_GRAY_WINDOW_OST" window by JSON file for test as "super-admin-hochland" 032ms

When Go to "WAREHOUSE_TAB" 826ms

And Select warehouse "Twarożkarnia wyrób gotowy" 1s 926ms

And Select view "DAYS_2" 2s 063ms

Then Check if gray window is in the schedule 2s 022ms

And Select warehouse "Opakowania, surowce twarożkarnia" 1s 282ms

And Select view "DAYS_2" 2s 044ms

And Check if gray window is in the schedule 2s 012ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 145ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create "CREATE_GRAY_WINDOW_TWG" window by JSON file for test as "super-admin-hochland" 033ms

And Create "CREATE_GRAY_WINDOW_OST" window by JSON file for test as "super-admin-hochland" 036ms

When Go to "WAREHOUSE_TAB" 831ms

And Select warehouse "Twarożkarnia wyrób gotowy" 1s 945ms

And Select view "DAYS_2" 2s 074ms

Then Check if gray window is in the schedule 2s 022ms

And Select warehouse "Opakowania, surowce twarożkarnia" 1s 289ms

And Select view "DAYS_2" 2s 042ms

And Check if gray window is in the schedule 2s 013ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 186ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pha1-carrier@qa.qa-test" and set token of apiUsername "super-admin-hochland" 2s 549ms

And Create "CREATE_GRAY_WINDOW_TWG" window by JSON file for test as "super-admin-hochland" 038ms

And Create "CREATE_GRAY_WINDOW_OST" window by JSON file for test as "super-admin-hochland" 033ms

When Go to "WAREHOUSE_TAB" 818ms

And Select warehouse "Twarożkarnia wyrób gotowy" 1s 912ms

And Select view "DAYS_2" 2s 065ms

Then Check if gray window is in the schedule 2s 021ms

And Select warehouse "Opakowania, surowce twarożkarnia" 1s 275ms

And Select view "DAYS_2" 2s 043ms

And Check if gray window is in the schedule 2s 014ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 157ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create "CREATE_GRAY_WINDOW_MGW" window by JSON file for test as "super-admin-skz" 030ms

And Create "CREATE_GRAY_WINDOW_HRL" window by JSON file for test as "super-admin-skz" 032ms

When Go to "WAREHOUSE_TAB" 460ms

And Select warehouse "MGW" 1s 168ms

And Select view "DAYS_2" 2s 067ms

Then Check if gray window is in the schedule 2s 018ms

And Select warehouse "HRL" 1s 410ms

And Select view "DAYS_2" 2s 053ms

And Check if gray window is in the schedule 2s 014ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 120ms

View Feature Schedule

@deleteTransportAfterTest @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if used pallet limit in schedule changing properly with given pallet settings [A-7575]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 097ms

And Set "transport" inputs from JSON file "CREATE_DELIVERY_PALLETS_IN_WAREHOUSE_STEP_ONLY" "super-admin-neuca" 000ms

And Get package type settings for transportType "DELIVERY" from "neuca" 174ms

And Set package type "PALLETS" settings with values: "visibleInContractorStep;visibleInWarehouseStep", "true;false" 171ms

When Login as "neuca-admin" 1s 720ms

And Go to new transport "DELIVERY" 359ms

And Fill transport form 35s 181ms

And Get sum of pallets of "load" in transport form 035ms

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

And Set advice window in schedule 2s 172ms

And Check is transport created in schedule and set transport id 904ms

Then Verify if used pallet limit in schedule changed properly in "I" on "RT1" 087ms

Hooks

After Hooks.deleteTransportAfterTest() 166ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 025ms

View Feature Schedule

@deleteTransportAfterTest @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if used pallet limit in schedule changing properly with given pallet settings [A-7575]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 102ms

And Set "transport" inputs from JSON file "CREATE_DELIVERY_PALLETS_IN_COMPANY_STEP_ONLY" "super-admin-neuca" 001ms

And Get package type settings for transportType "DELIVERY" from "neuca" 017ms

And Set package type "PALLETS" settings with values: "visibleInContractorStep;visibleInWarehouseStep", "false;true" 048ms

When Login as "neuca-admin" 1s 030ms

And Go to new transport "DELIVERY" 358ms

And Fill transport form 35s 187ms

And Get sum of pallets of "unload" in transport form 036ms

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

And Set advice window in schedule 2s 188ms

And Check is transport created in schedule and set transport id 772ms

Then Verify if used pallet limit in schedule changed properly in "I" on "RT1" 080ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 022ms

View Feature Schedule

@deleteTransportAfterTest @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if used pallet limit in schedule changing properly with given pallet settings [A-7575]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_DELIVERY_PALLETS_IN_WAREHOUSE_AND_COMPANY_STEPS" "super-admin-neuca" 001ms

And Get package type settings for transportType "DELIVERY" from "neuca" 014ms

And Set package type "PALLETS" settings with values: "visibleInContractorStep;visibleInWarehouseStep", "true;true" 037ms

When Login as "neuca-admin" 1s 057ms

And Go to new transport "DELIVERY" 366ms

And Fill transport form 37s 875ms

And Get sum of pallets of "unload" in transport form 035ms

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

And Set advice window in schedule 2s 169ms

And Check is transport created in schedule and set transport id 822ms

Then Verify if used pallet limit in schedule changed properly in "I" on "RT1" 084ms

Hooks

After Hooks.deleteTransportAfterTest() 141ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 020ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 017ms

Steps

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

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

And Mark custom fields as not obligatory 389ms

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

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

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

And Confirm statuses until reach "process-ended" 31s 604ms

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

Hooks

After Hooks.deleteTransportAfterTest() 130ms

After Hooks.rollbackAllCustomFieldsSettings() 563ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-pgf" 090ms

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

And Mark custom fields as not obligatory 004ms

And Login as "pgf-admin" 1s 344ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 123ms

After Hooks.rollbackAllCustomFieldsSettings() 085ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 096ms

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

And Mark custom fields as not obligatory 003ms

And Login as "adama-admin" 1s 436ms

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

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

And Confirm statuses until reach "process-ended" 23s 513ms

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

Hooks

After Hooks.deleteTransportAfterTest() 092ms

After Hooks.rollbackAllCustomFieldsSettings() 074ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-lantmannen" 102ms

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

And Mark custom fields as not obligatory 006ms

And Login as "lantmannen-admin" 1s 360ms

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

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

And Confirm statuses until reach "process-ended" 30s 945ms

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

Hooks

After Hooks.deleteTransportAfterTest() 105ms

After Hooks.rollbackAllCustomFieldsSettings() 004ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-lantmannen" 094ms

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

And Mark custom fields as not obligatory 004ms

And Login as "lantmannen-admin" 1s 057ms

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

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

And Confirm statuses until reach "process-ended" 34s 688ms

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

Hooks

After Hooks.deleteTransportAfterTest() 089ms

After Hooks.rollbackAllCustomFieldsSettings() 003ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Mark custom fields as not obligatory 083ms

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

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

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

And Confirm statuses until reach "process-ended" 30s 981ms

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

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.rollbackAllCustomFieldsSettings() 094ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Mark custom fields as not obligatory 092ms

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

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

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

And Confirm statuses until reach "process-ended" 31s 019ms

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

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.rollbackAllCustomFieldsSettings() 102ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

And Show "SMALLS_IMPORT" 081ms

When Accept or reject "accept" transferred transport 15s 914ms

And Set "advice" inputs from JSON file "ADVICE_SMALLS" "super-admin-skz" 001ms

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

And Set advice window in schedule 2s 646ms

And Fill advice form 16s 666ms

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

And Check if window is "silver" 4s 030ms

And Go to "TRANSPORT_TABLE" 225ms

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

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

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

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

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

And Show "SMALLS_EXPORT" 077ms

When Accept or reject "accept" transferred transport 15s 966ms

And Set "advice" inputs from JSON file "ADVICE_SMALLS" "super-admin-skz" 001ms

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

And Set advice window in schedule 2s 638ms

And Fill advice form 16s 695ms

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

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

And Go to "TRANSPORT_TABLE" 210ms

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

Hooks

After Hooks.deleteTransportAfterTest() 153ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackAllCustomFieldsSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Mark custom fields as not obligatory 376ms

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

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

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

And Confirm statuses until reach "arrived" 4s 855ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 100ms

After Hooks.rollbackAllCustomFieldsSettings() 475ms

After Hooks.rollbackAddedActionAuthorities() 058ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check is transport color changed after confirm status

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Mark custom fields as not obligatory 348ms

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

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

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

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

And Confirm statuses until reach "arrived" 4s 827ms

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

And Confirm statuses until reach "during-unload" 5s 272ms

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

And Confirm statuses until reach "unloaded" 4s 758ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 112ms

After Hooks.rollbackAllCustomFieldsSettings() 494ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 100ms

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

And Mark custom fields as not obligatory 005ms

And Login as "piast-admin" 1s 523ms

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

And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 001ms

And Show all transport types 1s 038ms

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

And Set advice window in schedule 2s 622ms

And Fill advice form 10s 558ms

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

And Go to "TRANSPORT_TABLE" 230ms

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

And Confirm statuses until reach "left-the-area" 25s 567ms

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

Hooks

After Hooks.deleteTransportAfterTest() 107ms

After Hooks.rollbackAllCustomFieldsSettings() 555ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 094ms

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

And Mark custom fields as not obligatory 008ms

And Login as "piast-admin" 1s 540ms

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

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

And Show all transport types 1s 041ms

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

And Set advice window in schedule 2s 651ms

And Fill advice form 10s 613ms

And Click advice save button and wait for advice form to disappear 10s 162ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='save'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.2KxY4c}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 27f8686fbbe216e38127d63861020cbd
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:217)
	at Pages.Transport.AdviceFormPage.confirm(AdviceFormPage.java:27)
	at CucumberTests.Transport.AdviceTransport.clickAdviceSaveButtonAndWaitForAdviceFormToDisappear(AdviceTransport.java:179)
	at ✽.Click advice save button and wait for advice form to disappear(file:Features/Atom/Statuses/ConfirmStatuses.feature:93)

And Go to "TRANSPORT_TABLE" 000ms

And Find transport in table with status "advice-added" 000ms

And Confirm statuses until reach "left-the-area" 000ms

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

Hooks

After Hooks.deleteTransportAfterTest() 062ms

After Hooks.rollbackAllCustomFieldsSettings() 673ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 112ms

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

And Mark custom fields as not obligatory 006ms

And Login as "piast-admin" 1s 534ms

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

And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 001ms

And Show all transport types 1s 038ms

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

And Set advice window in schedule 2s 645ms

And Fill advice form 10s 554ms

And Click advice save button and wait for advice form to disappear 10s 167ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='save'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.2KxY4c}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 27f8686fbbe216e38127d63861020cbd
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:217)
	at Pages.Transport.AdviceFormPage.confirm(AdviceFormPage.java:27)
	at CucumberTests.Transport.AdviceTransport.clickAdviceSaveButtonAndWaitForAdviceFormToDisappear(AdviceTransport.java:179)
	at ✽.Click advice save button and wait for advice form to disappear(file:Features/Atom/Statuses/ConfirmStatuses.feature:115)

And Go to "TRANSPORT_TABLE" 000ms

And Find transport in table with status "advice-added" 000ms

When Add file to transport by API 000ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 059ms

After Hooks.rollbackAllCustomFieldsSettings() 567ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 097ms

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

And Mark custom fields as not obligatory 006ms

And Login as "piast-admin" 1s 551ms

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

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

And Show all transport types 1s 038ms

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

And Set advice window in schedule 2s 638ms

And Fill advice form 10s 577ms

And Click advice save button and wait for advice form to disappear 10s 143ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='save'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.2KxY4c}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 27f8686fbbe216e38127d63861020cbd
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:217)
	at Pages.Transport.AdviceFormPage.confirm(AdviceFormPage.java:27)
	at CucumberTests.Transport.AdviceTransport.clickAdviceSaveButtonAndWaitForAdviceFormToDisappear(AdviceTransport.java:179)
	at ✽.Click advice save button and wait for advice form to disappear(file:Features/Atom/Statuses/ConfirmStatuses.feature:115)

And Go to "TRANSPORT_TABLE" 000ms

And Find transport in table with status "advice-added" 000ms

When Add file to transport by API 000ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 060ms

After Hooks.rollbackAllCustomFieldsSettings() 669ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - with advice step

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

And Mark custom fields as not obligatory 660ms

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

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 15s 146ms

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

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

And Show all transport types 1s 070ms

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

And Set advice window in schedule 6s 489ms

And Fill advice form 15s 024ms

Error message

java.lang.AssertionError: Nie można wypełnić pola car-registration-number, ponieważ nie udało się go znaleźć w formularzu
	at org.junit.Assert.fail(Assert.java:88)
	at CucumberTests.Transport.Transport.fillFields(Transport.java:158)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:150)
	at CucumberTests.Transport.AdviceTransport.fillAdviceForm(AdviceTransport.java:126)
	at ✽.Fill advice form(file:Features/Atom/Statuses/ConfirmStatuses.feature:139)

And Click advice save button and wait for advice form to disappear 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Find transport in table with status "advice-added" 000ms

And Confirm statuses until reach "during-load" 000ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 059ms

After Hooks.rollbackAllCustomFieldsSettings() 713ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - with advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Mark custom fields as not obligatory 105ms

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 15s 182ms

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

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

And Show all transport types 1s 142ms

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

And Set advice window in schedule 2s 455ms

And Fill advice form 15s 392ms

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

And Go to "TRANSPORT_TABLE" 206ms

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

And Confirm statuses until reach "arrived" 4s 829ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

After Hooks.rollbackAllCustomFieldsSettings() 142ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - with advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Mark custom fields as not obligatory 120ms

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

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

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

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

And Show all transport types 1s 069ms

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

And Set advice window in schedule 2s 463ms

And Fill advice form 15s 359ms

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

And Go to "TRANSPORT_TABLE" 190ms

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

And Confirm statuses until reach "arrived" 4s 796ms

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

After Hooks.rollbackAllCustomFieldsSettings() 116ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - without advice step

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

And Mark custom fields as not obligatory 083ms

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

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

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

And Go to "TRANSPORT_TABLE" 125ms

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

And Confirm statuses until reach "arrived" 4s 822ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 083ms

After Hooks.rollbackAllCustomFieldsSettings() 082ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - without advice step

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

And Mark custom fields as not obligatory 079ms

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

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

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

And Go to "TRANSPORT_TABLE" 110ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.rollbackAllCustomFieldsSettings() 122ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - without advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Mark custom fields as not obligatory 367ms

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

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

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

And Go to "TRANSPORT_TABLE" 205ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 103ms

After Hooks.rollbackAllCustomFieldsSettings() 499ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Mark custom fields as not obligatory 102ms

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

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

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

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

And Show all transport types 1s 164ms

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

And Set advice window in schedule 2s 434ms

And Fill advice form 15s 337ms

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

And Go to "TRANSPORT_TABLE" 167ms

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

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

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

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

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

And Click cancel in status confirmation modal 15s 118ms

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

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

And Fill transport form 25s 936ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 122ms

After Hooks.rollbackAllCustomFieldsSettings() 140ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Mark custom fields as not obligatory 116ms

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

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

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

And Show all transport types 1s 068ms

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

And Set advice window in schedule 2s 481ms

And Fill advice form 15s 314ms

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

And Go to "TRANSPORT_TABLE" 199ms

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

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

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

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

And Click cancel in status confirmation modal 15s 121ms

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

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

And Fill transport form 25s 968ms

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 132ms

After Hooks.rollbackAllCustomFieldsSettings() 145ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Mark custom fields as not obligatory 611ms

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

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

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

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

And Show all transport types 1s 079ms

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

And Set advice window in schedule 6s 478ms

And Fill advice form 15s 045ms

Error message

java.lang.AssertionError: Nie można wypełnić pola car-registration-number, ponieważ nie udało się go znaleźć w formularzu
	at org.junit.Assert.fail(Assert.java:88)
	at CucumberTests.Transport.Transport.fillFields(Transport.java:158)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:150)
	at CucumberTests.Transport.AdviceTransport.fillAdviceForm(AdviceTransport.java:126)
	at ✽.Fill advice form(file:Features/Atom/Statuses/ConfirmStatuses.feature:183)

And Click advice save button and wait for advice form to disappear 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Find transport in table with status "advice-added" 000ms

When Confirm statuses until reach "during-load" 000ms

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

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

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

And Click cancel in status confirmation modal 000ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 000ms

And Open section: "advice-panel" 000ms

And Fill transport form 000ms

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

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 000ms

And Open section: "advice-panel" 000ms

And Fill "warehouseman-(u)" in transport form 000ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 071ms

After Hooks.rollbackAllCustomFieldsSettings() 735ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Mark custom fields as not obligatory 094ms

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

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

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

And Go to "TRANSPORT_TABLE" 146ms

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

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

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

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

And Click cancel in status confirmation modal 15s 103ms

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

And Fill transport form 38s 527ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.rollbackAllCustomFieldsSettings() 090ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Mark custom fields as not obligatory 084ms

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

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

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

And Go to "TRANSPORT_TABLE" 144ms

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

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

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

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

And Click cancel in status confirmation modal 15s 143ms

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

And Fill transport form 38s 477ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 116ms

After Hooks.rollbackAllCustomFieldsSettings() 107ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Mark custom fields as not obligatory 366ms

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

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

And Go to "TRANSPORT_TABLE" 261ms

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

When Confirm statuses until reach "during-unload" 9s 035ms

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

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

And Click cancel in status confirmation modal 15s 173ms

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

And Fill transport form 38s 032ms

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

And Confirm statuses until reach "process-ended" 23s 591ms

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

Hooks

After Hooks.deleteTransportAfterTest() 129ms

After Hooks.rollbackAllCustomFieldsSettings() 473ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 227ms

When Confirm "Departure" status in transport row 070ms

Then Verify that "Departure" has been confirmed 255ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

And Mark custom fields as not obligatory 089ms

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

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

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

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

And Confirm statuses until reach "arrived" 4s 808ms

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

And Click cancel in status confirmation modal 15s 134ms

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

And Fill transport form 38s 540ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 095ms

After Hooks.rollbackAllCustomFieldsSettings() 089ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Mark custom fields as not obligatory 114ms

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

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

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

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

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

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

And Click cancel in status confirmation modal 15s 183ms

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

And Fill transport form 38s 516ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 103ms

After Hooks.rollbackAllCustomFieldsSettings() 108ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAllCustomFieldsSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Mark custom fields as not obligatory 372ms

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

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

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

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

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

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

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

And Click cancel in status confirmation modal 15s 193ms

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

And Fill transport form 37s 884ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 096ms

After Hooks.rollbackAllCustomFieldsSettings() 491ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest @rollbackAllCustomFieldsSettings @rollbackTaskChanges

Scenario Outline Check if it is possible to confirm status with given confirmation date [A-7159]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-bausch" 096ms

And Prepare task "ARRIVAL" setting "showPunctualityAlertAfterConfirmation" with value "false" for transport type "LOAD_EXPORT" and principal "bausch" 055ms

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

And Mark custom fields as not obligatory 116ms

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

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 1s 248ms

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

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" 792ms

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

And Go to "TRANSPORT_TABLE" 237ms

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

And Confirm statuses until reach "on-the-way" 12s 839ms

When Open statuses popup 058ms

And Toggle status date confirmation checkbox 289ms

And Confirm statuses until reach "process-ended" 19s 779ms

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

Hooks

After Hooks.deleteTransportAfterTest() 131ms

After Hooks.rollbackAllCustomFieldsSettings() 277ms

After Hooks.deleteModeOfTransportationAfterTest() 086ms

After Hooks.rollbackTaskChanges() 026ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest @rollbackAllCustomFieldsSettings @rollbackTaskChanges

Scenario Outline Check if it is not possible to confirm status with invalid confirmation date [A-7159]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 103ms

And Prepare task "ARRIVAL" setting "showPunctualityAlertAfterConfirmation" with value "false" for transport type "LOAD_EXPORT" and principal "bausch" 050ms

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

And Mark custom fields as not obligatory 117ms

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

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 1s 280ms

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

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" 782ms

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

And Go to "TRANSPORT_TABLE" 232ms

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

And Confirm statuses until reach "on-the-way" 12s 311ms

And Open statuses popup 074ms

And Toggle status date confirmation checkbox 315ms

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

Then Verify that status cannot be confirmed 1s 094ms

Hooks

After Hooks.deleteTransportAfterTest() 139ms

After Hooks.rollbackAllCustomFieldsSettings() 327ms

After Hooks.deleteModeOfTransportationAfterTest() 065ms

After Hooks.rollbackTaskChanges() 034ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest @rollbackAllCustomFieldsSettings @rollbackTaskChanges

Scenario Outline Check if it is not possible to confirm status with invalid confirmation date [A-7159]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare task "ARRIVAL" setting "showPunctualityAlertAfterConfirmation" with value "false" for transport type "LOAD_EXPORT" and principal "bausch" 044ms

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

And Mark custom fields as not obligatory 097ms

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

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 1s 230ms

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

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" 790ms

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

And Go to "TRANSPORT_TABLE" 230ms

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

And Confirm statuses until reach "on-the-way" 12s 304ms

And Open statuses popup 053ms

And Toggle status date confirmation checkbox 281ms

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

Then Verify that status cannot be confirmed 1s 070ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

After Hooks.rollbackAllCustomFieldsSettings() 315ms

After Hooks.deleteModeOfTransportationAfterTest() 047ms

After Hooks.rollbackTaskChanges() 031ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackTaskChanges @rollbackAllCustomFieldsSettings

Scenario Outline Confirmed statuses of existing orders should not be deleted - even after editing the order [A-6874]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 091ms

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

And Mark custom fields as not obligatory 006ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 237ms

And Confirm statuses until reach "during-unload" 13s 399ms

And Set actual confirmed transport status list 1s 382ms

And Disable task by API 034ms

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

And Edit transport hours and recalculate statuses 30s 249ms

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

Hooks

After Hooks.deleteTransportAfterTest() 114ms

After Hooks.rollbackAllCustomFieldsSettings() 055ms

After Hooks.rollbackTaskChanges() 033ms

View Feature Status confirmation

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest @rollbackAllCustomFieldsSettings @TmsLink=A-8004

Scenario Outline Check if timeliness alert is visible after checkpoint confirmation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Mark custom fields as not obligatory 111ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 1s 250ms

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

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

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" with interval "-30m" 791ms

And Login as "super-admin-bausch" 1s 827ms

And Go to "TRANSPORT_TABLE" 231ms

Then Confirm next status and expect alert "Status potwierdzony z opóźnieniem" 807ms

And Wait "1" seconds 1s

And Verify that note was added "Status potwierdzony po czasie" 1s 145ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.rollbackAllCustomFieldsSettings() 284ms

After Hooks.deleteModeOfTransportationAfterTest() 056ms

View Feature Status confirmation

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest @rollbackAllCustomFieldsSettings @TmsLink=A-8004

Scenario Outline Check if timeliness alert is visible after checkpoint confirmation

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

And Mark custom fields as not obligatory 115ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 1s 237ms

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

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

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" with interval "0m" 770ms

And Login as "super-admin-bausch" 1s 698ms

And Go to "TRANSPORT_TABLE" 226ms

Then Confirm next status and expect alert "" 239ms

And Wait "1" seconds 1s

And Verify that note was added "" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 139ms

After Hooks.rollbackAllCustomFieldsSettings() 317ms

After Hooks.deleteModeOfTransportationAfterTest() 068ms

View Feature Status confirmation

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest @rollbackAllCustomFieldsSettings @TmsLink=A-8004

Scenario Outline Check if timeliness alert is visible after checkpoint confirmation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 096ms

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

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

And Mark custom fields as not obligatory 118ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 1s 298ms

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

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

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" with interval "30m" 822ms

And Login as "super-admin-bausch" 1s 889ms

And Go to "TRANSPORT_TABLE" 223ms

Then Confirm next status and expect alert "Status potwierdzony przed czasem" 792ms

And Wait "1" seconds 1s

And Verify that note was added "Status potwierdzony przed czasem" 1s 163ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

After Hooks.rollbackAllCustomFieldsSettings() 290ms

After Hooks.deleteModeOfTransportationAfterTest() 049ms

View Feature Status rejection

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackWarehousesAccess

Scenario Outline Check if it is possible to reject status by guard in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file 222ms

And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 185ms

And Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file 129ms

And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 1s 233ms

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

And Check if reject date is not visible 15s 023ms

When Reject status: Book of disinfection 096ms

And Check if reject date is visible 261ms

Then If user is login then logout 279ms

And Login as "lantmannen-admin" 843ms

And Check if note was added to transport after status rejection 1s 242ms

And Check if history note was added to transport after status rejection - "LOAD" 6s 588ms

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji" 2m 46s 695ms

And Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

After Hooks.cleanUserDetailsAfterTest() 184ms

After Hooks.rollbackWarehousesAccess() 134ms

View Feature Status rejection

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject status twice and reject date is changing

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_LOAD_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 344ms

And Check if reject date is not visible 15s 022ms

When Reject status: Book of disinfection 096ms

And Check if reject date is visible 145ms

And Get rejection date 031ms

And Wait "60" seconds 1m

And Reject status: Book of disinfection 092ms

Then Check if reject date has changed 1s 106ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

View Feature Status rejection

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject status by admin in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

And Check if reject date is not visible 15s 017ms

When Reject status: Book of disinfection 099ms

Then Check if reject date is visible 142ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

View Feature Status rejection

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject status by admin in statuses popup

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 991ms

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

And Open statuses popup 109ms

And Check if reject date is not visible 15s 045ms

When Reject status: Book of disinfection 089ms

Then Open statuses popup 045ms

And Check if reject date is visible 083ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

View Feature Status revocation

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Confirm to the last status by API 242ms

When Find statuses for transport in table 2s 016ms

And Revoke statuses until reach "advice-added" 6s 872ms

Then Check if transport has "advice-added" 023ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

View Feature Status revocation

@deleteTransportAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Confirm to the last status by API 216ms

When Find statuses for transport in table 1s 748ms

And Revoke statuses until reach "planned" 6s 802ms

Then Check if transport has "planned" 019ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

View Feature Status

@deleteTransportAfterTest

Scenario Outline Check if after created transport without advice, transport has checkpoints only from "preparation" section

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 878ms

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

When Find transport in table with status "new" 3s 227ms

And Open statuses popup 088ms

Then Check if transport has checkpoints from list "Utworzenie zlecenia,Dodanie awizacji,Potwierdzenie okna czasowego" in "0" 068ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

View Feature Status

@deleteTransportAfterTest

Scenario Outline Check if after added advice, checkpoints are generated from "steps" section

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 046ms

And Set "advice" inputs from JSON file "ADVICE_EXTERNAL_DELIVERY" "super-admin-farmacol" 001ms

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

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

And Set advice window in schedule 2s 729ms

And Fill advice form 14s 173ms

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

And Go to "TRANSPORT_TABLE" 238ms

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

And Open statuses popup 082ms

Then Check if transport has checkpoints from list "Zgłoszenie kierowcy,Rozpoczęcie rozładunku,Zakończenie rozładunku" in "1" 067ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Status

@deleteTransportAfterTest @rollbackTaskChanges @rollbackAllCustomFieldsSettings

Scenario Outline Check if deleted task is not in new transports' workflow @A-6875

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 094ms

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

And Mark custom fields as not obligatory 005ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 219ms

And Confirm statuses until reach "registered-katowice-przyjęcia" 9s 652ms

And Disable task by API 034ms

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

And Click pencil and move transport to next day in schedule 18s 267ms

And Go to "TRANSPORT_TABLE" 210ms

Then Verify that "START_OF_UNLOADING" "is not" visible 162ms

Hooks

After Hooks.deleteTransportAfterTest() 142ms

After Hooks.rollbackAllCustomFieldsSettings() 051ms

After Hooks.rollbackTaskChanges() 033ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 079ms

When Go to "WAREHOUSE_TAB" 843ms

And Select warehouse "Serownia" 1s 495ms

And Set week view 1s 098ms

And Show yesterday 1s 069ms

And Move window into the past 298ms

Then Check if window is "red" 4s 029ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

After Hooks.rollbackAddedAuthorities() 051ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 978ms

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

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "lantmannen-admin" 030ms

When Go to "WAREHOUSE_TAB" 841ms

And Select warehouse "Magazyn - Nowa Sól" 2s 452ms

And Set week view 1s 105ms

And Show yesterday 1s 073ms

And Move window into the past 422ms

Then Check if window is "red" 4s 033ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

After Hooks.rollbackAddedAuthorities() 024ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past after add advice by advice button in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "piast-admin" 033ms

And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 001ms

When Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 591ms

And Fill advice form 10s 580ms

And Click advice save button and wait for advice form to disappear 10s 178ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='save'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.2KxY4c}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 27f8686fbbe216e38127d63861020cbd
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:217)
	at Pages.Transport.AdviceFormPage.confirm(AdviceFormPage.java:27)
	at CucumberTests.Transport.AdviceTransport.clickAdviceSaveButtonAndWaitForAdviceFormToDisappear(AdviceTransport.java:179)
	at ✽.Click advice save button and wait for advice form to disappear(file:Features/Atom/TimeWindow/TransportWindow.feature:30)

And Select warehouse "Magazyn Hala A" 000ms

And Set week view 000ms

And Show yesterday 000ms

And Move window into the past 000ms

Then Check if window is "red" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

After Hooks.rollbackAddedAuthorities() 021ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if time window resize with restriction to algorithm settings

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "EDIT_EXPORT" "super-admin-hochland" 000ms

And Set algorithm setting for "super-admin-hochland" in "Magazyn Zimny Kaźmierz" on "Magazyn Zimny" 373ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 414ms

When Go to "WAREHOUSE_TAB" 882ms

And Select warehouse "Magazyn Zimny Kaźmierz" 1s 807ms

And Set week view 1s 118ms

And Check if time window length is correct after "CREATE" 023ms

And Change number of pallets in transport 53s 284ms

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

And Check if time window length is correct after "EDIT" 025ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if time window has valid length with restriction to algorithm settings when quantity is set in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get package type settings for transportType "UNLOAD" from "keeeper" 019ms

And Set package type "PALLETS" settings with values: "defaultValue;required", "4;true" 045ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 079ms

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

When Go to "WAREHOUSE_TAB" 313ms

And Select warehouse "Magazyn Surowców" 1s 193ms

And Set week view 1s 098ms

Then Check if time window has proper "60" 033ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 025ms

After Hooks.clearAlgorithmSettings() 138ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if time window has valid length with restriction to algorithm settings when quantity is set from default quantity value and quantity field is not visible in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get package type settings for transportType "UNLOAD" from "keeeper" 017ms

And Set package type "PALLETS" settings with values: "defaultValue;required", "4;false" 043ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 077ms

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

When Go to "WAREHOUSE_TAB" 329ms

And Select warehouse "Magazyn Surowców" 1s 171ms

And Set week view 1s 080ms

Then Check if time window has proper "60" 018ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 022ms

After Hooks.clearAlgorithmSettings() 079ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if time window has valid length after advice is added with restriction to algorithm settings when quantity is set from default quantity value and quantity field is not visible in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get package type settings for transportType "LOAD" from "keeeper" 017ms

And Set package type "PALLETS" settings with values: "defaultValue;required", "4;false" 040ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 078ms

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

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

And Show all transport types 1s 041ms

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

And Set advice window in schedule 2s 450ms

And Fill advice form 15s 353ms

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

Then Check if time window has proper "30" 023ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 016ms

After Hooks.clearAlgorithmSettings() 063ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackPackageTypeTransportTypeSettings

Scenario Outline Check if time window has valid length after advice is added with restriction to algorithm settings when quantity is set from default quantity value and quantity field is not visible in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get package type settings for transportType "CONTAINER" from "keeeper" 015ms

And Set package type "PALLETS" settings with values: "defaultValue;required", "20;false" 035ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 071ms

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

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

And Show all transport types 1s 042ms

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

And Set advice window in schedule 2s 499ms

And Fill advice form 15s 351ms

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

Then Check if time window has proper "60" 026ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

After Hooks.rollbackPackageTypeTransportTypeSettings() 024ms

After Hooks.clearAlgorithmSettings() 074ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings

Scenario Outline Check if supplier can change time window size by change number of pallets

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set algorithm setting for "super-admin-hochland" in "Serownia" on "Magazyn Sera" 119ms

And Set token of apiUsername "dha1-supplier-2@qa.qa-test" 095ms

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

And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "super-admin-hochland" 2s 100ms

When Go to transport details "DELIVERY" 30s 671ms

And Change filled value in details "number-of-pallets-step-0" "number" "25" "0" 1s 326ms

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

And Go to "WAREHOUSE_TAB" 984ms

And Select warehouse "Serownia" 1s 505ms

And Set week view 1s 086ms

Then Check if time window has proper "60" 023ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

After Hooks.clearAlgorithmSettings() 107ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if window counter value in schedule changes

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_ACCESS_TO_NUMBER_OF_WINDOWS" to user "keeeper-admin" 057ms

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

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper" 547ms

And Go to "WAREHOUSE_TAB" 285ms

And Select warehouse "Magazyn Wyrobów Gotowych" 2s 114ms

And Go to next day in schedule 1s 083ms

And Check if time window counter value equals "1" 079ms

And Select view "DAYS_2" 2s 081ms

And Move advice window "2" 1s 332ms

And Select view "DAY" 2s 067ms

Then Check if time window counter value equals "0" 065ms

And Delete created transport by API 097ms

And Check if time window counter value equals "0" 039ms

And Click in free spot in schedule page to create gray window 179ms

And Check if time window counter value equals "0" 043ms

And Click in free spot in schedule page to create dedicated window 2s 045ms

And Check if time window counter value equals "0" 042ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-adama" 000ms

When Go to new transport "DELIVERY" 311ms

And Fill transport form 17s 648ms

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

And Set advice window in schedule 2s 166ms

And Check is transport created in schedule and set transport id 535ms

And Go to "TRANSPORT_TABLE" 263ms

When Click on time window date 1s 317ms

And Open transport form when in schedule 1s 146ms

Then Check are transport values equals 2s 240ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-hochland" 000ms

When Go to new transport "DELIVERY" 356ms

And Fill transport form 40s 952ms

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

And Set advice window in schedule 2s 147ms

And Check is transport created in schedule and set transport id 596ms

And Go to "TRANSPORT_TABLE" 261ms

When Click on time window date 1s 266ms

And Open transport form when in schedule 1s 396ms

Then Check are transport values equals 21s 408ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Go to new transport "CISTERN_DELIVERY" 421ms

And Fill transport form 43s 558ms

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

And Set advice window in schedule 2s 215ms

And Check is transport created in schedule and set transport id 506ms

And Go to "TRANSPORT_TABLE" 186ms

When Click on time window date 1s 525ms

And Open transport form when in schedule 1s 262ms

Then Check are transport values equals 8s 432ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_CISTERN_COLLECTION" "super-admin-hochland" 000ms

When Go to new transport "CISTERN_COLLECTION" 339ms

And Fill transport form 30s 512ms

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

And Set advice window in schedule 2s 226ms

And Check is transport created in schedule and set transport id 580ms

And Go to "TRANSPORT_TABLE" 216ms

When Click on time window date 1s 474ms

And Open transport form when in schedule 1s 257ms

Then Check are transport values equals 23s 408ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-lantmannen" 001ms

When Go to new transport "DELIVERY" 322ms

And Fill transport form 40s 114ms

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

And Set advice window in schedule 2s 165ms

And Check is transport created in schedule and set transport id 568ms

And Go to "TRANSPORT_TABLE" 202ms

When Click on time window date 1s 326ms

And Open transport form when in schedule 1s 168ms

Then Check are transport values equals 21s 342ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_LOAD" "super-admin-lantmannen" 001ms

When Go to new transport "LOAD" 322ms

And Fill transport form 40s 072ms

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

And Set advice window in schedule 2s 187ms

And Check is transport created in schedule and set transport id 612ms

And Go to "TRANSPORT_TABLE" 254ms

When Click on time window date 1s 382ms

And Open transport form when in schedule 1s 174ms

Then Check are transport values equals 21s 326ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackTransportTypeSettings

Scenario Outline Check if it is possible to add new warehouse step with new time window to existing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 091ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 096ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 073ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 137ms

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

And Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 819ms

And Go to "TRANSPORT_TABLE" 227ms

When Go to transport details "EXTERNAL_DELIVERY" 2s 505ms

And Add step "unload" 112ms

And Change filled value in details "warehouse-select-step-2" "select" "Mory Przyjęcia" "0" 3s 454ms

And Change filled value in details "weight-step-2" "number" "23" "0" 1s 363ms

And Change filled value in details "number-of-pallets-step-2" "number" "23" "0" 1s 340ms

And Change filled value in details "time-range-from-date-2" "date" "" "0" 3s 321ms

Then Click "save-transport" save button 175ms

And Set advice window in schedule in "2" days 5s 021ms

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

And Go to "TRANSPORT_TABLE" 262ms

And Check if transport has "2" time windows 016ms

Hooks

After Hooks.deleteTransportAfterTest() 152ms

After Hooks.rollbackTransportTypeSettings() 062ms

After Hooks.rollbackAddedActionAuthorities() 062ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest

Scenario Outline Check if window changes color properly in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 030ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 054ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 225ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 727ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY_2_WINDOWS" as "super-admin-farmacol" 766ms

And Go to "TRANSPORT_TABLE" 132ms

And Get checkpoint colors for transport 004ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "true" 061ms

Error message

java.lang.AssertionError
	at org.junit.Assert.fail(Assert.java:86)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.junit.Assert.assertTrue(Assert.java:52)
	at CucumberTests.TimeWindow.TimeWindowTest.verifyThatTransportColorsChangeInColumnProperlyWhenWindowColorDependsOnWarehouseIs(TimeWindowTest.java:102)
	at ✽.Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "true"(file:Features/Atom/TimeWindow/TransportWindow.feature:232)

Hooks

After Hooks.deleteTransportAfterTest() 126ms

After Hooks.rollbackTransportTypeSettings() 068ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest

Scenario Outline Check if window changes color properly in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 096ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 029ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 061ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 193ms

And Set double window advice 000ms

And Login as "farmacol-admin" 988ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY_2_WINDOWS" as "super-admin-farmacol" 806ms

And Go to "TRANSPORT_TABLE" 127ms

And Get checkpoint colors for transport 004ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "false" 049ms

Error message

java.lang.AssertionError
	at org.junit.Assert.fail(Assert.java:86)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.junit.Assert.assertTrue(Assert.java:52)
	at CucumberTests.TimeWindow.TimeWindowTest.verifyThatTransportColorsChangeInColumnProperlyWhenWindowColorDependsOnWarehouseIs(TimeWindowTest.java:102)
	at ✽.Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "false"(file:Features/Atom/TimeWindow/TransportWindow.feature:232)

Hooks

After Hooks.deleteTransportAfterTest() 148ms

After Hooks.rollbackTransportTypeSettings() 062ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest @FLAKY

Scenario Outline Check if window changes color properly in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 092ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 029ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 054ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 217ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 029ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY_2_WINDOWS" as "super-admin-farmacol" 763ms

And Get checkpoint colors for transport 004ms

And Go to "TRANSPORT_TABLE" 111ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true" 18s 648ms

Error message

java.lang.AssertionError: Niepoprawna zmiana koloru przy statusie waiting-to-driver-katowice-przyjęcia
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.TimeWindow.TimeWindowTest.verifyThatTransportColorsOfWindowsChangeProperlyInScheduleWhenWindowColorDependsOnWarehouseIs(TimeWindowTest.java:120)
	at ✽.Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true"(file:Features/Atom/TimeWindow/TransportWindow.feature:250)

Hooks

After Hooks.deleteTransportAfterTest() 128ms

After Hooks.rollbackTransportTypeSettings() 060ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest @FLAKY

Scenario Outline Check if window changes color properly in schedule

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 092ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 024ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 056ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 15s 150ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 102ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY_2_WINDOWS" as "super-admin-farmacol" 813ms

And Get checkpoint colors for transport 003ms

And Go to "TRANSPORT_TABLE" 138ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "false" 18s 683ms

Error message

java.lang.AssertionError: Niepoprawna zmiana koloru przy statusie waiting-to-driver-katowice-przyjęcia
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.TimeWindow.TimeWindowTest.verifyThatTransportColorsOfWindowsChangeProperlyInScheduleWhenWindowColorDependsOnWarehouseIs(TimeWindowTest.java:120)
	at ✽.Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "false"(file:Features/Atom/TimeWindow/TransportWindow.feature:250)

Hooks

After Hooks.deleteTransportAfterTest() 111ms

After Hooks.rollbackTransportTypeSettings() 101ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if window is active after using "create similar" on that window [A-7009]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 090ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 149ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 648ms

And Login as "super-admin-farmacol" 1s 629ms

And Show all transport types 1s 167ms

And Click on time window date 1s 600ms

Then Open transport form when in schedule 1s 311ms

And Click create similar button 15s 147ms

And Click cancel button in transport form 098ms

And Open transport form when in schedule 1s 233ms

Then Check if transport form modal is visible 041ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if min and max advice date changed after moving advice window [A-7503]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 146ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 674ms

And Get min and max advice date of created transport as "super-admin-farmacol" 136ms

And Login as "farmacol-admin" 1s 143ms

And Show all transport types 1s 169ms

And Click on time window date 1s 666ms

And Set week view 2s 422ms

And Move advice window "3" 1s 629ms

Then Check if min and max advice date changed after moving advice window as "super-admin-farmacol" 157ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedActionAuthorities

Scenario Outline Check if time window can not be moved in specified time before its start

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-bausch" 096ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 15s 205ms

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

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

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" with interval "60m" 805ms

And Add action authority with time interval: "bausch" "super-admin-bausch" "LOAD_EXPORT" "MOVE_ADVICE_WINDOW" "TIME_BASED" "-2h" "EARLIEST_TIME_WINDOW_START" 047ms

And Login as "super-admin-bausch" 1s 810ms

And Go to "WAREHOUSE_TAB" 781ms

And Change warehouse in schedule to: "Magazyn Bausch Health Poland" 443ms

And Wait "2" seconds 2s

When Move window by interval "1h" 420ms

And Alert after moving is displayed "Nie można przesunąć okna czasowego - minął dopuszczalny czas na wykonanie tej akcji" 239ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

After Hooks.rollbackAddedActionAuthorities() 027ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedActionAuthorities

Scenario Outline Check if time window can not be moved in specified time before its start

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 096ms

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

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

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

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" with interval "180m" 779ms

And Add action authority with time interval: "bausch" "super-admin-bausch" "LOAD_EXPORT" "MOVE_ADVICE_WINDOW" "TIME_BASED" "-2h" "EARLIEST_TIME_WINDOW_START" 043ms

And Login as "super-admin-bausch" 1s 759ms

And Go to "WAREHOUSE_TAB" 770ms

And Change warehouse in schedule to: "Magazyn Bausch Health Poland" 443ms

And Wait "2" seconds 2s

When Move window by interval "1h" 373ms

And Alert after moving is displayed "" 15s 062ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

After Hooks.rollbackAddedActionAuthorities() 032ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedActionAuthorities

Scenario Outline Check if time window can not be moved in specified time before its start

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 094ms

And Create transport "CREATE_LOAD_EXPORT" by JSON file as "super-admin-bausch" 15s 230ms

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

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

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_EXPORT" as "super-admin-bausch" with interval "180m" 747ms

And Add action authority with time interval: "bausch" "super-admin-bausch" "LOAD_EXPORT" "MOVE_ADVICE_WINDOW" "TIME_BASED" "-2h" "EARLIEST_TIME_WINDOW_START" 040ms

And Login as "super-admin-bausch" 1s 677ms

And Go to "WAREHOUSE_TAB" 765ms

And Change warehouse in schedule to: "Magazyn Bausch Health Poland" 445ms

And Wait "2" seconds 2s

When Move window by interval "-2h" 403ms

And Alert after moving is displayed "Nie można przesunąć okna czasowego - minął dopuszczalny czas na wykonanie tej akcji" 152ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

After Hooks.rollbackAddedActionAuthorities() 029ms

View Feature Move transport to archive

@rollbackSettings @deleteTransportAfterTest

Scenario Outline Check if delayed transport is moved to archived and can be restored

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 1s 606ms

And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 003ms

And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 025ms

And Set proper delay time to move order to archive after task timeout 021ms

When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 305ms

And Go to "WAREHOUSE_TAB" 582ms

And Change warehouse in schedule to: "Katowice" 1s 143ms

And Wait "60" seconds 1m

And Verify that transport window is grey 040ms

And Verify that transport is in archive 1s 575ms

Then Restore transport from archive 1s 290ms

And Verify that transport has been successfully restored 1s 399ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

After Hooks.rollbackSettings() 020ms

View Feature Move transport to archive

@deleteTransportAfterTest

Scenario Outline Check if removing a transport from the table moves it to the archive

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "dayco-admin" and set token of apiUsername "super-admin-dayco" 1s 480ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 195ms

When Go to "TRANSPORT_TABLE" 103ms

And Delete transport 20s 013ms

When Go to "ARCHIVE_TAB" 229ms

And Show "OWN_COLLECTION" 075ms

And Verify that created transport is "true" in transport table 15s 060ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

View Feature Move transport to archive

@deleteTransportAfterTest @rollbackSettings @rollbackAllCustomFieldsSettings

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Mark custom fields as not obligatory 003ms

And Login as "dayco-admin" 1s 020ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 219ms

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

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

When Go to "TRANSPORT_TABLE" 135ms

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

And Create advice by JSON file "CREATE_ADVICE_FOR_OWN_COLLECTION" as "super-admin-dayco" 641ms

And Go to "TRANSPORT_TABLE" 115ms

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

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

And Wait until transport disappear from transport table 24s 011ms

Then Go to "ARCHIVE_TAB" 288ms

And Show "OWN_COLLECTION" 072ms

And Verify that created transport is "true" in transport table 15s 034ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

After Hooks.rollbackAllCustomFieldsSettings() 079ms

After Hooks.rollbackSettings() 022ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to create new auction in transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 247ms

When Fill auction form 15s 461ms

Then Verify that the auction has been added to transport 051ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to create new auction in transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Fill auction form 15s 453ms

Then Verify that the auction has been added to transport 050ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept auction offer with minimum rate

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 219ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 086ms

When If user is login then logout 098ms

And Login as "paa1-carrier@qa.qa-test" 1s 612ms

And Go to auction offer 1s 303ms

And Accept transport with minimum rate 15s 672ms

Then Check if carrier is assigned to transport 021ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject auction offer

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 197ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 098ms

When If user is login then logout 395ms

And Login as "paa1-carrier@qa.qa-test" 1s 212ms

And Go to auction offer 1s 244ms

And Reject auction offer 15s 638ms

Then Verify that offer has been removed from transport 15s 058ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject auction offer

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 098ms

When If user is login then logout 312ms

And Login as "pskza1-carrier@qa.qa-test" 1s 632ms

And Go to auction offer 1s 230ms

And Reject auction offer 15s 680ms

Then Verify that offer has been removed from transport 15s 070ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add offer above maximum rate

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 222ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 098ms

When If user is login then logout 283ms

And Login as "paa1-carrier@qa.qa-test" 1s 143ms

And Go to auction offer 1s 306ms

And Offer prize above maximum - "20000" 192ms

Then Verify that is not possible to add offer 142ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add offer above maximum rate

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 100ms

When If user is login then logout 313ms

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

And Go to auction offer 1s 222ms

And Offer prize above maximum - "20000" 180ms

Then Verify that is not possible to add offer 138ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add auction again after previous auction end

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 195ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 079ms

And Wait till auction end 1m 58s 017ms

Then Verify that is possible to add auction 045ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add auction again after previous auction end

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 103ms

And Wait till auction end 1m 58s 016ms

Then Verify that is possible to add auction 050ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add valid offer

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 399ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 253ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 119ms

And Go to auction offer 1s 194ms

When Offer "1000" 185ms

Then Verify that offer with "1000" has been added to auction 3s 033ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add valid offer

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 096ms

And Go to auction offer 1s 194ms

When Offer "1000" 163ms

Then Verify that offer with "1000" has been added to auction 3s 031ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to revoke an offer

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 136ms

And Go to auction offer 1s 194ms

When Offer "1000" 175ms

And Verify that offer with "1000" has been added to auction 3s 030ms

Then Go to auction offer 1s 164ms

And Revoke current offer 609ms

And Verify that offer has been revoked 15s 595ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to offer more than last price

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 092ms

And Go to auction offer 1s 200ms

When Offer "1000" 182ms

And Verify that offer with "1000" has been added to auction 3s 038ms

Then Go to auction offer 1s 171ms

And Offer "1500" 159ms

And Verify that offer with "1500" has been added to auction 3s 022ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to finish active auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 092ms

And Go to auction offer 1s 183ms

When Offer "1000" 173ms

And Verify that offer with "1000" has been added to auction 3s 030ms

Then Login as "swisskrono-admin" 1s 012ms

And Go to auction details 1s 198ms

And Finish active auction 058ms

And Verify that the transport has no active auction 144ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if carrier can see current place in auction depending on the "canSeeCurrentPlaceInAuction" role

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 271ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 224ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 091ms

And Go to auction offer 1s 189ms

When Offer "1000" 175ms

Then Verify that carrier can see current place in auction depending on the "true" role 138ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if carrier can see current place in auction depending on the "canSeeCurrentPlaceInAuction" role

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 111ms

And Go to auction offer 1s 193ms

When Offer "1000" 188ms

Then Verify that carrier can see current place in auction depending on the "false" role 15s 035ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to add offer below min price

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 108ms

And Go to auction offer 1s 218ms

When Offer "300" 176ms

And Verify that carrier can't add offer to auction 029ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check carrier selection in create auction form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 201ms

And Show all transport "false" 164ms

When Go to auction form 1s 248ms

Then Verify carrier selection value "false" 039ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check carrier selection in create auction form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 019ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 263ms

And Show all transport "true" 231ms

When Go to auction form 1s 186ms

Then Verify carrier selection value "true" 036ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if auction is available to correct participants

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 199ms

When Open transport auction form 160ms

And Select all companies checkbox in transport auction form 061ms

And Unselect company "PAA2" in transport auction form 060ms

And Put transport on auction 15s 200ms

And Open transport auction history 087ms

And Open participants section in transport auction history 068ms

Then Check if unselected "PAA2" is in transport auction history as participant 15s 034ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if auction is available to correct participants

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

When Open transport auction form 180ms

And Select all companies checkbox in transport auction form 059ms

And Unselect company "PSKZA2" in transport auction form 056ms

And Put transport on auction 15s 204ms

And Open transport auction history 093ms

And Open participants section in transport auction history 060ms

Then Check if unselected "PSKZA2" is in transport auction history as participant 15s 031ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if "reason" field has validation error when passing to second carrier in auction [A-7573]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-varrocrychvald" 1s 286ms

And Set transport on auction with "1000" and "1500" by JSON file as "super-admin-varrocrychvald" 2s 095ms

And Add a bid "1500" to an auction by JSON file as "pvra1-carrier" for "super-admin-varrocrychvald" 183ms

And Add a bid "1000" to an auction by JSON file as "pvra2-carrier-2" for "super-admin-varrocrychvald" 178ms

When Login as "varrocrychvald-admin" and set token of apiUsername "super-admin-varrocrychvald" 1s 488ms

And Show all transport "true" 218ms

And Open transport auction history 807ms

And Pass transport to "2" carrier in auction history 1s 074ms

Then Verify if "REASON" is visible in pass transport modal 032ms

And Confirm pass transport to carrier in pass transport modal 054ms

And Verify that "REASON" in pass transport modal has validation error 1s 025ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

View Feature Set transport order on auction

@deleteTransportAfterTest @TmsLink=A-7038

Scenario Outline Check if carriers can see correct position in auction [A-7038]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-varrocrychvald" 101ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-varrocrychvald" 15s 238ms

And Set transport on auction with "100" and "300" by JSON file as "super-admin-varrocrychvald" 2s 087ms

And Add a bid "100" to an auction by JSON file as "pvra1-carrier" for "super-admin-varrocrychvald" 170ms

And Add a bid "200" to an auction by JSON file as "pvra2-carrier" for "super-admin-varrocrychvald" 177ms

And Add a bid "300" to an auction by JSON file as "pvra3-carrier" for "super-admin-varrocrychvald" 169ms

When Login as "pvra1-carrier" 1s 260ms

And Check if current position in auction is "1" 141ms

And If user is login then logout 566ms

And Login as "pvra2-carrier" 1s 183ms

And Check if current position in auction is "2" 148ms

And If user is login then logout 290ms

And Login as "pvra3-carrier" 1s 118ms

And Check if current position in auction is "3" 140ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature Set transport order on auction

@deleteTransportAfterTest @TMSLink=A-3739

Scenario Outline Check if transport is visible in transport table to auction participants only [A-3739]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 225ms

And Open transport auction form 190ms

And Select all companies checkbox in transport auction form 059ms

And Unselect company "PAA2" in transport auction form 065ms

And Put transport on auction 15s 185ms

When If user is login then logout 100ms

And Login as "paa1-carrier@qa.qa-test" 1s 644ms

And Show "TRANSPORT" 083ms

Then Check if transport is "visible" in table of transports 029ms

And If user is login then logout 081ms

And Login as "paa2-carrier@qa.qa-test" 1s 742ms

And Show "TRANSPORT" 054ms

And Check if transport is "not visible" in table of transports 15s 012ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 1s 423ms

And Set "transport" inputs from JSON file "CREATE_UNLOAD" "super-admin-pgf" 001ms

When Go to new transport "UNLOAD" 15s 315ms

And Fill transport form 28s 789ms

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

And Set advice window in schedule 2s 206ms

And Check is transport created in schedule and set transport id 530ms

And Go to "TRANSPORT_TABLE" 242ms

And Go to transport details "UNLOAD" 30s 412ms

Then Check are transport values equals 25s 369ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-adama" 000ms

When Go to new transport "DELIVERY" 294ms

And Fill transport form 17s 659ms

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

And Set advice window in schedule 2s 211ms

And Check is transport created in schedule and set transport id 516ms

And Go to "TRANSPORT_TABLE" 250ms

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

Then Check are transport values equals 2s 208ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-adama" 000ms

When Go to new transport "OWN_COLLECTION" 309ms

And Fill transport form 20s 166ms

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

And Set advice window in schedule 2s 178ms

And Check is transport created in schedule and set transport id 477ms

And Go to "TRANSPORT_TABLE" 197ms

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

Then Check are transport values equals 2s 182ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-hochland" 000ms

When Go to new transport "DELIVERY" 367ms

And Fill transport form 40s 884ms

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

And Set advice window in schedule 2s 160ms

And Check is transport created in schedule and set transport id 575ms

And Go to "TRANSPORT_TABLE" 259ms

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

Then Check are transport values equals 21s 388ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_CISTERN_DELIVERY" "super-admin-hochland" 000ms

When Go to new transport "CISTERN_DELIVERY" 430ms

And Fill transport form 43s 583ms

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

And Set advice window in schedule 2s 199ms

And Check is transport created in schedule and set transport id 595ms

And Go to "TRANSPORT_TABLE" 215ms

And Go to transport details "CISTERN_DELIVERY" 2s 418ms

Then Check are transport values equals 8s 396ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_CISTERN_COLLECTION" "super-admin-hochland" 000ms

When Go to new transport "CISTERN_COLLECTION" 355ms

And Fill transport form 30s 508ms

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

And Set advice window in schedule 2s 232ms

And Check is transport created in schedule and set transport id 561ms

And Go to "TRANSPORT_TABLE" 220ms

And Go to transport details "CISTERN_COLLECTION" 2s 401ms

Then Check are transport values equals 23s 383ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-hochland" 000ms

When Go to new transport "OWN_COLLECTION" 373ms

And Fill transport form 34s 953ms

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

And Set advice window in schedule 2s 174ms

And Check is transport created in schedule and set transport id 550ms

And Go to "TRANSPORT_TABLE" 197ms

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

Then Check are transport values equals 21s 389ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 000ms

When Go to new transport "OWN_COLLECTION_POWDER_FACTORY" 390ms

And Fill transport form 35s 019ms

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

And Set advice window in schedule 2s 199ms

And Check is transport created in schedule and set transport id 523ms

And Go to "TRANSPORT_TABLE" 200ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 2s 446ms

Then Check are transport values equals 6s 314ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_EXPORT" "super-admin-hochland" 000ms

When Go to new transport "EXPORT" 410ms

And Fill transport form 42s 828ms

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

And Set advice window in schedule 2s 176ms

And Check is transport created in schedule and set transport id 650ms

And Go to "TRANSPORT_TABLE" 200ms

And Go to transport details "EXPORT" 3s 549ms

Then Check are transport values equals 6s 379ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-skd" 000ms

When Go to new transport "DELIVERY" 15s 285ms

And Fill transport form 30s 494ms

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

And Set advice window in schedule 2s 172ms

And Check is transport created in schedule and set transport id 674ms

And Go to "TRANSPORT_TABLE" 252ms

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

Then Check are transport values equals 38s 396ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-lantmannen" 000ms

When Go to new transport "DELIVERY" 327ms

And Fill transport form 40s 147ms

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

And Set advice window in schedule 2s 156ms

And Check is transport created in schedule and set transport id 604ms

And Go to "TRANSPORT_TABLE" 184ms

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

Then Check are transport values equals 21s 366ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_LOAD" "super-admin-lantmannen" 000ms

When Go to new transport "LOAD" 317ms

And Fill transport form 40s 133ms

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

And Set advice window in schedule 2s 174ms

And Check is transport created in schedule and set transport id 532ms

And Go to "TRANSPORT_TABLE" 230ms

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

Then Check are transport values equals 21s 354ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-keeeper" 000ms

When Go to new transport "UNLOAD" 320ms

And Fill transport form 39s 738ms

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

And Set advice window in schedule 2s 148ms

And Check is transport created in schedule and set transport id 585ms

And Go to "TRANSPORT_TABLE" 200ms

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

Then Check are transport values equals 23s 386ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set "transport" inputs from JSON file "CREATE_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 000ms

When Go to new transport "TANKER_GRANULATE_DELIVERY" 329ms

And Fill transport form 39s 675ms

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

And Set advice window in schedule 2s 168ms

And Check is transport created in schedule and set transport id 521ms

And Go to "TRANSPORT_TABLE" 198ms

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

Then Check are transport values equals 23s 426ms

Hooks

After Hooks.deleteTransportAfterTest() 143ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 184ms

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-alrec" 000ms

When Go to new transport "DELIVERY" 317ms

And Fill transport form 24s 948ms

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

And Set advice window in schedule 2s 170ms

And Check is transport created in schedule and set transport id 558ms

And Go to "TRANSPORT_TABLE" 195ms

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

Then Check are transport values equals 19s 269ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "WEIGHING" 353ms

And Fill "transport" form "CREATE_WEIGHING" by "super-admin-hochland" 13s 763ms

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

And Show all transport "false" 160ms

And Go to "TRANSPORT_TABLE" 141ms

And Go to transport details "WEIGHING" 2s 398ms

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "TRANSPORT" 367ms

And Fill "transport" form "CREATE_TRANSPORT" by "super-admin-adama" 24s 681ms

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

And Show all transport "false" 164ms

And Go to "TRANSPORT_TABLE" 154ms

And Go to transport details "TRANSPORT" 2s 440ms

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "CONTAINER" 323ms

And Fill "transport" form "CREATE_CONTAINER" by "super-admin-adama" 9s 180ms

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

And Show all transport "false" 162ms

And Go to "TRANSPORT_TABLE" 153ms

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

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "TRANSFER_BETWEEN_WAREHOUSES" 345ms

And Fill "transport" form "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by "super-admin-hochland" 10s 914ms

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

And Show all transport "false" 158ms

And Go to "TRANSPORT_TABLE" 150ms

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

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "DELIVERY" 342ms

And Fill "transport" form "CREATE_DELIVERY" by "super-admin-piast" 20s 439ms

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

And Show all transport "false" 161ms

And Go to "TRANSPORT_TABLE" 153ms

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

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "LOAD" 380ms

And Fill "transport" form "CREATE_LOAD" by "super-admin-piast" 24s 221ms

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

And Show all transport "false" 160ms

And Go to "TRANSPORT_TABLE" 161ms

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

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 062ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "LOAD" 286ms

And Fill "transport" form "CREATE_LOAD" by "super-admin-keeeper" 22s 612ms

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

And Show all transport "false" 162ms

And Go to "TRANSPORT_TABLE" 138ms

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

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "CONTAINER" 297ms

And Fill "transport" form "CREATE_CONTAINER" by "super-admin-keeeper" 22s 606ms

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

And Show all transport "false" 161ms

And Go to "TRANSPORT_TABLE" 163ms

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

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "SMALLS_IMPORT" 435ms

And Fill "transport" form "CREATE_SMALLS_IMPORT" by "super-admin-skz" 17s 759ms

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

And Show all transport "false" 162ms

And Go to "TRANSPORT_TABLE" 162ms

And Go to transport details "SMALLS_IMPORT" 2s 454ms

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "SMALLS_EXPORT" 445ms

And Fill "transport" form "CREATE_SMALLS_EXPORT" by "super-admin-skz" 34s 298ms

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

And Show all transport "false" 161ms

And Go to "TRANSPORT_TABLE" 159ms

And Go to transport details "SMALLS_EXPORT" 2s 427ms

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 142ms

When Go to new transport "TRANSPORT_ORDER" 421ms

And Fill "transport" form "CREATE_TRANSPORT_ORDER" by "super-admin-alrec" 21s 840ms

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

And Show all transport "true" 249ms

And Go to "TRANSPORT_TABLE" 154ms

And Go to transport details "TRANSPORT_ORDER" 2s 469ms

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

When Go to new transport "TRANSPORT" 379ms

And Fill "transport" form "CREATE_TRANSPORT_ORDER_WITHOUT_WAREHOUSES" by "super-admin-adama" 35s 623ms

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

And Show all transport "false" 160ms

And Go to "TRANSPORT_TABLE" 152ms

And Go to transport details "TRANSPORT" 2s 458ms

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 173ms

When Go to new transport "INBOUND" 380ms

And Fill "transport" form "CREATE_INBOUND_WITHOUT_WAREHOUSES" by "super-admin-alrec" 38s 894ms

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

And Show all transport "true" 235ms

And Go to "TRANSPORT_TABLE" 130ms

And Go to transport details "INBOUND" 2s 453ms

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 063ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 767ms

When Go to new transport "EXTERNAL_DELIVERY" 372ms

And Fill "transport" form "CREATE_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" by "super-admin-farmacol" 51s 632ms

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

And Show all transport "false" 160ms

And Go to "TRANSPORT_TABLE" 140ms

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

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "dfa1-supplier" and set token of apiUsername "dfa1-supplier" 1s 843ms

When Go to new transport "EXTERNAL_DELIVERY" 15s 251ms

And Fill "transport" form "CREATE_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" by "dfa1-supplier" 45s 086ms

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

And Show all transport "false" 158ms

And Go to "TRANSPORT_TABLE" 134ms

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

And Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 1s 068ms

And Set "transport" inputs from JSON file "EDIT_UNLOAD" "super-admin-pgf" 000ms

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

And Show all transport "false" 167ms

When Go to transport details "UNLOAD" 30s 498ms

And Fill transport form 32s 507ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 106ms

And Go to transport details "UNLOAD" 30s 479ms

Then Check are transport values equals 6s 276ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 126ms

And Set "transport" inputs from JSON file "EDIT_TRANSPORT" "super-admin-adama" 000ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 224ms

And Show all transport "false" 160ms

When Go to transport details "TRANSPORT" 2s 445ms

And Fill transport form 10s 236ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 093ms

And Go to transport details "TRANSPORT" 2s 465ms

Then Check are transport values equals 4s 134ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 173ms

And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-adama" 000ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 173ms

And Show all transport "false" 157ms

When Go to transport details "CONTAINER" 2s 377ms

And Fill transport form 4s 707ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 075ms

And Go to transport details "CONTAINER" 2s 396ms

Then Check are transport values equals 041ms

Hooks

After Hooks.deleteTransportAfterTest() 052ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 143ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-adama" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 339ms

And Show all transport "false" 162ms

When Go to transport details "DELIVERY" 2s 364ms

And Fill transport form 13s 673ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 086ms

And Go to transport details "DELIVERY" 2s 391ms

Then Check are transport values equals 2s 152ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 134ms

And Set "transport" inputs from JSON file "EDIT_OWN_COLLECTION" "super-admin-adama" 000ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-adama" 1s 309ms

And Show all transport "false" 160ms

When Go to transport details "OWN_COLLECTION" 2s 381ms

And Fill transport form 23s 698ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 100ms

And Go to transport details "OWN_COLLECTION" 2s 328ms

Then Check are transport values equals 4s 225ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 463ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 383ms

And Show all transport "false" 165ms

When Go to transport details "DELIVERY" 2s 766ms

And Fill transport form 38s 055ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 091ms

And Go to transport details "DELIVERY" 2s 407ms

Then Check are transport values equals 12s 536ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 428ms

And Set "transport" inputs from JSON file "EDIT_OWN_COLLECTION" "super-admin-hochland" 000ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 329ms

And Show all transport "false" 158ms

When Go to transport details "OWN_COLLECTION" 2s 670ms

And Fill transport form 38s 682ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 116ms

And Go to transport details "OWN_COLLECTION" 2s 417ms

Then Check are transport values equals 8s 397ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 436ms

And Set "transport" inputs from JSON file "EDIT_EXPORT" "super-admin-hochland" 000ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 356ms

And Show all transport "false" 159ms

When Go to transport details "EXPORT" 3s 674ms

And Fill transport form 50s 002ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 092ms

And Go to transport details "EXPORT" 2s 489ms

Then Check are transport values equals 10s 491ms

Hooks

After Hooks.deleteTransportAfterTest() 142ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 473ms

And Set "transport" inputs from JSON file "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 191ms

And Show all transport "false" 160ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 693ms

And Fill transport form 36s 053ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 116ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 460ms

Then Check are transport values equals 12s 427ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 425ms

And Set "transport" inputs from JSON file "EDIT_CISTERN_DELIVERY" "super-admin-hochland" 000ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 295ms

And Show all transport "false" 163ms

When Go to transport details "CISTERN_DELIVERY" 2s 553ms

And Fill transport form 29s 410ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 125ms

And Go to transport details "CISTERN_DELIVERY" 2s 407ms

Then Check are transport values equals 8s 321ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 367ms

And Set "transport" inputs from JSON file "EDIT_CISTERN_COLLECTION" "super-admin-hochland" 000ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 1s 286ms

And Show all transport "false" 160ms

When Go to transport details "CISTERN_COLLECTION" 2s 476ms

And Fill transport form 27s 914ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 106ms

And Go to transport details "CISTERN_COLLECTION" 2s 392ms

Then Check are transport values equals 8s 300ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 449ms

And Set "transport" inputs from JSON file "EDIT_WEIGHING" "super-admin-hochland" 000ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 234ms

And Show all transport "false" 160ms

When Go to transport details "WEIGHING" 2s 389ms

And Fill transport form 14s 529ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 078ms

And Go to transport details "WEIGHING" 2s 325ms

Then Check are transport values equals 4s 173ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 405ms

And Set "transport" inputs from JSON file "EDIT_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 000ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 366ms

And Show all transport "false" 158ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 2s 567ms

And Fill transport form 37s 259ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 093ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 2s 428ms

Then Check are transport values equals 8s 362ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 1s 078ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-skd" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 237ms

And Show all transport "false" 167ms

When Go to transport details "DELIVERY" 30s 372ms

And Fill transport form 27s 795ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 157ms

And Go to transport details "DELIVERY" 30s 361ms

Then Check are transport values equals 4s 200ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 237ms

And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-piast" 000ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 214ms

And Show all transport "false" 163ms

When Go to transport details "LOAD" 2s 722ms

And Fill transport form 57s 145ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 093ms

And Go to transport details "LOAD" 2s 490ms

Then Check are transport values equals 24s 735ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 108ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-lantmannen" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 312ms

And Show all transport "false" 160ms

When Go to transport details "DELIVERY" 2s 374ms

And Fill transport form 16s 442ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 103ms

And Go to transport details "DELIVERY" 2s 340ms

Then Check are transport values equals 061ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 102ms

And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-lantmannen" 000ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 307ms

And Show all transport "false" 160ms

When Go to transport details "LOAD" 2s 362ms

And Fill transport form 30s 208ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 085ms

And Go to transport details "LOAD" 2s 323ms

Then Check are transport values equals 4s 253ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 174ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-keeeper" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 291ms

And Show all transport "false" 159ms

When Go to transport details "UNLOAD" 2s 403ms

And Fill transport form 38s 491ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 107ms

And Go to transport details "UNLOAD" 2s 379ms

Then Check are transport values equals 8s 391ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 130ms

And Set "transport" inputs from JSON file "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 000ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 326ms

And Show all transport "false" 158ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 428ms

And Fill transport form 38s 528ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 134ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 376ms

Then Check are transport values equals 8s 366ms

Hooks

After Hooks.deleteTransportAfterTest() 132ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 155ms

And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper" 000ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 209ms

And Show all transport "false" 161ms

When Go to transport details "LOAD" 2s 383ms

And Fill transport form 25s 964ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 124ms

And Go to transport details "LOAD" 2s 379ms

Then Check are transport values equals 4s 193ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 193ms

And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-keeeper" 000ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 196ms

And Show all transport "false" 159ms

When Go to transport details "CONTAINER" 2s 401ms

And Fill transport form 25s 973ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 136ms

And Go to transport details "CONTAINER" 2s 327ms

Then Check are transport values equals 4s 218ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 265ms

And Set "transport" inputs from JSON file "EDIT_SMALLS_EXPORT" "super-admin-skz" 000ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 227ms

And Show all transport "false" 159ms

When Go to transport details "SMALLS_EXPORT" 2s 522ms

And Fill transport form 32s 910ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 149ms

And Go to transport details "SMALLS_EXPORT" 2s 418ms

Then Check are transport values equals 8s 329ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 215ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-alrec" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 332ms

And Show all transport "true" 224ms

When Go to transport details "DELIVERY" 2s 370ms

And Fill transport form 21s 725ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 141ms

And Go to transport details "DELIVERY" 2s 329ms

Then Check are transport values equals 2s 199ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 175ms

And Set "transport" inputs from JSON file "EDIT_TRANSPORT_ORDER" "super-admin-alrec" 000ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 218ms

And Show all transport "true" 243ms

When Go to transport details "TRANSPORT_ORDER" 2s 457ms

And Fill transport form 26s 682ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 124ms

And Go to transport details "TRANSPORT_ORDER" 2s 431ms

Then Check are transport values equals 2s 200ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-warehouseman" and set token of apiUsername "super-admin-keeeper" 1s 759ms

And Set "transport" inputs from JSON file "EDIT_CONTAINER_WAREHOUSEMAN_CUSTOMFIELDS" "super-admin-keeeper" 000ms

And Create transport "CREATE_CONTAINER_KEEEPER_WAIMEA" by JSON file as "super-admin-keeeper" 1s 195ms

And Show all transport "false" 157ms

When Go to transport details "CONTAINER" 2s 398ms

And Fill transport form 10s 223ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 162ms

And Go to transport details "CONTAINER" 2s 368ms

Then Check are transport values equals 4s 121ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 405ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 393ms

And Show all transport "false" 159ms

When Delete transport 17s 940ms

Then Transport not displayed in table of transports 15s 017ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 294ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 200ms

And Show all transport "false" 162ms

When Delete transport 17s 230ms

Then Transport not displayed in table of transports 15s 021ms

Hooks

After Hooks.deleteTransportAfterTest() 058ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 139ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 310ms

And Show all transport "false" 158ms

When Delete transport 17s 094ms

Then Transport not displayed in table of transports 15s 044ms

Hooks

After Hooks.deleteTransportAfterTest() 10s 225ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 202ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 184ms

And Show all transport "false" 160ms

When Delete transport 17s 043ms

Then Transport not displayed in table of transports 15s 050ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 268ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 245ms

And Show all transport "false" 160ms

When Delete transport 17s 213ms

Then Transport not displayed in table of transports 15s 053ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 292ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 228ms

And Show all transport "false" 163ms

When Delete transport 17s 735ms

Then Transport not displayed in table of transports 15s 072ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 171ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 300ms

And Show all transport "true" 241ms

When Delete transport 19s 177ms

Then Transport not displayed in table of transports 15s 047ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 184ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 271ms

And Show all transport "true" 225ms

When Delete transport 17s 149ms

Then Transport not displayed in table of transports 15s 045ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 467ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 424ms

And Show all transport "false" 174ms

When Go to transport details "DELIVERY" 2s 726ms

And Fill transport form 37s 922ms

And Click "save-transport" save button 1s 217ms

And Click cancel button in transport form 079ms

And Go to transport details "DELIVERY" 2s 383ms

Then Check are transport values equals 12s 534ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 440ms

And Set "transport" inputs from JSON file "EDIT_OWN_COLLECTION" "super-admin-hochland" 001ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 322ms

And Show all transport "false" 216ms

When Go to transport details "OWN_COLLECTION" 2s 665ms

And Fill transport form 38s 646ms

And Click "save-transport" save button 1s 231ms

And Click cancel button in transport form 093ms

And Go to transport details "OWN_COLLECTION" 2s 361ms

Then Check are transport values equals 8s 366ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

View Feature Crud Transport

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

Scenario Outline Check if firstPossibleStart algorithm works properly when creating transport advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 148ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 182ms

And Create gray windows "CREATE_GRAY_WINDOW_MWG" on "PRZESYŁKI DROBNICOWE" in "Magazyn Wyrobów Gotowych" as "super-admin-keeeper" 185ms

And If user is login then logout 301ms

Then Login as "dka1-supplier" 1s 683ms

And Click button advice in transport table "LOAD" 122ms

And Check if moved to first possible start date in schedule 436ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

After Hooks.deleteAllGrayWindowsAfterTest() 1m 30s 492ms

View Feature Crud Transport

@deleteTransportAfterTest @deleteAddressAfterTest

Scenario Outline Check if it is possible to create transport with new address [A-7158]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 101ms

And Set "transport" inputs from JSON file "CREATE_LOAD_WITH_NEW_ADDRESS" "super-admin-piast" 000ms

When Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 253ms

Then Go to new transport "LOAD" 355ms

And Fill transport form 23s 354ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 130ms

And Go to "COMPANIES_TAB" 438ms

And Go to company "Dostawca Piast Automat 1" details 201ms

And Check if new address with "Adresat" is visible in company details 127ms

And Go to "TRANSPORT_TABLE" 313ms

And Go to transport details "LOAD" 2s 605ms

Hooks

After Hooks.deleteTransportAfterTest() 054ms

After Hooks.deleteAddressAfterTest() 028ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 207ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 186ms

When Go to "TRANSPORT_TABLE" 117ms

And Show all transport types 1s 031ms

And Verify that transport has "0" files 036ms

Then Add file to transport by API 500ms

And Verify that transport has "1" files 596ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 090ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 170ms

When Go to "TRANSPORT_TABLE" 127ms

And Show all transport types 1s 033ms

And Verify that transport has "0" files 032ms

Then Add file to transport by API 240ms

And Verify that transport has "1" files 549ms

Hooks

After Hooks.deleteTransportAfterTest() 063ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 316ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 445ms

When Go to "TRANSPORT_TABLE" 128ms

And Show all transport types 1s 046ms

And Verify that transport has "0" files 036ms

Then Add file to transport by API 262ms

And Verify that transport has "1" files 254ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 048ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 190ms

When Go to "TRANSPORT_TABLE" 109ms

And Show all transport types 1s 032ms

And Verify that transport has "0" files 037ms

Then Add file to transport by API 247ms

And Verify that transport has "1" files 924ms

Hooks

After Hooks.deleteTransportAfterTest() 055ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 031ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 177ms

And Delete transport 17s 736ms

When Go to "ARCHIVE_TAB" 219ms

And Show "DELIVERY" 055ms

And Verify that transport has "0" files 1s 195ms

Then Add file to transport 173ms

And Verify that transport has "1" files 393ms

Hooks

After Hooks.deleteTransportAfterTest() 057ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 182ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 203ms

And Delete transport 17s 384ms

When Go to "ARCHIVE_TAB" 270ms

And Show "LOAD" 425ms

And Verify that transport has "0" files 1s 114ms

Then Add file to transport 181ms

And Verify that transport has "1" files 451ms

Hooks

After Hooks.deleteTransportAfterTest() 053ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 392ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 401ms

And Delete transport 18s 016ms

When Go to "ARCHIVE_TAB" 263ms

And Show "DELIVERY" 065ms

And Verify that transport has "0" files 1s 107ms

Then Add file to transport 166ms

And Verify that transport has "1" files 411ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 133ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 186ms

And Delete transport 17s 600ms

When Go to "ARCHIVE_TAB" 241ms

And Show "CONTAINER" 090ms

And Verify that transport has "0" files 1s 089ms

Then Add file to transport 161ms

And Verify that transport has "1" files 328ms

Hooks

After Hooks.deleteTransportAfterTest() 062ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check that the file is added to the transport after carrier acceptance when the transport has been passed to the carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 092ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 15s 168ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 122ms

And Accept transferred transport by Api 082ms

And Login as "paa1-carrier@qa.qa-test" 1s 314ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 15s 565ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check that the file is automatically added to the transport after the transport has been passed to the carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 394ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 212ms

And Transfer transport to carrier by JSON file "super-admin-adama" "false" confirmation 102ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 911ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check that the file is added to the transport after winning the auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 095ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 184ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 107ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 269ms

And Login as "paa1-carrier@qa.qa-test" 1s 248ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 15s 980ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

View Feature Transport files

@deleteTransportAfterTest @FLAKY

Scenario Outline Check if it CMR documents are added to transport after creation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 237ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 215ms

When Go to "TRANSPORT_TABLE" 131ms

And Show all transport "true" 238ms

Then Verify that transport has "1" CMR file 1s 233ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

View Feature Transport files

@deleteTransportAfterTest @FLAKY

Scenario Outline Check if it CMR documents are added to transport after creation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 019ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 330ms

When Go to "TRANSPORT_TABLE" 111ms

And Show all transport "true" 214ms

Then Verify that transport has "2" CMR file 1s 228ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it CMR document can be downloaded

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 022ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 259ms

When Go to "TRANSPORT_TABLE" 121ms

And Show all transport "true" 219ms

Then Verify that "CMR" document can be downloaded 17s 307ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it CMR document can be downloaded in archive

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 081ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 250ms

And Show all transport "true" 231ms

And Delete transport 17s 194ms

When Go to "ARCHIVE_TAB" 253ms

And Show "TRANSPORT_ORDER" 063ms

Then Verify that "CMR" document can be downloaded 16s 471ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 416ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 381ms

And Show all transport "false" 158ms

When Find transport pencil button in transports table 1s 264ms

And Click pencil and move transport to next day in schedule 16s 881ms

Then Check if transport is in new location in schedule 2s 105ms

And Check if dates in transport form are correct 3s 479ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 169ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 301ms

And Show all transport "false" 199ms

When Find transport pencil button in transports table 1s 253ms

And Click pencil and move transport to next day in schedule 16s 763ms

Then Check if transport is in new location in schedule 2s 114ms

And Check if dates in transport form are correct 3s 329ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 093ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 371ms

And Show all transport "false" 158ms

When Find transport pencil button in transports table 1s 237ms

And Click pencil and move transport to next day in schedule 17s 237ms

Then Check if transport is in new location in schedule 2s 128ms

And Check if dates in transport form are correct 3s 350ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 179ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 324ms

And Show all transport "false" 163ms

When Find transport pencil button in transports table 1s 250ms

And Click pencil and move transport to next day in schedule 16s 300ms

Then Check if transport is in new location in schedule 2s 103ms

And Check if dates in transport form are correct 3s 401ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 189ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 324ms

And Show all transport "false" 159ms

When Find transport pencil button in transports table 1s 266ms

And Click pencil and move transport to next day in schedule 16s 340ms

Then Check if transport is in new location in schedule 2s 115ms

And Check if dates in transport form are correct 3s 358ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 148ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-alrec" 1s 378ms

And Show all transport "true" 237ms

When Find transport pencil button in transports table 1s 236ms

And Click pencil and move transport to next day in schedule 16s 733ms

Then Check if transport is in new location in schedule 2s 117ms

And Check if dates in transport form are correct 3s 424ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to add advice by advice button in transport table and edit transport by pencil

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 222ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 213ms

And Set "advice" inputs from JSON file "ADVICE_DELIVERY" "super-admin-piast" 001ms

When Show all transport types 1s 040ms

And Click button advice in transport table "DELIVERY" 104ms

And Set advice window in schedule 2s 620ms

And Fill advice form 10s 570ms

And Click advice save button and wait for advice form to disappear 10s 176ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='save'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.2KxY4c}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 27f8686fbbe216e38127d63861020cbd
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:217)
	at Pages.Transport.AdviceFormPage.confirm(AdviceFormPage.java:27)
	at CucumberTests.Transport.AdviceTransport.clickAdviceSaveButtonAndWaitForAdviceFormToDisappear(AdviceTransport.java:179)
	at ✽.Click advice save button and wait for advice form to disappear(file:Features/Atom/Transport/PencilEdition.feature:30)

And Go to "TRANSPORT_TABLE" 000ms

And Find transport pencil button in transports table 000ms

And Click pencil and move transport to next day in schedule 000ms

Then Check if transport is in new location in schedule 000ms

And Check if dates in transport form are correct 000ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 480ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 348ms

And Show all transport "false" 159ms

When Find transport pencil button in transports table 1s 263ms

And Click pencil and move transport to next day in schedule 16s 351ms

And Move advice window "3" 1s 344ms

Then Check if advice window is in new location 019ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 163ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 362ms

And Show all transport "false" 162ms

When Find transport pencil button in transports table 1s 225ms

And Click pencil and move transport to next day in schedule 16s 806ms

And Move advice window "3" 1s 366ms

Then Check if advice window is in new location 028ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 062ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 267ms

And Show all transport "false" 164ms

When Find transport pencil button in transports table 1s 230ms

And Click pencil and move transport to next day in schedule 17s 179ms

And Move advice window "3" 1s 399ms

Then Check if advice window is in new location 022ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 211ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 315ms

And Show all transport "false" 156ms

When Find transport pencil button in transports table 1s 265ms

And Click pencil and move transport to next day in schedule 16s 333ms

And Move advice window "3" 1s 305ms

Then Check if advice window is in new location 023ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 050ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 345ms

And Show all transport "false" 164ms

When Find transport pencil button in transports table 1s 210ms

And Click pencil and move transport to next day in schedule 16s 288ms

And Move advice window "3" 1s 334ms

Then Check if advice window is in new location 020ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 177ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 312ms

And Show all transport "true" 230ms

When Find transport pencil button in transports table 1s 235ms

And Click pencil and move transport to next day in schedule 16s 671ms

And Move advice window "3" 1s 354ms

Then Check if advice window is in new location 023ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report custom fields are visible in proper section

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 454ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 476ms

And Go to transport details "DELIVERY" 2s 756ms

When Open section: "discrepancy-report-panel" 1s 058ms

Then Verify that no discrepancies found label is visible in discrepancy report section 065ms

And Select "NIE" in the "insp.-accord.-with-ins." 2s 439ms

And Verify that discrepancy report custom fields are visible in discrepancy report section 092ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section will open with validation errors

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 320ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 390ms

And Go to transport details "DELIVERY" 2s 778ms

And Fill transport form 37s 946ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 136ms

When Go to transport details "DELIVERY" 2s 459ms

Then Select "NIE" in the "insp.-accord.-with-ins." 2s 422ms

And Click "save-transport" save button 702ms

And Wait "2" seconds 2s

And Verify that discrepancy report section is open 029ms

And Verify that discrepancy report section "not contains" validation errors 017ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 413ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 365ms

When Go to transport details "DELIVERY" 2s 756ms

Then Verify that discrepancy report section is available 028ms

And Open section: "discrepancy-report-panel" 1s 073ms

And Verify that generate new discrepancy report button is visible 037ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 307ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 309ms

When Go to transport details "OWN_COLLECTION" 2s 639ms

Then Verify that discrepancy report section is available 019ms

And Open section: "discrepancy-report-panel" 1s 071ms

And Verify that generate new discrepancy report button is visible 030ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 295ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 309ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 2s 512ms

Then Verify that discrepancy report section is available 021ms

And Open section: "discrepancy-report-panel" 1s 056ms

And Verify that generate new discrepancy report button is visible 022ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 307ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 352ms

When Go to transport details "EXPORT" 3s 616ms

Then Verify that discrepancy report section is available 018ms

And Open section: "discrepancy-report-panel" 1s 069ms

And Verify that generate new discrepancy report button is visible 023ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 290ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 193ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 2s 695ms

Then Verify that discrepancy report section is available 019ms

And Open section: "discrepancy-report-panel" 1s 063ms

And Verify that generate new discrepancy report button is visible 030ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is not available

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 321ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 298ms

When Go to transport details "CISTERN_DELIVERY" 2s 509ms

Then Verify that discrepancy report section is not available 15s 051ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is not available

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 389ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 1s 300ms

When Go to transport details "CISTERN_COLLECTION" 2s 510ms

Then Verify that discrepancy report section is not available 15s 046ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is not available

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 421ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 219ms

When Go to transport details "WEIGHING" 2s 381ms

Then Verify that discrepancy report section is not available 15s 036ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report is properly generated

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 424ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 429ms

When Go to "TRANSPORT_TABLE" 118ms

And Go to transport details "DELIVERY" 2s 709ms

And Change filled value in details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 515ms

And Change filled value in details "unloaded-stere" "text" "3" "0" 1s 322ms

And Open section: "discrepancy-report-panel" 1s 071ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Fill transport form 37s 909ms

And Fill discrepancy report section without closing the form 19s 507ms

And Generate discrepancy report 1s 213ms

And Download discrepancy report 136ms

Then Verify that discrepancy report file has correct values 15s 166ms

Error message

java.nio.file.NoSuchFileException: /home/teamcity/Downloads/75_2021_1.pdf
	at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
	at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
	at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)
	at java.nio.file.Files.newOutputStream(Files.java:216)
	at java.nio.file.Files.copy(Files.java:3016)
	at Utils.FileUtil.checkIfFileExist(FileUtil.java:45)
	at Utils.FileUtil.getPdfFileText(FileUtil.java:28)
	at CucumberTests.Transport.TransportFormTest.verifyThatDiscrepancyReportFileHasCorrectValues(TransportFormTest.java:260)
	at ✽.Verify that discrepancy report file has correct values(file:Features/Atom/Transport/TransportForm/DiscrepancyReport.feature:76)

Hooks

After Hooks.deleteTransportAfterTest() 130ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if edited discrepancy report is properly generated

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 446ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 460ms

When Go to "TRANSPORT_TABLE" 145ms

And Go to transport details "DELIVERY" 2s 755ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 000ms

And Fill transport form 37s 924ms

And Open section: "discrepancy-report-panel" 1s 064ms

And Fill discrepancy report section without closing the form 19s 413ms

And Generate discrepancy report 16s 226ms

And Download discrepancy report 164ms

And Verify that discrepancy report file has correct values 15s 130ms

Error message

java.nio.file.NoSuchFileException: /home/teamcity/Downloads/76_2021_1.pdf
	at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
	at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
	at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)
	at java.nio.file.Files.newOutputStream(Files.java:216)
	at java.nio.file.Files.copy(Files.java:3016)
	at Utils.FileUtil.checkIfFileExist(FileUtil.java:45)
	at Utils.FileUtil.getPdfFileText(FileUtil.java:28)
	at CucumberTests.Transport.TransportFormTest.verifyThatDiscrepancyReportFileHasCorrectValues(TransportFormTest.java:260)
	at ✽.Verify that discrepancy report file has correct values(file:Features/Atom/Transport/TransportForm/DiscrepancyReport.feature:93)

And Fill edited discrepancy report section 000ms

And Generate edited discrepancy report 000ms

And Download discrepancy report 000ms

Then Verify that discrepancy report file has correct values 000ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest @TmsLink=A-7987

Scenario Outline Check if it is not possible to confirm next status without filling required fields in status modal [A-7987]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 492ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 405ms

When Go to "TRANSPORT_TABLE" 128ms

And Confirm statuses until reach "during-unload" 8s 589ms

Then Check if confirm status modal appeared on confirming next status in transport "table" 322ms

And Change filled value in details "insp.-accord.-with-ins." "select" "NIE" "0" 3s 582ms

And Check if next status is not possible to confirm in status confirmation modal 095ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackTransportTypeSettings

Scenario Outline Check if added step is saved with transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 093ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 040ms

And Get "LOAD" settings from "piast" 034ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "false" 083ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-piast" 1s 219ms

And Login as "piast-admin" 1s 428ms

And Go to "TRANSPORT_TABLE" 212ms

When Go to transport details "LOAD" 2s 699ms

And Add step "unload" 108ms

And Change filled value in details "company-step-2" "autocomplete" "DPA2" "0" 6s 524ms

And Change filled value in details "recipient-step-2" "autocomplete" "Testowy" "0" 6s 504ms

Then Click "save-transport-and-close" save button and wait for form to disappear 30s 129ms

And Go to transport details "LOAD" 2s 594ms

And Verify that transport has "3" steps 014ms

Hooks

After Hooks.deleteTransportAfterTest() 055ms

After Hooks.rollbackTransportTypeSettings() 046ms

After Hooks.rollbackAddedActionAuthorities() 029ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest

Scenario Outline Check if supplier can't edit time range for load and unload step

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "pskza1-carrier-2@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 945ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 233ms

When Go to "TRANSPORT_TABLE" 129ms

And Go to transport details "SMALLS_IMPORT" 17s 128ms

Then Verify that user can't edit time range for load and unload 15s 019ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest

Scenario Outline Check if sum of number of pallets in transport form is correct

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 090ms

And Create transport "CREATE_DELIVERY_TWO_LOADS" by JSON file as "super-admin-neuca" 1s 343ms

And Login as "neuca-admin" 881ms

And Go to "TRANSPORT_TABLE" 214ms

And Show all transport types 1s 165ms

When Go to transport details "DELIVERY" 2s 418ms

Then Check if sum of number of pallets in transport form in "load" steps is correct 061ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest

Scenario Outline Check if sum of number of pallets in transport form is correct

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-hochland" 094ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 352ms

And Login as "hochland-admin" 1s 413ms

And Go to "TRANSPORT_TABLE" 137ms

And Show all transport types 1s 053ms

When Go to transport details "EXPORT" 3s 587ms

Then Check if sum of number of pallets in transport form in "unload" steps is correct 057ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackTransportTypeSettings

Scenario Outline Check if sum of number of pallets check message is displayed in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-neuca" 096ms

And Get "DELIVERY" settings from "neuca" 035ms

And Set transportType settings with values: "quantitySumCheckValue", "33" 083ms

And Login as "neuca-admin" 919ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 15s 347ms

When Go to "TRANSPORT_TABLE" 297ms

And Go to transport details "DELIVERY" 2s 573ms

And Set number of pallets in "load" step in transport - "32" 115ms

And Check if number of pallets check message is not visible in transport form 15s 023ms

And Set number of pallets in "load" step in transport - "34" 099ms

Then Check if number of pallets check message is visible in transport form 024ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

After Hooks.rollbackTransportTypeSettings() 093ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackTransportTypeSettings

Scenario Outline Check if time range fields are required in new warehouse step

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-farmacol" 096ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 040ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 062ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 052ms

And Login as "farmacol-admin" 1s 616ms

And Go to new transport "EXTERNAL_DELIVERY" 325ms

And Add step "unload" 104ms

And Click "save-transport-and-close" save button 695ms

Then Verify that "time-range-from-date-2" has validation error 1s 025ms

Then Verify that "time-range-to-date-2" has validation error 1s 027ms

And Change filled value in details "time-range-from-date-2" "date" "" "0" 3s 292ms

And Click "save-transport-and-close" save button 694ms

And Verify that "time-range-from-date-2" has no validation error 015ms

And Verify that "time-range-to-date-2" has no validation error 014ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.rollbackTransportTypeSettings() 051ms

After Hooks.rollbackAddedActionAuthorities() 032ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities

Scenario Outline Check if new step is added in proper column in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-piast" 096ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_LOAD_STEP_FROM_UNLOAD" "ACTIVE" 041ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 211ms

When Login as "piast-admin" 1s 437ms

And Go to transport details "LOAD" 2s 827ms

And Set "transport" inputs from JSON file "PIAST_LOAD_ADD_UNLOAD_STEP" "super-admin-piast" 000ms

And Add step "unload" 107ms

And Fill step data 15s 010ms

And Set "transport" inputs from JSON file "PIAST_LOAD_ADD_LOAD_STEP" "super-admin-piast" 001ms

And Add step "load" 116ms

And Fill step data 5s 464ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 080ms

Then Go to transport details "LOAD" 2s 621ms

And Check if "unload" step is added as "3" step in transport form 029ms

And Check if "load" step is added as "4" step in transport form 028ms

Hooks

After Hooks.deleteTransportAfterTest() 063ms

After Hooks.rollbackAddedActionAuthorities() 026ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackRemovedActionAuthorities

Scenario Outline Check if step is draggable according to authority @A-6865

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skz" 100ms

And Add action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_LOAD_STEPS" "UNLIMITED" 035ms

And Remove action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_UNLOAD_STEPS" "UNLIMITED" 008ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 182ms

When Login as "super-admin-skz" 1s 946ms

And Go to transport details "SMALLS_EXPORT" 2s 501ms

And Check if step is draggable "LOAD" 022ms

And Check if step is not draggable "UNLOAD" 020ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

After Hooks.rollbackAddedActionAuthorities() 034ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @ADAMA_NIE_DZIAŁA_PRZEZ_A-7134

Scenario Outline Check if transport created without advice by similar button has correct values

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set "transport" inputs from JSON file "CREATE_SMALLS_IMPORT" "super-admin-skz" 000ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 150ms

When Go to new transport "SMALLS_IMPORT" 388ms

And Fill transport form 19s 775ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 103ms

And Show all transport "false" 158ms

And Go to transport details "SMALLS_IMPORT" 2s 459ms

And Click create similar button 15s 139ms

And Fill "transport" form "CREATE_SIMILAR_SMALLS_IMPORT" by "super-admin-skz" 001ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 125ms

And Open similar transport details 311ms

Then Check are transport values equals 2s 123ms

Hooks

After Hooks.deleteTransportAfterTest() 062ms

After Hooks.deleteSimilarTransportAfterTest() 058ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @ADAMA_NIE_DZIAŁA_PRZEZ_A-7134

Scenario Outline Check if transport created with advice by similar button has correct values

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "pna1-carrier" 000ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 1s 753ms

When Go to new transport "DELIVERY" 15s 280ms

And Fill transport form 37s 972ms

And Click "save-transport" save button and wait for form to disappear 30s 137ms

And Set advice window in schedule 2s 172ms

And Check is transport created in schedule and set transport id 766ms

And Go to "TRANSPORT_TABLE" 305ms

And Go to transport details "DELIVERY" 30s 421ms

And Click create similar button 15s 161ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 11s 670ms

And Click "save-transport" save button and wait for form to disappear 30s 062ms

And Set advice window in schedule in "2" days 4s 227ms

And Go to "TRANSPORT_TABLE" 282ms

And Open similar transport details 481ms

Then Check are transport values equals 25s 481ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

After Hooks.deleteSimilarTransportAfterTest() 112ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

Scenario Outline Check if transport created with advice by similar button has correct carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "pna1-carrier" 000ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 1s 087ms

When Go to new transport "DELIVERY" 15s 331ms

And Fill transport form 37s 962ms

And Click "save-transport" save button and wait for form to disappear 30s 118ms

And Set advice window in schedule 2s 169ms

And Check is transport created in schedule and set transport id 736ms

And Go to "TRANSPORT_TABLE" 240ms

And Go to transport details "DELIVERY" 30s 396ms

And Click create similar button 15s 129ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 11s 604ms

And Click "save-transport" save button and wait for form to disappear 30s 094ms

And Set advice window in schedule in "2" days 4s 244ms

And Go to "TRANSPORT_TABLE" 261ms

And Open similar transport details 506ms

Then Check is field "CARRIER" of type "autocomplete" equals "Przewoźnik Neuca Automat 1" 020ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.deleteSimilarTransportAfterTest() 096ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is possible to show transport details print form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 255ms

And Set "transport" inputs from JSON file "CREATE_SMALLS_IMPORT_FOR_PRINT" "super-admin-skz" 000ms

When Go to new transport "SMALLS_IMPORT" 400ms

And Fill transport form 32s 908ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 103ms

And Go to transport details "SMALLS_IMPORT" 2s 472ms

And Go to transport print details form 3s 086ms

Then Check are transport values equals 8s 292ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to edit transport when auction is active

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 384ms

And Set "transport" inputs from JSON file "CREATE_SMALLS_IMPORT" "super-admin-skz" 000ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 251ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 108ms

And Go to transport details "SMALLS_IMPORT" 2s 468ms

Then Verify that the transport can be edited 1s 119ms

And Close transport details 15s 125ms

And If user is login then logout 118ms

And Login as "pskza1-carrier@qa.qa-test" 1s 420ms

And Go to transport details "SMALLS_IMPORT" 2s 494ms

And Verify that the transport cannot be edited 31s 172ms

Hooks

After Hooks.deleteTransportAfterTest() 141ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to edit transport when auction is active

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 369ms

And Set "transport" inputs from JSON file "CREATE_SMALLS_EXPORT" "super-admin-skz" 000ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 230ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 110ms

And Go to transport details "SMALLS_EXPORT" 2s 463ms

Then Verify that the transport can be edited 1s 302ms

And Close transport details 15s 120ms

And If user is login then logout 476ms

And Login as "pskza1-carrier@qa.qa-test" 1s 060ms

And Go to transport details "SMALLS_EXPORT" 2s 497ms

And Verify that the transport cannot be edited 46s 313ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to see hidden data in transport when auction is active

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 243ms

And Set "transport" inputs from JSON file "HIDDEN_DATA_SMALLS_IMPORT" "super-admin-skz" 000ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 296ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 102ms

And Go to transport details "SMALLS_IMPORT" 2s 444ms

Then Verify that the hidden data in transport are not visible 1s 045ms

And Close transport details 15s 098ms

And If user is login then logout 414ms

And Login as "swisskrono-admin" 1s 154ms

And Go to transport details "SMALLS_IMPORT" 2s 541ms

And Verify that the hidden data in transport are visible 1s 247ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to see hidden data in transport when auction is active

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 149ms

And Set "transport" inputs from JSON file "HIDDEN_DATA_SMALLS_EXPORT" "super-admin-skz" 000ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 294ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 106ms

And Go to transport details "SMALLS_EXPORT" 2s 415ms

Then Verify that the hidden data in transport are not visible 1s 034ms

And Close transport details 15s 125ms

And If user is login then logout 431ms

And Login as "swisskrono-admin" 1s 120ms

And Go to transport details "SMALLS_EXPORT" 2s 510ms

And Verify that the hidden data in transport are visible 1s 217ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is possible use 'save' and 'save transport and close' buttons after editing transport and fill discrepancy report panel

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 308ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 422ms

When Go to transport details "DELIVERY" 2s 754ms

And Change filled value in details "unloaded-stere" "text" "3" "0" 1s 327ms

And Change filled value in details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 501ms

And Change filled value in details "insp.-accord.-with-ins." "select" "NIE" "1" 3s 474ms

And Fill discrepancy report section without closing the form 19s 464ms

And Click "save-transport" save button 1s 244ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 103ms

And Check if transport details form is disappeared 15s 008ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest @rollbackWarehousesAccess

Scenario Outline Check if user can add description to transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-hochland" 094ms

And Add action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 040ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 192ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 424ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 2s 855ms

When Go to "TRANSPORT_TABLE" 254ms

And Go to transport details "DELIVERY" 2s 711ms

And Change filled value in details "transport-description" "text" "opis" "0" 1s 301ms

Then Verify that "transport-description" in transport has value "opis" 022ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

After Hooks.rollbackAddedActionAuthorities() 036ms

After Hooks.rollbackWarehousesAccess() 164ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest @rollbackWarehousesAccess

Scenario Outline Check if user can't add description to transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-hochland" 094ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 397ms

And Remove action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 045ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 146ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 2s 381ms

When Go to "TRANSPORT_TABLE" 200ms

And Go to transport details "DELIVERY" 2s 686ms

Then Verify that "transport-description" in transport form is disabled 017ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

After Hooks.rollbackRemovedActionAuthorities() 036ms

After Hooks.rollbackWarehousesAccess() 161ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can see `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-hochland" 094ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 044ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 368ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 517ms

And Show all transport "false" 158ms

When Go to "TRANSPORT_TABLE" 107ms

And Go to transport details "DELIVERY" 2s 725ms

Then Verify that "CARRIER" in transport form is visible 030ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

After Hooks.rollbackAddedActionAuthorities() 033ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can see `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-adama" 093ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 039ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 190ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 528ms

And Show all transport "false" 163ms

When Go to "TRANSPORT_TABLE" 139ms

And Go to transport details "TRANSPORT" 2s 458ms

Then Verify that "CARRIER" in transport form is visible 026ms

Hooks

After Hooks.deleteTransportAfterTest() 062ms

After Hooks.rollbackAddedActionAuthorities() 033ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can see `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-alrec" 096ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 041ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 169ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 516ms

And Show all transport "true" 237ms

When Go to "TRANSPORT_TABLE" 119ms

And Go to transport details "TRANSPORT_ORDER" 2s 478ms

Then Verify that "CARRIER" in transport form is visible 022ms

Hooks

After Hooks.deleteTransportAfterTest() 063ms

After Hooks.rollbackAddedActionAuthorities() 028ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't see `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-hochland" 103ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 033ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 327ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 334ms

And Show all transport "false" 164ms

When Go to "TRANSPORT_TABLE" 112ms

And Go to transport details "DELIVERY" 2s 726ms

Then Verify that "CARRIER" in transport form is not visible 15s 012ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

After Hooks.rollbackRemovedActionAuthorities() 040ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't see `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 089ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 034ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 191ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 572ms

And Show all transport "false" 163ms

When Go to "TRANSPORT_TABLE" 122ms

And Go to transport details "TRANSPORT" 2s 476ms

Then Verify that "CARRIER" in transport form is not visible 15s 008ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

After Hooks.rollbackRemovedActionAuthorities() 038ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't see `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-alrec" 091ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 040ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 187ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 406ms

And Show all transport "true" 239ms

When Go to "TRANSPORT_TABLE" 138ms

And Go to transport details "TRANSPORT_ORDER" 2s 472ms

Then Verify that "CARRIER" in transport form is not visible 15s 052ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

After Hooks.rollbackRemovedActionAuthorities() 037ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can edit `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-hochland" 095ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 036ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 034ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 373ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 435ms

And Show all transport "false" 166ms

When Go to "TRANSPORT_TABLE" 130ms

And Go to transport details "DELIVERY" 2s 754ms

Then Verify that "CARRIER" in transport form is not disabled 021ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

After Hooks.rollbackAddedActionAuthorities() 067ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can edit `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 091ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 040ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 039ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 224ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 519ms

And Show all transport "false" 160ms

When Go to "TRANSPORT_TABLE" 127ms

And Go to transport details "TRANSPORT" 2s 495ms

Then Verify that "CARRIER" in transport form is not disabled 019ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

After Hooks.rollbackAddedActionAuthorities() 062ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can edit `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-alrec" 095ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 040ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 041ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 223ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 412ms

And Show all transport "true" 210ms

When Go to "TRANSPORT_TABLE" 110ms

And Go to transport details "TRANSPORT_ORDER" 2s 487ms

Then Verify that "CARRIER" in transport form is not disabled 019ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

After Hooks.rollbackAddedActionAuthorities() 060ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't edit `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-hochland" 095ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 037ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 035ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 359ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 106ms

And Show all transport "false" 158ms

When Go to "TRANSPORT_TABLE" 129ms

And Go to transport details "DELIVERY" 2s 705ms

Then Verify that "CARRIER" in transport form is disabled 018ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

After Hooks.rollbackAddedActionAuthorities() 034ms

After Hooks.rollbackRemovedActionAuthorities() 039ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't edit `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 102ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 034ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 006ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 190ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 420ms

And Show all transport "false" 158ms

When Go to "TRANSPORT_TABLE" 129ms

And Go to transport details "TRANSPORT" 2s 459ms

Then Verify that "CARRIER" in transport form is disabled 017ms

Hooks

After Hooks.deleteTransportAfterTest() 057ms

After Hooks.rollbackAddedActionAuthorities() 026ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't edit `carrierCompany` field in transport form

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-alrec" 092ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 038ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 007ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 185ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 335ms

And Show all transport "true" 236ms

When Go to "TRANSPORT_TABLE" 112ms

And Go to transport details "TRANSPORT_ORDER" 2s 444ms

Then Verify that "CARRIER" in transport form is disabled 017ms

Hooks

After Hooks.deleteTransportAfterTest() 058ms

After Hooks.rollbackAddedActionAuthorities() 030ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if user can add description to archived transport

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 092ms

And Get custom field settings for "DELIVERY" transport type and "" company 017ms

And Mark custom fields as not obligatory 005ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 260ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_MAIN_DATA_SECTION" "UNLIMITED" 037ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_ADVICE" "UNLIMITED" 038ms

And Add action authority with: "adama" "adama-admin" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 031ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 391ms

When Find transport in table with status "planned" 3s 291ms

And Confirm statuses until reach "process-ended" 23s 584ms

And Wait "90" seconds 1m 30s

And Go to "ARCHIVE_TAB" 276ms

And Show "DELIVERY" 092ms

And Go to transport details "DELIVERY" 30s 467ms

And Change filled value in details "transport-description" "text" "opis" "0" 1s 323ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 153ms

And Wait "7" seconds 7s

And Go to transport details "DELIVERY" 30s 395ms

Then Verify that "transport-description" in transport has value "opis" 025ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

After Hooks.rollbackAllCustomFieldsSettings() 004ms

After Hooks.rollbackAddedActionAuthorities() 026ms

After Hooks.rollbackRemovedActionAuthorities() 064ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if driver is in list in transport form.

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 828ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 000ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 385ms

When Go to transport details "DELIVERY" 2s 722ms

And Fill transport form 37s 860ms

And Change filled value in details "driver-name" "text" "XXX ZZZ" "0" 1s 367ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 119ms

And Go to new transport "DELIVERY" 361ms

Then Verify that driver "XXX ZZZ" is in list 681ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if 'rate' field is visible in transport form with proper value and currency after passing transport to carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 304ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 234ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 33s 654ms

And If user is login then logout 410ms

And Login as "pskza1-carrier@qa.qa-test" 1s 185ms

Then Verify that the transport has been transferred 1s 153ms

And Accept or reject "accept" transferred transport 15s 756ms

And Go to transport details "SMALLS_IMPORT" 2s 591ms

And Verify that "transaction-price" in transport form is visible 024ms

And Verify that transaction price field has correct value 018ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_IMPORT" 020ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if 'rate' field is visible in transport form with proper value and currency after passing transport to carrier

Hooks

Before Hooks.showScenarioName(Scenario) 014ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 258ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 245ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 33s 726ms

And If user is login then logout 128ms

And Login as "pskza1-carrier@qa.qa-test" 1s 355ms

Then Verify that the transport has been transferred 1s 140ms

And Accept or reject "accept" transferred transport 15s 763ms

And Go to transport details "SMALLS_EXPORT" 2s 566ms

And Verify that "transaction-price" in transport form is visible 028ms

And Verify that transaction price field has correct value 025ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_EXPORT" 023ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if similar transport can be created based on transport with confirmed statuses [A-7322]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-dayco" 093ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 021ms

And Mark custom fields as not obligatory 005ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 211ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 001ms

When Login as "dayco-admin" 1s 280ms

And Click button advice in transport table "OWN_COLLECTION" 284ms

And Set advice window in schedule 2s 518ms

And Fill advice form 9s 222ms

And Click advice save button and wait for advice form to disappear 30s 715ms

And Go to "TRANSPORT_TABLE" 213ms

And Find transport in table with status "planned" 3s 223ms

And Confirm statuses until reach "on-the-area" 4s 808ms

And Go to transport details "OWN_COLLECTION" 2s 449ms

And Click create similar button 15s 096ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 6s 507ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 137ms

And Open similar transport details 275ms

Then Check if transport form modal is visible 033ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

After Hooks.deleteSimilarTransportAfterTest() 070ms

After Hooks.rollbackAllCustomFieldsSettings() 079ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @rollbackAllCustomFieldsSettings

Scenario Outline Check if similar transport can be created based on transport with confirmed statuses [A-7322]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-dayco" 094ms

And Get custom field settings for "OWN_COLLECTION" transport type and "dayco" company 019ms

And Mark custom fields as not obligatory 004ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 199ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 001ms

When Login as "dayco-admin" 1s 447ms

And Click button advice in transport table "OWN_COLLECTION" 307ms

And Set advice window in schedule 2s 524ms

And Fill advice form 9s 179ms

And Click advice save button and wait for advice form to disappear 30s 689ms

And Go to "TRANSPORT_TABLE" 196ms

And Find transport in table with status "planned" 3s 257ms

And Confirm statuses until reach "during-load" 8s 541ms

And Go to transport details "OWN_COLLECTION" 2s 414ms

And Click create similar button 15s 165ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 6s 467ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 102ms

And Open similar transport details 317ms

Then Check if transport form modal is visible 036ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

After Hooks.deleteSimilarTransportAfterTest() 053ms

After Hooks.rollbackAllCustomFieldsSettings() 070ms

View Feature Transport form

@deleteTransportAfterTest @deleteCustomFieldAfterTest @FLAKY-A-7982

Scenario Outline Check if date and time custom field appeared in transport details after creating transport

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-lisner" 094ms

And Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-lisner" 000ms

And Create custom field with "CREATE_DELIVERY_DATE_AND_TIME_CFD" by "super-admin-lisner" 300ms

When Login as "lisner-admin-2" and set token of apiUsername "super-admin-lisner" 1s 855ms

And Go to new transport "DELIVERY" 317ms

And Fill transport form 30s 032ms

And Click "save-transport" save button and wait for form to disappear 30s 115ms

And Set advice window in schedule 2s 152ms

And Go to "TRANSPORT_TABLE" 192ms

And Show all transport types 1s 063ms

And Go to transport details "DELIVERY" 2s 324ms

Then Verify that "date-and-time" in transport form is visible 026ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.deleteCustomFieldAfterTest() 265ms

View Feature Invoice

@deleteTransportAfterTest @rollbackInvoiceCurrency

Scenario Outline Check default value of currency in invoice form [A-7389]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 337ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 224ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 080ms

When Click invoice button 2s 469ms

And Set default invoice currency value 058ms

Then Check that default currency value in invoice form is "EUR" 042ms

When Change invoice default currency value in database for "USD" transport type alias "SMALLS_IMPORT" and principal alias "swisskrono" 051ms

And Clear all cache 858ms

And Login as "swisskrono-admin" 2s 114ms

And Go to "TRANSPORT_TABLE" 130ms

And Show all transport types 1s 067ms

And Click invoice button 127ms

Then Check that default currency value in invoice form is "USD" 060ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.rollbackInvoiceCurrency() 867ms

View Feature Invoice

@deleteTransportAfterTest @rollbackInvoiceCurrency

Scenario Outline Check default value of currency in invoice form [A-7389]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 112ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 202ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 088ms

When Click invoice button 2s 516ms

And Set default invoice currency value 057ms

Then Check that default currency value in invoice form is "EUR" 042ms

When Change invoice default currency value in database for "USD" transport type alias "SMALLS_EXPORT" and principal alias "swisskrono" 020ms

And Clear all cache 825ms

And Login as "swisskrono-admin" 2s 011ms

And Go to "TRANSPORT_TABLE" 134ms

And Show all transport types 1s 069ms

And Click invoice button 117ms

Then Check that default currency value in invoice form is "USD" 053ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.rollbackInvoiceCurrency() 866ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport details button is not shown

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "lantmannen-guard-3" and set token of apiUsername "super-admin-lantmannen" 1s 768ms

And Create transport "CREATE_DELIVERY_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 291ms

And Show all transport types 1s 042ms

Then Check if transport number is visible "DELIVERY" 15s 065ms

And Check if transport details is not visible 15s 029ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 420ms

And Show all transport "false" 158ms

And Go to "TRANSPORT_TABLE" 125ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 356ms

When Click on transport row 058ms

Then Verify if transport row is selected 030ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 650ms

And Show all transport "false" 159ms

And Go to "TRANSPORT_TABLE" 118ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 304ms

When Click on transport row 067ms

Then Verify if transport row is selected 025ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 1s 425ms

And Show all transport "false" 157ms

And Go to "TRANSPORT_TABLE" 116ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 262ms

When Click on transport row 064ms

Then Verify if transport row is selected 051ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 443ms

And Show all transport "false" 158ms

And Go to "TRANSPORT_TABLE" 138ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 343ms

When Click on transport row 063ms

Then Verify if transport row is selected 026ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 863ms

And Show all transport "false" 158ms

And Go to "TRANSPORT_TABLE" 109ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 288ms

When Click on transport row 062ms

Then Verify if transport row is selected 026ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 638ms

And Show all transport "true" 222ms

And Go to "TRANSPORT_TABLE" 117ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 287ms

When Click on transport row 064ms

Then Verify if transport row is selected 019ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 103ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 202ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 081ms

Then Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 971ms

And Show "TRANSPORT" 140ms

When Accept or reject "accept" transferred transport 15s 759ms

Then Verify that transport is accept or reject "accept" 019ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 090ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 267ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 084ms

Then Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 438ms

And Show "TRANSPORT" 140ms

When Accept or reject "reject" transferred transport 15s 774ms

Then Verify that transport is accept or reject "reject" 15s 028ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-skz" 092ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 270ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 068ms

Then Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 256ms

And Show "SMALLS_IMPORT" 092ms

When Accept or reject "accept" transferred transport 15s 988ms

Then Verify that transport is accept or reject "accept" 021ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skz" 094ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 249ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 073ms

Then Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 207ms

And Show "SMALLS_IMPORT" 087ms

When Accept or reject "reject" transferred transport 15s 999ms

Then Verify that transport is accept or reject "reject" 15s 060ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skz" 095ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 253ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 077ms

Then Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 366ms

And Show "SMALLS_EXPORT" 083ms

When Accept or reject "accept" transferred transport 16s 062ms

Then Verify that transport is accept or reject "accept" 020ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-skz" 100ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 235ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 083ms

Then Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 190ms

And Show "SMALLS_EXPORT" 101ms

When Accept or reject "reject" transferred transport 16s 005ms

Then Verify that transport is accept or reject "reject" 15s 030ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - with confirmation checkbox

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 150ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 232ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 33s 728ms

And If user is login then logout 116ms

And Login as "paa1-carrier@qa.qa-test" 1s 740ms

Then Verify that the transport has been transferred with "true" 1s 211ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - with confirmation checkbox

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 022ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 209ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 33s 765ms

And If user is login then logout 383ms

And Login as "paa1-carrier@qa.qa-test" 1s 323ms

Then Verify that the transport has been transferred with "false" 1s 120ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - without confirmation checkbox

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 157ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 248ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 33s 729ms

And If user is login then logout 085ms

And Login as "pskza1-carrier@qa.qa-test" 1s 220ms

Then Verify that the transport has been transferred 1s 141ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - without confirmation checkbox

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 163ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 220ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 33s 631ms

And If user is login then logout 382ms

And Login as "pskza1-carrier@qa.qa-test" 1s 126ms

Then Verify that the transport has been transferred 1s 148ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to pass transport to carrier during auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 225ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 255ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 112ms

And Go to auction offer 1s 213ms

When Offer "1000" 181ms

And Verify that offer with "1000" has been added to auction 3s 032ms

And If user is login then logout 068ms

And Login as "swisskrono-admin" 1s 319ms

Then Go to auction details 1s 201ms

And Pass transport to carrier from auction details 1s 268ms

And If user is login then logout 5s 610ms

And Login as "pskza1-carrier@qa.qa-test" 1s 062ms

And Verify that the transport has been transferred 1s 132ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to pass transport to carrier when auction is finished

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 122ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 332ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 101ms

And Go to auction offer 1s 202ms

When Offer "1000" 183ms

And Verify that offer with "1000" has been added to auction 3s 036ms

And Wait till auction end 1m 54s 015ms

And If user is login then logout 374ms

Then Login as "swisskrono-admin" 1s 170ms

And Go to auction details 1s 239ms

And Pass transport to carrier from auction details 1s 269ms

And If user is login then logout 435ms

And Login as "pskza1-carrier@qa.qa-test" 1s 302ms

And Verify that the transport has been transferred 1s 122ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if enabled carriers are shown in transport transfer select

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 287ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 233ms

And Go to "TRANSPORT_TABLE" 136ms

When Open transport transfer modal 1s 239ms

Then Verify that all enabled companies from "swisskrono" are shown in select 136ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest @rollbackRejectedSections

Scenario Outline Check if blocked carriers are shown as disabled in transport transfer select

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 096ms

And Reject main section of a "Przewoźnik Adama Automat 1" in "adama" by API 213ms

And Login as "adama-admin" 954ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 215ms

And Go to "TRANSPORT_TABLE" 122ms

When Open transport transfer modal 1s 214ms

Then Verify that "Przewoźnik Adama Automat 1" is blocked in select 095ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

After Hooks.rollbackRejectedSections() 071ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if transport is not visible to carrier after expiring of time to accept transport [A-7037]

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 081ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 229ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" with "120" seconds to accept transport 33s 891ms

And If user is login then logout 111ms

When Login as "paa1-carrier@qa.qa-test" 7s 456ms

And Verify that the transport has been transferred with "true" 1s 243ms

And Wait "120" seconds 2m

Then Verify if transport is not visible to carrier after expiring time to accept transport 15s 011ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature Assortment Group

@deleteTransportAfterTest

Scenario Outline Check if assortment group select is disabled when transport is during edition

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 051ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 394ms

When Go to "TRANSPORT_TABLE" 137ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 2s 411ms

Then Check if new assortment group is disabled in transport form 016ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to advice transport after double cancellation.

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 018ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 190ms

And Set "advice" inputs from JSON file "CREATE_ADVICE_CONTAINER" "super-admin-adama" 000ms

When Show all transport types 1s 037ms

And Click button advice in transport table "CONTAINER" 103ms

And Set advice window in schedule 2s 476ms

And Click button cancel in advice form 15s 356ms

And Set advice window in schedule 2s 168ms

And Click button cancel in advice form 15s 258ms

And Set advice window in schedule 2s 121ms

And Fill advice form 17s 855ms

And Click advice save button and wait for advice form to disappear 30s 738ms

And Go to "TRANSPORT_TABLE" 190ms

And Go to transport details "CONTAINER" 2s 381ms

Then Check are advice values equals 4s 376ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

View Feature Transport transfer full scenario

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer and retransfer transport to carrier

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 156ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-adama" 000ms

When Go to new transport "TRANSPORT" 393ms

And Fill transport form 26s 708ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 152ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 33s 754ms

And Check is transport "TRANSPORT" created in transport table and set transport id 1s 117ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 525ms

And Accept or reject "reject" transferred transport 15s 832ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 163ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 33s 753ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 405ms

And Accept or reject "accept" transferred transport 15s 871ms

Then Verify that transport is accept or reject "accept" 020ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

View Feature Transport transfer full scenario

@deleteTransportAfterTest @FLAKY-A-7905 @FLAKY-A-6187

Scenario Outline Check if possible to edit transport after advice cancellation.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 275ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-piast" 000ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 217ms

When Show all transport types 1s 036ms

And Click button advice in transport table "DELIVERY" 107ms

And Set advice window in schedule 2s 645ms

And Click button cancel in advice form 15s 394ms

And Go to "TRANSPORT_TABLE" 204ms

When Go to transport details "DELIVERY" 2s 475ms

And Fill transport form 1m 2s 215ms

And Click "save-transport-and-close" save button and wait for form to disappear 30s 141ms

And Go to transport details "DELIVERY" 2s 491ms

Then Check are transport values equals 24s 744ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@deleteTransportAfterTest	3891	34	118	0	0	4043	375	34	409	5h 28m 47s 225ms	Failed

Tag Report