Cucumber-JVM Reports - Tag: @deleteTransportAfterTest

Project	Number	Date
ApolloFullRunnerReport	develop.400	28 kwi 2021, 05:38

	Steps	Scenarios	Features
@deleteTransportAfterTest	3454	15	36	0	0	3505	368	17	385	5h 14m 46s 714ms	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.

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 180ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 3s 198ms

And Get inputs from database "CREATE_ADVICE_CONTAINER" "super-admin-adama" 1s 391ms

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

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

And Set advice window in schedule in the past 3s 140ms

And Fill advice form 16s 262ms

And Click advice save button to check error message 073ms

Then Check if possible advice alert is displayed 014ms

Hooks

After Hooks.deleteTransportAfterTest() 333ms

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.

Steps

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

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

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

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

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

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

And Fill advice form 8s 319ms

And Click advice save button to check error message 070ms

Then Check if possible advice alert is displayed 013ms

Hooks

After Hooks.deleteTransportAfterTest() 142ms

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.

Steps

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

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

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

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

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

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

And Fill advice form 8s 312ms

And Click advice save button to check error message 078ms

Then Check if possible advice alert is displayed 016ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

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.

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 269ms

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

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

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

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

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

And Fill advice form 13s 109ms

And Click advice save button to check error message 072ms

Then Check if possible advice alert is displayed 021ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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.

Steps

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

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

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

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

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

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

And Fill advice form 13s 082ms

And Click advice save button to check error message 077ms

Then Check if possible advice alert is displayed 016ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport types 1s 041ms

And Create advice "CREATE_ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 49s 550ms

And Go to "TRANSPORT_TABLE" 161ms

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

When Go to transport details "CONTAINER" 4s 417ms

And Fill transport form 4s 682ms

And Get inputs from database "EDIT_ADVICE_CONTAINER" "super-admin-adama" 003ms

And Expand advice panel 089ms

And Edit advice in transport details 12s 320ms

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

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

And Expand advice panel 101ms

Then Check are advice values equals after edition 197ms

Hooks

After Hooks.deleteTransportAfterTest() 154ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport types 1s 043ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 26s 685ms

And Go to "TRANSPORT_TABLE" 219ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-piast" 005ms

When Go to transport details "DELIVERY" 4s 423ms

And Fill transport form 1m 1s 826ms

And Get inputs from database "EDIT_ADVICE_DELIVERY" "super-admin-piast" 005ms

And Expand advice panel 077ms

And Edit advice in transport details 6s 548ms

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

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

And Expand advice panel 089ms

Then Check are advice values equals after edition 078ms

Hooks

After Hooks.deleteTransportAfterTest() 178ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport types 1s 039ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-piast" 41s 701ms

And Go to "TRANSPORT_TABLE" 175ms

And Get inputs from database "EDIT_LOAD" "super-admin-piast" 004ms

When Go to transport details "LOAD" 4s 666ms

And Fill transport form 56s 785ms

And Get inputs from database "EDIT_ADVICE_DELIVERY" "super-admin-piast" 005ms

And Expand advice panel 100ms

And Edit advice in transport details 6s 594ms

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

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

And Expand advice panel 089ms

Then Check are advice values equals after edition 084ms

Hooks

After Hooks.deleteTransportAfterTest() 188ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport types 1s 044ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 46s 200ms

And Go to "TRANSPORT_TABLE" 175ms

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

When Go to transport details "LOAD" 4s 417ms

And Fill transport form 24s 511ms

And Get inputs from database "EDIT_ADVICE_LOAD" "super-admin-keeeper" 006ms

And Expand advice panel 084ms

And Edit advice in transport details 18s 430ms

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

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

And Expand advice panel 107ms

Then Check are advice values equals after edition 6s 271ms

Hooks

After Hooks.deleteTransportAfterTest() 216ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport types 1s 042ms

And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-keeeper" 46s 251ms

And Go to "TRANSPORT_TABLE" 184ms

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

When Go to transport details "CONTAINER" 4s 398ms

And Fill transport form 24s 550ms

And Get inputs from database "EDIT_ADVICE_CONTAINER" "super-admin-keeeper" 005ms

And Expand advice panel 093ms

And Edit advice in transport details 18s 322ms

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

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

And Expand advice panel 096ms

Then Check are advice values equals after edition 6s 278ms

Hooks

After Hooks.deleteTransportAfterTest() 150ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Get inputs from database "EDIT_ADVICE_CONTAINER" "super-admin-adama" 004ms

When Show all transport types 1s 040ms

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

And Set advice window in schedule 2s 416ms

And Fill advice form 12s 217ms

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

And Go to "TRANSPORT_TABLE" 178ms

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

Then Check are advice values equals 286ms

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

Steps

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

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

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

When Show all transport types 1s 044ms

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

And Set advice window in schedule 6s 459ms

And Fill advice form 11s 668ms

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

And Go to "TRANSPORT_TABLE" 167ms

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

Then Check are advice values equals 2s 275ms

Hooks

After Hooks.deleteTransportAfterTest() 140ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

When Show all transport types 1s 035ms

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

And Set advice window in schedule 2s 565ms

And Fill advice form 8s 229ms

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

And Go to "TRANSPORT_TABLE" 211ms

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

Then Check are advice values equals 192ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

When Show all transport types 1s 048ms

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

And Set advice window in schedule 2s 594ms

And Fill advice form 8s 225ms

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

And Go to "TRANSPORT_TABLE" 193ms

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

Then Check are advice values equals 191ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

When Show all transport types 1s 032ms

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

And Set advice window in schedule 2s 460ms

And Fill advice form 12s 961ms

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

And Go to "TRANSPORT_TABLE" 171ms

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

Then Check are advice values equals 2s 281ms

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

Steps

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

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

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

When Show all transport types 1s 044ms

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

And Set advice window in schedule 2s 434ms

And Fill advice form 12s 993ms

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

And Go to "TRANSPORT_TABLE" 168ms

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

Then Check are advice values equals 2s 317ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

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

Steps

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

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

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

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

And Accept transferred transport by Api 409ms

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

And Get inputs from database "ADVICE_TRANSPORT" "super-admin-adama" 002ms

When Show all transport types 1s 065ms

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

And Set advice window in schedule 2s 453ms

And Fill advice form 11s 637ms

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

And Go to "TRANSPORT_TABLE" 201ms

And Go to transport details "TRANSPORT" 4s 453ms

Then Check are advice values equals 2s 246ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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

Steps

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

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

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

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

And Accept transferred transport by Api 137ms

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

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

When Show all transport types 1s 064ms

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

And Set advice window in schedule 2s 623ms

And Fill advice form 14s 357ms

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

And Go to "TRANSPORT_TABLE" 158ms

And Go to transport details "SMALLS_IMPORT" 4s 488ms

Then Check are advice values equals 2s 282ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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

Steps

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

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

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

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

And Accept transferred transport by Api 150ms

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

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

When Show all transport types 1s 059ms

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

And Set advice window in schedule 2s 613ms

And Fill advice form 14s 292ms

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

And Go to "TRANSPORT_TABLE" 162ms

And Go to transport details "SMALLS_EXPORT" 4s 456ms

Then Check are advice values equals 2s 271ms

Hooks

After Hooks.deleteTransportAfterTest() 143ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

And Accept transferred transport by Api 123ms

And Login as "paa1-carrier@qa.qa-test" 997ms

When Show all transport types 1s 047ms

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

And Set week view 1s 503ms

And Show yesterday 1s 067ms

Then Check if advice restriction blockade windows are visible 031ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

And Accept transferred transport by Api 101ms

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

When Show all transport types 1s 064ms

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

And Set week view 2s 001ms

And Show yesterday 1s 106ms

Then Check if advice restriction blockade windows are visible 033ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

And Accept transferred transport by Api 091ms

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

When Show all transport types 1s 063ms

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

And Set week view 1s 998ms

And Show yesterday 1s 095ms

Then Check if advice restriction blockade windows are visible 029ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

View Feature Advice transport

@deleteTransportAfterTest

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

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

And Show all transport "false" 019ms

And Click on time window date 1s 274ms

And Select view "DAYS_4" 2s 057ms

And Move advice window "3" 1s 362ms

Then Check if advice window is in new location 021ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 3s 675ms

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

And Show all transport "false" 012ms

And Click on time window date 15s 709ms

And Select view "DAYS_4" 2s 077ms

And Move advice window "3" 15s 055ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[@data-window-type='state-with-transport']/div"}
  (Session info: headless chrome=90.0.4430.72)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.a1iJQ8}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=90.0.4430.72, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: ad7ef55ccd6c049ed315433353249fb9
*** Element info: {Using=xpath, value=//div[@data-window-type='state-with-transport']/div}
	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:306)
	at CucumberTests.Transport.AdviceTransport.moveAdviceWindow(AdviceTransport.java:264)
	at ✽.Move advice window "3"(file:Features/Atom/Advice/AdviceTransport.feature:137)

Then Check if advice window is in new location 000ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport "false" 015ms

And Click on time window date 15s 473ms

And Select view "DAYS_4" 2s 065ms

And Move advice window "3" 1s 376ms

Then Check if advice window is in new location 023ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 936ms

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

And Show all transport "false" 012ms

And Click on time window date 1s 385ms

And Select view "DAYS_4" 2s 062ms

And Move advice window "3" 1s 381ms

Then Check if advice window is in new location 022ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport "false" 016ms

And Click on time window date 1s 296ms

And Select view "DAYS_4" 2s 049ms

And Move advice window "3" 1s 296ms

Then Check if advice window is in new location 020ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 887ms

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

And Show all transport "true" 079ms

And Click on time window date 1s 322ms

And Select view "DAYS_4" 2s 054ms

And Move advice window "3" 1s 344ms

Then Check if advice window is in new location 023ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

When Show all transport types 1s 034ms

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

And Set advice window in schedule 2s 581ms

And Fill advice form 8s 212ms

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

And Go to "TRANSPORT_TABLE" 203ms

And Click on time window date 1s 382ms

And Select view "DAYS_4" 2s 048ms

And Move advice window "3" 1s 404ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if late advice is red

Steps

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 137ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Go to "TRANSPORT_TABLE" 129ms

And Show all transport types 1s 037ms

And Click on time window date 1s 278ms

And Scroll to time window "adviceWindow" 041ms

And Set time window height "80" "adviceWindow" 2s 368ms

Then Check height of the time window after expanding by "80" in "adviceWindow" 021ms

Error message

java.lang.AssertionError: Okno nie zmieniło swojego rozmiaru
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Schedule.ResizeTimeWindowTest.checkHeightOfTimeWindowAfterExpandingByIn(ResizeTimeWindowTest.java:35)
	at ✽.Check height of the time window after expanding by "80" in "adviceWindow"(file:Features/Atom/Advice/AdviceTransport.feature:186)

Hooks

After Hooks.deleteTransportAfterTest() 142ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Go to "TRANSPORT_TABLE" 099ms

And Show all transport types 1s 029ms

And Click on time window date 1s 370ms

And Scroll to time window "adviceWindow" 036ms

And Set time window height "120" "adviceWindow" 2s 369ms

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

Hooks

After Hooks.deleteTransportAfterTest() 101ms

View Feature Advice transport

@deleteTransportAfterTest

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

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

And Go to "TRANSPORT_TABLE" 110ms

And Show all transport types 1s 030ms

And Click on time window date 1s 303ms

And Scroll to time window "adviceWindow" 032ms

And Set time window height "48" "adviceWindow" 2s 366ms

Then Check height of the time window after expanding by "48" in "adviceWindow" 019ms

Error message

java.lang.AssertionError: Okno nie zmieniło swojego rozmiaru
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Schedule.ResizeTimeWindowTest.checkHeightOfTimeWindowAfterExpandingByIn(ResizeTimeWindowTest.java:35)
	at ✽.Check height of the time window after expanding by "48" in "adviceWindow"(file:Features/Atom/Advice/AdviceTransport.feature:186)

Hooks

After Hooks.deleteTransportAfterTest() 106ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 3s 169ms

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

And Go to "TRANSPORT_TABLE" 279ms

And Show all transport types 15s 058ms

And Click on time window date 15s 717ms

And Scroll to time window "adviceWindow" 093ms

And Set time window height "40" "adviceWindow" 2s 402ms

Then Check height of the time window after expanding by "40" in "adviceWindow" 016ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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

Steps

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

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

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

When Show all transport types 1s 039ms

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

And Set advice window in schedule 2s 599ms

And Fill advice form 8s 214ms

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

And Go to "TRANSPORT_TABLE" 228ms

And Click on time window date 1s 387ms

And Set time window height "120" "adviceWindow" 2s 381ms

Then Check height of the time window after expanding by "120" in "adviceWindow" 019ms

Hooks

After Hooks.deleteTransportAfterTest() 144ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-hochland" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 446ms

And Go to "WAREHOUSE_TAB" 890ms

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

When Go to new transport "DELIVERY" 339ms

And Fill transport form 39s 768ms

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

And Click previous page button in browser 023ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-hochland" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 375ms

And Go to "WAREHOUSE_TAB" 760ms

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

When Go to new transport "DELIVERY" 321ms

And Fill transport form 39s 318ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

And Get inputs from database "ADVICE_TRANSPORT" "super-admin-adama" 002ms

When Show all transport types 1s 030ms

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

And Fill advice form 11s 504ms

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

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

And Open statuses popup 087ms

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

Hooks

After Hooks.deleteTransportAfterTest() 107ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if time window details preview displays correctly

Steps

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

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

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

And Login as "farmacol-admin" 4s 144ms

And Go to "WAREHOUSE_TAB" 658ms

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

And Set week view 2s 179ms

And Move cursor over time window element 406ms

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

Hooks

After Hooks.deleteTransportAfterTest() 114ms

View Feature Company Resources

@deleteTransportAfterTest

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

Steps

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

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

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

And Fill transport form 34s 175ms

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

When Click "save-transport" save button and wait for form to disappear 15s 646ms

And Set advice window in schedule 2s 154ms

And Check is transport created in schedule and set transport id 1s 429ms

Then Go to "OWN_COMPANY_TAB" 244ms

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

Hooks

After Hooks.deleteTransportAfterTest() 172ms

View Feature Company Resources

@deleteTransportAfterTest

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

Steps

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

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

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

And Fill transport form 16s 163ms

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

When Click "save-transport" save button and wait for form to disappear 15s 576ms

And Set advice window in schedule 2s 153ms

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

Then Go to "OWN_COMPANY_TAB" 237ms

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

Hooks

After Hooks.deleteTransportAfterTest() 138ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 186ms

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

And Show all transport types 1s 079ms

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

Hooks

After Hooks.deleteTransportAfterTest() 103ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 218ms

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

And Show all transport types 1s 081ms

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

Hooks

After Hooks.deleteTransportAfterTest() 117ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 135ms

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

And Show all transport types 1s 076ms

Then Verify that created transport is "false" in transport table 1m 18s 199ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 131ms

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

And Show all transport types 1s 084ms

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

Hooks

After Hooks.deleteTransportAfterTest() 093ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 100ms

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

When Go to "ARCHIVE_TAB" 222ms

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

And Show "SMALLS_IMPORT" 064ms

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

Hooks

After Hooks.deleteTransportAfterTest() 152ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 098ms

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

When Go to "ARCHIVE_TAB" 201ms

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

And Show "SMALLS_IMPORT" 088ms

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

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 105ms

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

When Go to "ARCHIVE_TAB" 215ms

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

And Show "SMALLS_IMPORT" 071ms

Then Verify that created transport is "false" in transport table 1m 32s 256ms

Hooks

After Hooks.deleteTransportAfterTest() 147ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

And Delete created transport by API 190ms

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

When Go to "ARCHIVE_TAB" 194ms

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

And Show "SMALLS_IMPORT" 063ms

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

Hooks

After Hooks.deleteTransportAfterTest() 133ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

And Go to "TRANSPORT_TABLE" 122ms

And Show all transport "true" 071ms

And Select transportType "TRANSPORT_ORDER" 1s 140ms

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

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

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

And Login as "neuca-admin" 2s 840ms

And Go to "TRANSPORT_TABLE" 197ms

Then Verify that created transport is "false" in transport table 1m 32s 208ms

And Toggle transport table days limit filter 080ms

And Verify that created transport is "true" in transport table 15s 058ms

Hooks

After Hooks.deleteTransportAfterTest() 157ms

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

Steps

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

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

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

When Go to "TRANSPORT_TABLE" 136ms

And Go to auction form 1s 330ms

And Select contractors group "Kraj" 098ms

Then Verify that carrier "PSKZA1" is selected 023ms

Hooks

After Hooks.deleteTransportAfterTest() 183ms

After Hooks.removeContractorsGroup() 083ms

View Feature Grouping of carriers

@deleteTransportAfterTest

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

Steps

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

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

When Go to "TRANSPORT_TABLE" 136ms

And Go to auction form 1s 215ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Grouping of carriers

@deleteTransportAfterTest

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

Steps

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

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

When Go to "TRANSPORT_TABLE" 131ms

And Go to auction form 1s 196ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 119ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

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

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

And Show all transport "false" 017ms

And Get inputs from database "ADD_INDEX" "super-admin-adama" 002ms

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

When Go to transport details "TRANSPORT" 4s 445ms

And Expand index panel 103ms

And Click add index button 121ms

And Fill index form 10s 515ms

And Click ok button in index form 15s 145ms

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

And Go to transport details "TRANSPORT" 4s 446ms

And Expand index panel 127ms

Then Check are transport values equals 091ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

After Hooks.deleteProductAfterTest() 067ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Show all transport "true" 064ms

And Get inputs from database "ADD_INDEX" "super-admin-alrec" 002ms

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

When Go to transport details "TRANSPORT_ORDER" 4s 431ms

And Expand index panel 093ms

And Click add index button 108ms

And Fill index form 7s 513ms

And Click ok button in index form 15s 105ms

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

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

And Expand index panel 125ms

Then Check are transport values equals 2s 118ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

After Hooks.deleteProductAfterTest() 000ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if it possible to delete index in transport

Steps

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

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

And Show all transport "false" 015ms

And Get inputs from database "ADD_INDEX" "super-admin-adama" 002ms

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

When Go to transport details "TRANSPORT" 4s 482ms

And Add index to transport 25s 887ms

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

When Go to transport details "TRANSPORT" 4s 461ms

And Expand index panel 117ms

And Click delete index button 079ms

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

And Go to transport details "TRANSPORT" 4s 337ms

And Expand index panel 094ms

Then Verify that transport has no indexes 15s 018ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.deleteProductAfterTest() 037ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if it possible to delete index in transport

Steps

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

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

And Show all transport "true" 071ms

And Get inputs from database "ADD_INDEX" "super-admin-alrec" 002ms

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

When Go to transport details "TRANSPORT_ORDER" 4s 440ms

And Add index to transport 22s 895ms

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

When Go to transport details "TRANSPORT_ORDER" 4s 377ms

And Expand index panel 103ms

And Click delete index button 061ms

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

And Go to transport details "TRANSPORT_ORDER" 4s 305ms

And Expand index panel 098ms

Then Verify that transport has no indexes 15s 050ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

After Hooks.deleteProductAfterTest() 000ms

View Feature Index

@deleteProductAfterTest @deleteTransportAfterTest

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

Steps

Given Login as "dayco-admin" and set token of apiUsername "super-admin-dayco" 2s 907ms

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

And Get inputs from database "ADD_INDEX" "super-admin-dayco" 003ms

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

And Go to transport details "OWN_COLLECTION" 4s 446ms

And Add index to transport 24s 578ms

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

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 40s 361ms

When Click on index details icon 102ms

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

Hooks

After Hooks.deleteTransportAfterTest() 109ms

After Hooks.deleteProductAfterTest() 036ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

And Get inputs from database "ADVICE_CONTAINER" "super-admin-adama" 004ms

And Show all transport types 1s 047ms

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

And Set advice window in schedule 2s 543ms

And Fill advice form 11s 829ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zapisano awizację! | Advice has been saved!" 7s 489ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 162ms

After Hooks.cleanUserDetailsAfterTest() 170ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

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

And Show all transport types 1s 044ms

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

And Set advice window in schedule 2s 649ms

And Fill advice form 8s 348ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zapisano awizację! | Advice has been saved!" 7s 334ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

After Hooks.cleanUserDetailsAfterTest() 139ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 326ms

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

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

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

And Show all transport types 1s 048ms

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

And Set advice window in schedule 2s 474ms

And Fill advice form 13s 204ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

After Hooks.cleanUserDetailsAfterTest() 206ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

And Show all transport types 1s 050ms

And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 45s 034ms

And Go to "TRANSPORT_TABLE" 190ms

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

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 003ms

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

And Fill transport form 4s 717ms

And Get inputs from database "EDIT_ADVICE_CONTAINER" "super-admin-adama" 003ms

And Expand advice panel 115ms

And Edit advice in transport details 12s 375ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zmiana w awizacji numer" 31s 246ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

After Hooks.cleanUserDetailsAfterTest() 173ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

And Show all transport types 1s 043ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 41s 813ms

And Go to "TRANSPORT_TABLE" 242ms

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-piast" 005ms

When Go to transport details "DELIVERY" 3s 191ms

And Fill transport form 1m 2s 400ms

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

And Expand advice panel 100ms

And Edit advice in transport details 6s 599ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zmiana w awizacji numer" 7s 587ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 166ms

After Hooks.cleanUserDetailsAfterTest() 158ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 2s 583ms

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

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

And Show all transport types 1s 044ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 46s 444ms

And Go to "TRANSPORT_TABLE" 197ms

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

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

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

And Fill transport form 24s 691ms

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

And Expand advice panel 119ms

And Edit advice in transport details 18s 578ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zmiana w awizacji numer" 50s 487ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

After Hooks.cleanUserDetailsAfterTest() 220ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Potwierdzono status Wjazd na teren zakładu" 43s 895ms

Then Check if user got a mail 000ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Potwierdzono status Wyjazd" 37s 338ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 180ms

After Hooks.cleanUserDetailsAfterTest() 185ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackVerificationEmailSettingAfterTest

Scenario Outline Check if verification mail was sent to transport creator

Steps

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

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

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

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

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

Error message

java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <401>.

	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.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy:175)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:64)
	at CucumberTests.Transport.CreateTransport.createByJSONFileAs(CreateTransport.java:76)
	at ✽.Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2@qa.qa-test"(file:Features/Atom/Mail/AdviceMail.feature:67)

And Wait "120" seconds 000ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Weryfikacja danych awizacji" 000ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.cleanUserDetailsAfterTest() 009ms

Error message

java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <401>.

	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.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy:179)
	at io.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.putObjectToApolloApi(RestUtil.java:92)
	at CucumberTests.Hooks.cleanUserDetailsAfterTest(Hooks.java:304)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

After Hooks.rollbackVerificationEmailSettingAfterTest() 004ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating a new auction

Steps

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Nowa aukcja" 25s 535ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

After Hooks.cleanUserDetailsAfterTest() 190ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing auction

Steps

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

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

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Nie otrzymano zlecenia" 19s 350ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

After Hooks.cleanUserDetailsAfterTest() 200ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after bid has been added to auction

Steps

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

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

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

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

And Wait till auction end 1m 58s 022ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Dodano nową ofertę" 7s 587ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

After Hooks.cleanUserDetailsAfterTest() 273ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after auction without bids

Steps

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

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

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

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

And Wait till auction end 1m 58s 022ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Aukcja zakończona bez ofert" 13s 493ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

After Hooks.cleanUserDetailsAfterTest() 182ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing first place in auction

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 576ms

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

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Oferta przelicytowana" 31s 902ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

After Hooks.cleanUserDetailsAfterTest() 178ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after winning an auction

Steps

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

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Otrzymano zlecenie" 2m 19s 888ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

After Hooks.cleanUserDetailsAfterTest() 172ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after accepting minimal price

Steps

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

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Otrzymano zlecenie" 7s 253ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

After Hooks.cleanUserDetailsAfterTest() 221ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail two hours before auction ends

Steps

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

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

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

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

Error message

java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <422>.

	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.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy:175)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:64)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuction(AuctionTransport.java:52)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuctionByApiWith(AuctionTransport.java:69)
	at ✽.Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes(file:Features/Atom/Mail/AuctionMail.feature:103)

And Wait "90" seconds 000ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zakończenie aukcji" 000ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

After Hooks.cleanUserDetailsAfterTest() 189ms

View Feature Discrepancy Report Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

And Go to "TRANSPORT_TABLE" 142ms

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

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

And Fill transport form 35s 869ms

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

And Fill discrepancy report section 35s 701ms

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

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

And Generate discrepancy report 18s 834ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Utworzono protokół niezgodności" 3m 12s 799ms

Then Check if user got a mail 000ms

Error message

java.lang.AssertionError: Użytkownik nie otrzymał maila. Actual: 
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failEquals(Assert.java:185)
	at org.junit.Assert.assertNotEquals(Assert.java:161)
	at CucumberTests.Mail.MailTest.checkIfUseGotMail(MailTest.java:39)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/DiscrepancyReportMail.feature:18)

Hooks

After Hooks.deleteTransportAfterTest() 124ms

After Hooks.cleanUserDetailsAfterTest() 354ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackAddedAuthorities

Scenario Outline Check if mail was sent to after transport delay

Steps

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

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

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

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

And Go to "WAREHOUSE_TAB" 840ms

And Select warehouse "Serownia" 1s 403ms

And Set week view 1s 097ms

And Show yesterday 1s 070ms

And Move window into the past 293ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "spóźnił się na" 31s 768ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

After Hooks.cleanUserDetailsAfterTest() 292ms

After Hooks.rollbackAddedAuthorities() 048ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Steps

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Drobnica import" 1m 469ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

After Hooks.cleanUserDetailsAfterTest() 240ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Steps

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Drobnica eksport" 42s 747ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

After Hooks.cleanUserDetailsAfterTest() 238ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zlecenie czeka na akceptację" 18s 890ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

After Hooks.cleanUserDetailsAfterTest() 194ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zostało przekazane nowe zlecenie" 6s 551ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

After Hooks.cleanUserDetailsAfterTest() 186ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

And Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 157ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zlecenie czeka na akceptację" 6s 628ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

After Hooks.cleanUserDetailsAfterTest() 271ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing inquiry

Steps

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

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

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

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

Error message

java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <422>.

	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.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy:175)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:64)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuction(AuctionTransport.java:52)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuctionByApi(AuctionTransport.java:61)
	at ✽.Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz"(file:Features/Atom/Mail/TransportTransferMail.feature:44)

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

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

Then If user is login then logout 000ms

And Login as "swisskrono-admin" 000ms

And Go to auction details 000ms

And Pass transport to carrier from auction details 000ms

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nie otrzymano zlecenia" 000ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

After Hooks.cleanUserDetailsAfterTest() 247ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating new inquiry

Steps

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

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

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

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

Error message

java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <422>.

	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.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy:175)
	at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.postObjectToApolloApi(RestUtil.java:64)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuction(AuctionTransport.java:52)
	at CucumberTests.Transport.AuctionTransport.setTransportOnAuctionByApi(AuctionTransport.java:61)
	at ✽.Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz"(file:Features/Atom/Mail/TransportTransferMail.feature:62)

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nowe zapytanie ofertowe" 000ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

After Hooks.cleanUserDetailsAfterTest() 205ms

View Feature Pallet limit

@deleteTransportAfterTest

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

Steps

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

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

When Go to new transport "DELIVERY" 15s 284ms

And Fill transport form 41s 020ms

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

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

And Set advice window in schedule 2s 180ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

View Feature Pallet limit

@deleteTransportAfterTest

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

Steps

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

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

And Go to "TRANSPORT_TABLE" 283ms

And Show all transport "false" 006ms

And Go to transport details "DELIVERY" 32s 461ms

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

And Click "save-transport" save button 714ms

Then Verify that the error is visible after exceeding the pallet limit 15s 067ms

Error message

java.lang.AssertionError: Komunikat: Limit awizacji w harmonogramie w dniu 29.04.2021 został przekroczony. Proszę wybrać inną datę awizacji.
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.MaxPallet.MaxPalletTest.verifyThatTheErrorIsVisibleAfterExceedingThePalletLimit(MaxPalletTest.java:23)
	at ✽.Verify that the error is visible after exceeding the pallet limit(file:Features/Atom/MaxPallet/MaxPallet.feature:27)

Hooks

After Hooks.deleteTransportAfterTest() 159ms

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]

Steps

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

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

And Set status of MOT to "AWAITING_VERIFICATION" 066ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 265ms

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

When Login as "super-admin-bausch" 2s 176ms

And Go to "TRANSPORT_TABLE" 213ms

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

And Set advice window in schedule 2s 772ms

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

Hooks

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.deleteModeOfTransportationAfterTest() 081ms

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]

Steps

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

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

And Set status of MOT to "DISABLED" 076ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 197ms

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

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

And Go to "TRANSPORT_TABLE" 223ms

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

And Set advice window in schedule 2s 823ms

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

Hooks

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.deleteModeOfTransportationAfterTest() 086ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Set status of MOT to "ACCEPTED" 086ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 197ms

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

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

And Go to "TRANSPORT_TABLE" 213ms

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

And Set advice window in schedule 2s 730ms

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

Hooks

After Hooks.deleteTransportAfterTest() 084ms

After Hooks.deleteModeOfTransportationAfterTest() 080ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Set status of MOT to "UPDATED" 074ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 275ms

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

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

And Go to "TRANSPORT_TABLE" 214ms

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

And Set advice window in schedule 2s 816ms

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

Hooks

After Hooks.deleteTransportAfterTest() 075ms

After Hooks.deleteModeOfTransportationAfterTest() 061ms

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]

Steps

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

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

And Set status of MOT to "REJECTED" 063ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 236ms

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

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

And Go to "TRANSPORT_TABLE" 208ms

And Click button advice in transport table "LOAD_PL" 075ms

And Set advice window in schedule 2s 806ms

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

And Check if "AAAA0000" MOT cannot be selected in advice form 077ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

After Hooks.deleteModeOfTransportationAfterTest() 074ms

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]

Steps

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

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

And Set status of MOT to "BLOCKED" 062ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 219ms

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

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

And Go to "TRANSPORT_TABLE" 230ms

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

And Set advice window in schedule 2s 833ms

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

And Check if "AAAA0000" MOT cannot be selected in advice form 094ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.deleteModeOfTransportationAfterTest() 070ms

View Feature SK Api - Statuses confirmation

@deleteTransportAfterTest

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

Steps

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

When Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 002ms

And Add transport by SKApi in "MGW" 228ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 54s 917ms

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

And Set advice window in schedule 2s 649ms

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

And Fill advice form 14s 621ms

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

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

And Confirm statuses until reach "left-the-factory" through SKAPI 5m 16s 704ms

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

Hooks

After Hooks.deleteTransportAfterTest() 188ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 002ms

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

When Add transport by SKApi in "MGW" 003ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 51s 306ms

And Go to "TRANSPORT_TABLE" 106ms

And Go to transport details "TRANSPORT_ORDER" 4s 448ms

Then Check are transport values equals 371ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

Given Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 002ms

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

When Add transport by SKApi in "MGW" 003ms

Then Check is transport "CONTAINER" created in transport table and set transport id 54s 403ms

And Go to "TRANSPORT_TABLE" 103ms

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

Then Check are transport values equals 388ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 002ms

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

When Add transport by SKApi in "MGW" 003ms

Then Check is transport "OWN_COLLECTION" created in transport table and set transport id 51s 464ms

And Go to "TRANSPORT_TABLE" 143ms

And Go to transport details "OWN_COLLECTION" 4s 450ms

Then Check are transport values equals 357ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 002ms

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

When Add transport by SKApi in "HRL" 002ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 51s 881ms

And Go to "TRANSPORT_TABLE" 125ms

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

Then Check are transport values equals 372ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

Given Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 002ms

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

When Add transport by SKApi in "HRL" 003ms

Then Check is transport "CONTAINER" created in transport table and set transport id 54s 410ms

And Go to "TRANSPORT_TABLE" 133ms

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

Then Check are transport values equals 391ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 003ms

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

When Add transport by SKApi in "HRL" 003ms

Then Check is transport "OWN_COLLECTION" created in transport table and set transport id 54s 565ms

And Go to "TRANSPORT_TABLE" 100ms

And Go to transport details "OWN_COLLECTION" 4s 454ms

Then Check are transport values equals 415ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 003ms

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

And Set another client name "Pepsi" 000ms

When Add transport by SKApi in "MGW" 002ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 51s 901ms

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

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 003ms

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

When Add transport by SKApi in "" 002ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 1m 328ms

And Go to "TRANSPORT_TABLE" 113ms

And Go to transport details "TRANSPORT_ORDER" 4s 448ms

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

Hooks

After Hooks.deleteTransportAfterTest() 096ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

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.

Steps

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

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

And Add transport by SKApi in "MGW" 002ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "CONTAINER" created in transport table and set transport id 54s 400ms

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

And Set advice window in schedule 2s 727ms

And Fill advice form 14s 603ms

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

And Go to "TRANSPORT_TABLE" 221ms

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

Then Check are advice values equals 2s 290ms

Hooks

After Hooks.deleteTransportAfterTest() 159ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

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.

Steps

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

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

And Add transport by SKApi in "MGW" 002ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 347ms

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

And Set advice window in schedule 2s 611ms

And Fill advice form 14s 575ms

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

And Go to "TRANSPORT_TABLE" 189ms

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

Then Check are advice values equals 2s 307ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

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.

Steps

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

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

And Add transport by SKApi in "MGW" 002ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 001ms

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

When Click button advice in transport table "TRANSPORT_ORDER" 087ms

And Set advice window in schedule 2s 540ms

And Fill advice form 14s 644ms

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

And Go to "TRANSPORT_TABLE" 215ms

And Go to transport details "TRANSPORT_ORDER" 4s 465ms

Then Check are advice values equals 2s 317ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

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.

Steps

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

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

And Add transport by SKApi in "MGW" 085ms

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

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 381ms

When Click button advice in transport table "OWN_COLLECTION" 083ms

And Set advice window in schedule 2s 590ms

And Fill advice form 14s 593ms

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

And Go to "TRANSPORT_TABLE" 208ms

Then Check advice data in SK API database "OWN_COLLECTION" 3s 173ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

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.

Steps

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

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

And Add transport by SKApi in "MGW" 002ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "CONTAINER" created in transport table and set transport id 6s 344ms

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

And Set advice window in schedule 2s 584ms

And Fill advice form 14s 627ms

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

And Go to "TRANSPORT_TABLE" 186ms

Then Check advice data in SK API database "CONTAINER" 3s 098ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

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.

Steps

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

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

And Add transport by SKApi in "MGW" 002ms

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 6s 844ms

When Click button advice in transport table "TRANSPORT_ORDER" 086ms

And Set advice window in schedule 2s 605ms

And Fill advice form 14s 503ms

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

And Go to "TRANSPORT_TABLE" 247ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 4s 040ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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

Steps

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

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

And Add transport by SKApi in "MGW" 003ms

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

And Check is transport "CONTAINER" created in transport table and set transport id 6s 331ms

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

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

And Fill advice form 14s 675ms

And Click advice save button to check error message 092ms

Then Check if possible advice alert is displayed 018ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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.

Steps

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

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

And Add transport by SKApi in "MGW" 002ms

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

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 42s 497ms

And Create advice "CREATE_ADVICE" "OWN_COLLECTION" "super-admin-skz" 48s 020ms

And Go to "TRANSPORT_TABLE" 199ms

When Go to transport details "OWN_COLLECTION" 4s 468ms

And Expand advice panel 126ms

And Edit advice in transport details 14s 004ms

And Fill arrival date field 2s 304ms

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

Then Check advice data in database after edition "OWN_COLLECTION" 038ms

Hooks

After Hooks.deleteTransportAfterTest() 148ms

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.

Steps

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

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

And Add transport by SKApi in "MGW" 002ms

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

And Check is transport "CONTAINER" created in transport table and set transport id 33s 444ms

And Create advice "CREATE_ADVICE" "CONTAINER" "super-admin-skz" 48s 063ms

And Go to "TRANSPORT_TABLE" 173ms

When Go to transport details "CONTAINER" 4s 493ms

And Expand advice panel 108ms

And Edit advice in transport details 13s 946ms

And Fill arrival date field 2s 286ms

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

Then Check advice data in database after edition "CONTAINER" 025ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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.

Steps

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

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

And Add transport by SKApi in "MGW" 002ms

And Get inputs from database "EDIT_ADVICE" "super-admin-skz" 001ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 48s 331ms

And Create advice "CREATE_ADVICE" "TRANSPORT_ORDER" "super-admin-skz" 48s 040ms

And Go to "TRANSPORT_TABLE" 237ms

When Go to transport details "TRANSPORT_ORDER" 4s 474ms

And Expand advice panel 112ms

And Edit advice in transport details 13s 911ms

And Fill arrival date field 2s 283ms

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

Then Check advice data in database after edition "TRANSPORT_ORDER" 035ms

Hooks

After Hooks.deleteTransportAfterTest() 158ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

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

And Create "CREATE_GRAY_WINDOW_TWG" window by JSON file for test as "super-admin-hochland" 238ms

And Create "CREATE_GRAY_WINDOW_OST" window by JSON file for test as "super-admin-hochland" 045ms

When Go to "WAREHOUSE_TAB" 811ms

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

And Select view "DAYS_2" 2s 084ms

Then Check if gray window is in the schedule 2s 021ms

And Select warehouse "Opakowania, surowce twarożkarnia" 1s 268ms

And Select view "DAYS_2" 2s 049ms

And Check if gray window is in the schedule 2s 015ms

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 161ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

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

And Create "CREATE_GRAY_WINDOW_TWG" window by JSON file for test as "super-admin-hochland" 037ms

And Create "CREATE_GRAY_WINDOW_OST" window by JSON file for test as "super-admin-hochland" 034ms

When Go to "WAREHOUSE_TAB" 734ms

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

And Select view "DAYS_2" 2s 077ms

Then Check if gray window is in the schedule 2s 024ms

And Select warehouse "Opakowania, surowce twarożkarnia" 1s 254ms

And Select view "DAYS_2" 2s 043ms

And Check if gray window is in the schedule 2s 015ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 158ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

Given Login as "pha1-carrier@qa.qa-test" and set token of apiUsername "super-admin-hochland" 2s 769ms

And Create "CREATE_GRAY_WINDOW_TWG" window by JSON file for test as "super-admin-hochland" 035ms

And Create "CREATE_GRAY_WINDOW_OST" window by JSON file for test as "super-admin-hochland" 038ms

When Go to "WAREHOUSE_TAB" 749ms

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

And Select view "DAYS_2" 2s 074ms

Then Check if gray window is in the schedule 2s 019ms

And Select warehouse "Opakowania, surowce twarożkarnia" 1s 280ms

And Select view "DAYS_2" 2s 052ms

And Check if gray window is in the schedule 2s 013ms

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 161ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

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

And Create "CREATE_GRAY_WINDOW_MGW" window by JSON file for test as "super-admin-skz" 034ms

And Create "CREATE_GRAY_WINDOW_HRL" window by JSON file for test as "super-admin-skz" 042ms

When Go to "WAREHOUSE_TAB" 449ms

And Select warehouse "MGW" 1s 179ms

And Select view "DAYS_2" 2s 077ms

Then Check if gray window is in the schedule 2s 023ms

And Select warehouse "HRL" 1s 368ms

And Select view "DAYS_2" 2s 053ms

And Check if gray window is in the schedule 2s 016ms

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 172ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 144ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 109ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 124ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

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

Then Check if transport has "departed" 028ms

Hooks

After Hooks.deleteTransportAfterTest() 170ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 123ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 110ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 113ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

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

And Set advice window in schedule 2s 849ms

And Fill advice form 14s 557ms

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

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

And Go to "TRANSPORT_TABLE" 199ms

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

Hooks

After Hooks.deleteTransportAfterTest() 126ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

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

And Set advice window in schedule 2s 835ms

And Fill advice form 14s 610ms

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

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

And Go to "TRANSPORT_TABLE" 194ms

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

Hooks

After Hooks.deleteTransportAfterTest() 126ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackAddedActionAuthorities

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

Steps

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

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 148ms

After Hooks.rollbackAddedActionAuthorities() 067ms

View Feature Status confirmation

@deleteTransportAfterTest

Scenario Outline Check is transport color changed after confirm status

Steps

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

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

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

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

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

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

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

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

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

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

And Confirm statuses until reach "process-ended" 4s 256ms

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

Hooks

After Hooks.deleteTransportAfterTest() 121ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

And Show all transport types 1s 048ms

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

And Set advice window in schedule 2s 608ms

And Fill advice form 8s 322ms

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

And Go to "TRANSPORT_TABLE" 211ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 113ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

And Show all transport types 1s 045ms

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

And Set advice window in schedule 2s 594ms

And Fill advice form 8s 310ms

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

And Go to "TRANSPORT_TABLE" 206ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

And Show all transport types 1s 041ms

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

And Set advice window in schedule 2s 586ms

And Fill advice form 8s 326ms

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

And Go to "TRANSPORT_TABLE" 232ms

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

When Add file to transport by API 637ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 121ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

And Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 596ms

And Fill advice form 8s 311ms

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

And Go to "TRANSPORT_TABLE" 211ms

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

When Add file to transport by API 250ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 123ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

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

And Login as "swiss-krono-delivery-guard" 2s 301ms

And Go to "TRANSPORT_TABLE" 176ms

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

Then Verify that "Departure" has been confirmed 028ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline Check if it is possible to confirm status with given confirmation date [A-7159]

Steps

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

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

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 15s 233ms

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

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

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

And Go to "TRANSPORT_TABLE" 219ms

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

When Confirm statuses until reach "on-the-way" 9s 817ms

And Open statuses popup 069ms

And Toggle status date confirmation checkbox 274ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 130ms

After Hooks.deleteModeOfTransportationAfterTest() 087ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline Check if it is not possible to confirm status with invalid confirmation date [A-7159]

Steps

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

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 210ms

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

When Confirm statuses until reach "on-the-way" 9s 311ms

And Open statuses popup 071ms

And Toggle status date confirmation checkbox 277ms

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

Then Verify that status cannot be confirmed 1s 076ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

After Hooks.deleteModeOfTransportationAfterTest() 075ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline Check if it is not possible to confirm status with invalid confirmation date [A-7159]

Steps

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

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

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

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

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

And Login as "bausch-admin" 968ms

And Go to "TRANSPORT_TABLE" 190ms

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

When Confirm statuses until reach "on-the-way" 9s 338ms

And Open statuses popup 065ms

And Toggle status date confirmation checkbox 273ms

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

Then Verify that status cannot be confirmed 1s 083ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

After Hooks.deleteModeOfTransportationAfterTest() 083ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackTaskChanges

Scenario Outline Confirmed statuses of existing orders should not be deleted - even after editing the order [A-6874]

Steps

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 234ms

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

And Set actual confirmed transport status list 1s 379ms

And Disable task by API 047ms

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

And Edit transport hours and recalculate statuses 16s 287ms

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

Hooks

After Hooks.deleteTransportAfterTest() 149ms

After Hooks.rollbackTaskChanges() 044ms

View Feature Status rejection

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it is possible to reject status by guard in transport table

Steps

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

And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 261ms

And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 1s 825ms

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

And Check if reject date is not visible 15s 032ms

When Reject status: Book of disinfection 076ms

And Check if reject date is visible 361ms

Then If user is login then logout 075ms

And Login as "lantmannen-admin" 1s 076ms

And Check if note was added to transport after status rejection 1s 226ms

And Check if history note was added to transport after status rejection - "LOAD" 5s 471ms

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nieaktualna księga mycia i dezynfekcji" 16s 617ms

And Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

After Hooks.cleanUserDetailsAfterTest() 173ms

View Feature Status rejection

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject status twice and reject date is changing

Steps

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

And Create transport "CREATE_LOAD_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 334ms

And Check if reject date is not visible 15s 008ms

When Reject status: Book of disinfection 080ms

And Check if reject date is visible 151ms

And Get rejection date 032ms

And Wait "60" seconds 1m

And Reject status: Book of disinfection 063ms

Then Check if reject date has changed 1s 079ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature Status rejection

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject status by admin in transport form

Steps

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

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

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

And Check if reject date is not visible 15s 047ms

When Reject status: Book of disinfection 082ms

Then Check if reject date is visible 153ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

View Feature Status rejection

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject status by admin in statuses popup

Steps

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

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

And Open statuses popup 094ms

And Check if reject date is not visible 15s 040ms

When Reject status: Book of disinfection 083ms

Then Open statuses popup 057ms

And Check if reject date is visible 089ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

View Feature Status revocation

@deleteTransportAfterTest

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

Steps

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

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

And Confirm to the last status by API 206ms

When Find statuses for transport in table 1s 994ms

And Revoke statuses until reach "advice-added" 6s 797ms

Then Check if transport has "advice-added" 026ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature Status revocation

@deleteTransportAfterTest

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

Steps

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

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

And Confirm to the last status by API 174ms

When Find statuses for transport in table 1s 731ms

And Revoke statuses until reach "planned" 6s 712ms

Then Check if transport has "planned" 026ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

View Feature Status

@deleteTransportAfterTest

Scenario Outline Check if after created transport without advice, transport has checkpoints only from "preparation" section

Steps

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

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

When Find transport in table with status "new" 3s 208ms

And Open statuses popup 092ms

Then Check if transport has checkpoints from list "Utworzenie zlecenia,Dodanie awizacji,Potwierdzenie okna czasowego" in "0" 070ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

View Feature Status

@deleteTransportAfterTest

Scenario Outline Check if after added advice, checkpoints are generated from "steps" section

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 039ms

And Get inputs from database "ADVICE_EXTERNAL_DELIVERY" "super-admin-farmacol" 002ms

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

And Click button advice in transport table "EXTERNAL_DELIVERY" 118ms

And Set advice window in schedule 2s 732ms

And Fill advice form 11s 954ms

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

And Go to "TRANSPORT_TABLE" 242ms

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

And Open statuses popup 085ms

Then Check if transport has checkpoints from list "Zgłoszenie kierowcy,Rozpoczęcie rozładunku,Zakończenie rozładunku" in "1" 073ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

View Feature Status

@deleteTransportAfterTest @rollbackTaskChanges

Scenario Outline Check if deleted task is not in new transports' workflow @A-6875

Steps

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 204ms

And Confirm statuses until reach "registered-katowice-przyjęcia" 6s 588ms

And Disable task by API 046ms

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

And Click pencil and move transport to next day in schedule 18s 601ms

And Go to "TRANSPORT_TABLE" 201ms

Then Verify that "START_OF_UNLOADING" is not visible 131ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

After Hooks.rollbackTaskChanges() 039ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past

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

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

When Go to "WAREHOUSE_TAB" 813ms

And Select warehouse "Serownia" 1s 400ms

And Set week view 1s 122ms

And Show yesterday 1s 063ms

And Move window into the past 300ms

Then Check if window is "red" 2s 023ms

Hooks

After Hooks.deleteTransportAfterTest() 139ms

After Hooks.rollbackAddedAuthorities() 069ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if time window turns red when moved into the past

Steps

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

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

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "lantmannen-admin" 051ms

When Go to "WAREHOUSE_TAB" 585ms

And Select warehouse "Magazyn - Nowa Sól" 2s 120ms

And Set week view 1s 099ms

And Show yesterday 1s 050ms

And Move window into the past 416ms

Then Check if window is "red" 2s 029ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

After Hooks.rollbackAddedAuthorities() 032ms

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

Steps

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

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

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "piast-admin" 043ms

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

When Show all transport types 1s 048ms

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

And Set advice window in schedule 2s 649ms

And Fill advice form 8s 390ms

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

And Select warehouse "Magazyn Hala A" 1s 196ms

And Set week view 2s 020ms

And Show yesterday 1s 165ms

And Move window into the past 538ms

Then Check if window is "red" 2s 055ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

After Hooks.rollbackAddedAuthorities() 033ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if time window resize with restriction to algorithm settings

Steps

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

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

And Set algorithm setting for "super-admin-hochland" in "Magazyn Zimny Kaźmierz" on "Magazyn Zimny" 440ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 407ms

When Go to "WAREHOUSE_TAB" 792ms

And Select warehouse "Magazyn Zimny Kaźmierz" 1s 689ms

And Set week view 1s 119ms

And Check if time window length is correct after "CREATE" 030ms

And Change number of pallets in transport 50s 629ms

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

And Check if time window length is correct after "EDIT" 040ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackTransportTypeSettings

Scenario Outline Check if time window has valid length with restriction to algorithm settings when quantity is set in transport form

Steps

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

And Get "UNLOAD" settings from "keeeper" 072ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 106ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;true" 106ms

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

When Go to "WAREHOUSE_TAB" 352ms

And Select warehouse "Magazyn Surowców" 1s 214ms

And Set week view 1s 094ms

Then Check if time window has proper "60" 024ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

After Hooks.rollbackTransportTypeSettings() 058ms

After Hooks.clearAlgorithmSettings() 133ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackTransportTypeSettings

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

Steps

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

And Get "UNLOAD" settings from "keeeper" 031ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 108ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;false" 057ms

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

When Go to "WAREHOUSE_TAB" 323ms

And Select warehouse "Magazyn Surowców" 1s 161ms

And Set week view 1s 090ms

Then Check if time window has proper "60" 021ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

After Hooks.rollbackTransportTypeSettings() 057ms

After Hooks.clearAlgorithmSettings() 096ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackTransportTypeSettings

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

Steps

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

And Get "LOAD" settings from "keeeper" 026ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 092ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;false" 052ms

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

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

And Show all transport types 1s 046ms

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

And Set advice window in schedule 2s 473ms

And Fill advice form 13s 179ms

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

Then Check if time window has proper "30" 027ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

After Hooks.rollbackTransportTypeSettings() 102ms

After Hooks.clearAlgorithmSettings() 079ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackTransportTypeSettings

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

Steps

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

And Get "CONTAINER" settings from "keeeper" 029ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 089ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "20;false" 063ms

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

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

And Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 451ms

And Fill advice form 13s 182ms

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

Then Check if time window has proper "60" 027ms

Hooks

After Hooks.deleteTransportAfterTest() 142ms

After Hooks.rollbackTransportTypeSettings() 054ms

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

Steps

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

And Set algorithm setting for "super-admin-hochland" in "Serownia" on "Magazyn Sera" 134ms

And Set token of apiUsername "dha1-supplier-2@qa.qa-test" 118ms

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

And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "super-admin-hochland" 1s 233ms

When Go to transport details "DELIVERY" 32s 641ms

And Change filled value in transport details "quantity" "number" "25" "0" 1s 346ms

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

And Go to "WAREHOUSE_TAB" 780ms

And Select warehouse "Serownia" 1s 374ms

And Set week view 1s 096ms

Then Check if time window has proper "60" 028ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

After Hooks.clearAlgorithmSettings() 153ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedAuthorities

Scenario Outline Check if window counter value in schedule changes

Steps

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

And Set basic authorities "ROLE_ACCESS_TO_NUMBER_OF_WINDOWS" to user "keeeper-admin" 044ms

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

When Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 46s 479ms

And Check if time window counter value equals "1" 076ms

And Select view "DAYS_2" 2s 085ms

And Move advice window "2" 1s 326ms

And Select view "DAY" 2s 082ms

Then Check if time window counter value equals "0" 069ms

And Delete created transport by API 161ms

And Check if time window counter value equals "0" 032ms

And Click in free spot in schedule page to create gray window 148ms

And Check if time window counter value equals "0" 037ms

And Click in free spot in schedule page to create dedicated window 044ms

And Check if time window counter value equals "0" 034ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

After Hooks.rollbackAddedAuthorities() 000ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-adama" 001ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 110ms

When Go to new transport "DELIVERY" 271ms

And Fill transport form 11s 474ms

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

And Set advice window in schedule 2s 171ms

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

And Go to "TRANSPORT_TABLE" 231ms

When Click on time window date 1s 315ms

And Open transport form when in schedule 1s 159ms

Then Check are transport values equals 151ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 450ms

When Go to new transport "DELIVERY" 365ms

And Fill transport form 38s 797ms

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

And Set advice window in schedule 2s 157ms

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

And Go to "TRANSPORT_TABLE" 234ms

When Click on time window date 1s 253ms

And Open transport form when in schedule 1s 224ms

Then Check are transport values equals 19s 349ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_CISTERN_DELIVERY" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 573ms

When Go to new transport "CISTERN_DELIVERY" 381ms

And Fill transport form 34s 939ms

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

And Set advice window in schedule 2s 187ms

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

And Go to "TRANSPORT_TABLE" 210ms

When Click on time window date 1s 413ms

And Open transport form when in schedule 1s 173ms

Then Check are transport values equals 21s 399ms

Hooks

After Hooks.deleteTransportAfterTest() 150ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_CISTERN_COLLECTION" "super-admin-hochland" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 592ms

When Go to new transport "CISTERN_COLLECTION" 302ms

And Fill transport form 28s 327ms

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

And Set advice window in schedule 2s 221ms

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

And Go to "TRANSPORT_TABLE" 166ms

When Click on time window date 1s 416ms

And Open transport form when in schedule 1s 220ms

Then Check are transport values equals 21s 341ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-lantmannen" 002ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 450ms

When Go to new transport "DELIVERY" 285ms

And Fill transport form 37s 938ms

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

And Set advice window in schedule 2s 165ms

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

And Go to "TRANSPORT_TABLE" 196ms

When Click on time window date 1s 329ms

And Open transport form when in schedule 1s 151ms

Then Check are transport values equals 19s 325ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-lantmannen" 003ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 128ms

When Go to new transport "LOAD" 270ms

And Fill transport form 37s 901ms

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

And Set advice window in schedule 2s 175ms

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

And Go to "TRANSPORT_TABLE" 243ms

When Click on time window date 1s 360ms

And Open transport form when in schedule 1s 161ms

Then Check are transport values equals 19s 308ms

Hooks

After Hooks.deleteTransportAfterTest() 143ms

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

Steps

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

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 087ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 054ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 086ms

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

And Login as "farmacol-admin" 2s 592ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 45s 620ms

And Go to "TRANSPORT_TABLE" 314ms

When Go to transport details "EXTERNAL_DELIVERY" 4s 437ms

And Add step "unload" 111ms

And Change filled value in transport details "warehouse-select-step-2" "select" "Mory Przyjęcia" "0" 3s 447ms

And Change filled value in transport details "weight-step-2" "number" "23" "0" 1s 350ms

And Change filled value in transport details "number-of-pallets-step-2" "number" "23" "0" 1s 360ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 311ms

Then Click "save-transport" save button 179ms

And Set advice window in schedule in "2" days 4s 985ms

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

And Go to "TRANSPORT_TABLE" 254ms

And Check if transport has "2" time windows 012ms

Hooks

After Hooks.deleteTransportAfterTest() 141ms

After Hooks.rollbackTransportTypeSettings() 121ms

After Hooks.rollbackAddedActionAuthorities() 047ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest

Scenario Outline Check if window changes color properly in transport table

Steps

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

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 037ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 058ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 205ms

And Set double window advice 000ms

And Login as "farmacol-admin" 2s 042ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 795ms

And Go to "TRANSPORT_TABLE" 341ms

And Get checkpoint colors for transport 004ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "true" 42s 071ms

Hooks

After Hooks.deleteTransportAfterTest() 171ms

After Hooks.rollbackTransportTypeSettings() 089ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest

Scenario Outline Check if window changes color properly in transport table

Steps

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

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 039ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 059ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 248ms

And Set double window advice 000ms

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

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 945ms

And Go to "TRANSPORT_TABLE" 303ms

And Get checkpoint colors for transport 005ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "false" 42s 023ms

Hooks

After Hooks.deleteTransportAfterTest() 148ms

After Hooks.rollbackTransportTypeSettings() 083ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest

Scenario Outline Check if window changes color properly in schedule

Steps

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

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 032ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 067ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 201ms

And Set double window advice 000ms

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

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 783ms

And Get checkpoint colors for transport 004ms

And Go to "TRANSPORT_TABLE" 317ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true" 5s 589ms

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.verifyThatTransportColorsOfWindowsChangeProperlyInScheduleWhenWindowColorDependsOnWarehouseIs(TimeWindowTest.java:118)
	at ✽.Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true"(file:Features/Atom/TimeWindow/TransportWindow.feature:247)

Hooks

After Hooks.deleteTransportAfterTest() 166ms

After Hooks.rollbackTransportTypeSettings() 154ms

View Feature TransportWindow atom tests

@rollbackTransportTypeSettings @deleteTransportAfterTest

Scenario Outline Check if window changes color properly in schedule

Steps

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

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 030ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 055ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 15s 154ms

And Set double window advice 000ms

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

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 920ms

And Get checkpoint colors for transport 006ms

And Go to "TRANSPORT_TABLE" 297ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "false" 31s 978ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

After Hooks.rollbackTransportTypeSettings() 071ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if window is active after using "create similar" on that window [A-7009]

Steps

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

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

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

And Login as "super-admin-farmacol" 2s 661ms

And Show all transport types 1s 150ms

And Click on time window date 1s 641ms

Then Open transport form when in schedule 1s 272ms

And Click create similar button 15s 141ms

And Click cancel button in transport form 110ms

And Open transport form when in schedule 1s 185ms

Then Check if transport form modal is visible 040ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Move transport to archive

@rollbackSettings @deleteTransportAfterTest

Scenario Outline Check if delayed transport is moved to archived and can be restored

Steps

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

And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 002ms

And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 023ms

And Set proper delay time to move order to archive after task timeout 066ms

When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 331ms

And Go to "WAREHOUSE_TAB" 702ms

And Change warehouse in schedule to: "Katowice" 1s 090ms

And Wait "60" seconds 1m

And Verify that transport window is grey 034ms

And Verify that transport is in archive 1s 159ms

Then Restore transport from archive 1s 103ms

And Verify that transport has been successfully restored 15s 320ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

After Hooks.rollbackSettings() 026ms

View Feature Move transport to archive

@deleteTransportAfterTest @rollbackSettings

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

Steps

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

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

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

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

When Go to "TRANSPORT_TABLE" 138ms

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

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 40s 191ms

And Go to "TRANSPORT_TABLE" 230ms

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

And Confirm statuses until reach "process-ended" 24s 284ms

And Wait "12" seconds 12s

Then Go to "ARCHIVE_TAB" 267ms

And Show "OWN_COLLECTION" 078ms

And Verify that created transport is "true" in transport table 15s 049ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

After Hooks.rollbackSettings() 026ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to create new auction in transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 032ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 259ms

When Fill auction form 15s 503ms

Then Verify that the auction has been added to transport 054ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to create new auction in transport

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 300ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 236ms

When Fill auction form 15s 407ms

Then Verify that the auction has been added to transport 053ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept auction offer with minimum rate

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 154ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 232ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 105ms

When If user is login then logout 097ms

And Login as "paa1-carrier@qa.qa-test" 2s 442ms

And Go to auction offer 1s 273ms

And Accept transport with minimum rate 15s 610ms

Then Check if carrier is assigned to transport 017ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject auction offer

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 064ms

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 099ms

When If user is login then logout 227ms

And Login as "paa1-carrier@qa.qa-test" 1s 151ms

And Go to auction offer 1s 228ms

And Reject auction offer 15s 587ms

Then Verify that offer has been removed from transport 15s 015ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject auction offer

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 218ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 269ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 116ms

When If user is login then logout 253ms

And Login as "pskza1-carrier@qa.qa-test" 1s 035ms

And Go to auction offer 1s 221ms

And Reject auction offer 15s 610ms

Then Verify that offer has been removed from transport 15s 054ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add offer above maximum rate

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 113ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 223ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 106ms

When If user is login then logout 248ms

And Login as "paa1-carrier@qa.qa-test" 1s 083ms

And Go to auction offer 1s 215ms

And Offer prize above maximum - "20000" 140ms

Then Verify that is not possible to add offer 152ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add offer above maximum rate

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 143ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 236ms

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 104ms

And Login as "pskza1-carrier@qa.qa-test" 1s 271ms

And Go to auction offer 1s 196ms

And Offer prize above maximum - "20000" 125ms

Then Verify that is not possible to add offer 134ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add auction again after previous auction end

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 021ms

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 097ms

And Wait till auction end 1m 58s 018ms

Then Verify that is possible to add auction 052ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add auction again after previous auction end

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 258ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 282ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 129ms

And Wait till auction end 1m 58s 017ms

Then Verify that is possible to add auction 050ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add valid offer

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 709ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 236ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 093ms

And Go to auction offer 1s 231ms

When Offer "1000" 127ms

Then Verify that offer with "1000" has been added to auction 3s 035ms

Hooks

After Hooks.deleteTransportAfterTest() 328ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add valid offer

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 517ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 229ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 096ms

And Go to auction offer 1s 186ms

When Offer "1000" 129ms

Then Verify that offer with "1000" has been added to auction 3s 034ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to revoke an offer

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 032ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 250ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 104ms

And Go to auction offer 1s 200ms

When Offer "1000" 125ms

And Verify that offer with "1000" has been added to auction 3s 034ms

Then Go to auction offer 1s 171ms

And Revoke current offer 572ms

And Verify that offer has been revoked 30s 611ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to offer more than last price

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 131ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 239ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 111ms

And Go to auction offer 1s 203ms

When Offer "1000" 137ms

And Verify that offer with "1000" has been added to auction 3s 039ms

Then Go to auction offer 1s 173ms

And Offer "1500" 131ms

And Verify that offer with "1500" has been added to auction 3s 029ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to finish active auction

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 054ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 226ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 109ms

And Go to auction offer 1s 191ms

When Offer "1000" 146ms

And Verify that offer with "1000" has been added to auction 3s 034ms

Then Login as "swisskrono-admin" 1s 037ms

And Go to auction details 1s 208ms

And Finish active auction 057ms

And Verify that the transport has no active auction 145ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if carrier can see current place in auction depending on the "canSeeCurrentPlaceInAuction" role

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 030ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 213ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 102ms

And Go to auction offer 1s 202ms

When Offer "1000" 135ms

Then Verify that carrier can see current place in auction depending on the "true" role 150ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if carrier can see current place in auction depending on the "canSeeCurrentPlaceInAuction" role

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 090ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 227ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 116ms

And Go to auction offer 1s 199ms

When Offer "1000" 135ms

Then Verify that carrier can see current place in auction depending on the "false" role 15s 056ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it isn't possible to add offer below min price

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 143ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 227ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 108ms

And Go to auction offer 1s 222ms

When Offer "300" 143ms

And Verify that carrier can't add offer to auction 033ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check carrier selection in create auction form

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 069ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 219ms

And Show all transport "false" 012ms

When Go to auction form 1s 255ms

Then Verify carrier selection value "false" 044ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check carrier selection in create auction form

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 051ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 253ms

And Show all transport "true" 077ms

When Go to auction form 1s 190ms

Then Verify carrier selection value "true" 040ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if auction is available to correct participants

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 049ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 246ms

When Open transport auction form 178ms

And Select all companies checkbox in transport auction form 049ms

And Unselect company "PAA2" in transport auction form 075ms

And Put transport on auction 15s 160ms

And Open transport auction history 099ms

And Open participants section in transport auction history 057ms

Then Check if unselected "PAA2" is in transport auction history as participant 15s 042ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if auction is available to correct participants

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 249ms

When Open transport auction form 177ms

And Select all companies checkbox in transport auction form 076ms

And Unselect company "PSKZA2" in transport auction form 070ms

And Put transport on auction 15s 153ms

And Open transport auction history 096ms

And Open participants section in transport auction history 055ms

Then Check if unselected "PSKZA2" is in transport auction history as participant 15s 033ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_UNLOAD" "super-admin-pgf" 002ms

And Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 1s 120ms

When Go to new transport "UNLOAD" 15s 261ms

And Fill transport form 16s 184ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//li//span[text()='Magazyn Rozładunków'] | //li[text()='Magazyn Rozładunków' and @role='option']"}
  (Session info: headless chrome=90.0.4430.72)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.a1iJQ8}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=90.0.4430.72, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: ad7ef55ccd6c049ed315433353249fb9
*** Element info: {Using=xpath, value=//li//span[text()='Magazyn Rozładunków'] | //li[text()='Magazyn Rozładunków' and @role='option']}
	at sun.reflect.GeneratedConstructorAccessor211.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at CucumberTests.Transport.Transport.selectValue(Transport.java:229)
	at CucumberTests.Transport.Transport.fillSelectInput(Transport.java:214)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:166)
	at CucumberTests.Transport.CreateTransport.fillTransportForm(CreateTransport.java:170)
	at ✽.Fill transport form(file:Features/Atom/Transport/CrudTransport.feature:8)

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

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 182ms

When Go to new transport "DELIVERY" 275ms

And Fill transport form 11s 394ms

And Click "save-transport" save button and wait for form to disappear 15s 653ms

And Set advice window in schedule 2s 179ms

And Check is transport created in schedule and set transport id 760ms

And Go to "TRANSPORT_TABLE" 222ms

And Go to transport details "DELIVERY" 4s 340ms

Then Check are transport values equals 156ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 145ms

When Go to new transport "OWN_COLLECTION" 301ms

And Fill transport form 17s 967ms

And Click "save-transport" save button and wait for form to disappear 15s 628ms

And Set advice window in schedule 2s 149ms

And Check is transport created in schedule and set transport id 496ms

And Go to "TRANSPORT_TABLE" 191ms

And Go to transport details "OWN_COLLECTION" 4s 309ms

Then Check are transport values equals 158ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 473ms

When Go to new transport "DELIVERY" 326ms

And Fill transport form 38s 808ms

And Click "save-transport" save button and wait for form to disappear 15s 624ms

And Set advice window in schedule 2s 154ms

And Check is transport created in schedule and set transport id 666ms

And Go to "TRANSPORT_TABLE" 258ms

And Go to transport details "DELIVERY" 4s 652ms

Then Check are transport values equals 19s 381ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_CISTERN_DELIVERY" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 369ms

When Go to new transport "CISTERN_DELIVERY" 329ms

And Fill transport form 34s 881ms

And Click "save-transport" save button and wait for form to disappear 15s 882ms

And Set advice window in schedule 2s 209ms

And Check is transport created in schedule and set transport id 627ms

And Go to "TRANSPORT_TABLE" 202ms

And Go to transport details "CISTERN_DELIVERY" 4s 394ms

Then Check are transport values equals 21s 381ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_CISTERN_COLLECTION" "super-admin-hochland" 001ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 508ms

When Go to new transport "CISTERN_COLLECTION" 326ms

And Fill transport form 28s 294ms

And Click "save-transport" save button and wait for form to disappear 15s 902ms

And Set advice window in schedule 2s 203ms

And Check is transport created in schedule and set transport id 609ms

And Go to "TRANSPORT_TABLE" 184ms

And Go to transport details "CISTERN_COLLECTION" 4s 382ms

Then Check are transport values equals 21s 350ms

Hooks

After Hooks.deleteTransportAfterTest() 155ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 425ms

When Go to new transport "OWN_COLLECTION" 330ms

And Fill transport form 32s 795ms

And Click "save-transport" save button and wait for form to disappear 15s 684ms

And Set advice window in schedule 2s 157ms

And Check is transport created in schedule and set transport id 651ms

And Go to "TRANSPORT_TABLE" 188ms

And Go to transport details "OWN_COLLECTION" 4s 512ms

Then Check are transport values equals 19s 322ms

Hooks

After Hooks.deleteTransportAfterTest() 132ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 524ms

When Go to new transport "OWN_COLLECTION_POWDER_FACTORY" 339ms

And Fill transport form 32s 798ms

And Click "save-transport" save button and wait for form to disappear 15s 705ms

And Set advice window in schedule 2s 171ms

And Check is transport created in schedule and set transport id 705ms

And Go to "TRANSPORT_TABLE" 187ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 454ms

Then Check are transport values equals 4s 321ms

Hooks

After Hooks.deleteTransportAfterTest() 143ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_EXPORT" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 393ms

When Go to new transport "EXPORT" 371ms

And Fill transport form 40s 631ms

And Click "save-transport" save button and wait for form to disappear 15s 577ms

And Set advice window in schedule 2s 154ms

And Check is transport created in schedule and set transport id 649ms

And Go to "TRANSPORT_TABLE" 200ms

And Go to transport details "EXPORT" 5s 452ms

Then Check are transport values equals 4s 355ms

Hooks

After Hooks.deleteTransportAfterTest() 146ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-skd" 003ms

And Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 1s 087ms

When Go to new transport "DELIVERY" 15s 243ms

And Fill transport form 28s 344ms

And Click "save-transport" save button and wait for form to disappear 15s 595ms

And Set advice window in schedule 2s 177ms

And Check is transport created in schedule and set transport id 747ms

And Go to "TRANSPORT_TABLE" 251ms

And Go to transport details "DELIVERY" 32s 344ms

Then Check are transport values equals 36s 372ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-lantmannen" 003ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 123ms

When Go to new transport "DELIVERY" 308ms

And Fill transport form 37s 978ms

And Click "save-transport" save button and wait for form to disappear 15s 627ms

And Set advice window in schedule 2s 160ms

And Check is transport created in schedule and set transport id 580ms

And Go to "TRANSPORT_TABLE" 182ms

And Go to transport details "DELIVERY" 4s 314ms

Then Check are transport values equals 19s 287ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-lantmannen" 002ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 079ms

When Go to new transport "LOAD" 299ms

And Fill transport form 37s 888ms

And Click "save-transport" save button and wait for form to disappear 15s 624ms

And Set advice window in schedule 2s 169ms

And Check is transport created in schedule and set transport id 585ms

And Go to "TRANSPORT_TABLE" 239ms

And Go to transport details "LOAD" 4s 279ms

Then Check are transport values equals 19s 331ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-keeeper" 003ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 190ms

When Go to new transport "UNLOAD" 315ms

And Fill transport form 37s 635ms

And Click "save-transport" save button and wait for form to disappear 15s 582ms

And Set advice window in schedule 2s 157ms

And Check is transport created in schedule and set transport id 541ms

And Go to "TRANSPORT_TABLE" 202ms

And Go to transport details "UNLOAD" 4s 365ms

Then Check are transport values equals 21s 447ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 002ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 153ms

When Go to new transport "TANKER_GRANULATE_DELIVERY" 315ms

And Fill transport form 37s 627ms

And Click "save-transport" save button and wait for form to disappear 15s 578ms

And Set advice window in schedule 2s 133ms

And Check is transport created in schedule and set transport id 534ms

And Go to "TRANSPORT_TABLE" 198ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 379ms

Then Check are transport values equals 21s 470ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-alrec" 002ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 198ms

When Go to new transport "DELIVERY" 310ms

And Fill transport form 22s 860ms

And Click "save-transport" save button and wait for form to disappear 15s 594ms

And Set advice window in schedule 2s 164ms

And Check is transport created in schedule and set transport id 535ms

And Go to "TRANSPORT_TABLE" 195ms

And Go to transport details "DELIVERY" 4s 333ms

Then Check are transport values equals 17s 258ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_WEIGHING" "super-admin-hochland" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 508ms

When Go to new transport "WEIGHING" 301ms

And Fill transport form 13s 557ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 603ms

And Show all transport "false" 013ms

And Go to "TRANSPORT_TABLE" 127ms

And Go to transport details "WEIGHING" 4s 327ms

And Check are transport values equals 2s 195ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_TRANSPORT" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 157ms

When Go to new transport "TRANSPORT" 337ms

And Fill transport form 26s 766ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 132ms

And Show all transport "false" 012ms

And Go to "TRANSPORT_TABLE" 156ms

And Go to transport details "TRANSPORT" 4s 428ms

And Check are transport values equals 6s 238ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_CONTAINER" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 135ms

When Go to new transport "CONTAINER" 307ms

And Fill transport form 11s 188ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 629ms

And Show all transport "false" 013ms

And Go to "TRANSPORT_TABLE" 142ms

And Go to transport details "CONTAINER" 4s 373ms

And Check are transport values equals 070ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 405ms

When Go to new transport "TRANSFER_BETWEEN_WAREHOUSES" 327ms

And Fill transport form 12s 959ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 626ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 152ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 614ms

And Check are transport values equals 4s 186ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-piast" 002ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 577ms

When Go to new transport "DELIVERY" 289ms

And Fill transport form 22s 505ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 619ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 136ms

And Go to transport details "DELIVERY" 4s 526ms

And Check are transport values equals 17s 166ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-piast" 002ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 195ms

When Go to new transport "LOAD" 355ms

And Fill transport form 26s 353ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 607ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 147ms

And Go to transport details "LOAD" 4s 623ms

And Check are transport values equals 2s 140ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-keeeper" 002ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 134ms

When Go to new transport "LOAD" 286ms

And Fill transport form 24s 697ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 630ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 154ms

And Go to transport details "LOAD" 4s 363ms

And Check are transport values equals 19s 196ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_CONTAINER" "super-admin-keeeper" 002ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 174ms

When Go to new transport "CONTAINER" 293ms

And Fill transport form 24s 635ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 629ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 150ms

And Go to transport details "CONTAINER" 4s 345ms

And Check are transport values equals 19s 222ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_SMALLS_IMPORT" "super-admin-skz" 003ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 279ms

When Go to new transport "SMALLS_IMPORT" 405ms

And Fill transport form 36s 437ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 585ms

And Show all transport "false" 012ms

And Go to "TRANSPORT_TABLE" 127ms

And Go to transport details "SMALLS_IMPORT" 4s 441ms

And Check are transport values equals 10s 374ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_SMALLS_EXPORT" "super-admin-skz" 002ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 202ms

When Go to new transport "SMALLS_EXPORT" 398ms

And Fill transport form 36s 379ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 613ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 152ms

And Go to transport details "SMALLS_EXPORT" 4s 415ms

And Check are transport values equals 10s 384ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-alrec" 002ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 146ms

When Go to new transport "TRANSPORT_ORDER" 371ms

And Fill transport form 30s 012ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 634ms

And Show all transport "true" 089ms

And Go to "TRANSPORT_TABLE" 129ms

And Go to transport details "TRANSPORT_ORDER" 4s 408ms

And Check are transport values equals 19s 330ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER_WITHOUT_WAREHOUSES" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 163ms

When Go to new transport "TRANSPORT" 353ms

And Fill transport form 37s 649ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 598ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 137ms

And Go to transport details "TRANSPORT" 4s 413ms

And Check are transport values equals 4s 246ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_INBOUND_WITHOUT_WAREHOUSES" "super-admin-alrec" 002ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 159ms

When Go to new transport "INBOUND" 347ms

And Fill transport form 41s 020ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 645ms

And Show all transport "true" 092ms

And Go to "TRANSPORT_TABLE" 141ms

And Go to transport details "INBOUND" 4s 441ms

And Check are transport values equals 2s 265ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" "super-admin-farmacol" 002ms

And Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 379ms

When Go to new transport "EXTERNAL_DELIVERY" 327ms

And Fill transport form 53s 731ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 643ms

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 168ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 375ms

And Check are transport values equals 4s 487ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" "dfa1-supplier" 002ms

And Login as "dfa1-supplier" and set token of apiUsername "dfa1-supplier" 2s 714ms

When Go to new transport "EXTERNAL_DELIVERY" 15s 280ms

And Fill transport form 47s 192ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 592ms

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 170ms

And Go to transport details "EXTERNAL_DELIVERY" 32s 425ms

And Check are transport values equals 4s 471ms

Hooks

After Hooks.deleteTransportAfterTest() 012ms

Error message

java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <401>.

	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.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy:179)
	at io.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.putResponse(RestUtil.java:163)
	at Utils.RestUtils.RestUtil.putToApolloApi(RestUtil.java:76)
	at CucumberTests.Hooks.deleteTransportAfterTest(Hooks.java:175)
	at sun.reflect.GeneratedMethodAccessor207.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 1s 169ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 001ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 591ms

And Show all transport "false" 010ms

When Go to transport details "UNLOAD" 32s 470ms

And Fill transport form 30s 397ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 140ms

And Go to transport details "UNLOAD" 32s 371ms

Then Check are transport values equals 4s 279ms

Hooks

After Hooks.deleteTransportAfterTest() 145ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 163ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 002ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 256ms

And Show all transport "false" 011ms

When Go to transport details "TRANSPORT" 4s 485ms

And Fill transport form 10s 296ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 631ms

And Go to transport details "TRANSPORT" 4s 403ms

Then Check are transport values equals 4s 133ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 171ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 197ms

And Show all transport "false" 012ms

When Go to transport details "CONTAINER" 4s 396ms

And Fill transport form 4s 684ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 632ms

And Go to transport details "CONTAINER" 4s 289ms

Then Check are transport values equals 046ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 147ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 324ms

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 4s 366ms

And Fill transport form 11s 592ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 609ms

And Go to transport details "DELIVERY" 4s 274ms

Then Check are transport values equals 125ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 141ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-adama" 001ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-adama" 1s 312ms

And Show all transport "false" 011ms

When Go to transport details "OWN_COLLECTION" 4s 341ms

And Fill transport form 21s 641ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 603ms

And Go to transport details "OWN_COLLECTION" 4s 327ms

Then Check are transport values equals 2s 227ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 550ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 450ms

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 4s 741ms

And Fill transport form 35s 946ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 134ms

And Go to transport details "DELIVERY" 4s 486ms

Then Check are transport values equals 10s 504ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 520ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-hochland" 001ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 315ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION" 4s 665ms

And Fill transport form 36s 501ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 128ms

And Go to transport details "OWN_COLLECTION" 4s 433ms

Then Check are transport values equals 6s 391ms

Hooks

After Hooks.deleteTransportAfterTest() 155ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 485ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 373ms

And Show all transport "false" 010ms

When Go to transport details "EXPORT" 5s 268ms

And Fill transport form 47s 979ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 146ms

And Go to transport details "EXPORT" 4s 507ms

Then Check are transport values equals 8s 497ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 551ms

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 002ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 171ms

And Show all transport "false" 010ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 718ms

And Fill transport form 36s 090ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 677ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 408ms

Then Check are transport values equals 12s 469ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 497ms

And Get inputs from database "EDIT_CISTERN_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 311ms

And Show all transport "false" 010ms

When Go to transport details "CISTERN_DELIVERY" 4s 471ms

And Fill transport form 27s 239ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 633ms

And Go to transport details "CISTERN_DELIVERY" 4s 408ms

Then Check are transport values equals 6s 283ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 497ms

And Get inputs from database "EDIT_CISTERN_COLLECTION" "super-admin-hochland" 001ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 1s 306ms

And Show all transport "false" 011ms

When Go to transport details "CISTERN_COLLECTION" 4s 452ms

And Fill transport form 25s 822ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 600ms

And Go to transport details "CISTERN_COLLECTION" 4s 373ms

Then Check are transport values equals 6s 302ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 467ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 001ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 206ms

And Show all transport "false" 010ms

When Go to transport details "WEIGHING" 4s 388ms

And Fill transport form 12s 237ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 588ms

And Go to transport details "WEIGHING" 4s 320ms

Then Check are transport values equals 2s 157ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 430ms

And Get inputs from database "EDIT_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 001ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 365ms

And Show all transport "false" 009ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 498ms

And Fill transport form 35s 228ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 123ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 438ms

Then Check are transport values equals 6s 324ms

Hooks

After Hooks.deleteTransportAfterTest() 140ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 1s 130ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 329ms

And Show all transport "false" 009ms

When Go to transport details "DELIVERY" 32s 355ms

And Fill transport form 25s 603ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 591ms

And Go to transport details "DELIVERY" 32s 320ms

Then Check are transport values equals 2s 187ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 238ms

And Get inputs from database "EDIT_LOAD" "super-admin-piast" 002ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 210ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 683ms

And Fill transport form 57s 285ms

And Click "save-transport-and-close" save button and wait for form to disappear 670ms

And Go to transport details "LOAD" 4s 457ms

Then Check are transport values equals 24s 800ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 117ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 332ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 358ms

And Fill transport form 16s 433ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 611ms

And Go to transport details "DELIVERY" 4s 332ms

Then Check are transport values equals 074ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 149ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 321ms

And Show all transport "false" 011ms

When Go to transport details "LOAD" 4s 334ms

And Fill transport form 28s 131ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 128ms

And Go to transport details "LOAD" 4s 334ms

Then Check are transport values equals 2s 237ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 193ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 360ms

And Show all transport "false" 011ms

When Go to transport details "UNLOAD" 4s 414ms

And Fill transport form 37s 808ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 643ms

And Go to transport details "UNLOAD" 4s 371ms

Then Check are transport values equals 6s 428ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 189ms

And Get inputs from database "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 002ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 370ms

And Show all transport "false" 011ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 401ms

And Fill transport form 36s 208ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 639ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 386ms

Then Check are transport values equals 6s 358ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 229ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 195ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 381ms

And Fill transport form 24s 707ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 654ms

And Go to transport details "LOAD" 4s 355ms

Then Check are transport values equals 4s 208ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 185ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 002ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 184ms

And Show all transport "false" 011ms

When Go to transport details "CONTAINER" 4s 407ms

And Fill transport form 24s 713ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 614ms

And Go to transport details "CONTAINER" 4s 354ms

Then Check are transport values equals 4s 178ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 274ms

And Get inputs from database "EDIT_SMALLS_EXPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 228ms

And Show all transport "false" 010ms

When Go to transport details "SMALLS_EXPORT" 4s 521ms

And Fill transport form 33s 044ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 601ms

And Go to transport details "SMALLS_EXPORT" 4s 391ms

Then Check are transport values equals 8s 329ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 225ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 368ms

And Show all transport "true" 086ms

When Go to transport details "DELIVERY" 4s 310ms

And Fill transport form 19s 537ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 628ms

And Go to transport details "DELIVERY" 4s 301ms

Then Check are transport values equals 195ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 446ms

And Get inputs from database "EDIT_TRANSPORT_ORDER" "super-admin-alrec" 002ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 309ms

And Show all transport "true" 079ms

When Go to transport details "TRANSPORT_ORDER" 4s 459ms

And Fill transport form 26s 768ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 635ms

And Go to transport details "TRANSPORT_ORDER" 4s 349ms

Then Check are transport values equals 2s 267ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "keeeper-warehouseman" and set token of apiUsername "super-admin-keeeper" 2s 602ms

And Get inputs from database "EDIT_CONTAINER_WAREHOUSEMAN_CUSTOMFIELDS" "super-admin-keeeper" 001ms

And Create transport "CREATE_CONTAINER_KEEEPER_WAIMEA" by JSON file as "super-admin-keeeper" 1s 174ms

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 418ms

And Fill transport form 8s 882ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 631ms

And Go to transport details "CONTAINER" 4s 355ms

Then Check are transport values equals 4s 119ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 604ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 434ms

And Show all transport "false" 010ms

When Delete transport 17s 882ms

Then Transport not displayed in table of transports 15s 062ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 215ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 233ms

And Show all transport "false" 011ms

When Delete transport 17s 192ms

Then Transport not displayed in table of transports 15s 064ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 106ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 344ms

And Show all transport "false" 010ms

When Delete transport 17s 501ms

Then Transport not displayed in table of transports 15s 063ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 151ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 198ms

And Show all transport "false" 010ms

When Delete transport 17s 037ms

Then Transport not displayed in table of transports 15s 065ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

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 318ms

And Show all transport "false" 010ms

When Delete transport 17s 646ms

Then Transport not displayed in table of transports 15s 037ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 297ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 263ms

And Show all transport "false" 011ms

When Delete transport 17s 665ms

Then Transport not displayed in table of transports 15s 054ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 161ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 328ms

And Show all transport "true" 076ms

When Delete transport 19s 114ms

Then Transport not displayed in table of transports 15s 049ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 627ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 249ms

And Show all transport "true" 088ms

When Delete transport 17s 107ms

Then Transport not displayed in table of transports 15s 037ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 1s 120ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 001ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 625ms

And Show all transport "false" 009ms

When Go to transport details "UNLOAD" 32s 425ms

And Fill transport form 30s 442ms

And Click "save-transport" save button 1s 274ms

And Click cancel button in transport form 079ms

And Go to transport details "UNLOAD" 32s 390ms

Then Check are transport values equals 4s 288ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 165ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 001ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 234ms

And Show all transport "false" 011ms

When Go to transport details "TRANSPORT" 4s 498ms

And Fill transport form 10s 323ms

And Click "save-transport" save button 733ms

And Click cancel button in transport form 077ms

And Go to transport details "TRANSPORT" 4s 287ms

Then Check are transport values equals 4s 133ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 143ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 188ms

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 376ms

And Fill transport form 4s 724ms

And Click "save-transport" save button 711ms

And Click cancel button in transport form 071ms

And Go to transport details "CONTAINER" 4s 283ms

Then Check are transport values equals 038ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 134ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 309ms

And Show all transport "false" 009ms

When Go to transport details "DELIVERY" 4s 354ms

And Fill transport form 11s 532ms

And Click "save-transport" save button 694ms

And Click cancel button in transport form 064ms

And Go to transport details "DELIVERY" 4s 242ms

Then Check are transport values equals 106ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 134ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-adama" 002ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-adama" 1s 322ms

And Show all transport "false" 012ms

When Go to transport details "OWN_COLLECTION" 4s 373ms

And Fill transport form 21s 570ms

And Click "save-transport" save button 700ms

And Click cancel button in transport form 082ms

And Go to transport details "OWN_COLLECTION" 4s 282ms

Then Check are transport values equals 2s 232ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 414ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 412ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 596ms

And Fill transport form 35s 906ms

And Click "save-transport" save button 1s 239ms

And Click cancel button in transport form 088ms

And Go to transport details "DELIVERY" 4s 377ms

Then Check are transport values equals 10s 503ms

Hooks

After Hooks.deleteTransportAfterTest() 134ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 583ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-hochland" 001ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 285ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION" 4s 676ms

And Fill transport form 36s 533ms

And Click "save-transport" save button 878ms

And Click cancel button in transport form 082ms

And Go to transport details "OWN_COLLECTION" 4s 405ms

Then Check are transport values equals 6s 380ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 464ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 336ms

And Show all transport "false" 010ms

When Go to transport details "EXPORT" 5s 681ms

And Fill transport form 48s 050ms

And Click "save-transport" save button 891ms

And Click cancel button in transport form 093ms

And Go to transport details "EXPORT" 4s 369ms

Then Check are transport values equals 8s 487ms

Hooks

After Hooks.deleteTransportAfterTest() 162ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 534ms

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 171ms

And Show all transport "false" 010ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 710ms

And Fill transport form 36s 044ms

And Click "save-transport" save button 911ms

And Click cancel button in transport form 081ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 384ms

Then Check are transport values equals 12s 445ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 461ms

And Get inputs from database "EDIT_CISTERN_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 315ms

And Show all transport "false" 010ms

When Go to transport details "CISTERN_DELIVERY" 4s 477ms

And Fill transport form 27s 158ms

And Click "save-transport" save button 827ms

And Click cancel button in transport form 086ms

And Go to transport details "CISTERN_DELIVERY" 4s 360ms

Then Check are transport values equals 6s 305ms

Hooks

After Hooks.deleteTransportAfterTest() 142ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 490ms

And Get inputs from database "EDIT_CISTERN_COLLECTION" "super-admin-hochland" 001ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 1s 311ms

And Show all transport "false" 010ms

When Go to transport details "CISTERN_COLLECTION" 4s 460ms

And Fill transport form 25s 835ms

And Click "save-transport" save button 777ms

And Click cancel button in transport form 067ms

And Go to transport details "CISTERN_COLLECTION" 4s 390ms

Then Check are transport values equals 6s 290ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 413ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 001ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 240ms

And Show all transport "false" 010ms

When Go to transport details "WEIGHING" 4s 372ms

And Fill transport form 12s 326ms

And Click "save-transport" save button 711ms

And Click cancel button in transport form 073ms

And Go to transport details "WEIGHING" 4s 279ms

Then Check are transport values equals 2s 166ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 554ms

And Get inputs from database "EDIT_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 001ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 324ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 562ms

And Fill transport form 35s 177ms

And Click "save-transport" save button 1s 244ms

And Click cancel button in transport form 078ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 382ms

Then Check are transport values equals 6s 346ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 1s 098ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 293ms

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 32s 386ms

And Fill transport form 25s 624ms

And Click "save-transport" save button 705ms

And Click cancel button in transport form 077ms

And Go to transport details "DELIVERY" 32s 309ms

Then Check are transport values equals 2s 210ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 250ms

And Get inputs from database "EDIT_LOAD" "super-admin-piast" 001ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 217ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 678ms

And Fill transport form 57s 251ms

And Click "save-transport" save button 930ms

And Click cancel button in transport form 070ms

And Go to transport details "LOAD" 4s 435ms

Then Check are transport values equals 24s 819ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 158ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 308ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 375ms

And Fill transport form 16s 474ms

And Click "save-transport" save button 714ms

And Click cancel button in transport form 069ms

And Go to transport details "DELIVERY" 4s 314ms

Then Check are transport values equals 079ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 104ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 325ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 319ms

And Fill transport form 28s 108ms

And Click "save-transport" save button 1s 227ms

And Click cancel button in transport form 074ms

And Go to transport details "LOAD" 4s 313ms

Then Check are transport values equals 2s 245ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 154ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 372ms

And Show all transport "false" 009ms

When Go to transport details "UNLOAD" 4s 427ms

And Fill transport form 37s 841ms

And Click "save-transport" save button 1s 242ms

And Click cancel button in transport form 075ms

And Go to transport details "UNLOAD" 4s 339ms

Then Check are transport values equals 6s 373ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 148ms

And Get inputs from database "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 001ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 325ms

And Show all transport "false" 011ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 407ms

And Fill transport form 36s 242ms

And Click "save-transport" save button 763ms

And Click cancel button in transport form 085ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 316ms

Then Check are transport values equals 6s 323ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 185ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 180ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 403ms

And Fill transport form 24s 707ms

And Click "save-transport" save button 744ms

And Click cancel button in transport form 075ms

And Go to transport details "LOAD" 4s 310ms

Then Check are transport values equals 4s 199ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 162ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 215ms

And Show all transport "false" 009ms

When Go to transport details "CONTAINER" 4s 390ms

And Fill transport form 24s 753ms

And Click "save-transport" save button 718ms

And Click cancel button in transport form 065ms

And Go to transport details "CONTAINER" 4s 314ms

Then Check are transport values equals 4s 203ms

Hooks

After Hooks.deleteTransportAfterTest() 054ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 287ms

And Get inputs from database "EDIT_SMALLS_IMPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 224ms

And Show all transport "false" 011ms

When Go to transport details "SMALLS_IMPORT" 4s 496ms

And Fill transport form 32s 988ms

And Click "save-transport" save button 756ms

And Click cancel button in transport form 077ms

And Go to transport details "SMALLS_IMPORT" 4s 344ms

Then Check are transport values equals 8s 335ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 672ms

And Get inputs from database "EDIT_SMALLS_EXPORT" "super-admin-skz" 002ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 240ms

And Show all transport "false" 010ms

When Go to transport details "SMALLS_EXPORT" 4s 498ms

And Fill transport form 33s 020ms

And Click "save-transport" save button 710ms

And Click cancel button in transport form 075ms

And Go to transport details "SMALLS_EXPORT" 4s 338ms

Then Check are transport values equals 8s 348ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 152ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 246ms

And Show all transport "true" 090ms

When Go to transport details "DELIVERY" 4s 327ms

And Fill transport form 19s 625ms

And Click "save-transport" save button 700ms

And Click cancel button in transport form 085ms

And Go to transport details "DELIVERY" 4s 312ms

Then Check are transport values equals 188ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 195ms

And Get inputs from database "EDIT_TRANSPORT_ORDER" "super-admin-alrec" 002ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 294ms

And Show all transport "true" 078ms

When Go to transport details "TRANSPORT_ORDER" 4s 494ms

And Fill transport form 26s 741ms

And Click "save-transport" save button 733ms

And Click cancel button in transport form 078ms

And Go to transport details "TRANSPORT_ORDER" 4s 347ms

Then Check are transport values equals 2s 257ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Crud Transport

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

Scenario Outline Check if firstPossibleStart algorithm works properly when creating transport advice

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 201ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 203ms

And Create gray windows "CREATE_GRAY_WINDOW_MWG" on "PRZESYŁKI DROBNICOWE" in "Magazyn Wyrobów Gotowych" as "super-admin-keeeper" 271ms

And If user is login then logout 255ms

Then Login as "dka1-supplier" 2s 443ms

And Click button advice in transport table "LOAD" 192ms

And Check if moved to first possible start date in schedule 418ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

After Hooks.deleteAllGrayWindowsAfterTest() 1m 30s 549ms

View Feature Crud Transport

@deleteTransportAfterTest @deleteAddressAfterTest

Scenario Outline Check if it is possible to create transport with new address [A-7158]

Steps

Given Set token of apiUsername "super-admin-piast" 124ms

And Set "transport" inputs from JSON file "CREATE_LOAD_WITH_NEW_ADDRESS" "super-admin-piast" 008ms

When Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 347ms

Then Go to new transport "LOAD" 336ms

And Fill transport form 23s 400ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 655ms

And Go to "COMPANIES_TAB" 406ms

And Go to company "Dostawca Piast Automat 1" details 202ms

And Check if new address with "Adresat" is visible in company details 130ms

And Go to "TRANSPORT_TABLE" 225ms

And Go to transport details "LOAD" 4s 625ms

Hooks

After Hooks.deleteTransportAfterTest() 064ms

After Hooks.deleteAddressAfterTest() 077ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 146ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 174ms

When Go to "TRANSPORT_TABLE" 129ms

And Show all transport types 1s 038ms

And Verify that transport has "0" files 037ms

Then Add file to transport by API 420ms

And Verify that transport has "1" files 594ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 033ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 159ms

When Go to "TRANSPORT_TABLE" 126ms

And Show all transport types 1s 038ms

And Verify that transport has "0" files 037ms

Then Add file to transport by API 293ms

And Verify that transport has "1" files 478ms

Hooks

After Hooks.deleteTransportAfterTest() 054ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 299ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 371ms

When Go to "TRANSPORT_TABLE" 138ms

And Show all transport types 1s 040ms

And Verify that transport has "0" files 038ms

Then Add file to transport by API 211ms

And Verify that transport has "1" files 369ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in transport table

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 067ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 199ms

When Go to "TRANSPORT_TABLE" 116ms

And Show all transport types 1s 041ms

And Verify that transport has "0" files 042ms

Then Add file to transport by API 198ms

And Verify that transport has "1" files 943ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 125ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 179ms

And Delete transport 17s 725ms

When Go to "ARCHIVE_TAB" 229ms

And Show "DELIVERY" 063ms

And Verify that transport has "0" files 640ms

Then Add file to transport 144ms

And Verify that transport has "1" files 385ms

Hooks

After Hooks.deleteTransportAfterTest() 061ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 215ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 214ms

And Delete transport 17s 335ms

When Go to "ARCHIVE_TAB" 266ms

And Show "LOAD" 090ms

And Verify that transport has "0" files 1s 114ms

Then Add file to transport 158ms

And Verify that transport has "1" files 388ms

Hooks

After Hooks.deleteTransportAfterTest() 050ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 440ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 402ms

And Delete transport 18s 021ms

When Go to "ARCHIVE_TAB" 209ms

And Show "DELIVERY" 066ms

And Verify that transport has "0" files 853ms

Then Add file to transport 136ms

And Verify that transport has "1" files 345ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 434ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 204ms

And Delete transport 17s 561ms

When Go to "ARCHIVE_TAB" 257ms

And Show "CONTAINER" 078ms

And Verify that transport has "0" files 1s 014ms

Then Add file to transport 146ms

And Verify that transport has "1" files 320ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

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

Steps

Given Set token of apiUsername "super-admin-adama" 105ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 15s 230ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 121ms

And Accept transferred transport by Api 160ms

And Login as "paa1-carrier@qa.qa-test" 1s 049ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 16s 258ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

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

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 207ms

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" "false" confirmation 116ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 810ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check that the file is added to the transport after winning the auction

Steps

Given Set token of apiUsername "super-admin-adama" 100ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 221ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 159ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 371ms

And Login as "paa1-carrier@qa.qa-test" 1s 172ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 15s 656ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it CMR documents are added to transport after creation

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 194ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 236ms

When Go to "TRANSPORT_TABLE" 135ms

And Show all transport "true" 063ms

Then Verify that transport has "1" CMR file 1s 212ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it CMR documents are added to transport after creation

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 089ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 214ms

When Go to "TRANSPORT_TABLE" 129ms

And Show all transport "true" 072ms

Then Verify that transport has "2" CMR file 1s 180ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it CMR document can be downloaded

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 039ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 272ms

When Go to "TRANSPORT_TABLE" 110ms

And Show all transport "true" 055ms

Then Verify that "CMR" document can be downloaded 17s 482ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it CMR document can be downloaded in archive

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 114ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 264ms

And Show all transport "true" 074ms

And Delete transport 17s 167ms

When Go to "ARCHIVE_TAB" 228ms

And Show "TRANSPORT_ORDER" 072ms

Then Verify that "CMR" document can be downloaded 16s 771ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

View Feature Transport files

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline The link to the delivery document appears after confirming the respective status [A-6905]

Steps

Given Login as "pba1-carrier" and set token of apiUsername "super-admin-bausch" 2s 353ms

And Create default accepted mode of transportation by API with "pba1-carrier" 472ms

And If user is login then logout 250ms

And Login as "bausch-admin" and set token of apiUsername "super-admin-bausch" 1s 286ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 308ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 099ms

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-bausch" 009ms

And Click button advice in transport table "LOAD_PL" 1s 804ms

And Set advice window in schedule 2s 855ms

And Fill advice form 9s 153ms

And Click advice save button and wait for advice form to disappear 30s 775ms

And Find transport in table with status "advice-added" 3s 349ms

When Confirm statuses until reach "on-the-way" 9s 312ms

Then Verify that "delivery_document" document can be downloaded 16s 355ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

After Hooks.deleteModeOfTransportationAfterTest() 069ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 387ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 440ms

And Show all transport "false" 011ms

When Find transport pencil button in transports table 1s 259ms

And Click pencil and move transport to next day in schedule 16s 401ms

Then Check if transport is in new location in schedule 2s 114ms

And Check if dates in transport form are correct 3s 429ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 193ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 313ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 242ms

And Click pencil and move transport to next day in schedule 16s 794ms

Then Check if transport is in new location in schedule 2s 121ms

And Check if dates in transport form are correct 3s 338ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

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 372ms

And Show all transport "false" 011ms

When Find transport pencil button in transports table 1s 237ms

And Click pencil and move transport to next day in schedule 16s 847ms

Then Check if transport is in new location in schedule 2s 136ms

And Check if dates in transport form are correct 3s 398ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 188ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 352ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 254ms

And Click pencil and move transport to next day in schedule 16s 296ms

Then Check if transport is in new location in schedule 2s 110ms

And Check if dates in transport form are correct 3s 351ms

Hooks

After Hooks.deleteTransportAfterTest() 157ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 218ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 269ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 252ms

And Click pencil and move transport to next day in schedule 16s 330ms

Then Check if transport is in new location in schedule 2s 111ms

And Check if dates in transport form are correct 3s 364ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 145ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-alrec" 1s 380ms

And Show all transport "true" 088ms

When Find transport pencil button in transports table 1s 226ms

And Click pencil and move transport to next day in schedule 16s 393ms

Then Check if transport is in new location in schedule 2s 126ms

And Check if dates in transport form are correct 3s 405ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 263ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 192ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 002ms

When Show all transport types 1s 044ms

And Click button advice in transport table "DELIVERY" 111ms

And Set advice window in schedule 2s 589ms

And Fill advice form 8s 277ms

And Click advice save button and wait for advice form to disappear 30s 731ms

And Go to "TRANSPORT_TABLE" 250ms

And Find transport pencil button in transports table 1s 230ms

And Click pencil and move transport to next day in schedule 17s 537ms

Then Check if transport is in new location in schedule 2s 116ms

And Check if dates in transport form are correct 3s 427ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

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 374ms

And Show all transport "false" 009ms

When Find transport pencil button in transports table 1s 265ms

And Click pencil and move transport to next day in schedule 16s 340ms

And Move advice window "3" 1s 325ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 122ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 316ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 252ms

And Click pencil and move transport to next day in schedule 16s 693ms

And Move advice window "3" 1s 366ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 036ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 262ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 217ms

And Click pencil and move transport to next day in schedule 16s 784ms

And Move advice window "3" 1s 417ms

Then Check if advice window is in new location 038ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 192ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 291ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 261ms

And Click pencil and move transport to next day in schedule 16s 324ms

And Move advice window "3" 1s 316ms

Then Check if advice window is in new location 024ms

Hooks

After Hooks.deleteTransportAfterTest() 143ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 049ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 373ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 239ms

And Click pencil and move transport to next day in schedule 16s 304ms

And Move advice window "3" 1s 314ms

Then Check if advice window is in new location 020ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 199ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 307ms

And Show all transport "true" 067ms

When Find transport pencil button in transports table 1s 226ms

And Click pencil and move transport to next day in schedule 16s 411ms

And Move advice window "3" 1s 363ms

Then Check if advice window is in new location 024ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report custom fields are visible in proper section

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 506ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 423ms

And Go to transport details "DELIVERY" 4s 775ms

When Open section: "discrepancy-report-panel" 1s 078ms

Then Verify that no discrepancies found label is visible in discrepancy report section 063ms

And Select "NIE" in the "insp.-accord.-with-ins." 2s 446ms

And Verify that discrepancy report custom fields are visible in discrepancy report section 097ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section will open with validation errors

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 302ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 379ms

And Go to transport details "DELIVERY" 4s 744ms

And Fill transport form 35s 922ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 127ms

When Go to transport details "DELIVERY" 4s 413ms

Then Select "NIE" in the "insp.-accord.-with-ins." 2s 418ms

And Click "save-transport" save button 698ms

And Wait "2" seconds 2s

And Verify that discrepancy report section is open 029ms

And Verify that discrepancy report section contains validation errors 014ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 460ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 435ms

When Go to transport details "DELIVERY" 4s 819ms

Then Verify that discrepancy report section is available 038ms

And Open section: "discrepancy-report-panel" 1s 063ms

And Verify that generate new discrepancy report button is visible 039ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 288ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 291ms

When Go to transport details "OWN_COLLECTION" 4s 649ms

Then Verify that discrepancy report section is available 037ms

And Open section: "discrepancy-report-panel" 1s 052ms

And Verify that generate new discrepancy report button is visible 030ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 431ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 376ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 540ms

Then Verify that discrepancy report section is available 032ms

And Open section: "discrepancy-report-panel" 1s 061ms

And Verify that generate new discrepancy report button is visible 029ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 393ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 384ms

When Go to transport details "EXPORT" 5s 601ms

Then Verify that discrepancy report section is available 035ms

And Open section: "discrepancy-report-panel" 1s 047ms

And Verify that generate new discrepancy report button is visible 035ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is available

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 303ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 175ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 697ms

Then Verify that discrepancy report section is available 037ms

And Open section: "discrepancy-report-panel" 1s 068ms

And Verify that generate new discrepancy report button is visible 030ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is not available

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 365ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 294ms

When Go to transport details "CISTERN_DELIVERY" 4s 468ms

Then Verify that discrepancy report section is not available 15s 041ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is not available

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 398ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 1s 333ms

When Go to transport details "CISTERN_COLLECTION" 4s 457ms

Then Verify that discrepancy report section is not available 15s 058ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report section is not available

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 504ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 215ms

When Go to transport details "WEIGHING" 4s 390ms

Then Verify that discrepancy report section is not available 15s 014ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report is properly generated

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 422ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 417ms

When Go to "TRANSPORT_TABLE" 154ms

And Go to transport details "DELIVERY" 4s 731ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 503ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 334ms

And Open section: "discrepancy-report-panel" 1s 076ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 002ms

And Fill transport form 35s 773ms

And Fill discrepancy report section without closing the form 19s 549ms

And Generate discrepancy report 1s 280ms

And Download discrepancy report 126ms

Then Verify that discrepancy report file has correct values 15s 135ms

Error message

java.nio.file.NoSuchFileException: /home/teamcity/Downloads/44_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:250)
	at ✽.Verify that discrepancy report file has correct values(file:Features/Atom/Transport/TransportForm/DiscrepancyReport.feature:76)

Hooks

After Hooks.deleteTransportAfterTest() 158ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if edited discrepancy report is properly generated

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 422ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 477ms

When Go to "TRANSPORT_TABLE" 148ms

And Go to transport details "DELIVERY" 4s 724ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 002ms

And Fill transport form 35s 892ms

And Open section: "discrepancy-report-panel" 1s 059ms

And Fill discrepancy report section without closing the form 19s 606ms

And Generate discrepancy report 16s 223ms

And Download discrepancy report 142ms

And Verify that discrepancy report file has correct values 15s 184ms

Error message

java.nio.file.NoSuchFileException: /home/teamcity/Downloads/45_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:250)
	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() 129ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackTransportTypeSettings

Scenario Outline Check if added step is saved with transport

Steps

Given Set token of apiUsername "super-admin-piast" 099ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 050ms

And Get "LOAD" settings from "piast" 037ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "false" 080ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-piast" 1s 215ms

And Login as "piast-admin" 1s 877ms

And Go to "TRANSPORT_TABLE" 201ms

When Go to transport details "LOAD" 4s 710ms

And Add step "unload" 120ms

And Change filled value in transport details "company-step-2" "autocomplete" "DPA2" "0" 6s 502ms

And Change filled value in transport details "recipient-step-2" "autocomplete" "Testowy" "0" 6s 525ms

Then Click "save-transport-and-close" save button and wait for form to disappear 15s 635ms

And Go to transport details "LOAD" 4s 569ms

And Verify that transport has "3" steps 024ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

After Hooks.rollbackTransportTypeSettings() 052ms

After Hooks.rollbackAddedActionAuthorities() 042ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest

Scenario Outline Check if supplier can't edit time range for load and unload step

Steps

Given Login as "pskza1-carrier-2@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 284ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 259ms

When Go to "TRANSPORT_TABLE" 151ms

And Go to transport details "SMALLS_IMPORT" 17s 118ms

Then Verify that user can't edit time range for load and unload 15s 051ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest

Scenario Outline Check if sum of number of pallets in transport form is correct

Steps

Given Set token of apiUsername "super-admin-neuca" 101ms

And Create transport "CREATE_DELIVERY_TWO_LOADS" by JSON file as "super-admin-neuca" 1s 374ms

And Login as "neuca-admin" 898ms

And Go to "TRANSPORT_TABLE" 201ms

And Show all transport types 15s 033ms

When Go to transport details "DELIVERY" 32s 525ms

Then Check if sum of number of pallets in transport form in "load" steps is correct 067ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest

Scenario Outline Check if sum of number of pallets in transport form is correct

Steps

Given Set token of apiUsername "super-admin-hochland" 105ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 15s 365ms

And Login as "hochland-admin" 1s 459ms

And Go to "TRANSPORT_TABLE" 124ms

And Show all transport types 1s 044ms

When Go to transport details "EXPORT" 5s 592ms

Then Check if sum of number of pallets in transport form in "unload" steps is correct 071ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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

Steps

Given Set token of apiUsername "super-admin-neuca" 101ms

And Get "DELIVERY" settings from "neuca" 035ms

And Set transportType settings with values: "quantitySumCheckValue", "33" 088ms

And Login as "neuca-admin" 924ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 15s 341ms

When Go to "TRANSPORT_TABLE" 267ms

And Go to transport details "DELIVERY" 32s 497ms

And Set number of pallets in "load" step in transport - "32" 127ms

And Check if number of pallets check message is not visible in transport form 15s 080ms

And Set number of pallets in "load" step in transport - "34" 148ms

Then Check if number of pallets check message is visible in transport form 045ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

After Hooks.rollbackTransportTypeSettings() 105ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackTransportTypeSettings

Scenario Outline Check if time range fields are required in new warehouse step

Steps

Given Set token of apiUsername "super-admin-farmacol" 110ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 052ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 055ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 073ms

And Login as "farmacol-admin" 2s 149ms

And Go to new transport "EXTERNAL_DELIVERY" 358ms

And Add step "unload" 114ms

And Click "save-transport-and-close" save button 686ms

Then Verify that "time-range-from-date-2" has validation error 1s 028ms

Then Verify that "time-range-to-date-2" has validation error 1s 031ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 312ms

And Click "save-transport-and-close" save button 707ms

And Verify that "time-range-from-date-2" has no validation error 017ms

And Verify that "time-range-to-date-2" has no validation error 015ms

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.rollbackTransportTypeSettings() 066ms

After Hooks.rollbackAddedActionAuthorities() 050ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities

Scenario Outline Check if new step is added in proper column in transport form

Steps

Given Set token of apiUsername "super-admin-piast" 105ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_LOAD_STEP_FROM_UNLOAD" "ACTIVE" 046ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 240ms

When Login as "piast-admin" 1s 827ms

And Go to transport details "LOAD" 4s 790ms

And Get inputs from database "PIAST_LOAD_ADD_UNLOAD_STEP" "super-admin-piast" 002ms

And Add step "unload" 125ms

And Fill step data 15s 035ms

And Get inputs from database "PIAST_LOAD_ADD_LOAD_STEP" "super-admin-piast" 002ms

And Add step "load" 123ms

And Fill step data 5s 475ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 601ms

Then Go to transport details "LOAD" 4s 577ms

And Check if "unload" step is added as "3" step in transport form 043ms

And Check if "load" step is added as "4" step in transport form 031ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

After Hooks.rollbackAddedActionAuthorities() 036ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackRemovedActionAuthorities

Scenario Outline Check if step is draggable according to authority @A-6865

Steps

Given Set token of apiUsername "super-admin-skz" 104ms

And Add action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_LOAD_STEPS" "UNLIMITED" 050ms

And Remove action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_UNLOAD_STEPS" "UNLIMITED" 009ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 240ms

When Login as "super-admin-skz" 2s 429ms

And Go to transport details "SMALLS_EXPORT" 4s 480ms

And Check if step is draggable "LOAD" 029ms

And Check if step is not draggable "UNLOAD" 022ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

After Hooks.rollbackAddedActionAuthorities() 038ms

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

Steps

Given Set "transport" inputs from JSON file "CREATE_SMALLS_IMPORT" "super-admin-skz" 001ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 148ms

When Go to new transport "SMALLS_IMPORT" 375ms

And Fill transport form 19s 823ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 600ms

And Show all transport "false" 009ms

And Go to transport details "SMALLS_IMPORT" 4s 461ms

And Click create similar button 15s 175ms

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 15s 612ms

And Open similar transport details 260ms

Then Check are transport values equals 2s 098ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

After Hooks.deleteSimilarTransportAfterTest() 086ms

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

Steps

Given Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-alrec" 006ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 997ms

When Go to new transport "TRANSPORT_ORDER" 381ms

And Fill transport form 23s 881ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 644ms

And Show all transport "true" 089ms

And Go to transport details "TRANSPORT_ORDER" 4s 402ms

And Click create similar button 15s 149ms

And Fill "transport" form "CREATE_SIMILAR_TRANSPORT_ORDER" by "super-admin-alrec" 001ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 591ms

And Open similar transport details 264ms

Then Check are transport values equals 2s 168ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

After Hooks.deleteSimilarTransportAfterTest() 069ms

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

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "pna1-carrier" 007ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 2s 199ms

When Go to new transport "DELIVERY" 15s 296ms

And Fill transport form 35s 842ms

And Click "save-transport" save button and wait for form to disappear 15s 710ms

And Set advice window in schedule 2s 160ms

And Check is transport created in schedule and set transport id 812ms

And Go to "TRANSPORT_TABLE" 208ms

And Go to transport details "DELIVERY" 32s 381ms

And Click create similar button 15s 149ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 9s 464ms

And Click "save-transport" save button and wait for form to disappear 15s 601ms

And Set advice window in schedule in "2" days 4s 213ms

And Go to "TRANSPORT_TABLE" 214ms

And Open similar transport details 563ms

Then Check are transport values equals 23s 461ms

Hooks

After Hooks.deleteTransportAfterTest() 014ms

Error message

java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <401>.

	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.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy:179)
	at io.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.putResponse(RestUtil.java:163)
	at Utils.RestUtils.RestUtil.putToApolloApi(RestUtil.java:76)
	at CucumberTests.Hooks.deleteTransportAfterTest(Hooks.java:175)
	at sun.reflect.GeneratedMethodAccessor207.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

After Hooks.deleteSimilarTransportAfterTest() 008ms

Error message

java.lang.AssertionError: 1 expectation failed.
Expected status code <200> but was <401>.

	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.codehaus.groovy.reflection.CachedConstructor.invoke(CachedConstructor.java:83)
	at org.codehaus.groovy.reflection.CachedConstructor.doConstructorInvoke(CachedConstructor.java:77)
	at org.codehaus.groovy.runtime.callsite.ConstructorSite$ConstructorSiteNoUnwrap.callConstructor(ConstructorSite.java:84)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callConstructor(AbstractCallSite.java:250)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure.validate(ResponseSpecificationImpl.groovy:494)
	at io.restassured.internal.ResponseSpecificationImpl$HamcrestAssertionClosure$validate$1.call(Unknown Source)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1750)
	at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.applyPathParamsAndSendRequest(RequestSpecificationImpl.groovy:1755)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:98)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1225)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1034)
	at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:822)
	at io.restassured.internal.RequestSpecificationImpl.invokeMethod(RequestSpecificationImpl.groovy)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.call(PogoInterceptableSite.java:47)
	at org.codehaus.groovy.runtime.callsite.PogoInterceptableSite.callCurrent(PogoInterceptableSite.java:57)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:185)
	at io.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy:179)
	at io.restassured.internal.RequestSpecificationImpl.put(RequestSpecificationImpl.groovy)
	at Utils.RestUtils.RestUtil.putResponse(RestUtil.java:163)
	at Utils.RestUtils.RestUtil.putToApolloApi(RestUtil.java:76)
	at CucumberTests.Hooks.deleteSimilarTransportAfterTest(Hooks.java:188)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

Scenario Outline Check if transport created with advice by similar button has correct carrier

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "pna1-carrier" 001ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 1s 125ms

When Go to new transport "DELIVERY" 15s 289ms

And Fill transport form 35s 900ms

And Click "save-transport" save button and wait for form to disappear 15s 661ms

And Set advice window in schedule 2s 152ms

And Check is transport created in schedule and set transport id 15s 020ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[@id='slot-114767102-2021-04-29-00-15']//div[@data-transport-id]"}
  (Session info: headless chrome=90.0.4430.72)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=90.0.4430.24 (4c6d850f087da467d926e8eddb76550aed655991-refs/branch-heads/4430@{#429}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.a1iJQ8}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, acceptInsecureCerts=false, browserVersion=90.0.4430.72, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: ad7ef55ccd6c049ed315433353249fb9
*** Element info: {Using=xpath, value=//div[@id='slot-114767102-2021-04-29-00-15']//div[@data-transport-id]}
	at sun.reflect.GeneratedConstructorAccessor211.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.Schedule.SchedulePage.getTransportId(SchedulePage.java:161)
	at CucumberTests.Transport.AdviceTransport.checkIsTransportCreatedInScheduleAndSetTransportId(AdviceTransport.java:157)
	at ✽.Check is transport created in schedule and set transport id(file:Features/Atom/Transport/TransportForm/TransportForm.feature:56)

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "DELIVERY" 000ms

And Click create similar button 000ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 000ms

And Click "save-transport" save button and wait for form to disappear 000ms

And Set advice window in schedule in "2" days 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Open similar transport details 000ms

Then Check is field "CARRIER" of type "autocomplete" equals "Przewoźnik Neuca Automat 1" 000ms

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteSimilarTransportAfterTest() 000ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is possible to show transport details print form

Steps

Given Get inputs from database "CREATE_SMALLS_IMPORT_FOR_PRINT" "super-admin-skz" 002ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 341ms

When Go to new transport "SMALLS_IMPORT" 377ms

And Fill transport form 32s 926ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 619ms

And Go to transport details "SMALLS_IMPORT" 4s 402ms

And Go to transport print details form 3s 126ms

Then Check are transport values equals 8s 347ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to edit transport when auction is active

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 265ms

And Get inputs from database "CREATE_SMALLS_IMPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 249ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 190ms

And Go to transport details "SMALLS_IMPORT" 4s 485ms

Then Verify that the transport can be edited 1s 322ms

And Close transport details 15s 095ms

And If user is login then logout 116ms

And Login as "pskza1-carrier@qa.qa-test" 1s 272ms

And Go to transport details "SMALLS_IMPORT" 4s 549ms

And Verify that the transport cannot be edited 46s 319ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to edit transport when auction is active

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 288ms

And Get inputs from database "CREATE_SMALLS_EXPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 232ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 114ms

And Go to transport details "SMALLS_EXPORT" 4s 459ms

Then Verify that the transport can be edited 1s 305ms

And Close transport details 15s 113ms

And If user is login then logout 122ms

And Login as "pskza1-carrier@qa.qa-test" 1s 292ms

And Go to transport details "SMALLS_EXPORT" 4s 483ms

And Verify that the transport cannot be edited 46s 361ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to see hidden data in transport when auction is active

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 163ms

And Get inputs from database "HIDDEN_DATA_SMALLS_IMPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 254ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 116ms

And Go to transport details "SMALLS_IMPORT" 4s 440ms

Then Verify that the hidden data in transport are not visible 1s 041ms

And Close transport details 15s 112ms

And If user is login then logout 112ms

And Login as "swisskrono-admin" 1s 501ms

And Go to transport details "SMALLS_IMPORT" 4s 495ms

And Verify that the hidden data in transport are visible 1s 241ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to see hidden data in transport when auction is active

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 042ms

And Get inputs from database "HIDDEN_DATA_SMALLS_EXPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 279ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 129ms

And Go to transport details "SMALLS_EXPORT" 4s 411ms

Then Verify that the hidden data in transport are not visible 1s 039ms

And Close transport details 15s 084ms

And If user is login then logout 122ms

And Login as "swisskrono-admin" 1s 568ms

And Go to transport details "SMALLS_EXPORT" 4s 479ms

And Verify that the hidden data in transport are visible 1s 206ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 501ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 469ms

When Go to transport details "DELIVERY" 4s 723ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 331ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 507ms

And Change filled value in transport details "insp.-accord.-with-ins." "select" "NIE" "1" 3s 506ms

And Fill discrepancy report section without closing the form 19s 558ms

And Click "save-transport" save button 1s 226ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 662ms

And Check if transport details form is disappeared 15s 044ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest @rollbackWarehousesAccess

Scenario Outline Check if user can add description to transport

Steps

Given Set token of apiUsername "super-admin-hochland" 098ms

And Add action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 053ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 252ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 472ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 3s 300ms

When Go to "TRANSPORT_TABLE" 187ms

And Go to transport details "DELIVERY" 4s 710ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 331ms

Then Verify that "transport-description" in transport has value "opis" 028ms

Hooks

After Hooks.deleteTransportAfterTest() 138ms

After Hooks.rollbackAddedActionAuthorities() 037ms

After Hooks.rollbackWarehousesAccess() 159ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest @rollbackWarehousesAccess

Scenario Outline Check if user can't add description to transport

Steps

Given Set token of apiUsername "super-admin-hochland" 104ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 408ms

And Remove action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 050ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 152ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 2s 556ms

When Go to "TRANSPORT_TABLE" 161ms

And Go to transport details "DELIVERY" 4s 636ms

Then Verify that "transport-description" in transport form is disabled 030ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

After Hooks.rollbackRemovedActionAuthorities() 049ms

After Hooks.rollbackWarehousesAccess() 177ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can see `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-hochland" 110ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 039ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 414ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 682ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 225ms

And Go to transport details "DELIVERY" 4s 669ms

Then Verify that "CARRIER" in transport form is visible 032ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

After Hooks.rollbackAddedActionAuthorities() 039ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can see `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-adama" 103ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 046ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 240ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 118ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 118ms

And Go to transport details "TRANSPORT" 4s 460ms

Then Verify that "CARRIER" in transport form is visible 031ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.rollbackAddedActionAuthorities() 059ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can see `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-alrec" 171ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 061ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 232ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 967ms

And Show all transport "true" 068ms

When Go to "TRANSPORT_TABLE" 112ms

And Go to transport details "TRANSPORT_ORDER" 4s 454ms

Then Verify that "CARRIER" in transport form is visible 032ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

After Hooks.rollbackAddedActionAuthorities() 038ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't see `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-hochland" 106ms

And Remove 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 395ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 557ms

And Show all transport "false" 003ms

When Go to "TRANSPORT_TABLE" 183ms

And Go to transport details "DELIVERY" 4s 695ms

Then Verify that "CARRIER" in transport form is not visible 15s 050ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

After Hooks.rollbackRemovedActionAuthorities() 074ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't see `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-adama" 108ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 043ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 228ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 965ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 111ms

And Go to transport details "TRANSPORT" 4s 458ms

Then Verify that "CARRIER" in transport form is not visible 15s 017ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

After Hooks.rollbackRemovedActionAuthorities() 044ms

View Feature Transport form

@rollbackRemovedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't see `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-alrec" 097ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 043ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 222ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 928ms

And Show all transport "true" 069ms

When Go to "TRANSPORT_TABLE" 134ms

And Go to transport details "TRANSPORT_ORDER" 4s 450ms

Then Verify that "CARRIER" in transport form is not visible 15s 059ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

After Hooks.rollbackRemovedActionAuthorities() 052ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can edit `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-hochland" 100ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 047ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 045ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 420ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 539ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 204ms

And Go to transport details "DELIVERY" 4s 720ms

Then Verify that "CARRIER" in transport form is not disabled 035ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

After Hooks.rollbackAddedActionAuthorities() 075ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can edit `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-adama" 104ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 050ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 055ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 231ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 878ms

And Show all transport "false" 007ms

When Go to "TRANSPORT_TABLE" 101ms

And Go to transport details "TRANSPORT" 4s 447ms

Then Verify that "CARRIER" in transport form is not disabled 027ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

After Hooks.rollbackAddedActionAuthorities() 079ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can edit `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-alrec" 107ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 047ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 047ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 242ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 710ms

And Show all transport "true" 057ms

When Go to "TRANSPORT_TABLE" 126ms

And Go to transport details "TRANSPORT_ORDER" 4s 476ms

Then Verify that "CARRIER" in transport form is not disabled 029ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

After Hooks.rollbackAddedActionAuthorities() 073ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't edit `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-hochland" 104ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 044ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 040ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 439ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 521ms

And Show all transport "false" 004ms

When Go to "TRANSPORT_TABLE" 193ms

And Go to transport details "DELIVERY" 4s 615ms

Then Verify that "CARRIER" in transport form is disabled 025ms

Hooks

After Hooks.deleteTransportAfterTest() 134ms

After Hooks.rollbackAddedActionAuthorities() 040ms

After Hooks.rollbackRemovedActionAuthorities() 037ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't edit `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-adama" 105ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 045ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 008ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 206ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 812ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 118ms

And Go to transport details "TRANSPORT" 4s 448ms

Then Verify that "CARRIER" in transport form is disabled 027ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

After Hooks.rollbackAddedActionAuthorities() 035ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can't edit `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-alrec" 100ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 043ms

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 209ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 821ms

And Show all transport "true" 069ms

When Go to "TRANSPORT_TABLE" 129ms

And Go to transport details "TRANSPORT_ORDER" 4s 473ms

Then Verify that "CARRIER" in transport form is disabled 024ms

Hooks

After Hooks.deleteTransportAfterTest() 180ms

After Hooks.rollbackAddedActionAuthorities() 187ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

View Feature Transport form

@rollbackRemovedActionAuthorities @rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can add description to archived transport

Steps

Given Set token of apiUsername "super-admin-adama" 153ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 296ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_MAIN_DATA_SECTION" "UNLIMITED" 078ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_ADVICE" "UNLIMITED" 060ms

And Add action authority with: "adama" "adama-admin" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 059ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 6s 160ms

When Find transport in table with status "planned" 3s 293ms

And Confirm statuses until reach "process-ended" 21s 577ms

And Wait "90" seconds 1m 30s

And Go to "ARCHIVE_TAB" 278ms

And Show "DELIVERY" 070ms

And Go to transport details "DELIVERY" 32s 430ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 326ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 603ms

And Wait "7" seconds 7s

And Go to transport details "DELIVERY" 32s 344ms

Then Verify that "transport-description" in transport has value "opis" 025ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

After Hooks.rollbackAddedActionAuthorities() 041ms

After Hooks.rollbackRemovedActionAuthorities() 089ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if driver is in list in transport form.

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 3s 449ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 358ms

When Go to transport details "DELIVERY" 4s 683ms

And Fill transport form 35s 844ms

And Change filled value in transport details "driver-name" "text" "XXX ZZZ" "0" 1s 417ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 159ms

And Go to new transport "DELIVERY" 304ms

Then Verify that driver "XXX ZZZ" is in list 679ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 235ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 289ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 229ms

And If user is login then logout 097ms

And Login as "pskza1-carrier@qa.qa-test" 1s 253ms

Then Verify that the transport has been transferred 1s 132ms

And Accept or reject "accept" transferred transport 15s 820ms

And Go to transport details "SMALLS_IMPORT" 4s 520ms

And Verify that "transaction-price" in transport form is visible 039ms

And Verify that transaction price field has correct value 025ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_IMPORT" 026ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 251ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 234ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 205ms

And If user is login then logout 124ms

And Login as "pskza1-carrier@qa.qa-test" 1s 329ms

Then Verify that the transport has been transferred 1s 129ms

And Accept or reject "accept" transferred transport 15s 773ms

And Go to transport details "SMALLS_EXPORT" 4s 486ms

And Verify that "transaction-price" in transport form is visible 033ms

And Verify that transaction price field has correct value 022ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_EXPORT" 025ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

Scenario Outline Check if similar transport can be created based on transport with confirmed statuses [A-7322]

Steps

Given Set token of apiUsername "super-admin-dayco" 113ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 256ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 001ms

When Login as "dayco-admin" 1s 862ms

And Click button advice in transport table "OWN_COLLECTION" 281ms

And Set advice window in schedule 2s 568ms

And Fill advice form 6s 945ms

And Click advice save button and wait for advice form to disappear 30s 689ms

And Go to "TRANSPORT_TABLE" 184ms

And Find transport in table with status "planned" 3s 222ms

And Confirm statuses until reach "on-the-area" 3s 799ms

And Go to transport details "OWN_COLLECTION" 4s 405ms

And Click create similar button 15s 132ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 6s 505ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 617ms

And Open similar transport details 314ms

Then Check if transport form modal is visible 030ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

After Hooks.deleteSimilarTransportAfterTest() 073ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

Scenario Outline Check if similar transport can be created based on transport with confirmed statuses [A-7322]

Steps

Given Set token of apiUsername "super-admin-dayco" 102ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 225ms

And Set "advice" inputs from JSON file "ADVICE_OWN_COLLECTION" "super-admin-dayco" 002ms

When Login as "dayco-admin" 1s 111ms

And Click button advice in transport table "OWN_COLLECTION" 272ms

And Set advice window in schedule 2s 521ms

And Fill advice form 6s 921ms

And Click advice save button and wait for advice form to disappear 30s 767ms

And Go to "TRANSPORT_TABLE" 196ms

And Find transport in table with status "planned" 3s 251ms

And Confirm statuses until reach "during-load" 6s 560ms

And Go to transport details "OWN_COLLECTION" 4s 451ms

And Click create similar button 15s 142ms

And Fill "transport" form "CREATE_SIMILAR_OWN_COLLECTION" by "super-admin-dayco" 6s 493ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 604ms

And Open similar transport details 328ms

Then Check if transport form modal is visible 029ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

After Hooks.deleteSimilarTransportAfterTest() 077ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport details button is not shown

Steps

Given Login as "lantmannen-guard-3" and set token of apiUsername "super-admin-lantmannen" 2s 371ms

And Create transport "CREATE_DELIVERY_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 283ms

And Show all transport types 1s 039ms

Then Check if transport number is visible "DELIVERY" 15s 048ms

And Check if transport details is not visible 15s 023ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 878ms

And Show all transport "false" 006ms

And Go to "TRANSPORT_TABLE" 127ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 504ms

When Click on transport row 065ms

Then Verify if transport row is selected 024ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 902ms

And Show all transport "false" 004ms

And Go to "TRANSPORT_TABLE" 116ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 333ms

When Click on transport row 066ms

Then Verify if transport row is selected 023ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 1s 798ms

And Show all transport "false" 004ms

And Go to "TRANSPORT_TABLE" 101ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 275ms

When Click on transport row 067ms

Then Verify if transport row is selected 034ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 945ms

And Show all transport "false" 004ms

And Go to "TRANSPORT_TABLE" 106ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 270ms

When Click on transport row 064ms

Then Verify if transport row is selected 021ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 960ms

And Show all transport "false" 004ms

And Go to "TRANSPORT_TABLE" 103ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 276ms

When Click on transport row 069ms

Then Verify if transport row is selected 022ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 974ms

And Show all transport "true" 061ms

And Go to "TRANSPORT_TABLE" 127ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 323ms

When Click on transport row 066ms

Then Verify if transport row is selected 025ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 802ms

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" "true" confirmation 072ms

When Accept or reject "accept" transferred transport 17s 650ms

Then Verify that transport is accept or reject "accept" 024ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 184ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 209ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 060ms

When Accept or reject "reject" transferred transport 17s 672ms

Then Verify that transport is accept or reject "reject" 15s 026ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 323ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 227ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 088ms

When Accept or reject "accept" transferred transport 17s 989ms

Then Verify that transport is accept or reject "accept" 018ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 034ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 245ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 075ms

When Accept or reject "reject" transferred transport 18s

Then Verify that transport is accept or reject "reject" 15s 024ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 117ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 211ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 072ms

When Accept or reject "accept" transferred transport 18s 072ms

Then Verify that transport is accept or reject "accept" 023ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 137ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 227ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 069ms

When Accept or reject "reject" transferred transport 18s 021ms

Then Verify that transport is accept or reject "reject" 15s 015ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - with confirmation checkbox

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 177ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 233ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 411ms

And If user is login then logout 105ms

And Login as "paa1-carrier@qa.qa-test" 1s 190ms

Then Verify that the transport has been transferred with "true" 1s 122ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - with confirmation checkbox

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 045ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 234ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 19s 207ms

And If user is login then logout 107ms

And Login as "paa1-carrier@qa.qa-test" 1s 265ms

Then Verify that the transport has been transferred with "false" 1s 124ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - without confirmation checkbox

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 869ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 232ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 164ms

And If user is login then logout 114ms

And Login as "pskza1-carrier@qa.qa-test" 1s 248ms

Then Verify that the transport has been transferred 1s 135ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - without confirmation checkbox

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 157ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 213ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 096ms

And If user is login then logout 105ms

And Login as "pskza1-carrier@qa.qa-test" 1s 141ms

Then Verify that the transport has been transferred 1s 129ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to pass transport to carrier during auction

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 069ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 218ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 173ms

And Go to auction offer 1s 201ms

When Offer "1000" 124ms

And Verify that offer with "1000" has been added to auction 3s 039ms

And If user is login then logout 085ms

And Login as "swisskrono-admin" 1s 244ms

Then Go to auction details 1s 192ms

And Pass transport to carrier from auction details 1s 245ms

And If user is login then logout 582ms

And Login as "pskza1-carrier@qa.qa-test" 1s 226ms

And Verify that the transport has been transferred 1s 122ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to pass transport to carrier when auction is finished

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 059ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 223ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 099ms

And Go to auction offer 1s 195ms

When Offer "1000" 128ms

And Verify that offer with "1000" has been added to auction 3s 031ms

And Wait till auction end 1m 54s 016ms

And If user is login then logout 126ms

Then Login as "swisskrono-admin" 1s 367ms

And Go to auction details 1s 187ms

And Pass transport to carrier from auction details 1s 272ms

And If user is login then logout 606ms

And Login as "pskza1-carrier@qa.qa-test" 1s 149ms

And Verify that the transport has been transferred 1s 109ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if enabled carriers are shown in transport transfer select

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 179ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 240ms

And Go to "TRANSPORT_TABLE" 126ms

When Open transport transfer modal 1s 251ms

Then Verify that all enabled companies from "swisskrono" are shown in select 130ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest @rollbackRejectedSections

Scenario Outline Check if blocked carriers are shown as disabled in transport transfer select

Steps

Given Set token of apiUsername "super-admin-adama" 108ms

And Reject main section of a "Przewoźnik Adama Automat 1" in "adama" by API 360ms

And Login as "adama-admin" 925ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 223ms

And Go to "TRANSPORT_TABLE" 129ms

When Open transport transfer modal 1s 253ms

Then Verify that "Przewoźnik Adama Automat 1" is blocked in select 106ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

After Hooks.rollbackRejectedSections() 094ms

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]

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 064ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 189ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" with "120" seconds to accept transport 19s 228ms

And If user is login then logout 092ms

When Login as "paa1-carrier@qa.qa-test" 2s 689ms

And Verify that the transport has been transferred with "true" 1s 119ms

And Wait "120" seconds 2m

Then Verify if transport is not visible to carrier after expiring time to accept transport 15s 017ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature Assortment Group

@deleteTransportAfterTest

Scenario Outline Check if assortment group select is disabled when transport is during edition

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 044ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 384ms

When Go to "TRANSPORT_TABLE" 149ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 370ms

Then Check if new assortment group is disabled in transport form 036ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if possible to advice transport after double cancellation.

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 160ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 177ms

And Get inputs from database "CREATE_ADVICE_CONTAINER" "super-admin-adama" 002ms

When Show all transport types 1s 050ms

And Click button advice in transport table "CONTAINER" 100ms

And Set advice window in schedule 2s 425ms

And Click button cancel in advice form 15s 330ms

And Set advice window in schedule 2s 172ms

And Click button cancel in advice form 15s 288ms

And Set advice window in schedule 2s 120ms

And Fill advice form 15s 770ms

And Click advice save button and wait for advice form to disappear 30s 717ms

And Go to "TRANSPORT_TABLE" 165ms

And Go to transport details "CONTAINER" 4s 388ms

Then Check are advice values equals 2s 371ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

View Feature Transport transfer full scenario

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer and retransfer transport to carrier

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 111ms

And Get inputs from database "CREATE_TRANSPOSRT_ORDER" "super-admin-adama" 001ms

When Go to new transport "TRANSPORT" 334ms

And Fill transport form 26s 696ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 597ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 188ms

And Check is transport "TRANSPORT" created in transport table and set transport id 1s 120ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 236ms

And Accept or reject "reject" transferred transport 15s 836ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 125ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 214ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 053ms

And Accept or reject "accept" transferred transport 15s 826ms

Then Verify that transport is accept or reject "accept" 023ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

View Feature Transport transfer full scenario

@deleteTransportAfterTest

Scenario Outline Check if possible to edit transport after advice cancellation.

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 130ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-piast" 001ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 181ms

When Show all transport types 1s 044ms

And Click button advice in transport table "DELIVERY" 107ms

And Set advice window in schedule 2s 649ms

And Click button cancel in advice form 15s 363ms

And Go to "TRANSPORT_TABLE" 217ms

When Go to transport details "DELIVERY" 4s 532ms

And Fill transport form 1m 2s 336ms

And Click "save-transport-and-close" save button and wait for form to disappear 667ms

And Go to transport details "DELIVERY" 4s 373ms

Then Check are transport values equals 122ms

Error message

org.junit.ComparisonFailure: Wartości w formularzu w polu CARRIER są niepoprawne, wartość na stronie: Przewoźnik Piast Automat 1 wartość poprawna: Przewoźnik Piast Automat 2 expected:<...oźnik Piast Automat [2]> but was:<...oźnik Piast Automat [1]>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at CucumberTests.Transport.Transport.checkAreValuesEquals(Transport.java:122)
	at CucumberTests.Transport.Transport.checkValueInTransportDetails(Transport.java:261)
	at CucumberTests.Transport.CreateTransport.checkTransportValues(CreateTransport.java:225)
	at ✽.Check are transport values equals(file:Features/Scenario/TransportTransfer.feature:39)

Hooks

After Hooks.deleteTransportAfterTest() 095ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@deleteTransportAfterTest	3454	15	36	0	0	3505	368	17	385	5h 14m 46s 714ms	Failed

Tag Report