Cucumber-JVM Reports - Tag: @deleteTransportAfterTest

Project	Number	Date
ApolloFullRunnerReport	develop.365	01 kwi 2021, 05:48

	Steps	Scenarios	Features
@deleteTransportAfterTest	3680	28	84	0	0	3792	379	28	407	5h 38m 37s 942ms	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" 2s 469ms

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

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

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

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

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

And Fill advice form 16s 399ms

And Click advice save button to check error message 076ms

Then Check if possible advice alert is displayed 018ms

Hooks

After Hooks.deleteTransportAfterTest() 367ms

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

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

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

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

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

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

And Fill advice form 8s 382ms

And Click advice save button to check error message 076ms

Then Check if possible advice alert is displayed 019ms

Hooks

After Hooks.deleteTransportAfterTest() 172ms

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

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

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

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

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

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

And Fill advice form 8s 429ms

And Click advice save button to check error message 079ms

Then Check if possible advice alert is displayed 022ms

Hooks

After Hooks.deleteTransportAfterTest() 139ms

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

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

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

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

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

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

And Fill advice form 13s 136ms

And Click advice save button to check error message 071ms

Then Check if possible advice alert is displayed 020ms

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 "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 218ms

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

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

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

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

And Fill advice form 13s 091ms

And Click advice save button to check error message 066ms

Then Check if possible advice alert is displayed 014ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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

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

And Show all transport types 1s 049ms

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

And Go to "TRANSPORT_TABLE" 155ms

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

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

And Fill transport form 4s 719ms

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

And Expand advice panel 108ms

And Edit advice in transport details 12s 462ms

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

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

And Expand advice panel 113ms

Then Check are advice values equals after edition 202ms

Hooks

After Hooks.deleteTransportAfterTest() 167ms

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

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

And Show all transport types 1s 037ms

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

And Go to "TRANSPORT_TABLE" 215ms

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

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

And Fill transport form 1m 1s 998ms

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

And Expand advice panel 096ms

And Edit advice in transport details 6s 590ms

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

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

And Expand advice panel 099ms

Then Check are advice values equals after edition 098ms

Hooks

After Hooks.deleteTransportAfterTest() 166ms

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

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

And Show all transport types 1s 037ms

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

And Go to "TRANSPORT_TABLE" 198ms

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

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

And Fill transport form 56s 996ms

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

And Expand advice panel 117ms

And Edit advice in transport details 6s 652ms

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

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

And Expand advice panel 111ms

Then Check are advice values equals after edition 106ms

Hooks

After Hooks.deleteTransportAfterTest() 225ms

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

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

And Show all transport types 1s 045ms

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

And Go to "TRANSPORT_TABLE" 179ms

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

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

And Fill transport form 24s 586ms

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

And Expand advice panel 116ms

And Edit advice in transport details 18s 412ms

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

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

And Expand advice panel 088ms

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

Hooks

After Hooks.deleteTransportAfterTest() 151ms

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

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

And Show all transport types 1s 042ms

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

And Go to "TRANSPORT_TABLE" 161ms

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

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

And Fill transport form 24s 593ms

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

And Expand advice panel 096ms

And Edit advice in transport details 18s 409ms

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

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

And Expand advice panel 100ms

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

Hooks

After Hooks.deleteTransportAfterTest() 125ms

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

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

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

When Show all transport types 1s 038ms

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

And Set advice window in schedule 2s 410ms

And Fill advice form 12s 311ms

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

And Go to "TRANSPORT_TABLE" 173ms

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

Then Check are advice values equals 294ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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

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

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

When Show all transport types 1s 042ms

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

And Set advice window in schedule 6s 417ms

And Fill advice form 11s 759ms

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

And Go to "TRANSPORT_TABLE" 225ms

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

Then Check are advice values equals 2s 311ms

Hooks

After Hooks.deleteTransportAfterTest() 151ms

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

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

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

When Show all transport types 1s 035ms

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

And Set advice window in schedule 2s 563ms

And Fill advice form 8s 355ms

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

And Go to "TRANSPORT_TABLE" 220ms

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

Then Check are advice values equals 177ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

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

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

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

When Show all transport types 1s 035ms

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

And Set advice window in schedule 2s 564ms

And Fill advice form 8s 314ms

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

And Go to "TRANSPORT_TABLE" 174ms

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

Then Check are advice values equals 201ms

Hooks

After Hooks.deleteTransportAfterTest() 242ms

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

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

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

When Show all transport types 1s 041ms

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

And Set advice window in schedule 2s 397ms

And Fill advice form 13s 110ms

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

And Go to "TRANSPORT_TABLE" 162ms

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

Then Check are advice values equals 2s 310ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

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

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

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

When Show all transport types 1s 039ms

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

And Set advice window in schedule 2s 387ms

And Fill advice form 13s 066ms

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

And Go to "TRANSPORT_TABLE" 178ms

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

Then Check are advice values equals 2s 277ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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 Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 067ms

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

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

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

And Accept transferred transport by Api 494ms

And Set token of apiUsername "super-admin-adama" 094ms

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

When Show all transport types 1s 037ms

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

And Set advice window in schedule 2s 392ms

And Fill advice form 11s 672ms

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

And Go to "TRANSPORT_TABLE" 205ms

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

Then Check are advice values equals 2s 249ms

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 Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 214ms

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

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

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

And Accept transferred transport by Api 271ms

And Set token of apiUsername "super-admin-skz" 099ms

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

When Show all transport types 1s 042ms

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

And Set advice window in schedule 2s 570ms

And Fill advice form 14s 416ms

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

And Go to "TRANSPORT_TABLE" 186ms

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

Then Check are advice values equals 2s 308ms

Hooks

After Hooks.deleteTransportAfterTest() 132ms

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 Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 103ms

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

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

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

And Accept transferred transport by Api 094ms

And Set token of apiUsername "super-admin-skz" 105ms

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

When Show all transport types 1s 030ms

And Click button advice in transport table "SMALLS_EXPORT" 1s 054ms

And Set advice window in schedule 2s 641ms

And Fill advice form 14s 453ms

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

And Go to "TRANSPORT_TABLE" 188ms

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

Then Check are advice values equals 2s 280ms

Hooks

After Hooks.deleteTransportAfterTest() 179ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

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

And Accept transferred transport by Api 104ms

And Set token of apiUsername "super-admin-adama" 094ms

When Show all transport types 1s 041ms

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

And Set week view 1s 556ms

And Show yesterday 1s 109ms

Then Check if advice restriction blockade windows are visible 026ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

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

And Accept transferred transport by Api 109ms

And Set token of apiUsername "super-admin-skz" 099ms

When Show all transport types 1s 033ms

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

And Set week view 2s 003ms

And Show yesterday 1s 111ms

Then Check if advice restriction blockade windows are visible 029ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

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

And Accept transferred transport by Api 112ms

And Set token of apiUsername "super-admin-skz" 093ms

When Show all transport types 1s 034ms

And Click button advice in transport table "SMALLS_EXPORT" 1s 044ms

And Set week view 2s 075ms

And Show yesterday 1s 120ms

Then Check if advice restriction blockade windows are visible 030ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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

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

And Show all transport "false" 020ms

And Click on time window date 1s 287ms

And Select view "DAYS_4" 2s 063ms

And Move advice window "3" 1s 308ms

Then Check if advice window is in new location 022ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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" 2s 072ms

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

And Show all transport "false" 016ms

And Click on time window date 15s 737ms

And Select view "DAYS_4" 2s 065ms

And Move advice window "3" 15s 034ms

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=89.0.4389.114)
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=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.9IPk1e}, 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=89.0.4389.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: a29274008b6467118e33d32e9ee1aa75
*** 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:138)

Then Check if advice window is in new location 000ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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

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

And Show all transport "false" 015ms

And Click on time window date 15s 518ms

And Select view "DAYS_4" 2s 069ms

And Move advice window "3" 1s 364ms

Then Check if advice window is in new location 020ms

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

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

And Show all transport "false" 016ms

And Click on time window date 1s 388ms

And Select view "DAYS_4" 2s 064ms

And Move advice window "3" 1s 332ms

Then Check if advice window is in new location 021ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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

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

And Show all transport "false" 016ms

And Click on time window date 1s 297ms

And Select view "DAYS_4" 2s 053ms

And Move advice window "3" 1s 309ms

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 "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 467ms

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

And Show all transport "true" 069ms

And Click on time window date 1s 323ms

And Select view "DAYS_4" 2s 059ms

And Move advice window "3" 1s 349ms

Then Check if advice window is in new location 024ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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

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

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

When Show all transport types 1s 037ms

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

And Set advice window in schedule 2s 577ms

And Fill advice form 8s 244ms

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

And Go to "TRANSPORT_TABLE" 237ms

And Click on time window date 1s 422ms

And Select view "DAYS_4" 2s 053ms

And Move advice window "3" 1s 395ms

Then Check if advice window is in new location 027ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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

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

And Go to "TRANSPORT_TABLE" 123ms

And Show all transport types 1s 035ms

And Click on time window date 1s 284ms

And Scroll to time window "adviceWindow" 033ms

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

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

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:187)

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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

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

And Go to "TRANSPORT_TABLE" 100ms

And Show all transport types 1s 035ms

And Click on time window date 1s 384ms

And Scroll to time window "adviceWindow" 028ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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

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

And Go to "TRANSPORT_TABLE" 106ms

And Show all transport types 1s 037ms

And Click on time window date 1s 284ms

And Scroll to time window "adviceWindow" 031ms

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

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

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:187)

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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

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

And Go to "TRANSPORT_TABLE" 259ms

And Show all transport types 15s 033ms

And Click on time window date 15s 823ms

And Scroll to time window "adviceWindow" 033ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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

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

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

When Show all transport types 1s 034ms

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

And Set advice window in schedule 2s 515ms

And Fill advice form 8s 279ms

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

And Go to "TRANSPORT_TABLE" 229ms

And Click on time window date 1s 435ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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

And Go to "WAREHOUSE_TAB" 887ms

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

When Go to new transport "DELIVERY" 329ms

And Fill transport form 39s 499ms

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

And Click previous page button in browser 020ms

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

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

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

And Go to "WAREHOUSE_TAB" 775ms

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

When Go to new transport "DELIVERY" 326ms

And Fill transport form 39s 478ms

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

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

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

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

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

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

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

When Show all transport types 1s 027ms

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

And Fill advice form 11s 507ms

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

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

And Open statuses popup 115ms

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

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if time window details preview displays correctly

Steps

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

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

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

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

And Go to "WAREHOUSE_TAB" 670ms

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

And Set week view 2s 254ms

And Move cursor over time window element 392ms

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

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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

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

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

And Fill transport form 34s 325ms

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

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

And Set advice window in schedule 2s 145ms

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

Then Go to "OWN_COMPANY_TAB" 261ms

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

Hooks

After Hooks.deleteTransportAfterTest() 194ms

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" and set token of apiUsername "super-admin-alrec" 31s 223ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: Nie udalo sie poprawnie zalogowac daa1-supplier (tried for 20 second(s) with 500 MILLISECONDS interval)
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.checkElementIsVisible(BasePage.java:166)
	at Pages.LoginPage.loginAs(LoginPage.java:33)
	at CucumberTests.BaseTest.loginAs(BaseTest.java:101)
	at CucumberTests.LoginTest.loginAsAndSetTokenOfApiUsername(LoginTest.java:68)
	at ✽.Login as "daa1-supplier" and set token of apiUsername "super-admin-alrec"(file:Features/Atom/Companies/CompanyResources.feature:6)
Caused by: org.openqa.selenium.NoSuchElementException: Cannot locate an element using By.xpath: //a[text()='Logout'] | //a[text()='Wyloguj']
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: driver.version: unknown
	at org.openqa.selenium.support.ui.ExpectedConditions.lambda$findElement$0(ExpectedConditions.java:882)
	at java.util.Optional.orElseThrow(Optional.java:290)
	at org.openqa.selenium.support.ui.ExpectedConditions.findElement(ExpectedConditions.java:881)
	at org.openqa.selenium.support.ui.ExpectedConditions.access$000(ExpectedConditions.java:43)
	at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:205)
	at org.openqa.selenium.support.ui.ExpectedConditions$7.apply(ExpectedConditions.java:201)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:208)
	at Pages.BasePage.checkElementIsVisible(BasePage.java:166)
	at Pages.LoginPage.loginAs(LoginPage.java:33)
	at CucumberTests.BaseTest.loginAs(BaseTest.java:101)
	at CucumberTests.LoginTest.loginAsAndSetTokenOfApiUsername(LoginTest.java:68)
	at sun.reflect.GeneratedMethodAccessor204.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.JavaStepDefinition.execute(JavaStepDefinition.java:57)
	at cucumber.runner.PickleStepDefinitionMatch.runStep(PickleStepDefinitionMatch.java:50)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.PickleStepTestStep.run(PickleStepTestStep.java:43)
	at cucumber.runner.TestCase.run(TestCase.java:45)
	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)

And Go to new transport "DELIVERY" 000ms

And Fill transport form 000ms

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

When 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

Then Go to "OWN_COMPANY_TAB" 000ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

Given Login as "swisskrono-purchasing-department" and set token of apiUsername "swisskrono-purchasing-department" 3s 221ms

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

When Go to "TRANSPORT_TABLE" 118ms

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

And Show all transport types 1s 042ms

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

Hooks

After Hooks.deleteTransportAfterTest() 098ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

Given Login as "swisskrono-purchasing-department" and set token of apiUsername "swisskrono-purchasing-department" 1s 089ms

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

When Go to "TRANSPORT_TABLE" 112ms

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

And Show all transport types 1s 043ms

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

Hooks

After Hooks.deleteTransportAfterTest() 108ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

Given Login as "swisskrono-purchasing-department" and set token of apiUsername "swisskrono-admin" 1s 280ms

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

When Go to "TRANSPORT_TABLE" 105ms

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

And Show all transport types 1s 044ms

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

Hooks

After Hooks.deleteTransportAfterTest() 171ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

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

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

When Go to "TRANSPORT_TABLE" 139ms

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

And Show all transport types 1s 044ms

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

Hooks

After Hooks.deleteTransportAfterTest() 117ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

Given Login as "swisskrono-purchasing-department" and set token of apiUsername "swisskrono-purchasing-department" 1s 176ms

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

And Delete created transport by API 098ms

When Go to "ARCHIVE_TAB" 176ms

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

And Show "SMALLS_IMPORT" 085ms

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

Hooks

After Hooks.deleteTransportAfterTest() 090ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

Given Login as "swisskrono-purchasing-department" and set token of apiUsername "swisskrono-purchasing-department" 1s 242ms

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

And Delete created transport by API 106ms

When Go to "ARCHIVE_TAB" 187ms

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

And Show "SMALLS_IMPORT" 082ms

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

Hooks

After Hooks.deleteTransportAfterTest() 160ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

Given Login as "swisskrono-purchasing-department" and set token of apiUsername "swisskrono-admin" 1s 236ms

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

And Delete created transport by API 117ms

When Go to "ARCHIVE_TAB" 227ms

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

And Show "SMALLS_IMPORT" 095ms

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

Hooks

After Hooks.deleteTransportAfterTest() 102ms

View Feature Filters

@deleteTransportAfterTest

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

Steps

Given Login as "swisskrono-purchasing-department" and set token of apiUsername "swisskrono-admin" 1s 274ms

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

And Delete created transport by API 098ms

When Go to "ARCHIVE_TAB" 199ms

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

And Show "SMALLS_IMPORT" 076ms

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

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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

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

When Login as "alrec-admin" 998ms

And Go to "TRANSPORT_TABLE" 134ms

And Show all transport "true" 066ms

And Select transportType "TRANSPORT_ORDER" 1s 137ms

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

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 205ms

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

And Toggle transport table days limit filter 091ms

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

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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

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

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

When Go to "TRANSPORT_TABLE" 121ms

And Go to auction form 1s 330ms

And Select contractors group "Kraj" 100ms

Then Verify that carrier "PSKZA1" is selected 022ms

Hooks

After Hooks.removeContractorsGroup() 066ms

After Hooks.deleteTransportAfterTest() 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 077ms

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

When Go to "TRANSPORT_TABLE" 111ms

And Go to auction form 1s 185ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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

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

When Go to "TRANSPORT_TABLE" 133ms

And Go to auction form 1s 218ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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

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

And Show all transport "false" 016ms

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

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

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

And Expand index panel 111ms

And Click add index button 130ms

And Fill index form 10s 569ms

And Click ok button in index form 15s 136ms

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

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

And Expand index panel 124ms

Then Check are transport values equals 090ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

After Hooks.deleteProductAfterTest() 077ms

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

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

And Show all transport "true" 081ms

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

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

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

And Expand index panel 096ms

And Click add index button 128ms

And Fill index form 7s 483ms

And Click ok button in index form 15s 126ms

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

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

And Expand index panel 132ms

Then Check are transport values equals 2s 128ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

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

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

And Show all transport "false" 014ms

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

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

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

And Add index to transport 25s 950ms

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

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

And Expand index panel 124ms

And Click delete index button 068ms

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

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

And Expand index panel 095ms

Then Verify that transport has no indexes 15s 016ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

After Hooks.deleteProductAfterTest() 029ms

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

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

And Show all transport "true" 075ms

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

And Add index to transport 22s 933ms

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

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

And Expand index panel 124ms

And Click delete index button 070ms

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

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

And Expand index panel 100ms

Then Verify that transport has no indexes 15s 063ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

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

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

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

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

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

And Add index to transport 24s 542ms

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

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

When Click on index details icon 119ms

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

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.deleteProductAfterTest() 035ms

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

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

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

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

And Show all transport types 1s 049ms

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

And Set advice window in schedule 2s 464ms

And Fill advice form 11s 877ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 199ms

After Hooks.deleteTransportAfterTest() 124ms

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

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

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

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

And Set advice window in schedule 2s 581ms

And Fill advice form 8s 383ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 180ms

After Hooks.deleteTransportAfterTest() 117ms

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

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

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

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

And Show all transport types 1s 050ms

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

And Set advice window in schedule 2s 404ms

And Fill advice form 13s 202ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 248ms

After Hooks.deleteTransportAfterTest() 127ms

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" 2s 640ms

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

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

And Show all transport types 1s 046ms

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

And Go to "TRANSPORT_TABLE" 204ms

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

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

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

And Fill transport form 4s 739ms

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

And Expand advice panel 129ms

And Edit advice in transport details 12s 472ms

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" 1m 14s 499ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 183ms

After Hooks.deleteTransportAfterTest() 106ms

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

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

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

And Show all transport types 1s 049ms

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

And Go to "TRANSPORT_TABLE" 266ms

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

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

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

And Fill transport form 1m 2s 557ms

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

And Expand advice panel 129ms

And Edit advice in transport details 6s 612ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zmiana w awizacji numer" 1m 2s 451ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 191ms

After Hooks.deleteTransportAfterTest() 138ms

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

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

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

And Show all transport types 1s 048ms

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

And Go to "TRANSPORT_TABLE" 187ms

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

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

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

And Fill transport form 24s 766ms

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

And Expand advice panel 115ms

And Edit advice in transport details 18s 717ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 270ms

After Hooks.deleteTransportAfterTest() 141ms

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

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

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

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

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

Then Check if user got a mail 000ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 195ms

After Hooks.deleteTransportAfterTest() 118ms

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

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

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

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

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

And Wait "120" seconds 2m

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 247ms

After Hooks.deleteTransportAfterTest() 125ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 006ms

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" 2s 534ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 201ms

After Hooks.deleteTransportAfterTest() 095ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 217ms

After Hooks.deleteTransportAfterTest() 098ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after bid has been added to auction

Steps

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

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

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

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

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

And Wait till auction end 1m 58s 022ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Dodano nową ofertę" 3m 14s 915ms

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:33)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/AuctionMail.feature:39)

Hooks

After Hooks.cleanUserDetailsAfterTest() 315ms

After Hooks.deleteTransportAfterTest() 088ms

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

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

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

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

And Wait till auction end 1m 58s 022ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 194ms

After Hooks.deleteTransportAfterTest() 087ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 203ms

After Hooks.deleteTransportAfterTest() 085ms

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

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Otrzymano zlecenie" 1m 51s 525ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 224ms

After Hooks.deleteTransportAfterTest() 096ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 197ms

After Hooks.deleteTransportAfterTest() 074ms

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

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

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

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

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.cleanUserDetailsAfterTest() 177ms

After Hooks.deleteTransportAfterTest() 089ms

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

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

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

And Go to "TRANSPORT_TABLE" 126ms

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

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

And Fill transport form 35s 991ms

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

And Fill discrepancy report section 35s 748ms

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

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

And Generate discrepancy report 18s 804ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Utworzono protokół niezgodności" 7s 770ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 373ms

After Hooks.deleteTransportAfterTest() 116ms

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" 3s 016ms

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

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

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

And Go to "WAREHOUSE_TAB" 807ms

And Select warehouse "Serownia" 1s 399ms

And Set week view 1s 094ms

And Show yesterday 1s 078ms

And Move window into the past 308ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "spóźnił się na" 3m 13s 821ms

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:33)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/TransportMail.feature:15)

Hooks

After Hooks.cleanUserDetailsAfterTest() 305ms

After Hooks.rollbackAddedAuthorities() 053ms

After Hooks.deleteTransportAfterTest() 119ms

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Drobnica import" 43s 254ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 292ms

After Hooks.deleteTransportAfterTest() 112ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 241ms

After Hooks.deleteTransportAfterTest() 097ms

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

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

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

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

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='PASS'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: '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=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.9IPk1e}, 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=89.0.4389.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: a29274008b6467118e33d32e9ee1aa75
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:198)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:278)
	at CucumberTests.Transport.TransferTransportTest.transferTransportToCarrier(TransferTransportTest.java:37)
	at ✽.Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true"(file:Features/Atom/Mail/TransportTransferMail.feature:8)

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 211ms

After Hooks.deleteTransportAfterTest() 073ms

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

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

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

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

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='PASS'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: '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=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.9IPk1e}, 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=89.0.4389.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: a29274008b6467118e33d32e9ee1aa75
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:198)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:278)
	at CucumberTests.Transport.TransferTransportTest.transferTransportToCarrier(TransferTransportTest.java:37)
	at ✽.Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false"(file:Features/Atom/Mail/TransportTransferMail.feature:20)

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 241ms

After Hooks.deleteTransportAfterTest() 100ms

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

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

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

And Transfer transport to carrier "Przewoźnik SKZ Automat 1" 13s 684ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@data-button-name='PASS'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: '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=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.9IPk1e}, 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=89.0.4389.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: a29274008b6467118e33d32e9ee1aa75
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:198)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:278)
	at CucumberTests.Transport.TransferTransportTest.transferTransportToCarrier(TransferTransportTest.java:43)
	at ✽.Transfer transport to carrier "Przewoźnik SKZ Automat 1"(file:Features/Atom/Mail/TransportTransferMail.feature:32)

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 270ms

After Hooks.deleteTransportAfterTest() 089ms

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

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

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

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

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.cleanUserDetailsAfterTest() 277ms

After Hooks.deleteTransportAfterTest() 086ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 293ms

After Hooks.deleteTransportAfterTest() 089ms

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

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

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

And Fill transport form 41s 071ms

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

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

And Set advice window in schedule 2s 180ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

View Feature Pallet limit

@deleteTransportAfterTest

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

Steps

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

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

And Go to "TRANSPORT_TABLE" 240ms

And Show all transport "false" 008ms

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

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

And Click "save-transport" save button 723ms

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

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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

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

And Set status of MOT to "AWAITING_VERIFICATION" 063ms

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

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

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

And Go to "TRANSPORT_TABLE" 235ms

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

And Set advice window in schedule 2s 760ms

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

Hooks

After Hooks.deleteTransportAfterTest() 074ms

After Hooks.deleteModeOfTransportationAfterTest() 069ms

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

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

And Set status of MOT to "DISABLED" 061ms

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

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

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

And Go to "TRANSPORT_TABLE" 221ms

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

And Set advice window in schedule 2s 783ms

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

Hooks

After Hooks.deleteTransportAfterTest() 077ms

After Hooks.deleteModeOfTransportationAfterTest() 061ms

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

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

And Set status of MOT to "ACCEPTED" 063ms

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

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

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

And Go to "TRANSPORT_TABLE" 232ms

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

And Set advice window in schedule 2s 769ms

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

Hooks

After Hooks.deleteTransportAfterTest() 080ms

After Hooks.deleteModeOfTransportationAfterTest() 077ms

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

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

And Set status of MOT to "UPDATED" 060ms

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

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

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

And Go to "TRANSPORT_TABLE" 201ms

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

And Set advice window in schedule 2s 750ms

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

Hooks

After Hooks.deleteTransportAfterTest() 081ms

After Hooks.deleteModeOfTransportationAfterTest() 068ms

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

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

And Set status of MOT to "REJECTED" 058ms

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

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

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

And Go to "TRANSPORT_TABLE" 215ms

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

And Set advice window in schedule 2s 735ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.deleteModeOfTransportationAfterTest() 080ms

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

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

And Set status of MOT to "BLOCKED" 072ms

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

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

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

And Go to "TRANSPORT_TABLE" 224ms

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

And Set advice window in schedule 2s 758ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.deleteModeOfTransportationAfterTest() 062ms

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

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

And Add transport by SKApi in "MGW" 167ms

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

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

And Set advice window in schedule 2s 762ms

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

And Fill advice form 14s 888ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 175ms

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

When Add transport by SKApi in "MGW" 003ms

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

And Go to "TRANSPORT_TABLE" 127ms

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

Then Check are transport values equals 393ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

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

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

When Add transport by SKApi in "MGW" 003ms

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

And Go to "TRANSPORT_TABLE" 131ms

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

Then Check are transport values equals 421ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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" and set token of apiUsername "super-admin-skz" 1s 227ms

When Add transport by SKApi in "MGW" 002ms

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

And Go to "TRANSPORT_TABLE" 121ms

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

Then Check are transport values equals 419ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

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

When Add transport by SKApi in "HRL" 002ms

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

And Go to "TRANSPORT_TABLE" 136ms

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

Then Check are transport values equals 391ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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

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

When Add transport by SKApi in "HRL" 003ms

Then Check is transport "CONTAINER" created in transport table and set transport id 51s 417ms

And Go to "TRANSPORT_TABLE" 148ms

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

Then Check are transport values equals 415ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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

When Add transport by SKApi in "HRL" 003ms

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

And Go to "TRANSPORT_TABLE" 144ms

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

Then Check are transport values equals 420ms

Hooks

After Hooks.deleteTransportAfterTest() 145ms

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

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

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 54s 341ms

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

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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

When Add transport by SKApi in "" 003ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 57s 335ms

And Go to "TRANSPORT_TABLE" 125ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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

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

And Add transport by SKApi in "MGW" 013ms

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

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

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

And Set advice window in schedule 2s 744ms

And Fill advice form 14s 871ms

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

And Go to "TRANSPORT_TABLE" 212ms

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

Then Check are advice values equals 2s 327ms

Hooks

After Hooks.deleteTransportAfterTest() 146ms

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

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

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

And Set advice window in schedule 2s 522ms

And Fill advice form 14s 662ms

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

And Go to "TRANSPORT_TABLE" 229ms

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

Then Check are advice values equals 2s 336ms

Hooks

After Hooks.deleteTransportAfterTest() 139ms

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

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

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

And Set advice window in schedule 2s 513ms

And Fill advice form 14s 719ms

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

And Go to "TRANSPORT_TABLE" 260ms

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

Then Check are advice values equals 2s 340ms

Hooks

After Hooks.deleteTransportAfterTest() 147ms

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

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

And Add transport by SKApi in "MGW" 003ms

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

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

And Set advice window in schedule 2s 599ms

And Fill advice form 14s 666ms

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

And Go to "TRANSPORT_TABLE" 214ms

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

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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

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 9s 342ms

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

And Set advice window in schedule 2s 613ms

And Fill advice form 14s 752ms

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

And Go to "TRANSPORT_TABLE" 216ms

Then Check advice data in SK API database "CONTAINER" 1s 094ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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

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

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

And Set advice window in schedule 2s 527ms

And Fill advice form 14s 684ms

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

And Go to "TRANSPORT_TABLE" 251ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 3s 057ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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

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

And Check is transport "CONTAINER" created in transport table and set transport id 9s 352ms

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

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

And Fill advice form 14s 748ms

And Click advice save button to check error message 099ms

Then Check if possible advice alert is displayed 024ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

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

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

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 39s 470ms

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

And Go to "TRANSPORT_TABLE" 204ms

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

And Expand advice panel 107ms

And Edit advice in transport details 14s 071ms

And Fill arrival date field 2s 296ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 143ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 221ms

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

And Expand advice panel 117ms

And Edit advice in transport details 14s 168ms

And Fill arrival date field 2s 290ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 137ms

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

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 33s 346ms

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

And Go to "TRANSPORT_TABLE" 255ms

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

And Expand advice panel 108ms

And Edit advice in transport details 14s 120ms

And Fill arrival date field 2s 303ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 110ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

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

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

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

When Go to "WAREHOUSE_TAB" 757ms

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

And Select view "DAYS_2" 2s 083ms

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

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

And Select view "DAYS_2" 2s 055ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 182ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

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

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

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

When Go to "WAREHOUSE_TAB" 727ms

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

And Select view "DAYS_2" 2s 074ms

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

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

And Select view "DAYS_2" 2s 054ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 147ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

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

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

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

When Go to "WAREHOUSE_TAB" 738ms

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

And Select view "DAYS_2" 2s 077ms

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

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

And Select view "DAYS_2" 2s 052ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 131ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

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

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

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

When Go to "WAREHOUSE_TAB" 454ms

And Select warehouse "MGW" 1s 171ms

And Select view "DAYS_2" 2s 074ms

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

And Select warehouse "HRL" 1s 388ms

And Select view "DAYS_2" 2s 057ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 186ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

Scenario Outline Check if windows are visible after switching warehouse

Steps

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

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

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

When Go to "WAREHOUSE_TAB" 413ms

And Select warehouse "MGW" 1s 316ms

And Select view "DAYS_2" 2s 062ms

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

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[@data-window-type='state-disabled'] | //div[@data-window-type='state-template']"}
  (Session info: headless chrome=89.0.4389.114)
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=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.9IPk1e}, 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=89.0.4389.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: a29274008b6467118e33d32e9ee1aa75
*** Element info: {Using=xpath, value=//div[@data-window-type='state-disabled'] | //div[@data-window-type='state-template']}
	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.GrayWindow.CreateGrayWindowTest.checkIfGrayWindowIsInTheSchedule(CreateGrayWindowTest.java:114)
	at ✽.Check if gray window is in the schedule(file:Features/Atom/Schedule/Schedule.feature:41)

And Select warehouse "HRL" 000ms

And Select view "DAYS_2" 000ms

And Check if gray window is in the schedule 000ms

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 30s 213ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

Scenario Outline Check if windows are visible after switching warehouse

Steps

Given Login as "3cargo-carrier" and set token of apiUsername "super-admin-skz" 2s 647ms

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

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

When Go to "WAREHOUSE_TAB" 424ms

And Select warehouse "MGW" 1s 324ms

And Select view "DAYS_2" 2s 065ms

Then Check if gray window is in the schedule 17s 029ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[@data-window-type='state-disabled'] | //div[@data-window-type='state-template']"}
  (Session info: headless chrome=89.0.4389.114)
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=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.9IPk1e}, 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=89.0.4389.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: a29274008b6467118e33d32e9ee1aa75
*** Element info: {Using=xpath, value=//div[@data-window-type='state-disabled'] | //div[@data-window-type='state-template']}
	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.GrayWindow.CreateGrayWindowTest.checkIfGrayWindowIsInTheSchedule(CreateGrayWindowTest.java:114)
	at ✽.Check if gray window is in the schedule(file:Features/Atom/Schedule/Schedule.feature:41)

And Select warehouse "HRL" 000ms

And Select view "DAYS_2" 000ms

And Check if gray window is in the schedule 000ms

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 30s 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 394ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 133ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 133ms

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

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

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

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

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

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 "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 1s 126ms

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

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

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

Then Check if transport has "departed" 028ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 102ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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

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

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

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

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

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

And Set advice window in schedule 2s 720ms

And Fill advice form 14s 773ms

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

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

And Go to "TRANSPORT_TABLE" 191ms

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

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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

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

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

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

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

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

And Set advice window in schedule 2s 679ms

And Fill advice form 14s 608ms

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

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

And Go to "TRANSPORT_TABLE" 209ms

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

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

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

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

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

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

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

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

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

Hooks

After Hooks.rollbackAddedActionAuthorities() 061ms

After Hooks.deleteTransportAfterTest() 107ms

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

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

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

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

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

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 129ms

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

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

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

And Show all transport types 1s 050ms

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

And Set advice window in schedule 2s 553ms

And Fill advice form 8s 391ms

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

And Go to "TRANSPORT_TABLE" 231ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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

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

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

And Show all transport types 1s 039ms

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

And Set advice window in schedule 2s 587ms

And Fill advice form 8s 391ms

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

And Go to "TRANSPORT_TABLE" 209ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 109ms

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

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

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

And Show all transport types 1s 057ms

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

And Set advice window in schedule 2s 572ms

And Fill advice form 8s 451ms

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

And Go to "TRANSPORT_TABLE" 207ms

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

When Add file to transport by API 513ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 102ms

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

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

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

And Show all transport types 1s 029ms

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

And Set advice window in schedule 2s 575ms

And Fill advice form 8s 426ms

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

And Go to "TRANSPORT_TABLE" 198ms

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

When Add file to transport by API 263ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - with advice step

Steps

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

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

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

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

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

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

And Show all transport types 1s 042ms

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

And Set advice window in schedule 6s 436ms

And Fill advice form 11s 882ms

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

And Go to "TRANSPORT_TABLE" 218ms

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

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

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

Hooks

After Hooks.rollbackCustomFieldSettings() 058ms

After Hooks.deleteTransportAfterTest() 089ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - with advice step

Steps

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

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

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

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

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

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

And Show all transport types 1s 151ms

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

And Set advice window in schedule 2s 385ms

And Fill advice form 13s 211ms

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

And Go to "TRANSPORT_TABLE" 168ms

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

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

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

Hooks

After Hooks.rollbackCustomFieldSettings() 041ms

After Hooks.deleteTransportAfterTest() 127ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - with advice step

Steps

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

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

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

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 Login as "keeeper-admin" 2s 050ms

And Show all transport types 1s 066ms

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

And Set advice window in schedule 2s 426ms

And Fill advice form 13s 230ms

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

And Go to "TRANSPORT_TABLE" 214ms

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

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

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

Hooks

After Hooks.rollbackCustomFieldSettings() 047ms

After Hooks.deleteTransportAfterTest() 104ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - without advice step

Steps

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 119ms

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

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

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

Hooks

After Hooks.rollbackCustomFieldSettings() 035ms

After Hooks.deleteTransportAfterTest() 083ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - without advice step

Steps

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 117ms

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

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

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

Hooks

After Hooks.rollbackCustomFieldSettings() 048ms

After Hooks.deleteTransportAfterTest() 112ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is not possible to confirm statuses when there is customFields blockade - without advice step

Steps

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 172ms

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

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

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

Hooks

After Hooks.rollbackCustomFieldSettings() 110ms

After Hooks.deleteTransportAfterTest() 115ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Steps

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

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

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

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

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

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

And Show all transport types 1s 122ms

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

And Set advice window in schedule 2s 403ms

And Fill advice form 13s 229ms

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

And Go to "TRANSPORT_TABLE" 210ms

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

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

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

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

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

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

And Fill transport form 24s 803ms

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

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

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

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

And Confirm statuses until reach "process-ended" 24s 316ms

Then Check if transport has "process-ended" 028ms

Hooks

After Hooks.rollbackCustomFieldSettings() 043ms

After Hooks.deleteTransportAfterTest() 102ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 094ms

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "CONTAINER" 025ms

And Get inputs from database "ADVICE_CONTAINER" "super-admin-keeeper" 002ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_CONTAINER_SANITARY_CONDITIONS_CFD" in "CONTAINER" - "keeeper" by "super-admin-keeeper" 043ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 213ms

And Login as "keeeper-admin" 2s 524ms

And Show all transport types 1s 059ms

And Click button advice in transport table "CONTAINER" 111ms

And Set advice window in schedule 2s 368ms

And Fill advice form 13s 197ms

And Click advice save button and wait for advice form to disappear 30s 700ms

And Go to "TRANSPORT_TABLE" 215ms

And Find transport in table with status "advice-added" 3s 245ms

When Confirm statuses until reach "arrived" 3s 826ms

And Check if next status is not possible to confirm 106ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 001ms

And Go to transport details "CONTAINER" 4s 381ms

And Open section: "advice-panel" 1s 073ms

And Fill transport form 24s 807ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 638ms

And Go to transport details "CONTAINER" 4s 361ms

And Open section: "advice-panel" 1s 069ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 15s 813ms

And Confirm statuses until reach "process-ended" 24s 258ms

Then Check if transport has "process-ended" 026ms

Hooks

After Hooks.rollbackCustomFieldSettings() 071ms

After Hooks.deleteTransportAfterTest() 100ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - with advice step

Steps

Given Set token of apiUsername "super-admin-hochland" 097ms

And Get "Magazynier (R)" settings from "hochland" in "TRANSFER_BETWEEN_WAREHOUSES" 024ms

And Get inputs from database "ADVICE_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 002ms

And Set custom field "Magazynier (R)" with "EDIT_TRANSFER_BETWEEN_WAREHOUSES_WAREHOUSEMAN_U_CFD" in "TRANSFER_BETWEEN_WAREHOUSES" - "hochland" by "super-admin-hochland" 064ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 182ms

And Login as "hochland-admin" 3s 146ms

And Show all transport types 1s 065ms

And Click button advice in transport table "TRANSFER_BETWEEN_WAREHOUSES" 138ms

And Set advice window in schedule 6s 435ms

And Fill advice form 11s 892ms

And Click advice save button and wait for advice form to disappear 30s 733ms

And Go to "TRANSPORT_TABLE" 219ms

And Find transport in table with status "advice-added" 3s 227ms

When Confirm statuses until reach "during-load" 7s 053ms

And Check if next status is not possible to confirm 102ms

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 002ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 617ms

And Open section: "advice-panel" 1s 078ms

And Fill transport form 36s 267ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 161ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 549ms

And Open section: "advice-panel" 1s 075ms

And Fill "warehouseman-(u)" in transport form 15s 857ms

And Confirm statuses until reach "process-ended" 32s 525ms

Then Check if transport has "process-ended" 028ms

Hooks

After Hooks.rollbackCustomFieldSettings() 069ms

After Hooks.deleteTransportAfterTest() 146ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 097ms

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "UNLOAD" 016ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 001ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 046ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 354ms

And Login as "keeeper-admin" 2s 409ms

And Go to "TRANSPORT_TABLE" 109ms

And Find transport in table with status "planned" 3s 203ms

When Confirm statuses until reach "arrived" 3s 852ms

And Check if next status is not possible to confirm 109ms

And Go to transport details "UNLOAD" 4s 418ms

And Fill transport form 37s 954ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 679ms

And Confirm statuses until reach "process-ended" 24s 272ms

Then Check if transport has "process-ended" 029ms

Hooks

After Hooks.rollbackCustomFieldSettings() 059ms

After Hooks.deleteTransportAfterTest() 150ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 094ms

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "TANKER_GRANULATE_DELIVERY" 021ms

And Get inputs from database "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 002ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_TANKER_GRANULATE_DELIVERY_SANITARY_CONDITIONS_CFD" in "TANKER_GRANULATE_DELIVERY" - "keeeper" by "super-admin-keeeper" 038ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 341ms

And Login as "keeeper-admin" 2s 012ms

And Go to "TRANSPORT_TABLE" 120ms

And Find transport in table with status "planned" 3s 177ms

When Confirm statuses until reach "arrived" 3s 815ms

And Check if next status is not possible to confirm 109ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 394ms

And Fill transport form 36s 377ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 625ms

And Confirm statuses until reach "process-ended" 24s 310ms

Then Check if transport has "process-ended" 029ms

Hooks

After Hooks.rollbackCustomFieldSettings() 087ms

After Hooks.deleteTransportAfterTest() 090ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm statuses when there is customFields blockade and conditions are fulfilled - without advice step

Steps

Given Set token of apiUsername "super-admin-hochland" 093ms

And Get "Magazynier" settings from "hochland" in "DELIVERY" 021ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 100ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 394ms

And Login as "hochland-admin" 2s 568ms

And Go to "TRANSPORT_TABLE" 196ms

And Find transport in table with status "advice-added" 3s 226ms

When Confirm statuses until reach "during-unload" 6s 573ms

And Check if next status is not possible to confirm 104ms

And Go to transport details "DELIVERY" 4s 655ms

And Fill transport form 36s 036ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 163ms

And Confirm statuses until reach "process-ended" 21s 550ms

Then Check if transport has "process-ended" 024ms

Hooks

After Hooks.rollbackCustomFieldSettings() 112ms

After Hooks.deleteTransportAfterTest() 103ms

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" 096ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 1s 351ms

And Confirm status "REPORTING" by Public API "v1" 091ms

And Confirm status "ARRIVAL" by Public API "v1" 117ms

And Login as "swiss-krono-delivery-guard" 1s 837ms

And Go to "TRANSPORT_TABLE" 186ms

When Confirm "Departure" status in transport row 3s 078ms

Then Verify that "Departure" has been confirmed 037ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm next status in transport details on transport details reopen after filling blocade customfields and not saving changes - without advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 101ms

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "UNLOAD" 024ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 002ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 044ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 15s 363ms

When Login as "keeeper-admin" 2s 035ms

And Find transport in table with status "planned" 3s 212ms

And Confirm statuses until reach "arrived" 3s 806ms

And Go to transport details "UNLOAD" 4s 393ms

And Fill transport form 37s 978ms

Then Check if next status is not possible to confirm in transport details 059ms

Hooks

After Hooks.rollbackCustomFieldSettings() 054ms

After Hooks.deleteTransportAfterTest() 112ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm next status in transport details on transport details reopen after filling blocade customfields and not saving changes - without advice step

Steps

Given Set token of apiUsername "super-admin-keeeper" 096ms

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "TANKER_GRANULATE_DELIVERY" 025ms

And Get inputs from database "EDIT_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 003ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_TANKER_GRANULATE_DELIVERY_SANITARY_CONDITIONS_CFD" in "TANKER_GRANULATE_DELIVERY" - "keeeper" by "super-admin-keeeper" 044ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 348ms

When Login as "keeeper-admin" 2s 101ms

And Find transport in table with status "planned" 3s 238ms

And Confirm statuses until reach "arrived" 3s 818ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 393ms

And Fill transport form 36s 359ms

Then Check if next status is not possible to confirm in transport details 070ms

Hooks

After Hooks.rollbackCustomFieldSettings() 039ms

After Hooks.deleteTransportAfterTest() 087ms

View Feature Status confirmation

@deleteTransportAfterTest @rollbackCustomFieldSettings

Scenario Outline Check if it is possible to confirm next status in transport details on transport details reopen after filling blocade customfields and not saving changes - without advice step

Steps

Given Set token of apiUsername "super-admin-hochland" 096ms

And Get "Magazynier" settings from "hochland" in "DELIVERY" 021ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 002ms

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 096ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 405ms

When Login as "hochland-admin" 2s 460ms

And Find transport in table with status "advice-added" 3s 315ms

And Confirm statuses until reach "during-unload" 6s 586ms

And Go to transport details "DELIVERY" 4s 684ms

And Fill transport form 36s 072ms

Then Check if next status is not possible to confirm in transport details 065ms

Hooks

After Hooks.rollbackCustomFieldSettings() 117ms

After Hooks.deleteTransportAfterTest() 103ms

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" 095ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 498ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 236ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 138ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 750ms

And Login as "bausch-admin" 2s 084ms

And Go to "TRANSPORT_TABLE" 240ms

And Find transport in table with status "advice-added" 3s 199ms

When Confirm statuses until reach "on-the-way" 9s 365ms

And Open statuses popup 067ms

And Toggle status date confirmation checkbox 280ms

And Confirm statuses until reach "process-ended" 18s 732ms

Then Check if transport has "process-ended" 030ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

After Hooks.deleteModeOfTransportationAfterTest() 093ms

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" 094ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 283ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 252ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 120ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 700ms

And Login as "bausch-admin" 1s 107ms

And Go to "TRANSPORT_TABLE" 203ms

And Find transport in table with status "advice-added" 3s 219ms

When Confirm statuses until reach "on-the-way" 9s 850ms

And Open statuses popup 066ms

And Toggle status date confirmation checkbox 280ms

And Change status execution date to "1" days from today 2s 202ms

Then Verify that status cannot be confirmed 1s 080ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

After Hooks.deleteModeOfTransportationAfterTest() 152ms

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" 091ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 309ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 175ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 118ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 701ms

And Login as "bausch-admin" 1s 030ms

And Go to "TRANSPORT_TABLE" 203ms

And Find transport in table with status "advice-added" 3s 207ms

When Confirm statuses until reach "on-the-way" 9s 302ms

And Open statuses popup 059ms

And Toggle status date confirmation checkbox 261ms

And Change status execution date to "-1" days from today 2s 182ms

Then Verify that status cannot be confirmed 1s 070ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

After Hooks.deleteModeOfTransportationAfterTest() 076ms

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" 095ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 248ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 694ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 182ms

When Login as "farmacol-admin" 2s 289ms

And Go to "TRANSPORT_TABLE" 216ms

And Confirm statuses until reach "during-unload" 9s 383ms

And Set actual confirmed transport status list 1s 398ms

And Disable task by API 203ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 473ms

And Edit transport hours and recalculate statuses 16s 343ms

Then Verify that all confirmed statuses are still on transport status list 194ms

Hooks

After Hooks.deleteTransportAfterTest() 143ms

After Hooks.rollbackTaskChanges() 050ms

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 887ms

And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 253ms

And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 1s 577ms

And Create transport "CREATE_LOAD_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 380ms

And Check if reject date is not visible 15s 013ms

When Reject status: Book of disinfection 15s 053ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//button[@data-button-name='reject-checkpoint']"}
  (Session info: headless chrome=89.0.4389.114)
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=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.9IPk1e}, 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=89.0.4389.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: a29274008b6467118e33d32e9ee1aa75
*** Element info: {Using=xpath, value=//button[@data-button-name='reject-checkpoint']}
	at sun.reflect.GeneratedConstructorAccessor206.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at CucumberTests.StatusTests.RejectStatuses.rejectStatusBookOfDisinfection(RejectStatuses.java:41)
	at ✽.Reject status: Book of disinfection(file:Features/Atom/Statuses/RejectStatuses.feature:10)

And Check if reject date is visible 000ms

Then If user is login then logout 000ms

And Login as "lantmannen-admin" 000ms

And Check if note was added to transport after status rejection 000ms

And Check if history note was added to transport after status rejection - "LOAD" 000ms

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nieaktualna księga mycia i dezynfekcji" 000ms

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 180ms

After Hooks.deleteTransportAfterTest() 098ms

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 751ms

And Create transport "CREATE_LOAD_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 268ms

And Check if reject date is not visible 15s 033ms

When Reject status: Book of disinfection 080ms

And Check if reject date is visible 260ms

And Get rejection date 023ms

And Wait "60" seconds 1m

And Reject status: Book of disinfection 067ms

Then Check if reject date has changed 1s 089ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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 123ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 332ms

And Go to transport details "LOAD" 4s 341ms

And Check if reject date is not visible 15s 023ms

When Reject status: Book of disinfection 069ms

Then Check if reject date is visible 141ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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" 976ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 389ms

And Open statuses popup 104ms

And Check if reject date is not visible 15s 026ms

When Reject status: Book of disinfection 088ms

Then Open statuses popup 057ms

And Check if reject date is visible 093ms

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 "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 646ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 418ms

And Confirm to the last status by API 235ms

When Find statuses for transport in table 1s 982ms

And Revoke statuses until reach "advice-added" 6s 841ms

Then Check if transport has "advice-added" 025ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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 985ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 355ms

And Confirm to the last status by API 221ms

When Find statuses for transport in table 1s 715ms

And Revoke statuses until reach "planned" 6s 753ms

Then Check if transport has "planned" 024ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

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 154ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 186ms

When Find transport in table with status "new" 3s 224ms

And Open statuses popup 092ms

Then Check if transport has checkpoints from list "Utworzenie zlecenia,Dodanie awizacji,Potwierdzenie okna czasowego" in "0" 072ms

Hooks

After Hooks.deleteTransportAfterTest() 059ms

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 087ms

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 184ms

And Click button advice in transport table "EXTERNAL_DELIVERY" 115ms

And Set advice window in schedule 2s 640ms

And Fill advice form 12s 073ms

And Click advice save button and wait for advice form to disappear 30s 781ms

And Go to "TRANSPORT_TABLE" 262ms

When Find transport in table with status "advice-added" 3s 201ms

And Open statuses popup 108ms

Then Check if transport has checkpoints from list "Zgłoszenie kierowcy,Rozpoczęcie rozładunku,Zakończenie rozładunku" in "1" 079ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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" 093ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 183ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 521ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 022ms

When Login as "farmacol-admin" 1s 170ms

And Go to "TRANSPORT_TABLE" 209ms

And Confirm statuses until reach "registered-katowice-przyjęcia" 6s 631ms

And Disable task by API 046ms

And Find transport pencil button in transports table 1s 256ms

And Click pencil and move transport to next day in schedule 18s 144ms

And Go to "TRANSPORT_TABLE" 264ms

Then Verify that "START_OF_UNLOADING" is not visible 129ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

After Hooks.rollbackTaskChanges() 046ms

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 483ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 375ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 095ms

When Go to "WAREHOUSE_TAB" 765ms

And Select warehouse "Serownia" 1s 424ms

And Set week view 1s 119ms

And Show yesterday 1s 075ms

And Move window into the past 309ms

Then Check if window is "red" 2s 027ms

Hooks

After Hooks.rollbackAddedAuthorities() 055ms

After Hooks.deleteTransportAfterTest() 135ms

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" 1s 002ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 353ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "lantmannen-admin" 046ms

When Go to "WAREHOUSE_TAB" 302ms

And Select warehouse "Magazyn - Nowa Sól" 2s 167ms

And Set week view 1s 191ms

And Show yesterday 1s 067ms

And Move window into the past 426ms

Then Check if window is "red" 2s 028ms

Hooks

After Hooks.rollbackAddedAuthorities() 042ms

After Hooks.deleteTransportAfterTest() 122ms

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 337ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 224ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "piast-admin" 049ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 002ms

When Show all transport types 1s 051ms

And Click button advice in transport table "DELIVERY" 133ms

And Set advice window in schedule 2s 554ms

And Fill advice form 8s 480ms

And Click advice save button and wait for advice form to disappear 30s 674ms

And Select warehouse "Magazyn Hala A" 1s 191ms

And Set week view 2s 031ms

And Show yesterday 1s 162ms

And Move window into the past 577ms

Then Check if window is "red" 2s 058ms

Hooks

After Hooks.rollbackAddedAuthorities() 048ms

After Hooks.deleteTransportAfterTest() 112ms

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 903ms

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" 541ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 414ms

When Go to "WAREHOUSE_TAB" 758ms

And Select warehouse "Magazyn Zimny Kaźmierz" 1s 700ms

And Set week view 1s 119ms

And Check if time window length is correct after "CREATE" 025ms

And Change number of pallets in transport 50s 956ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 207ms

And Check if time window length is correct after "EDIT" 051ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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 183ms

And Get "UNLOAD" settings from "keeeper" 057ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 107ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;true" 115ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 358ms

When Go to "WAREHOUSE_TAB" 323ms

And Select warehouse "Magazyn Surowców" 1s 188ms

And Set week view 1s 094ms

Then Check if time window has proper "60" 022ms

Hooks

After Hooks.rollbackTransportTypeSettings() 090ms

After Hooks.clearAlgorithmSettings() 126ms

After Hooks.deleteTransportAfterTest() 086ms

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 105ms

And Get "UNLOAD" settings from "keeeper" 026ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 084ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;false" 049ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 299ms

When Go to "WAREHOUSE_TAB" 325ms

And Select warehouse "Magazyn Surowców" 1s 144ms

And Set week view 1s 090ms

Then Check if time window has proper "60" 024ms

Hooks

After Hooks.rollbackTransportTypeSettings() 057ms

After Hooks.clearAlgorithmSettings() 095ms

After Hooks.deleteTransportAfterTest() 108ms

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 112ms

And Get "LOAD" settings from "keeeper" 028ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 100ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;false" 066ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 187ms

And Get inputs from database "ADVICE_LOAD" "super-admin-keeeper" 003ms

And Show all transport types 1s 051ms

And Click button advice in transport table "LOAD" 120ms

And Set advice window in schedule 2s 399ms

And Fill advice form 13s 273ms

And Click advice save button and wait for advice form to disappear 30s 743ms

Then Check if time window has proper "30" 026ms

Hooks

After Hooks.rollbackTransportTypeSettings() 117ms

After Hooks.clearAlgorithmSettings() 102ms

After Hooks.deleteTransportAfterTest() 125ms

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 148ms

And Get "CONTAINER" settings from "keeeper" 019ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 090ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "20;false" 059ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 199ms

And Get inputs from database "ADVICE_CONTAINER" "super-admin-keeeper" 003ms

And Show all transport types 1s 050ms

And Click button advice in transport table "CONTAINER" 135ms

And Set advice window in schedule 2s 386ms

And Fill advice form 13s 229ms

And Click advice save button and wait for advice form to disappear 30s 657ms

Then Check if time window has proper "60" 025ms

Hooks

After Hooks.rollbackTransportTypeSettings() 057ms

After Hooks.clearAlgorithmSettings() 105ms

After Hooks.deleteTransportAfterTest() 082ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings

Scenario Outline Check if supplier can change time window size by change number of pallets

Steps

Given Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "super-admin-hochland" 2s 553ms

And Set algorithm setting for "super-admin-hochland" in "Serownia" on "Magazyn Sera" 181ms

And Set token of apiUsername "dha1-supplier-2@qa.qa-test" 089ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 15s 328ms

And Set token of apiUsername "super-admin-hochland" 107ms

When Go to transport details "DELIVERY" 32s 789ms

And Change filled value in transport details "quantity" "number" "25" "0" 1s 355ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 102ms

Error message

org.openqa.selenium.InvalidElementStateException: invalid element state: Element is not currently interactable and may not be manipulated
  (Session info: headless chrome=89.0.4389.114)
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=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.9IPk1e}, 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=89.0.4389.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: a29274008b6467118e33d32e9ee1aa75
	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.RemoteWebElement.execute(RemoteWebElement.java:279)
	at org.openqa.selenium.remote.RemoteWebElement.clear(RemoteWebElement.java:118)
	at CucumberTests.Transport.Transport.fillTextOrNumberInput(Transport.java:189)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:160)
	at CucumberTests.Transport.TransportFormTest.changeFilledValueInTransportDetails(TransportFormTest.java:274)
	at ✽.Change filled value in transport details "unloaded-stere" "text" "3" "0"(file:Features/Atom/TimeWindow/TransportWindow.feature:140)

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 000ms

And Change filled value in transport details "insp.-accord.-with-ins." "select" "TAK" "0" 000ms

And Click "save-transport-and-close" save button and wait for form to disappear 000ms

And Go to "WAREHOUSE_TAB" 000ms

And Select warehouse "Serownia" 000ms

And Set week view 000ms

Then Check if time window has proper "60" 000ms

Hooks

After Hooks.clearAlgorithmSettings() 171ms

After Hooks.deleteTransportAfterTest() 095ms

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 188ms

And Set basic authorities "ROLE_ACCESS_TO_NUMBER_OF_WINDOWS" to user "keeeper-admin" 041ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 191ms

When Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 46s 569ms

And Check if time window counter value equals "1" 079ms

And Select view "DAYS_2" 2s 084ms

And Move advice window "2" 1s 352ms

And Select view "DAY" 2s 079ms

Then Check if time window counter value equals "0" 075ms

And Delete created transport by API 157ms

And Check if time window counter value equals "0" 055ms

And Click in free spot in schedule page to create gray window 189ms

And Check if time window counter value equals "0" 049ms

And Click in free spot in schedule page to create dedicated window 054ms

And Check if time window counter value equals "0" 060ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.deleteTransportAfterTest() 085ms

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" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 039ms

When Go to new transport "DELIVERY" 288ms

And Fill transport form 11s 470ms

And Click "save-transport" save button and wait for form to disappear 15s 611ms

And Set advice window in schedule 2s 196ms

And Check is transport created in schedule and set transport id 559ms

And Go to "TRANSPORT_TABLE" 277ms

When Click on time window date 1s 323ms

And Open transport form when in schedule 1s 151ms

Then Check are transport values equals 136ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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 402ms

When Go to new transport "DELIVERY" 353ms

And Fill transport form 38s 870ms

And Click "save-transport" save button and wait for form to disappear 15s 633ms

And Set advice window in schedule 2s 149ms

And Check is transport created in schedule and set transport id 630ms

And Go to "TRANSPORT_TABLE" 282ms

When Click on time window date 1s 278ms

And Open transport form when in schedule 1s 356ms

Then Check are transport values equals 19s 419ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 429ms

When Go to new transport "CISTERN_DELIVERY" 373ms

And Fill transport form 35s 060ms

And Click "save-transport" save button and wait for form to disappear 15s 881ms

And Set advice window in schedule 2s 222ms

And Check is transport created in schedule and set transport id 657ms

And Go to "TRANSPORT_TABLE" 201ms

When Click on time window date 1s 422ms

And Open transport form when in schedule 1s 201ms

Then Check are transport values equals 21s 398ms

Hooks

After Hooks.deleteTransportAfterTest() 147ms

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" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 422ms

When Go to new transport "CISTERN_COLLECTION" 339ms

And Fill transport form 28s 408ms

And Click "save-transport" save button and wait for form to disappear 15s 802ms

And Set advice window in schedule 2s 229ms

And Check is transport created in schedule and set transport id 611ms

And Go to "TRANSPORT_TABLE" 213ms

When Click on time window date 1s 469ms

And Open transport form when in schedule 1s 216ms

Then Check are transport values equals 21s 425ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

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 387ms

When Go to new transport "DELIVERY" 299ms

And Fill transport form 38s 064ms

And Click "save-transport" save button and wait for form to disappear 15s 620ms

And Set advice window in schedule 2s 157ms

And Check is transport created in schedule and set transport id 601ms

And Go to "TRANSPORT_TABLE" 191ms

When Click on time window date 1s 340ms

And Open transport form when in schedule 1s 164ms

Then Check are transport values equals 19s 331ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

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 166ms

When Go to new transport "LOAD" 309ms

And Fill transport form 38s 098ms

And Click "save-transport" save button and wait for form to disappear 15s 683ms

And Set advice window in schedule 2s 152ms

And Check is transport created in schedule and set transport id 554ms

And Go to "TRANSPORT_TABLE" 236ms

When Click on time window date 1s 335ms

And Open transport form when in schedule 1s 177ms

Then Check are transport values equals 19s 367ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackTransportTypeSettings

Scenario Outline Check if it is possible to add new warehouse step with new time window to existing transport

Steps

Given Set token of apiUsername "super-admin-farmacol" 096ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 092ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 052ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 102ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 182ms

And Login as "farmacol-admin" 2s 391ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 45s 698ms

And Go to "TRANSPORT_TABLE" 295ms

When Go to transport details "EXTERNAL_DELIVERY" 4s 438ms

And Add step "unload" 102ms

And Change filled value in transport details "warehouse-select-step-2" "select" "Mory Przyjęcia" "0" 3s 464ms

And Change filled value in transport details "weight-step-2" "number" "23" "0" 1s 366ms

And Change filled value in transport details "number-of-pallets-step-2" "number" "23" "0" 1s 355ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 328ms

Then Click "save-transport" save button 181ms

And Set advice window in schedule in "2" days 4s 930ms

And Click advice save button and wait for advice form to disappear 31s 003ms

And Go to "TRANSPORT_TABLE" 261ms

And Check if transport has "2" time windows 013ms

Hooks

After Hooks.rollbackTransportTypeSettings() 069ms

After Hooks.rollbackAddedActionAuthorities() 058ms

After Hooks.deleteTransportAfterTest() 099ms

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" 095ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 032ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 053ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 200ms

And Set double window advice 000ms

And Login as "farmacol-admin" 2s 004ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 22s 058ms

Error message

java.lang.AssertionError: Nie można wypełnić pola driver-name, ponieważ nie udało się go znaleźć w formularzu
	at org.junit.Assert.fail(Assert.java:88)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:152)
	at CucumberTests.Transport.AdviceTransport.fillAdviceForm(AdviceTransport.java:114)
	at CucumberTests.Transport.AdviceTransport.createAdvice(AdviceTransport.java:60)
	at ✽.Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol"(file:Features/Atom/TimeWindow/TransportWindow.feature:229)

And Go to "TRANSPORT_TABLE" 000ms

And Get checkpoint colors for transport 000ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "true" 000ms

Hooks

After Hooks.rollbackTransportTypeSettings() 130ms

After Hooks.deleteTransportAfterTest() 079ms

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" 096ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 041ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 094ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 15s 182ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 082ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 22s 070ms

Error message

java.lang.AssertionError: Nie można wypełnić pola driver-name, ponieważ nie udało się go znaleźć w formularzu
	at org.junit.Assert.fail(Assert.java:88)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:152)
	at CucumberTests.Transport.AdviceTransport.fillAdviceForm(AdviceTransport.java:114)
	at CucumberTests.Transport.AdviceTransport.createAdvice(AdviceTransport.java:60)
	at ✽.Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol"(file:Features/Atom/TimeWindow/TransportWindow.feature:229)

And Go to "TRANSPORT_TABLE" 000ms

And Get checkpoint colors for transport 000ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "false" 000ms

Hooks

After Hooks.rollbackTransportTypeSettings() 082ms

After Hooks.deleteTransportAfterTest() 082ms

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" 096ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 033ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 058ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 15s 169ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 122ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 22s 100ms

Error message

java.lang.AssertionError: Nie można wypełnić pola driver-name, ponieważ nie udało się go znaleźć w formularzu
	at org.junit.Assert.fail(Assert.java:88)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:152)
	at CucumberTests.Transport.AdviceTransport.fillAdviceForm(AdviceTransport.java:114)
	at CucumberTests.Transport.AdviceTransport.createAdvice(AdviceTransport.java:60)
	at ✽.Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol"(file:Features/Atom/TimeWindow/TransportWindow.feature:247)

And Get checkpoint colors for transport 000ms

And Go to "TRANSPORT_TABLE" 000ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true" 000ms

Hooks

After Hooks.rollbackTransportTypeSettings() 093ms

After Hooks.deleteTransportAfterTest() 061ms

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" 092ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 031ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 066ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 15s 158ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 090ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 22s 126ms

Error message

java.lang.AssertionError: Nie można wypełnić pola driver-name, ponieważ nie udało się go znaleźć w formularzu
	at org.junit.Assert.fail(Assert.java:88)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:152)
	at CucumberTests.Transport.AdviceTransport.fillAdviceForm(AdviceTransport.java:114)
	at CucumberTests.Transport.AdviceTransport.createAdvice(AdviceTransport.java:60)
	at ✽.Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol"(file:Features/Atom/TimeWindow/TransportWindow.feature:247)

And Get checkpoint colors for transport 000ms

And Go to "TRANSPORT_TABLE" 000ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "false" 000ms

Hooks

After Hooks.rollbackTransportTypeSettings() 075ms

After Hooks.deleteTransportAfterTest() 073ms

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" 097ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 156ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 617ms

And Login as "super-admin-farmacol" 2s 641ms

And Show all transport types 1s 193ms

And Click on time window date 1s 631ms

Then Open transport form when in schedule 1s 255ms

And Click create similar button 15s 176ms

And Click cancel button in transport form 097ms

And Open transport form when in schedule 1s 159ms

Then Check if transport form modal is visible 048ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

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" 093ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 156ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 597ms

And Login as "super-admin-farmacol" 1s 117ms

And Show all transport types 1s 157ms

And Click on time window date 1s 621ms

Then Open transport form when in schedule 1s 251ms

And Click create similar button 15s 181ms

And Click cancel button in transport form 110ms

And Open transport form when in schedule 1s 199ms

Then Check if transport form modal is visible 056ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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" 2s 030ms

And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 003ms

And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 038ms

And Set proper delay time to move order to archive after task timeout 051ms

When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 318ms

And Wait "60" seconds 1m

And Go to "WAREHOUSE_TAB" 616ms

And Change warehouse in schedule to: "Katowice" 1s 170ms

And Verify that transport window is grey 099ms

Error message

java.lang.AssertionError: Okno zlecenia nie zrobiło się szare
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.Warehouse.WarehouseTest.verifyThatTransportWindowIsGrey(WarehouseTest.java:113)
	at ✽.Verify that transport window is grey(file:Features/Atom/Transport/Archive.feature:13)

And Verify that transport is in archive 000ms

Then Restore transport from archive 000ms

And Verify that transport has been successfully restored 000ms

Hooks

After Hooks.rollbackSettings() 035ms

After Hooks.deleteTransportAfterTest() 135ms

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 140ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 225ms

And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 034ms

And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 003ms

When Go to "TRANSPORT_TABLE" 136ms

And Click button advice in transport table "OWN_COLLECTION" 1s 983ms

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 326ms

Error message

org.openqa.selenium.StaleElementReferenceException: stale element reference: element is not attached to the page document
  (Session info: headless chrome=89.0.4389.114)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/stale_element_reference.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=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.9IPk1e}, 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=89.0.4389.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: a29274008b6467118e33d32e9ee1aa75
	at sun.reflect.GeneratedConstructorAccessor184.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.RemoteWebElement.execute(RemoteWebElement.java:279)
	at org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:83)
	at CucumberTests.Transport.AdviceTransport.adviceTransport(AdviceTransport.java:69)
	at CucumberTests.Transport.AdviceTransport.createAdvice(AdviceTransport.java:57)
	at ✽.Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco"(file:Features/Atom/Transport/Archive.feature:42)

And Go to "TRANSPORT_TABLE" 000ms

And Find transport in table with status "planned-magazyn-tychy" 000ms

And Confirm statuses until reach "process-ended" 000ms

And Wait "12" seconds 000ms

Then Go to "ARCHIVE_TAB" 000ms

And Show "OWN_COLLECTION" 000ms

And Verify that created transport is "true" in transport table 000ms

Hooks

After Hooks.rollbackSettings() 027ms

After Hooks.deleteTransportAfterTest() 099ms

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 015ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 240ms

When Fill auction form 15s 497ms

Then Verify that the auction has been added to transport 059ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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 192ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 261ms

When Fill auction form 15s 452ms

Then Verify that the auction has been added to transport 049ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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 132ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 205ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 102ms

When If user is login then logout 107ms

And Login as "paa1-carrier@qa.qa-test" 1s 942ms

And Go to auction offer 1s 206ms

And Accept transport with minimum rate 15s 637ms

Then Check if carrier is assigned to transport 019ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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 067ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 216ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 088ms

When If user is login then logout 127ms

And Login as "paa1-carrier@qa.qa-test" 1s 084ms

And Go to auction offer 1s 291ms

And Reject auction offer 15s 611ms

Then Verify that offer has been removed from transport 15s 028ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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 246ms

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 087ms

When If user is login then logout 104ms

And Login as "pskza1-carrier@qa.qa-test" 1s 130ms

And Go to auction offer 1s 205ms

And Reject auction offer 15s 599ms

Then Verify that offer has been removed from transport 15s 061ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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 164ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 225ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 101ms

When If user is login then logout 134ms

And Login as "paa1-carrier@qa.qa-test" 1s 187ms

And Go to auction offer 1s 277ms

And Offer prize above maximum - "20000" 146ms

Then Verify that is not possible to add offer 157ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

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 102ms

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 087ms

When If user is login then logout 097ms

And Login as "pskza1-carrier@qa.qa-test" 1s 096ms

And Go to auction offer 1s 213ms

And Offer prize above maximum - "20000" 129ms

Then Verify that is not possible to add offer 153ms

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 029ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 212ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 089ms

And Wait till auction end 1m 58s 018ms

Then Verify that is possible to add auction 053ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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 289ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 256ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 113ms

And Wait till auction end 1m 58s 028ms

Then Verify that is possible to add auction 054ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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 224ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 208ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 100ms

And Go to auction offer 1s 209ms

When Offer "1000" 142ms

Then Verify that offer with "1000" has been added to auction 3s 040ms

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 "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 518ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 246ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 109ms

And Go to auction offer 1s 218ms

When Offer "1000" 145ms

Then Verify that offer with "1000" has been added to auction 3s 038ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

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 025ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 222ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 089ms

And Go to auction offer 1s 196ms

When Offer "1000" 139ms

And Verify that offer with "1000" has been added to auction 3s 040ms

Then Go to auction offer 1s 188ms

And Revoke current offer 564ms

And Verify that offer has been revoked 30s 627ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

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 144ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 278ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 116ms

And Go to auction offer 1s 202ms

When Offer "1000" 149ms

And Verify that offer with "1000" has been added to auction 3s 040ms

Then Go to auction offer 1s 190ms

And Offer "1500" 130ms

And Verify that offer with "1500" has been added to auction 3s 031ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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 064ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 238ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 107ms

And Go to auction offer 1s 222ms

When Offer "1000" 146ms

And Verify that offer with "1000" has been added to auction 3s 033ms

Then Login as "swisskrono-admin" 1s 037ms

And Go to auction details 1s 218ms

And Finish active auction 052ms

And Verify that the transport has no active auction 161ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

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 046ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 216ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 100ms

And Go to auction offer 1s 200ms

When Offer "1000" 106ms

Then Verify that carrier can see current place in auction depending on the "true" role 138ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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" 986ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 225ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 106ms

And Go to auction offer 1s 187ms

When Offer "1000" 137ms

Then Verify that carrier can see current place in auction depending on the "false" role 15s 019ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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 090ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 254ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 114ms

And Go to auction offer 1s 213ms

When Offer "300" 145ms

And Verify that carrier can't add offer to auction 034ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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 049ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 233ms

And Show all transport "false" 012ms

When Go to auction form 1s 239ms

Then Verify carrier selection value "false" 035ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

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 045ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 284ms

And Show all transport "true" 092ms

When Go to auction form 1s 200ms

Then Verify carrier selection value "true" 044ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

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 069ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 243ms

When Open transport auction form 190ms

And Select all companies checkbox in transport auction form 069ms

And Unselect company "PAA2" in transport auction form 070ms

And Put transport on auction 15s 181ms

And Open transport auction history 096ms

And Open participants section in transport auction history 053ms

Then Check if unselected "PAA2" is in transport auction history as participant 15s 007ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

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 191ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 259ms

When Open transport auction form 187ms

And Select all companies checkbox in transport auction form 071ms

And Unselect company "PSKZA2" in transport auction form 067ms

And Put transport on auction 15s 199ms

And Open transport auction history 102ms

And Open participants section in transport auction history 059ms

Then Check if unselected "PSKZA2" is in transport auction history as participant 15s 022ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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" 2s 282ms

When Go to new transport "UNLOAD" 15s 274ms

And Fill transport form 24s 618ms

And Click "save-transport" save button and wait for form to disappear 15s 948ms

And Set advice window in schedule 2s 226ms

And Check is transport created in schedule and set transport id 610ms

And Go to "TRANSPORT_TABLE" 213ms

And Go to transport details "UNLOAD" 32s 392ms

Then Check are transport values equals 21s 399ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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" 003ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 127ms

When Go to new transport "DELIVERY" 286ms

And Fill transport form 11s 463ms

And Click "save-transport" save button and wait for form to disappear 15s 598ms

And Set advice window in schedule 2s 191ms

And Check is transport created in schedule and set transport id 517ms

And Go to "TRANSPORT_TABLE" 248ms

And Go to transport details "DELIVERY" 4s 347ms

Then Check are transport values equals 147ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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 100ms

When Go to new transport "OWN_COLLECTION" 313ms

And Fill transport form 18s 042ms

And Click "save-transport" save button and wait for form to disappear 15s 645ms

And Set advice window in schedule 2s 164ms

And Check is transport created in schedule and set transport id 485ms

And Go to "TRANSPORT_TABLE" 191ms

And Go to transport details "OWN_COLLECTION" 4s 328ms

Then Check are transport values equals 161ms

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_DELIVERY" "super-admin-hochland" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 451ms

When Go to new transport "DELIVERY" 341ms

And Fill transport form 39s 072ms

And Click "save-transport" save button and wait for form to disappear 15s 600ms

And Set advice window in schedule 2s 167ms

And Check is transport created in schedule and set transport id 642ms

And Go to "TRANSPORT_TABLE" 267ms

And Go to transport details "DELIVERY" 4s 557ms

Then Check are transport values equals 19s 385ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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 505ms

When Go to new transport "CISTERN_DELIVERY" 387ms

And Fill transport form 35s 016ms

And Click "save-transport" save button and wait for form to disappear 15s 839ms

And Set advice window in schedule 2s 222ms

And Check is transport created in schedule and set transport id 627ms

And Go to "TRANSPORT_TABLE" 206ms

And Go to transport details "CISTERN_DELIVERY" 4s 397ms

Then Check are transport values equals 21s 415ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

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" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 508ms

When Go to new transport "CISTERN_COLLECTION" 336ms

And Fill transport form 28s 421ms

And Click "save-transport" save button and wait for form to disappear 15s 806ms

And Set advice window in schedule 2s 236ms

And Check is transport created in schedule and set transport id 601ms

And Go to "TRANSPORT_TABLE" 218ms

And Go to transport details "CISTERN_COLLECTION" 4s 410ms

Then Check are transport values equals 21s 392ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 448ms

When Go to new transport "OWN_COLLECTION" 342ms

And Fill transport form 32s 868ms

And Click "save-transport" save button and wait for form to disappear 15s 661ms

And Set advice window in schedule 2s 161ms

And Check is transport created in schedule and set transport id 538ms

And Go to "TRANSPORT_TABLE" 188ms

And Go to transport details "OWN_COLLECTION" 4s 529ms

Then Check are transport values equals 19s 371ms

Hooks

After Hooks.deleteTransportAfterTest() 134ms

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" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 451ms

When Go to new transport "OWN_COLLECTION_POWDER_FACTORY" 349ms

And Fill transport form 32s 921ms

And Click "save-transport" save button and wait for form to disappear 15s 656ms

And Set advice window in schedule 2s 175ms

And Check is transport created in schedule and set transport id 588ms

And Go to "TRANSPORT_TABLE" 206ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 508ms

Then Check are transport values equals 4s 316ms

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_EXPORT" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 364ms

When Go to new transport "EXPORT" 366ms

And Fill transport form 40s 881ms

And Click "save-transport" save button and wait for form to disappear 15s 632ms

And Set advice window in schedule 2s 158ms

And Check is transport created in schedule and set transport id 570ms

And Go to "TRANSPORT_TABLE" 200ms

And Go to transport details "EXPORT" 5s 465ms

Then Check are transport values equals 4s 376ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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" 002ms

And Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 2s 310ms

When Go to new transport "DELIVERY" 15s 244ms

And Fill transport form 28s 418ms

And Click "save-transport" save button and wait for form to disappear 15s 628ms

And Set advice window in schedule 2s 160ms

And Check is transport created in schedule and set transport id 720ms

And Go to "TRANSPORT_TABLE" 244ms

And Go to transport details "DELIVERY" 32s 328ms

Then Check are transport values equals 36s 357ms

Hooks

After Hooks.deleteTransportAfterTest() 138ms

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" 002ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 118ms

When Go to new transport "DELIVERY" 311ms

And Fill transport form 38s 007ms

And Click "save-transport" save button and wait for form to disappear 15s 597ms

And Set advice window in schedule 2s 173ms

And Check is transport created in schedule and set transport id 608ms

And Go to "TRANSPORT_TABLE" 207ms

And Go to transport details "DELIVERY" 4s 329ms

Then Check are transport values equals 19s 337ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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 051ms

When Go to new transport "LOAD" 310ms

And Fill transport form 38s 128ms

And Click "save-transport" save button and wait for form to disappear 15s 716ms

And Set advice window in schedule 2s 171ms

And Check is transport created in schedule and set transport id 573ms

And Go to "TRANSPORT_TABLE" 244ms

And Go to transport details "LOAD" 4s 311ms

Then Check are transport values equals 19s 334ms

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_DELIVERY" "super-admin-keeeper" 002ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 622ms

When Go to new transport "UNLOAD" 315ms

And Fill transport form 37s 704ms

And Click "save-transport" save button and wait for form to disappear 15s 611ms

And Set advice window in schedule 2s 165ms

And Check is transport created in schedule and set transport id 537ms

And Go to "TRANSPORT_TABLE" 201ms

And Go to transport details "UNLOAD" 4s 377ms

Then Check are transport values equals 21s 405ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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" 003ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 134ms

When Go to new transport "TANKER_GRANULATE_DELIVERY" 333ms

And Fill transport form 37s 671ms

And Click "save-transport" save button and wait for form to disappear 15s 584ms

And Set advice window in schedule 2s 166ms

And Check is transport created in schedule and set transport id 541ms

And Go to "TRANSPORT_TABLE" 211ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 391ms

Then Check are transport values equals 21s 418ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

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 127ms

When Go to new transport "DELIVERY" 330ms

And Fill transport form 22s 930ms

And Click "save-transport" save button and wait for form to disappear 15s 600ms

And Set advice window in schedule 2s 147ms

And Check is transport created in schedule and set transport id 589ms

And Go to "TRANSPORT_TABLE" 210ms

And Go to transport details "DELIVERY" 4s 306ms

Then Check are transport values equals 17s 295ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 366ms

When Go to new transport "WEIGHING" 310ms

And Fill transport form 13s 591ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 622ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 131ms

And Go to transport details "WEIGHING" 4s 410ms

And Check are transport values equals 2s 196ms

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_TRANSPORT" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 168ms

When Go to new transport "TRANSPORT" 398ms

And Fill transport form 26s 818ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 644ms

And Show all transport "false" 012ms

And Go to "TRANSPORT_TABLE" 144ms

And Go to transport details "TRANSPORT" 4s 461ms

And Check are transport values equals 6s 259ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

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 177ms

When Go to new transport "CONTAINER" 338ms

And Fill transport form 11s 219ms

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" 158ms

And Go to transport details "CONTAINER" 4s 398ms

And Check are transport values equals 081ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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 503ms

When Go to new transport "TRANSFER_BETWEEN_WAREHOUSES" 346ms

And Fill transport form 13s 018ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 651ms

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 149ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 634ms

And Check are transport values equals 4s 198ms

Hooks

After Hooks.deleteTransportAfterTest() 059ms

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" 001ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 362ms

When Go to new transport "DELIVERY" 322ms

And Fill transport form 22s 550ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 603ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 148ms

And Go to transport details "DELIVERY" 4s 578ms

And Check are transport values equals 17s 211ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

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 194ms

When Go to new transport "LOAD" 363ms

And Fill transport form 26s 374ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 613ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 149ms

And Go to transport details "LOAD" 4s 645ms

And Check are transport values equals 2s 162ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

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" 003ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 134ms

When Go to new transport "LOAD" 315ms

And Fill transport form 24s 701ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 671ms

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 153ms

And Go to transport details "LOAD" 4s 398ms

And Check are transport values equals 19s 199ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

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 061ms

When Go to new transport "CONTAINER" 318ms

And Fill transport form 24s 679ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 647ms

And Show all transport "false" 012ms

And Go to "TRANSPORT_TABLE" 153ms

And Go to transport details "CONTAINER" 4s 378ms

And Check are transport values equals 19s 214ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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" 002ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 214ms

When Go to new transport "SMALLS_IMPORT" 393ms

And Fill transport form 36s 438ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 646ms

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 149ms

And Go to transport details "SMALLS_IMPORT" 4s 417ms

And Check are transport values equals 10s 402ms

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_SMALLS_EXPORT" "super-admin-skz" 002ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 234ms

When Go to new transport "SMALLS_EXPORT" 413ms

And Fill transport form 36s 530ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 629ms

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 122ms

And Go to transport details "SMALLS_EXPORT" 4s 425ms

And Check are transport values equals 10s 417ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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 144ms

When Go to new transport "TRANSPORT_ORDER" 420ms

And Fill transport form 30s 139ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 614ms

And Show all transport "true" 101ms

And Go to "TRANSPORT_TABLE" 143ms

And Go to transport details "TRANSPORT_ORDER" 4s 409ms

And Check are transport values equals 19s 352ms

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_ORDER_WITHOUT_WAREHOUSES" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 191ms

When Go to new transport "TRANSPORT" 370ms

And Fill transport form 37s 780ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 627ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 135ms

And Go to transport details "TRANSPORT" 4s 443ms

And Check are transport values equals 4s 245ms

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_INBOUND_WITHOUT_WAREHOUSES" "super-admin-alrec" 002ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 160ms

When Go to new transport "INBOUND" 381ms

And Fill transport form 41s 188ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 606ms

And Show all transport "true" 070ms

And Go to "TRANSPORT_TABLE" 117ms

And Go to transport details "INBOUND" 4s 432ms

And Check are transport values equals 2s 300ms

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_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" "super-admin-farmacol" 002ms

And Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 183ms

When Go to new transport "EXTERNAL_DELIVERY" 337ms

And Fill transport form 53s 877ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 643ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 135ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 426ms

And Check are transport values equals 4s 514ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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 423ms

When Go to new transport "EXTERNAL_DELIVERY" 15s 303ms

And Fill transport form 47s 373ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 637ms

And Show all transport "false" 016ms

And Go to "TRANSPORT_TABLE" 127ms

And Go to transport details "EXTERNAL_DELIVERY" 32s 409ms

And Check are transport values equals 4s 492ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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 065ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 002ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 666ms

And Show all transport "false" 010ms

When Go to transport details "UNLOAD" 32s 494ms

And Fill transport form 30s 522ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 133ms

And Go to transport details "UNLOAD" 32s 407ms

Then Check are transport values equals 4s 295ms

Hooks

After Hooks.deleteTransportAfterTest() 152ms

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 155ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 001ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 248ms

And Show all transport "false" 010ms

When Go to transport details "TRANSPORT" 4s 476ms

And Fill transport form 10s 324ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 649ms

And Go to transport details "TRANSPORT" 4s 457ms

Then Check are transport values equals 4s 131ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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 154ms

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" 013ms

When Go to transport details "CONTAINER" 4s 353ms

And Fill transport form 4s 735ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 637ms

And Go to transport details "CONTAINER" 4s 360ms

Then Check are transport values equals 051ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

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 148ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 308ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 384ms

And Fill transport form 11s 636ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 590ms

And Go to transport details "DELIVERY" 4s 337ms

Then Check are transport values equals 157ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 130ms

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 311ms

And Show all transport "false" 009ms

When Go to transport details "OWN_COLLECTION" 4s 372ms

And Fill transport form 21s 654ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 633ms

And Go to transport details "OWN_COLLECTION" 4s 326ms

Then Check are transport values equals 2s 231ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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 455ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 363ms

And Show all transport "false" 009ms

When Go to transport details "DELIVERY" 4s 504ms

And Fill transport form 36s 009ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 168ms

And Go to transport details "DELIVERY" 4s 499ms

Then Check are transport values equals 10s 562ms

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 458ms

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 304ms

And Show all transport "false" 011ms

When Go to transport details "OWN_COLLECTION" 4s 729ms

And Fill transport form 36s 672ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 723ms

And Go to transport details "OWN_COLLECTION" 4s 424ms

Then Check are transport values equals 6s 384ms

Hooks

After Hooks.deleteTransportAfterTest() 145ms

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 411ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 395ms

And Show all transport "false" 008ms

When Go to transport details "EXPORT" 5s 605ms

And Fill transport form 48s 113ms

And Click "save-transport-and-close" save button and wait for form to disappear 707ms

And Go to transport details "EXPORT" 4s 459ms

Then Check are transport values equals 8s 542ms

Hooks

After Hooks.deleteTransportAfterTest() 141ms

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 476ms

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 185ms

And Show all transport "false" 010ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 701ms

And Fill transport form 36s 258ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 655ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 452ms

Then Check are transport values equals 12s 495ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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 448ms

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 310ms

And Show all transport "false" 010ms

When Go to transport details "CISTERN_DELIVERY" 4s 506ms

And Fill transport form 27s 309ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 606ms

And Go to transport details "CISTERN_DELIVERY" 4s 399ms

Then Check are transport values equals 6s 339ms

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 579ms

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 273ms

And Show all transport "false" 010ms

When Go to transport details "CISTERN_COLLECTION" 4s 511ms

And Fill transport form 25s 994ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 631ms

And Go to transport details "CISTERN_COLLECTION" 4s 388ms

Then Check are transport values equals 6s 299ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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 450ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 001ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 208ms

And Show all transport "false" 012ms

When Go to transport details "WEIGHING" 4s 399ms

And Fill transport form 12s 356ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 626ms

And Go to transport details "WEIGHING" 4s 345ms

Then Check are transport values equals 2s 138ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

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 448ms

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 316ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 551ms

And Fill transport form 35s 240ms

And Click "save-transport-and-close" save button and wait for form to disappear 723ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 409ms

Then Check are transport values equals 6s 361ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

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 124ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 327ms

And Show all transport "false" 008ms

When Go to transport details "DELIVERY" 32s 419ms

And Fill transport form 25s 777ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 618ms

And Go to transport details "DELIVERY" 32s 356ms

Then Check are transport values equals 2s 220ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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 227ms

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 219ms

And Show all transport "false" 006ms

When Go to transport details "DELIVERY" 4s 549ms

And Fill transport form 1m 2s 584ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 169ms

And Go to transport details "DELIVERY" 4s 475ms

Then Check are transport values equals 132ms

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/Atom/Transport/CrudTransport.feature:76)

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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 169ms

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 194ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 658ms

And Fill transport form 57s 512ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 149ms

And Go to transport details "LOAD" 4s 500ms

Then Check are transport values equals 24s 851ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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 108ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 356ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 374ms

And Fill transport form 16s 454ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 656ms

And Go to transport details "DELIVERY" 4s 344ms

Then Check are transport values equals 070ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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 076ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 002ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 343ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 359ms

And Fill transport form 28s 194ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 146ms

And Go to transport details "LOAD" 4s 332ms

Then Check are transport values equals 2s 246ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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 199ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 323ms

And Show all transport "false" 010ms

When Go to transport details "UNLOAD" 4s 422ms

And Fill transport form 37s 968ms

And Click "save-transport-and-close" save button and wait for form to disappear 630ms

And Go to transport details "UNLOAD" 4s 386ms

Then Check are transport values equals 6s 388ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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 145ms

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 312ms

And Show all transport "false" 010ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 450ms

And Fill transport form 36s 337ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 656ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 393ms

Then Check are transport values equals 6s 375ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

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 168ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 002ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 199ms

And Show all transport "false" 011ms

When Go to transport details "LOAD" 4s 377ms

And Fill transport form 24s 774ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 640ms

And Go to transport details "LOAD" 4s 374ms

Then Check are transport values equals 4s 223ms

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-admin" and set token of apiUsername "super-admin-keeeper" 1s 172ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 002ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 200ms

And Show all transport "false" 012ms

When Go to transport details "CONTAINER" 4s 403ms

And Fill transport form 24s 748ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 613ms

And Go to transport details "CONTAINER" 4s 369ms

Then Check are transport values equals 4s 220ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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 258ms

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 266ms

And Show all transport "false" 010ms

When Go to transport details "SMALLS_IMPORT" 4s 510ms

And Fill transport form 33s 111ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 626ms

And Go to transport details "SMALLS_IMPORT" 4s 415ms

Then Check are transport values equals 8s 356ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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 250ms

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 283ms

And Show all transport "false" 010ms

When Go to transport details "SMALLS_EXPORT" 4s 533ms

And Fill transport form 33s 108ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 638ms

And Go to transport details "SMALLS_EXPORT" 4s 402ms

Then Check are transport values equals 8s 365ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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 143ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 377ms

And Show all transport "true" 083ms

When Go to transport details "DELIVERY" 4s 342ms

And Fill transport form 19s 600ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 632ms

And Go to transport details "DELIVERY" 4s 333ms

Then Check are transport values equals 188ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

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 144ms

And Get inputs from database "EDIT_TRANSPORT_ORDER" "super-admin-alrec" 001ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 290ms

And Show all transport "true" 076ms

When Go to transport details "TRANSPORT_ORDER" 4s 443ms

And Fill transport form 26s 849ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 629ms

And Go to transport details "TRANSPORT_ORDER" 4s 391ms

Then Check are transport values equals 2s 265ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

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 550ms

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 182ms

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 400ms

And Fill transport form 8s 892ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 608ms

And Go to transport details "CONTAINER" 4s 419ms

Then Check are transport values equals 4s 118ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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 476ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 399ms

And Show all transport "false" 013ms

When Delete transport 17s 937ms

Then Transport not displayed in table of transports 15s 063ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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 212ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 206ms

And Show all transport "false" 010ms

When Delete transport 17s 210ms

Then Transport not displayed in table of transports 15s 061ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

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 127ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 322ms

And Show all transport "false" 010ms

When Delete transport 17s 548ms

Then Transport not displayed in table of transports 15s 015ms

Hooks

After Hooks.deleteTransportAfterTest() 058ms

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 204ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 181ms

And Show all transport "false" 010ms

When Delete transport 17s 032ms

Then Transport not displayed in table of transports 15s 032ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

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 247ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 261ms

And Show all transport "false" 010ms

When Delete transport 17s 654ms

Then Transport not displayed in table of transports 15s 068ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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 150ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 242ms

And Show all transport "false" 010ms

When Delete transport 17s 696ms

Then Transport not displayed in table of transports 15s 048ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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 132ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 298ms

And Show all transport "true" 084ms

When Delete transport 19s 141ms

Then Transport not displayed in table of transports 15s 037ms

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 157ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 239ms

And Show all transport "true" 082ms

When Delete transport 17s 115ms

Then Transport not displayed in table of transports 15s 062ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

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 133ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 002ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 576ms

And Show all transport "false" 007ms

When Go to transport details "UNLOAD" 32s 508ms

And Fill transport form 30s 434ms

And Click "save-transport" save button 1s 253ms

And Click cancel button in transport form 088ms

And Go to transport details "UNLOAD" 32s 408ms

Then Check are transport values equals 4s 298ms

Hooks

After Hooks.deleteTransportAfterTest() 155ms

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 139ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 001ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 247ms

And Show all transport "false" 011ms

When Go to transport details "TRANSPORT" 4s 500ms

And Fill transport form 10s 301ms

And Click "save-transport" save button 745ms

And Click cancel button in transport form 073ms

And Go to transport details "TRANSPORT" 4s 343ms

Then Check are transport values equals 4s 130ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

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 104ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 193ms

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 378ms

And Fill transport form 4s 734ms

And Click "save-transport" save button 713ms

And Click cancel button in transport form 079ms

And Go to transport details "CONTAINER" 4s 257ms

Then Check are transport values equals 051ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

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 021ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 307ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 384ms

And Fill transport form 11s 648ms

And Click "save-transport" save button 737ms

And Click cancel button in transport form 087ms

And Go to transport details "DELIVERY" 4s 306ms

Then Check are transport values equals 120ms

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 "adama-admin" and set token of apiUsername "super-admin-adama" 1s 020ms

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 290ms

And Show all transport "false" 006ms

When Go to transport details "OWN_COLLECTION" 4s 389ms

And Fill transport form 21s 634ms

And Click "save-transport" save button 722ms

And Click cancel button in transport form 080ms

And Go to transport details "OWN_COLLECTION" 4s 327ms

Then Check are transport values equals 2s 234ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

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 382ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 335ms

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 4s 691ms

And Fill transport form 36s 029ms

And Click "save-transport" save button 1s 255ms

And Click cancel button in transport form 088ms

And Go to transport details "DELIVERY" 4s 424ms

Then Check are transport values equals 10s 568ms

Hooks

After Hooks.deleteTransportAfterTest() 138ms

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 429ms

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 321ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION" 4s 678ms

And Fill transport form 36s 647ms

And Click "save-transport" save button 1s 280ms

And Click cancel button in transport form 087ms

And Go to transport details "OWN_COLLECTION" 4s 375ms

Then Check are transport values equals 6s 416ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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 442ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 376ms

And Show all transport "false" 009ms

When Go to transport details "EXPORT" 5s 559ms

And Fill transport form 48s 180ms

And Click "save-transport" save button 879ms

And Click cancel button in transport form 071ms

And Go to transport details "EXPORT" 4s 452ms

Then Check are transport values equals 8s 513ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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 484ms

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 175ms

And Show all transport "false" 010ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 694ms

And Fill transport form 36s 144ms

And Click "save-transport" save button 885ms

And Click cancel button in transport form 108ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 408ms

Then Check are transport values equals 12s 488ms

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 "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 456ms

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 291ms

And Show all transport "false" 011ms

When Go to transport details "CISTERN_DELIVERY" 4s 510ms

And Fill transport form 27s 361ms

And Click "save-transport" save button 837ms

And Click cancel button in transport form 085ms

And Go to transport details "CISTERN_DELIVERY" 4s 355ms

Then Check are transport values equals 6s 339ms

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 "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 439ms

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 276ms

And Show all transport "false" 010ms

When Go to transport details "CISTERN_COLLECTION" 4s 468ms

And Fill transport form 25s 929ms

And Click "save-transport" save button 736ms

And Click cancel button in transport form 094ms

And Go to transport details "CISTERN_COLLECTION" 4s 363ms

Then Check are transport values equals 6s 274ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

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 439ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 001ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 205ms

And Show all transport "false" 009ms

When Go to transport details "WEIGHING" 4s 407ms

And Fill transport form 12s 380ms

And Click "save-transport" save button 705ms

And Click cancel button in transport form 075ms

And Go to transport details "WEIGHING" 4s 302ms

Then Check are transport values equals 2s 163ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

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 339ms

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 343ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 537ms

And Fill transport form 35s 248ms

And Click "save-transport" save button 925ms

And Click cancel button in transport form 094ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 397ms

Then Check are transport values equals 6s 347ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

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 138ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 331ms

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 32s 389ms

And Fill transport form 25s 725ms

And Click "save-transport" save button 732ms

And Click cancel button in transport form 068ms

And Go to transport details "DELIVERY" 32s 352ms

Then Check are transport values equals 2s 203ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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 217ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-piast" 002ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 194ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 584ms

And Fill transport form 1m 2s 571ms

And Click "save-transport" save button 858ms

And Click cancel button in transport form 076ms

And Go to transport details "DELIVERY" 4s 382ms

Then Check are transport values equals 126ms

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/Atom/Transport/CrudTransport.feature:136)

Hooks

After Hooks.deleteTransportAfterTest() 140ms

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 246ms

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 246ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 703ms

And Fill transport form 57s 489ms

And Click "save-transport" save button 1s 264ms

And Click cancel button in transport form 087ms

And Go to transport details "LOAD" 4s 428ms

Then Check are transport values equals 24s 816ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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 113ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 345ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 357ms

And Fill transport form 16s 497ms

And Click "save-transport" save button 719ms

And Click cancel button in transport form 079ms

And Go to transport details "DELIVERY" 4s 286ms

Then Check are transport values equals 076ms

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 "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 086ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 322ms

And Show all transport "false" 011ms

When Go to transport details "LOAD" 4s 317ms

And Fill transport form 28s 226ms

And Click "save-transport" save button 1s 245ms

And Click cancel button in transport form 074ms

And Go to transport details "LOAD" 4s 330ms

Then Check are transport values equals 2s 240ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

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 163ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 340ms

And Show all transport "false" 010ms

When Go to transport details "UNLOAD" 4s 440ms

And Fill transport form 37s 997ms

And Click "save-transport" save button 1s 317ms

And Click cancel button in transport form 075ms

And Go to transport details "UNLOAD" 4s 345ms

Then Check are transport values equals 6s 373ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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 197ms

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 345ms

And Show all transport "false" 010ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 450ms

And Fill transport form 36s 374ms

And Click "save-transport" save button 739ms

And Click cancel button in transport form 082ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 338ms

Then Check are transport values equals 6s 380ms

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 "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 176ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 194ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 403ms

And Fill transport form 24s 755ms

And Click "save-transport" save button 732ms

And Click cancel button in transport form 068ms

And Go to transport details "LOAD" 4s 323ms

Then Check are transport values equals 4s 223ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

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 122ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 195ms

And Show all transport "false" 011ms

When Go to transport details "CONTAINER" 4s 381ms

And Fill transport form 24s 840ms

And Click "save-transport" save button 725ms

And Click cancel button in transport form 072ms

And Go to transport details "CONTAINER" 4s 309ms

Then Check are transport values equals 4s 180ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

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 212ms

And Get inputs from database "EDIT_SMALLS_IMPORT" "super-admin-skz" 002ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 278ms

And Show all transport "false" 003ms

When Go to transport details "SMALLS_IMPORT" 4s 506ms

And Fill transport form 33s 132ms

And Click "save-transport" save button 755ms

And Click cancel button in transport form 080ms

And Go to transport details "SMALLS_IMPORT" 4s 349ms

Then Check are transport values equals 8s 366ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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 282ms

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 233ms

And Show all transport "false" 010ms

When Go to transport details "SMALLS_EXPORT" 4s 518ms

And Fill transport form 33s 024ms

And Click "save-transport" save button 751ms

And Click cancel button in transport form 078ms

And Go to transport details "SMALLS_EXPORT" 4s 360ms

Then Check are transport values equals 8s 368ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

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 174ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 357ms

And Show all transport "true" 098ms

When Go to transport details "DELIVERY" 4s 353ms

And Fill transport form 19s 600ms

And Click "save-transport" save button 716ms

And Click cancel button in transport form 093ms

And Go to transport details "DELIVERY" 4s 310ms

Then Check are transport values equals 163ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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 116ms

And Get inputs from database "EDIT_TRANSPORT_ORDER" "super-admin-alrec" 001ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 290ms

And Show all transport "true" 083ms

When Go to transport details "TRANSPORT_ORDER" 4s 448ms

And Fill transport form 26s 858ms

And Click "save-transport" save button 745ms

And Click cancel button in transport form 076ms

And Go to transport details "TRANSPORT_ORDER" 4s 336ms

Then Check are transport values equals 2s 279ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

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 152ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 195ms

And Create gray windows "CREATE_GRAY_WINDOW_MWG" on "PRZESYŁKI DROBNICOWE" in "Magazyn Wyrobów Gotowych" as "super-admin-keeeper" 288ms

And If user is login then logout 114ms

Then Login as "dka1-supplier" 2s 388ms

And Click button advice in transport table "LOAD" 174ms

And Check if moved to first possible start date in schedule 387ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

After Hooks.deleteAllGrayWindowsAfterTest() 1m 30s 596ms

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" 100ms

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 278ms

Then Go to new transport "LOAD" 362ms

And Fill transport form 27s 395ms

Error message

java.lang.NullPointerException
	at CucumberTests.Transport.Transport.clickButton(Transport.java:184)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:175)
	at CucumberTests.Transport.CreateTransport.fillTransportForm(CreateTransport.java:170)
	at ✽.Fill transport form(file:Features/Atom/Transport/CrudTransport.feature:185)

And Click "save-transport-and-close" save button and wait for form to disappear 000ms

And Go to "COMPANIES_TAB" 000ms

And Go to company "Dostawca Piast Automat 1" details 000ms

And Check if new address with "Adresat" is visible in company details 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "LOAD" 000ms

Hooks

After Hooks.deleteAddressAfterTest() 001ms

After Hooks.deleteTransportAfterTest() 000ms

View Feature Crud Transport

@deleteTransportAfterTest @deleteAddressAfterTest

Scenario Outline Check if it is possible to add new address in existing transport [A-7158]

Steps

Given Set token of apiUsername "super-admin-piast" 097ms

When Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 278ms

And Set "transport" inputs from JSON file "EDIT_TRANSPORT_ADDRESS" "super-admin-piast" 002ms

Then Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 205ms

And Go to transport details "LOAD" 4s 829ms

And Fill transport form 16s 073ms

Error message

java.lang.NullPointerException
	at CucumberTests.Transport.Transport.clickButton(Transport.java:184)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:175)
	at CucumberTests.Transport.CreateTransport.fillTransportForm(CreateTransport.java:170)
	at ✽.Fill transport form(file:Features/Atom/Transport/CrudTransport.feature:204)

And Click "save-transport-and-close" save button and wait for form to disappear 000ms

And Go to "COMPANIES_TAB" 000ms

And Go to company "Dostawca Piast Automat 1" details 000ms

And Check if new address with "Adresat" is visible in company details 000ms

Hooks

After Hooks.deleteAddressAfterTest() 001ms

After Hooks.deleteTransportAfterTest() 070ms

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 093ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 189ms

When Go to "TRANSPORT_TABLE" 157ms

And Show all transport types 1s 034ms

And Verify that transport has "0" files 038ms

Then Add file to transport by API 485ms

And Verify that transport has "1" files 551ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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 086ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 198ms

When Go to "TRANSPORT_TABLE" 128ms

And Show all transport types 1s 035ms

And Verify that transport has "0" files 036ms

Then Add file to transport by API 271ms

And Verify that transport has "1" files 512ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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 336ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 360ms

When Go to "TRANSPORT_TABLE" 132ms

And Show all transport types 1s 027ms

And Verify that transport has "0" files 036ms

Then Add file to transport by API 244ms

And Verify that transport has "1" files 378ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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 091ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 199ms

When Go to "TRANSPORT_TABLE" 129ms

And Show all transport types 1s 040ms

And Verify that transport has "0" files 040ms

Then Add file to transport by API 210ms

And Verify that transport has "1" files 926ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

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 080ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 176ms

And Delete transport 17s 707ms

When Go to "ARCHIVE_TAB" 236ms

And Show "DELIVERY" 057ms

And Verify that transport has "0" files 729ms

Then Add file to transport 145ms

And Verify that transport has "1" files 408ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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 209ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 191ms

And Delete transport 17s 334ms

When Go to "ARCHIVE_TAB" 260ms

And Show "LOAD" 222ms

And Verify that transport has "0" files 1s 115ms

Then Add file to transport 161ms

And Verify that transport has "1" files 381ms

Hooks

After Hooks.deleteTransportAfterTest() 058ms

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 418ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 349ms

And Delete transport 17s 883ms

When Go to "ARCHIVE_TAB" 256ms

And Show "DELIVERY" 070ms

And Verify that transport has "0" files 995ms

Then Add file to transport 160ms

And Verify that transport has "1" files 359ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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 135ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 198ms

And Delete transport 17s 571ms

When Go to "ARCHIVE_TAB" 238ms

And Show "CONTAINER" 082ms

And Verify that transport has "0" files 1s 108ms

Then Add file to transport 159ms

And Verify that transport has "1" files 355ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

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" 095ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 15s 203ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 120ms

And Set token of apiUsername "paa1-carrier@qa.qa-test" 096ms

And Accept transferred transport by Api 206ms

And Login as "paa1-carrier@qa.qa-test" 1s 040ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 15s 720ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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 070ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 230ms

And Transfer transport to carrier by JSON file "super-admin-adama" "false" confirmation 118ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 784ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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" 092ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 199ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 201ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 335ms

And Login as "paa1-carrier@qa.qa-test" 1s 205ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 16s 095ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

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 174ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 256ms

When Go to "TRANSPORT_TABLE" 140ms

And Show all transport "true" 067ms

Then Verify that transport has "1" CMR file 1s 187ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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 059ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 274ms

When Go to "TRANSPORT_TABLE" 130ms

And Show all transport "true" 058ms

Then Verify that transport has "2" CMR file 1s 181ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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 041ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 265ms

When Go to "TRANSPORT_TABLE" 126ms

And Show all transport "true" 070ms

Then Verify that "CMR" document can be downloaded 17s 426ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

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 207ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 279ms

And Show all transport "true" 079ms

And Delete transport 17s 192ms

When Go to "ARCHIVE_TAB" 244ms

And Show "TRANSPORT_ORDER" 052ms

Then Verify that "CMR" document can be downloaded 16s 814ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

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 475ms

And Create default accepted mode of transportation by API with "pba1-carrier" 446ms

And If user is login then logout 097ms

And Login as "bausch-admin" and set token of apiUsername "super-admin-bausch" 1s 297ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 257ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 109ms

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-bausch" 009ms

And Click button advice in transport table "LOAD_PL" 1s 827ms

And Set advice window in schedule 2s 793ms

And Fill advice form 9s 288ms

And Click advice save button and wait for advice form to disappear 30s 844ms

And Find transport in table with status "advice-added" 3s 315ms

When Confirm statuses until reach "on-the-way" 9s 373ms

Then Verify that "delivery_document" document can be downloaded 16s 257ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

After Hooks.deleteModeOfTransportationAfterTest() 079ms

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 565ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 395ms

And Show all transport "false" 009ms

When Find transport pencil button in transports table 1s 254ms

And Click pencil and move transport to next day in schedule 16s 382ms

Then Check if transport is in new location in schedule 2s 108ms

And Check if dates in transport form are correct 3s 420ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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 149ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 285ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 256ms

And Click pencil and move transport to next day in schedule 16s 777ms

Then Check if transport is in new location in schedule 2s 121ms

And Check if dates in transport form are correct 3s 309ms

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 103ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 323ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 267ms

And Click pencil and move transport to next day in schedule 16s 918ms

Then Check if transport is in new location in schedule 2s 122ms

And Check if dates in transport form are correct 3s 399ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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 180ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 317ms

And Show all transport "false" 011ms

When Find transport pencil button in transports table 1s 251ms

And Click pencil and move transport to next day in schedule 16s 365ms

Then Check if transport is in new location in schedule 2s 112ms

And Check if dates in transport form are correct 3s 375ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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 166ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 359ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 265ms

And Click pencil and move transport to next day in schedule 16s 372ms

Then Check if transport is in new location in schedule 2s 120ms

And Check if dates in transport form are correct 3s 388ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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 168ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-alrec" 1s 382ms

And Show all transport "true" 046ms

When Find transport pencil button in transports table 1s 218ms

And Click pencil and move transport to next day in schedule 16s 475ms

Then Check if transport is in new location in schedule 2s 123ms

And Check if dates in transport form are correct 3s 399ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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 225ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 232ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 002ms

When Show all transport types 1s 050ms

And Click button advice in transport table "DELIVERY" 137ms

And Set advice window in schedule 2s 590ms

And Fill advice form 8s 428ms

And Click advice save button and wait for advice form to disappear 30s 747ms

And Go to "TRANSPORT_TABLE" 244ms

And Find transport pencil button in transports table 1s 221ms

And Click pencil and move transport to next day in schedule 17s 477ms

Then Check if transport is in new location in schedule 2s 127ms

And Check if dates in transport form are correct 3s 437ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

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 461ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 386ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 263ms

And Click pencil and move transport to next day in schedule 16s 342ms

And Move advice window "3" 1s 330ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 141ms

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 147ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 340ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 267ms

And Click pencil and move transport to next day in schedule 16s 721ms

And Move advice window "3" 1s 386ms

Then Check if advice window is in new location 022ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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 436ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 302ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 237ms

And Click pencil and move transport to next day in schedule 16s 934ms

And Move advice window "3" 1s 496ms

Then Check if advice window is in new location 023ms

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 "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 153ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 338ms

And Show all transport "false" 008ms

When Find transport pencil button in transports table 1s 240ms

And Click pencil and move transport to next day in schedule 16s 364ms

And Move advice window "3" 1s 323ms

Then Check if advice window is in new location 026ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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 139ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 331ms

And Show all transport "false" 009ms

When Find transport pencil button in transports table 1s 237ms

And Click pencil and move transport to next day in schedule 16s 348ms

And Move advice window "3" 1s 321ms

Then Check if advice window is in new location 025ms

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 "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 066ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 304ms

And Show all transport "true" 080ms

When Find transport pencil button in transports table 1s 228ms

And Click pencil and move transport to next day in schedule 16s 411ms

And Move advice window "3" 1s 376ms

Then Check if advice window is in new location 027ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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 475ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 384ms

And Go to transport details "DELIVERY" 4s 753ms

When Open section: "discrepancy-report-panel" 1s 067ms

Then Verify that no discrepancies found label is visible in discrepancy report section 058ms

And Select "NIE" in the "insp.-accord.-with-ins." 2s 441ms

And Verify that discrepancy report custom fields are visible in discrepancy report section 106ms

Hooks

After Hooks.deleteTransportAfterTest() 146ms

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 277ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 369ms

And Go to transport details "DELIVERY" 4s 714ms

And Fill transport form 35s 976ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 159ms

When Go to transport details "DELIVERY" 4s 465ms

Then Select "NIE" in the "insp.-accord.-with-ins." 2s 428ms

And Click "save-transport" save button 712ms

And Wait "2" seconds 2s

And Verify that discrepancy report section is open 031ms

And Verify that discrepancy report section contains validation errors 020ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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 401ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 395ms

When Go to transport details "DELIVERY" 4s 489ms

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 040ms

Hooks

After Hooks.deleteTransportAfterTest() 155ms

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 405ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 297ms

When Go to transport details "OWN_COLLECTION" 4s 648ms

Then Verify that discrepancy report section is available 035ms

And Open section: "discrepancy-report-panel" 1s 068ms

And Verify that generate new discrepancy report button is visible 030ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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 284ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 374ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 533ms

Then Verify that discrepancy report section is available 029ms

And Open section: "discrepancy-report-panel" 1s 063ms

And Verify that generate new discrepancy report button is visible 036ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

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 349ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 336ms

When Go to transport details "EXPORT" 4s 829ms

Then Verify that discrepancy report section is available 030ms

And Open section: "discrepancy-report-panel" 1s 057ms

And Verify that generate new discrepancy report button is visible 035ms

Hooks

After Hooks.deleteTransportAfterTest() 139ms

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 361ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 192ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 675ms

Then Verify that discrepancy report section is available 037ms

And Open section: "discrepancy-report-panel" 1s 066ms

And Verify that generate new discrepancy report button is visible 035ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

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 273ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 353ms

When Go to transport details "CISTERN_DELIVERY" 4s 503ms

Then Verify that discrepancy report section is not available 15s 059ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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 437ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 1s 291ms

When Go to transport details "CISTERN_COLLECTION" 4s 470ms

Then Verify that discrepancy report section is not available 15s 026ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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 406ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 226ms

When Go to transport details "WEIGHING" 4s 446ms

Then Verify that discrepancy report section is not available 15s 049ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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 443ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 346ms

When Go to "TRANSPORT_TABLE" 149ms

And Go to transport details "DELIVERY" 4s 747ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 535ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 325ms

And Open section: "discrepancy-report-panel" 1s 072ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 002ms

And Fill transport form 35s 881ms

And Fill discrepancy report section without closing the form 19s 677ms

And Generate discrepancy report 17s 333ms

And Download discrepancy report 149ms

Then Verify that discrepancy report file has correct values 15s 149ms

Error message

java.nio.file.NoSuchFileException: /home/teamcity/Downloads/39_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() 132ms

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 442ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 402ms

When Go to "TRANSPORT_TABLE" 156ms

And Go to transport details "DELIVERY" 4s 723ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 002ms

And Fill transport form 36s 009ms

And Open section: "discrepancy-report-panel" 1s 081ms

And Fill discrepancy report section without closing the form 19s 599ms

And Generate discrepancy report 16s 238ms

And Download discrepancy report 162ms

And Verify that discrepancy report file has correct values 15s 144ms

Error message

java.nio.file.NoSuchFileException: /home/teamcity/Downloads/40_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() 110ms

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" 091ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 045ms

And Get "LOAD" settings from "piast" 038ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "false" 062ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-piast" 1s 178ms

And Login as "piast-admin" 1s 938ms

And Go to "TRANSPORT_TABLE" 204ms

When Go to transport details "LOAD" 4s 707ms

And Add step "unload" 125ms

And Change filled value in transport details "company-step-2" "autocomplete" "DPA2" "0" 6s 521ms

And Change filled value in transport details "recipient-step-2" "autocomplete" "Testowy" "0" 6s 508ms

Then Click "save-transport-and-close" save button and wait for form to disappear 15s 607ms

And Go to transport details "LOAD" 4s 583ms

And Verify that transport has "3" steps 023ms

Hooks

After Hooks.rollbackTransportTypeSettings() 073ms

After Hooks.rollbackAddedActionAuthorities() 047ms

After Hooks.deleteTransportAfterTest() 068ms

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 089ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 216ms

When Go to "TRANSPORT_TABLE" 142ms

And Go to transport details "SMALLS_IMPORT" 17s 116ms

Then Verify that user can't edit time range for load and unload 15s 042ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

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" 089ms

And Create transport "CREATE_DELIVERY_TWO_LOADS" by JSON file as "super-admin-neuca" 1s 439ms

And Login as "neuca-admin" 905ms

And Go to "TRANSPORT_TABLE" 194ms

And Show all transport types 15s 035ms

When Go to transport details "DELIVERY" 32s 537ms

Then Check if sum of number of pallets in transport form in "load" steps is correct 074ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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" 092ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 15s 373ms

And Login as "hochland-admin" 1s 461ms

And Go to "TRANSPORT_TABLE" 124ms

And Show all transport types 1s 044ms

When Go to transport details "EXPORT" 5s 586ms

Then Check if sum of number of pallets in transport form in "unload" steps is correct 069ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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" 096ms

And Get "DELIVERY" settings from "neuca" 034ms

And Set transportType settings with values: "quantitySumCheckValue", "33" 111ms

And Login as "neuca-admin" 916ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 15s 325ms

When Go to "TRANSPORT_TABLE" 271ms

And Go to transport details "DELIVERY" 32s 458ms

And Set number of pallets in "load" step in transport - "32" 118ms

And Check if number of pallets check message is not visible in transport form 15s 068ms

And Set number of pallets in "load" step in transport - "34" 126ms

Then Check if number of pallets check message is visible in transport form 050ms

Hooks

After Hooks.rollbackTransportTypeSettings() 112ms

After Hooks.deleteTransportAfterTest() 109ms

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" 090ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 060ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 054ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 067ms

And Login as "farmacol-admin" 2s 066ms

And Go to new transport "EXTERNAL_DELIVERY" 305ms

And Add step "unload" 092ms

And Click "save-transport-and-close" save button 721ms

Then Verify that "time-range-from-date-2" has validation error 1s 030ms

Then Verify that "time-range-to-date-2" has validation error 1s 021ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 331ms

And Click "save-transport-and-close" save button 705ms

And Verify that "time-range-from-date-2" has no validation error 021ms

And Verify that "time-range-to-date-2" has no validation error 017ms

Hooks

After Hooks.rollbackTransportTypeSettings() 074ms

After Hooks.rollbackAddedActionAuthorities() 046ms

After Hooks.deleteTransportAfterTest() 000ms

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" 096ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_LOAD_STEP_FROM_UNLOAD" "ACTIVE" 054ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 195ms

When Login as "piast-admin" 1s 814ms

And Go to transport details "LOAD" 4s 803ms

And Get inputs from database "PIAST_LOAD_ADD_UNLOAD_STEP" "super-admin-piast" 002ms

And Add step "unload" 114ms

And Fill step data 15s 060ms

And Get inputs from database "PIAST_LOAD_ADD_LOAD_STEP" "super-admin-piast" 002ms

And Add step "load" 131ms

And Fill step data 5s 494ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 673ms

Then Go to transport details "LOAD" 4s 597ms

And Check if "unload" step is added as "3" step in transport form 040ms

And Check if "load" step is added as "4" step in transport form 036ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 062ms

After Hooks.deleteTransportAfterTest() 072ms

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" 097ms

And Add action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_LOAD_STEPS" "UNLIMITED" 054ms

And Remove action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_UNLOAD_STEPS" "UNLIMITED" 005ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 216ms

When Login as "super-admin-skz" 2s 596ms

And Go to transport details "SMALLS_EXPORT" 4s 500ms

And Check if step is draggable "LOAD" 027ms

And Check if step is not draggable "UNLOAD" 020ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 051ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

After Hooks.deleteTransportAfterTest() 107ms

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" 005ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 115ms

When Go to new transport "SMALLS_IMPORT" 370ms

And Fill transport form 19s 843ms

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 details "SMALLS_IMPORT" 4s 478ms

And Click create similar button 15s 185ms

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 586ms

And Open similar transport details 264ms

Then Check are transport values equals 2s 134ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.deleteSimilarTransportAfterTest() 091ms

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 885ms

When Go to new transport "TRANSPORT_ORDER" 414ms

And Fill transport form 23s 952ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 617ms

And Show all transport "true" 094ms

And Go to transport details "TRANSPORT_ORDER" 4s 441ms

And Click create similar button 15s 181ms

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 632ms

And Open similar transport details 274ms

Then Check are transport values equals 2s 204ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.deleteSimilarTransportAfterTest() 079ms

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" "super-admin-adama" 001ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 157ms

When Go to new transport "TRANSPORT" 392ms

And Fill transport form 26s 803ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 656ms

And Show all transport "false" 008ms

And Go to transport details "TRANSPORT" 4s 455ms

And Click create similar button 15s 222ms

And Fill "transport" form "CREATE_SIMILAR_TRANSPORT" by "super-admin-adama" 1s 371ms

And Click "save-transport-and-close" save button and wait for form to disappear 10s 156ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@type='submit' and @data-field-name='save-transport-and-close'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: '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=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.9IPk1e}, 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=89.0.4389.114, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: a29274008b6467118e33d32e9ee1aa75
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:198)
	at Pages.Transport.TransportFormPage.clickSaveButtonAndWaitForFormToDisappear(TransportFormPage.java:192)
	at CucumberTests.Transport.CreateTransport.clickSaveButtonAndWaitForFormToDisappear(CreateTransport.java:188)
	at ✽.Click "save-transport-and-close" save button and wait for form to disappear(file:Features/Atom/Transport/TransportForm/TransportForm.feature:14)

And Open similar transport details 000ms

Then Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

After Hooks.deleteSimilarTransportAfterTest() 000ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

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" 004ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 2s 534ms

When Go to new transport "DELIVERY" 15s 272ms

And Fill transport form 35s 964ms

And Click "save-transport" save button and wait for form to disappear 15s 675ms

And Set advice window in schedule 2s 178ms

And Check is transport created in schedule and set transport id 878ms

And Go to "TRANSPORT_TABLE" 238ms

And Go to transport details "DELIVERY" 32s 322ms

And Click create similar button 15s 151ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 9s 557ms

And Click "save-transport" save button and wait for form to disappear 15s 620ms

And Set advice window in schedule in "2" days 4s 231ms

And Go to "TRANSPORT_TABLE" 223ms

And Open similar transport details 532ms

Then Check are transport values equals 23s 479ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

After Hooks.deleteSimilarTransportAfterTest() 091ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

Scenario Outline Check if transport created with advice by similar button has correct values

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "super-admin-adama" 006ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 125ms

When Go to new transport "DELIVERY" 311ms

And Fill transport form 15s 484ms

And Click "save-transport" save button and wait for form to disappear 15s 649ms

And Set advice window in schedule 2s 174ms

And Check is transport created in schedule and set transport id 521ms

And Go to "TRANSPORT_TABLE" 249ms

And Go to transport details "DELIVERY" 4s 345ms

And Click create similar button 15s 207ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "super-admin-adama" 10s 896ms

And Click "save-transport" save button and wait for form to disappear 15s 576ms

And Set advice window in schedule in "2" days 4s 239ms

And Go to "TRANSPORT_TABLE" 190ms

And Open similar transport details 352ms

Then Check are transport values equals 201ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

After Hooks.deleteSimilarTransportAfterTest() 000ms

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 039ms

When Go to new transport "DELIVERY" 15s 298ms

And Fill transport form 35s 988ms

And Click "save-transport" save button and wait for form to disappear 15s 700ms

And Set advice window in schedule 2s 168ms

And Check is transport created in schedule and set transport id 783ms

And Go to "TRANSPORT_TABLE" 217ms

And Go to transport details "DELIVERY" 32s 383ms

And Click create similar button 15s 198ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 9s 542ms

And Click "save-transport" save button and wait for form to disappear 15s 591ms

And Set advice window in schedule in "2" days 4s 220ms

And Go to "TRANSPORT_TABLE" 194ms

And Open similar transport details 548ms

Then Check is field "CARRIER" of type "autocomplete" equals "Przewoźnik Neuca Automat 1" 020ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

After Hooks.deleteSimilarTransportAfterTest() 118ms

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" 001ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 233ms

When Go to new transport "SMALLS_IMPORT" 392ms

And Fill transport form 32s 975ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 622ms

And Go to transport details "SMALLS_IMPORT" 4s 441ms

And Go to transport print details form 3s 100ms

Then Check are transport values equals 8s 340ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to edit transport when auction is active

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 273ms

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 240ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 182ms

And Go to transport details "SMALLS_IMPORT" 4s 454ms

Then Verify that the transport can be edited 1s 299ms

And Close transport details 15s 117ms

And If user is login then logout 106ms

And Login as "pskza1-carrier@qa.qa-test" 1s 266ms

And Go to transport details "SMALLS_IMPORT" 4s 467ms

And Verify that the transport cannot be edited 46s 293ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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 267ms

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 235ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 111ms

And Go to transport details "SMALLS_EXPORT" 4s 484ms

Then Verify that the transport can be edited 1s 329ms

And Close transport details 15s 127ms

And If user is login then logout 114ms

And Login as "pskza1-carrier@qa.qa-test" 1s 295ms

And Go to transport details "SMALLS_EXPORT" 4s 487ms

And Verify that the transport cannot be edited 46s 385ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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 165ms

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 242ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 100ms

And Go to transport details "SMALLS_IMPORT" 4s 460ms

Then Verify that the hidden data in transport are not visible 1s 051ms

And Close transport details 15s 086ms

And If user is login then logout 109ms

And Login as "swisskrono-admin" 1s 365ms

And Go to transport details "SMALLS_IMPORT" 4s 523ms

And Verify that the hidden data in transport are visible 1s 258ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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 082ms

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 195ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 101ms

And Go to transport details "SMALLS_EXPORT" 4s 428ms

Then Verify that the hidden data in transport are not visible 1s 045ms

And Close transport details 15s 119ms

And If user is login then logout 126ms

And Login as "swisskrono-admin" 1s 402ms

And Go to transport details "SMALLS_EXPORT" 4s 539ms

And Verify that the hidden data in transport are visible 1s 259ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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 443ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 390ms

When Go to transport details "DELIVERY" 4s 702ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 317ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 536ms

And Change filled value in transport details "insp.-accord.-with-ins." "select" "NIE" "1" 3s 514ms

And Fill discrepancy report section without closing the form 19s 569ms

And Click "save-transport" save button 1s 240ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 644ms

And Check if transport details form is disappeared 15s 036ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

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" 095ms

And Add action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 088ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 260ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 408ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 3s 267ms

When Go to "TRANSPORT_TABLE" 174ms

And Go to transport details "DELIVERY" 4s 695ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 335ms

Then Verify that "transport-description" in transport has value "opis" 026ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 058ms

After Hooks.rollbackWarehousesAccess() 135ms

After Hooks.deleteTransportAfterTest() 097ms

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" 091ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 346ms

And Remove action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 054ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 137ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 2s 586ms

When Go to "TRANSPORT_TABLE" 191ms

And Go to transport details "DELIVERY" 4s 662ms

Then Verify that "transport-description" in transport form is disabled 033ms

Hooks

After Hooks.rollbackRemovedActionAuthorities() 062ms

After Hooks.rollbackWarehousesAccess() 156ms

After Hooks.deleteTransportAfterTest() 107ms

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" 095ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 065ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 348ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 531ms

And Show all transport "false" 010ms

When Go to "TRANSPORT_TABLE" 212ms

And Go to transport details "DELIVERY" 4s 715ms

Then Verify that "CARRIER" in transport form is visible 038ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 049ms

After Hooks.deleteTransportAfterTest() 108ms

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" 095ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 063ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 216ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 938ms

And Show all transport "false" 006ms

When Go to "TRANSPORT_TABLE" 188ms

And Go to transport details "TRANSPORT" 4s 463ms

Then Verify that "CARRIER" in transport form is visible 035ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 050ms

After Hooks.deleteTransportAfterTest() 082ms

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" 096ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 067ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 277ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 788ms

And Show all transport "true" 074ms

When Go to "TRANSPORT_TABLE" 105ms

And Go to transport details "TRANSPORT_ORDER" 4s 464ms

Then Verify that "CARRIER" in transport form is visible 037ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 054ms

After Hooks.deleteTransportAfterTest() 077ms

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" 093ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 049ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 371ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 482ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 226ms

And Go to transport details "DELIVERY" 4s 710ms

Then Verify that "CARRIER" in transport form is not visible 15s 044ms

Hooks

After Hooks.rollbackRemovedActionAuthorities() 053ms

After Hooks.deleteTransportAfterTest() 110ms

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" 087ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 048ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 318ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 924ms

And Show all transport "false" 012ms

When Go to "TRANSPORT_TABLE" 222ms

And Go to transport details "TRANSPORT" 4s 473ms

Then Verify that "CARRIER" in transport form is not visible 15s 038ms

Hooks

After Hooks.rollbackRemovedActionAuthorities() 058ms

After Hooks.deleteTransportAfterTest() 079ms

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" 096ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 054ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 219ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 907ms

And Show all transport "true" 083ms

When Go to "TRANSPORT_TABLE" 116ms

And Go to transport details "TRANSPORT_ORDER" 4s 485ms

Then Verify that "CARRIER" in transport form is not visible 15s 059ms

Hooks

After Hooks.rollbackRemovedActionAuthorities() 062ms

After Hooks.deleteTransportAfterTest() 082ms

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" 096ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 054ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 053ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 372ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 565ms

And Show all transport "false" 004ms

When Go to "TRANSPORT_TABLE" 215ms

And Go to transport details "DELIVERY" 4s 729ms

Then Verify that "CARRIER" in transport form is not disabled 032ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 102ms

After Hooks.deleteTransportAfterTest() 078ms

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" 093ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 049ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 045ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 204ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 873ms

And Show all transport "false" 004ms

When Go to "TRANSPORT_TABLE" 188ms

And Go to transport details "TRANSPORT" 4s 444ms

Then Verify that "CARRIER" in transport form is not disabled 029ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 089ms

After Hooks.deleteTransportAfterTest() 073ms

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" 088ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 050ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 055ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 237ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 957ms

And Show all transport "true" 067ms

When Go to "TRANSPORT_TABLE" 101ms

And Go to transport details "TRANSPORT_ORDER" 4s 445ms

Then Verify that "CARRIER" in transport form is not disabled 030ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 085ms

After Hooks.deleteTransportAfterTest() 062ms

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" 089ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 057ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 044ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 364ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 478ms

And Show all transport "false" 004ms

When Go to "TRANSPORT_TABLE" 221ms

And Go to transport details "DELIVERY" 4s 713ms

Then Verify that "CARRIER" in transport form is disabled 029ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 045ms

After Hooks.rollbackRemovedActionAuthorities() 065ms

After Hooks.deleteTransportAfterTest() 088ms

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" 093ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 060ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 004ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 219ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 994ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 163ms

And Go to transport details "TRANSPORT" 4s 492ms

Then Verify that "CARRIER" in transport form is disabled 026ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 047ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

After Hooks.deleteTransportAfterTest() 090ms

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" 092ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 047ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 004ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 195ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 722ms

And Show all transport "true" 063ms

When Go to "TRANSPORT_TABLE" 124ms

And Go to transport details "TRANSPORT_ORDER" 4s 464ms

Then Verify that "CARRIER" in transport form is disabled 029ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 047ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

After Hooks.deleteTransportAfterTest() 069ms

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" 094ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 277ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_MAIN_DATA_SECTION" "UNLIMITED" 065ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_ADVICE" "UNLIMITED" 046ms

And Add action authority with: "adama" "adama-admin" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 052ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 943ms

When Find transport in table with status "planned" 3s 339ms

And Confirm statuses until reach "process-ended" 21s 585ms

And Wait "90" seconds 1m 30s

And Go to "ARCHIVE_TAB" 295ms

And Show "DELIVERY" 081ms

And Go to transport details "DELIVERY" 32s 385ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 338ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 590ms

And Wait "7" seconds 7s

And Go to transport details "DELIVERY" 32s 350ms

Then Verify that "transport-description" in transport has value "opis" 030ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 063ms

After Hooks.rollbackRemovedActionAuthorities() 096ms

After Hooks.deleteTransportAfterTest() 103ms

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 354ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 481ms

When Go to transport details "DELIVERY" 4s 556ms

And Fill transport form 36s 032ms

And Change filled value in transport details "driver-name" "text" "XXX ZZZ" "0" 1s 394ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 108ms

And Go to new transport "DELIVERY" 307ms

Then Verify that driver "XXX ZZZ" is in list 703ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

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 248ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 212ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 290ms

And If user is login then logout 097ms

And Login as "pskza1-carrier@qa.qa-test" 1s 224ms

Then Verify that the transport has been transferred 1s 139ms

And Accept or reject "accept" transferred transport 15s 848ms

And Go to transport details "SMALLS_IMPORT" 4s 532ms

And Verify that "transaction-price" in transport form is visible 040ms

And Verify that transaction price field has correct value 024ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_IMPORT" 047ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

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 256ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 246ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 206ms

And If user is login then logout 101ms

And Login as "pskza1-carrier@qa.qa-test" 1s 231ms

Then Verify that the transport has been transferred 1s 126ms

And Accept or reject "accept" transferred transport 15s 760ms

And Go to transport details "SMALLS_EXPORT" 4s 504ms

And Verify that "transaction-price" in transport form is visible 038ms

And Verify that transaction price field has correct value 026ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_EXPORT" 044ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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" 1s 816ms

And Create transport "CREATE_DELIVERY_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 384ms

And Show all transport types 1s 049ms

Then Check if transport number is visible "DELIVERY" 15s 092ms

And Check if transport details is not visible 15s 048ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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 977ms

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 122ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 490ms

When Click on transport row 067ms

Then Verify if transport row is selected 035ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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 824ms

And Show all transport "false" 006ms

And Go to "TRANSPORT_TABLE" 176ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 312ms

When Click on transport row 1s 732ms

Then Verify if transport row is selected 025ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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 776ms

And Show all transport "false" 014ms

And Go to "TRANSPORT_TABLE" 108ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 257ms

When Click on transport row 072ms

Then Verify if transport row is selected 030ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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 718ms

And Show all transport "false" 019ms

And Go to "TRANSPORT_TABLE" 104ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 336ms

When Click on transport row 059ms

Then Verify if transport row is selected 026ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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 882ms

And Show all transport "false" 006ms

And Go to "TRANSPORT_TABLE" 095ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 281ms

When Click on transport row 073ms

Then Verify if transport row is selected 024ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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 738ms

And Show all transport "true" 066ms

And Go to "TRANSPORT_TABLE" 127ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 294ms

When Click on transport row 077ms

Then Verify if transport row is selected 027ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

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 798ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 202ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 071ms

When Accept or reject "accept" transferred transport 17s 712ms

Then Verify that transport is accept or reject "accept" 023ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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 179ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 207ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 064ms

When Accept or reject "reject" transferred transport 2s 136ms

Then Verify that transport is accept or reject "reject" 15s 027ms

Hooks

After Hooks.deleteTransportAfterTest() 056ms

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" 6s 167ms

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 072ms

When Accept or reject "accept" transferred transport 18s 006ms

Then Verify that transport is accept or reject "accept" 021ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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 252ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 225ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 072ms

When Accept or reject "reject" transferred transport 17s 986ms

Then Verify that transport is accept or reject "reject" 15s 050ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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 178ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 218ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 077ms

When Accept or reject "accept" transferred transport 18s 068ms

Then Verify that transport is accept or reject "accept" 018ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

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 071ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 223ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 074ms

When Accept or reject "reject" transferred transport 18s 027ms

Then Verify that transport is accept or reject "reject" 15s 068ms

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 431ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 228ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 212ms

And If user is login then logout 108ms

And Login as "paa1-carrier@qa.qa-test" 1s 061ms

Then Verify that the transport has been transferred with "true" 1s 222ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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 021ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 211ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 19s 271ms

And If user is login then logout 121ms

And Login as "paa1-carrier@qa.qa-test" 1s 204ms

Then Verify that the transport has been transferred with "false" 1s 194ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

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 818ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 189ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 178ms

And If user is login then logout 122ms

And Login as "pskza1-carrier@qa.qa-test" 1s 211ms

Then Verify that the transport has been transferred 1s 139ms

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 136ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 233ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 207ms

And If user is login then logout 113ms

And Login as "pskza1-carrier@qa.qa-test" 1s 218ms

Then Verify that the transport has been transferred 1s 129ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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 016ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 298ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 190ms

And Go to auction offer 1s 205ms

When Offer "1000" 145ms

And Verify that offer with "1000" has been added to auction 3s 038ms

And If user is login then logout 079ms

And Login as "swisskrono-admin" 1s 281ms

Then Go to auction details 1s 176ms

And Pass transport to carrier from auction details 1s 271ms

And If user is login then logout 420ms

And Login as "pskza1-carrier@qa.qa-test" 1s 224ms

And Verify that the transport has been transferred 1s 123ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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 009ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 247ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 108ms

And Go to auction offer 1s 203ms

When Offer "1000" 136ms

And Verify that offer with "1000" has been added to auction 3s 042ms

And Wait till auction end 1m 54s 017ms

And If user is login then logout 119ms

Then Login as "swisskrono-admin" 1s 407ms

And Go to auction details 1s 198ms

And Pass transport to carrier from auction details 1s 262ms

And If user is login then logout 412ms

And Login as "pskza1-carrier@qa.qa-test" 1s 245ms

And Verify that the transport has been transferred 1s 127ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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 112ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 214ms

And Go to "TRANSPORT_TABLE" 122ms

When Open transport transfer modal 1s 244ms

Then Verify that all enabled companies from "swisskrono" are shown in select 132ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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" 093ms

And Reject main section of a "Przewoźnik Adama Automat 1" in "adama" by API 405ms

And Login as "adama-admin" 935ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 216ms

And Go to "TRANSPORT_TABLE" 130ms

When Open transport transfer modal 1s 265ms

Then Verify that "Przewoźnik Adama Automat 1" is blocked in select 105ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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 091ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 215ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" with "120" seconds to accept transport 19s 284ms

And If user is login then logout 118ms

When Login as "paa1-carrier@qa.qa-test" 2s 797ms

And Verify that the transport has been transferred with "true" 1s 229ms

And Wait "120" seconds 2m

Then Verify if transport is not visible to carrier after expiring time to accept transport 15s 060ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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 021ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 437ms

When Go to "TRANSPORT_TABLE" 138ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 391ms

Then Check if new assortment group is disabled in transport form 032ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

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 019ms

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 049ms

And Click button advice in transport table "CONTAINER" 115ms

And Set advice window in schedule 2s 393ms

And Click button cancel in advice form 15s 321ms

And Set advice window in schedule 2s 165ms

And Click button cancel in advice form 15s 269ms

And Set advice window in schedule 2s 139ms

And Fill advice form 15s 914ms

And Click advice save button and wait for advice form to disappear 30s 713ms

And Go to "TRANSPORT_TABLE" 191ms

And Go to transport details "CONTAINER" 4s 442ms

Then Check are advice values equals 2s 396ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

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 143ms

And Get inputs from database "CREATE_TRANSPOSRT_ORDER" "super-admin-adama" 001ms

When Go to new transport "TRANSPORT" 429ms

And Fill transport form 26s 830ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 651ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 134ms

And Check is transport "TRANSPORT" created in transport table and set transport id 1s 104ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 071ms

And Accept or reject "reject" transferred transport 15s 862ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 173ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 322ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 055ms

And Accept or reject "accept" transferred transport 15s 936ms

Then Verify that transport is accept or reject "accept" 026ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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 099ms

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 182ms

When Show all transport types 1s 045ms

And Click button advice in transport table "DELIVERY" 131ms

And Set advice window in schedule 2s 573ms

And Click button cancel in advice form 15s 360ms

And Go to "TRANSPORT_TABLE" 218ms

When Go to transport details "DELIVERY" 4s 556ms

And Fill transport form 1m 2s 450ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 657ms

And Go to transport details "DELIVERY" 4s 414ms

Then Check are transport values equals 24s 845ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@deleteTransportAfterTest	3680	28	84	0	0	3792	379	28	407	5h 38m 37s 942ms	Failed

Tag Report