Cucumber-JVM Reports - Tag: @deleteTransportAfterTest

Project	Number	Date
ApolloFullRunnerReport	develop.372	08 kwi 2021, 05:40

	Steps	Scenarios	Features
@deleteTransportAfterTest	3643	37	92	0	0	3772	368	37	405	5h 37m 17s 798ms	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 855ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 5s 087ms

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

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

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

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

And Fill advice form 16s 447ms

And Click advice save button to check error message 088ms

Then Check if possible advice alert is displayed 028ms

Hooks

After Hooks.deleteTransportAfterTest() 697ms

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

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

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

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

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

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

And Fill advice form 8s 399ms

And Click advice save button to check error message 095ms

Then Check if possible advice alert is displayed 023ms

Hooks

After Hooks.deleteTransportAfterTest() 156ms

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

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

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

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

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

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

And Fill advice form 8s 383ms

And Click advice save button to check error message 090ms

Then Check if possible advice alert is displayed 029ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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

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

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

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

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

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

And Fill advice form 13s 122ms

And Click advice save button to check error message 071ms

Then Check if possible advice alert is displayed 020ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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

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

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

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

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

And Fill advice form 13s 136ms

And Click advice save button to check error message 061ms

Then Check if possible advice alert is displayed 018ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport types 1s 045ms

And Create advice "CREATE_ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 50s 076ms

And Go to "TRANSPORT_TABLE" 156ms

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

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

And Fill transport form 4s 719ms

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

And Expand advice panel 109ms

And Edit advice in transport details 12s 393ms

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

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

And Expand advice panel 112ms

Then Check are advice values equals after edition 176ms

Hooks

After Hooks.deleteTransportAfterTest() 139ms

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

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

And Show all transport types 1s 037ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 42s 189ms

And Go to "TRANSPORT_TABLE" 233ms

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

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

And Fill transport form 1m 2s 053ms

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

And Expand advice panel 120ms

And Edit advice in transport details 6s 583ms

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

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

And Expand advice panel 105ms

Then Check are advice values equals after edition 134ms

Hooks

After Hooks.deleteTransportAfterTest() 190ms

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

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

And Show all transport types 1s 045ms

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

And Go to "TRANSPORT_TABLE" 180ms

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

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

And Fill transport form 56s 999ms

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

And Expand advice panel 110ms

And Edit advice in transport details 6s 641ms

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

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

And Expand advice panel 106ms

Then Check are advice values equals after edition 098ms

Hooks

After Hooks.deleteTransportAfterTest() 188ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport types 1s 049ms

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

And Go to "TRANSPORT_TABLE" 160ms

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

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

And Fill transport form 24s 614ms

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

And Expand advice panel 102ms

And Edit advice in transport details 18s 529ms

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

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

And Expand advice panel 111ms

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

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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

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

And Show all transport types 1s 041ms

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

And Go to "TRANSPORT_TABLE" 169ms

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

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

And Fill transport form 24s 614ms

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

And Expand advice panel 109ms

And Edit advice in transport details 18s 506ms

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

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

And Expand advice panel 087ms

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

Hooks

After Hooks.deleteTransportAfterTest() 113ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

When Show all transport types 1s 041ms

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

And Set advice window in schedule 2s 363ms

And Fill advice form 12s 287ms

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

And Go to "TRANSPORT_TABLE" 203ms

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

Then Check are advice values equals 265ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

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

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

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

When Show all transport types 1s 035ms

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

And Set advice window in schedule 6s 416ms

And Fill advice form 11s 753ms

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

And Go to "TRANSPORT_TABLE" 192ms

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

Then Check are advice values equals 2s 298ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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

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

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

When Show all transport types 1s 036ms

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

And Set advice window in schedule 2s 548ms

And Fill advice form 8s 260ms

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

And Go to "TRANSPORT_TABLE" 212ms

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

Then Check are advice values equals 190ms

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

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

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

When Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 547ms

And Fill advice form 8s 346ms

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

And Go to "TRANSPORT_TABLE" 173ms

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

Then Check are advice values equals 187ms

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

Steps

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

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

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

When Show all transport types 1s 044ms

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

And Set advice window in schedule 2s 379ms

And Fill advice form 13s 093ms

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

And Go to "TRANSPORT_TABLE" 169ms

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

Then Check are advice values equals 2s 289ms

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

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

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

When Show all transport types 1s 037ms

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

And Set advice window in schedule 2s 421ms

And Fill advice form 13s 045ms

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

And Go to "TRANSPORT_TABLE" 180ms

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

Then Check are advice values equals 2s 305ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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

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

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

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

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

And Set advice window in schedule 2s 418ms

And Fill advice form 11s 716ms

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

And Go to "TRANSPORT_TABLE" 202ms

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

Then Check are advice values equals 2s 258ms

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

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

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

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

And Accept transferred transport by Api 115ms

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

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

When Show all transport types 1s 036ms

And Click button advice in transport table "SMALLS_IMPORT" 1s 005ms

And Set advice window in schedule 2s 581ms

And Fill advice form 14s 465ms

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

And Go to "TRANSPORT_TABLE" 166ms

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

Then Check are advice values equals 2s 320ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

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

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

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

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

And Accept transferred transport by Api 114ms

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

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

When Show all transport types 1s 035ms

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

And Set advice window in schedule 2s 617ms

And Fill advice form 14s 473ms

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

And Go to "TRANSPORT_TABLE" 154ms

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

Then Check are advice values equals 2s 287ms

Hooks

After Hooks.deleteTransportAfterTest() 194ms

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

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

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

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

And Accept transferred transport by Api 103ms

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

When Show all transport types 1s 035ms

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

And Set week view 1s 688ms

And Show yesterday 1s 107ms

Then Check if advice restriction blockade windows are visible 018ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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

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

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

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

And Accept transferred transport by Api 098ms

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

When Show all transport types 1s 035ms

And Click button advice in transport table "SMALLS_IMPORT" 1s 032ms

And Set week view 2s 059ms

And Show yesterday 1s 109ms

Then Check if advice restriction blockade windows are visible 028ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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_EXPORT" by JSON file as "super-admin-skz" 1s 261ms

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

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

And Accept transferred transport by Api 106ms

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

When Show all transport types 1s 039ms

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

And Set week view 2s 036ms

And Show yesterday 1s 124ms

Then Check if advice restriction blockade windows are visible 029ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

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

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

And Show all transport "false" 020ms

And Click on time window date 1s 302ms

And Select view "DAYS_4" 2s 047ms

And Move advice window "3" 1s 320ms

Then Check if advice window is in new location 023ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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

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

And Show all transport "false" 013ms

And Click on time window date 15s 763ms

And Select view "DAYS_4" 2s 070ms

And Move advice window "3" 15s 077ms

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.9iALdo}, 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: 866ed84e0ec4ca228401960068e7b9da
*** 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() 099ms

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

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

And Show all transport "false" 016ms

And Click on time window date 15s 531ms

And Select view "DAYS_4" 2s 065ms

And Move advice window "3" 1s 398ms

Then Check if advice window is in new location 022ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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

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

And Show all transport "false" 016ms

And Click on time window date 1s 404ms

And Select view "DAYS_4" 2s 047ms

And Move advice window "3" 1s 365ms

Then Check if advice window is in new location 019ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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

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

And Show all transport "false" 016ms

And Click on time window date 1s 275ms

And Select view "DAYS_4" 2s 069ms

And Move advice window "3" 1s 296ms

Then Check if advice window is in new location 017ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

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

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

And Show all transport "true" 079ms

And Click on time window date 1s 315ms

And Select view "DAYS_4" 2s 064ms

And Move advice window "3" 1s 335ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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

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

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

When Show all transport types 1s 038ms

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

And Set advice window in schedule 2s 550ms

And Fill advice form 8s 292ms

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

And Go to "TRANSPORT_TABLE" 222ms

And Click on time window date 1s 378ms

And Select view "DAYS_4" 2s 044ms

And Move advice window "3" 1s 419ms

Then Check if advice window is in new location 029ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 125ms

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

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

And Go to "TRANSPORT_TABLE" 124ms

And Show all transport types 1s 041ms

And Click on time window date 1s 309ms

And Scroll to time window "adviceWindow" 031ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 113ms

And Show all transport types 1s 038ms

And Click on time window date 1s 392ms

And Scroll to time window "adviceWindow" 034ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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

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

And Go to "TRANSPORT_TABLE" 105ms

And Show all transport types 1s 035ms

And Click on time window date 1s 311ms

And Scroll to time window "adviceWindow" 028ms

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

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

Error message

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

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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

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

And Go to "TRANSPORT_TABLE" 247ms

And Show all transport types 15s 027ms

And Click on time window date 15s 815ms

And Scroll to time window "adviceWindow" 037ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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

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

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

When Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 562ms

And Fill advice form 8s 297ms

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

And Go to "TRANSPORT_TABLE" 202ms

And Click on time window date 1s 394ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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

And Go to "WAREHOUSE_TAB" 842ms

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

When Go to new transport "DELIVERY" 331ms

And Fill transport form 39s 390ms

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

And Click previous page button in browser 022ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Go to "WAREHOUSE_TAB" 748ms

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

When Go to new transport "DELIVERY" 330ms

And Fill transport form 39s 385ms

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

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

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

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

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

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

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

When Show all transport types 1s 041ms

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

And Fill advice form 11s 573ms

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

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

And Open statuses popup 114ms

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

Hooks

After Hooks.deleteTransportAfterTest() 078ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if time window details preview displays correctly

Steps

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

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

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

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

And Go to "WAREHOUSE_TAB" 772ms

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

And Set week view 2s 229ms

And Move cursor over time window element 390ms

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

Hooks

After Hooks.deleteTransportAfterTest() 159ms

View Feature Company Resources

@deleteTransportAfterTest

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

Steps

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

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

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

And Fill transport form 34s 251ms

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

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

And Set advice window in schedule 2s 169ms

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

Then Go to "OWN_COMPANY_TAB" 266ms

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

Hooks

After Hooks.deleteTransportAfterTest() 187ms

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

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

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

And Fill transport form 16s 293ms

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

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

And Set advice window in schedule 2s 151ms

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

Then Go to "OWN_COMPANY_TAB" 236ms

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

Hooks

After Hooks.deleteTransportAfterTest() 129ms

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

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

When Go to "TRANSPORT_TABLE" 157ms

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

And Show all transport types 1s 045ms

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

Hooks

After Hooks.deleteTransportAfterTest() 146ms

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

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

When Go to "TRANSPORT_TABLE" 129ms

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

And Show all transport types 1s 047ms

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

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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

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

When Go to "TRANSPORT_TABLE" 129ms

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

And Show all transport types 1s 050ms

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

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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

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

When Go to "TRANSPORT_TABLE" 144ms

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

And Show all transport types 1s 046ms

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

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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

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

And Delete created transport by API 117ms

When Go to "ARCHIVE_TAB" 215ms

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

And Show "SMALLS_IMPORT" 083ms

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

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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

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

And Delete created transport by API 114ms

When Go to "ARCHIVE_TAB" 231ms

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

And Show "SMALLS_IMPORT" 080ms

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

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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

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

And Delete created transport by API 083ms

When Go to "ARCHIVE_TAB" 201ms

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

And Show "SMALLS_IMPORT" 078ms

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

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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

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

And Delete created transport by API 097ms

When Go to "ARCHIVE_TAB" 214ms

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

And Show "SMALLS_IMPORT" 082ms

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

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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

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

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

And Go to "TRANSPORT_TABLE" 134ms

And Show all transport "true" 070ms

And Select transportType "TRANSPORT_ORDER" 1s 139ms

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

Hooks

After Hooks.deleteTransportAfterTest() 084ms

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

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

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

And Go to "TRANSPORT_TABLE" 211ms

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

And Toggle transport table days limit filter 074ms

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

Hooks

After Hooks.deleteTransportAfterTest() 151ms

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

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

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

When Go to "TRANSPORT_TABLE" 129ms

And Go to auction form 1s 384ms

And Select contractors group "Kraj" 094ms

Then Verify that carrier "PSKZA1" is selected 021ms

Hooks

After Hooks.removeContractorsGroup() 084ms

After Hooks.deleteTransportAfterTest() 071ms

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

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

When Go to "TRANSPORT_TABLE" 132ms

And Go to auction form 1s 215ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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

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

When Go to "TRANSPORT_TABLE" 136ms

And Go to auction form 1s 223ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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

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

And Show all transport "false" 013ms

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

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

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

And Expand index panel 107ms

And Click add index button 129ms

And Fill index form 10s 552ms

And Click ok button in index form 15s 127ms

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

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

And Expand index panel 136ms

Then Check are transport values equals 086ms

Hooks

After Hooks.deleteProductAfterTest() 081ms

After Hooks.deleteTransportAfterTest() 071ms

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

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

And Show all transport "true" 082ms

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

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

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

And Expand index panel 098ms

And Click add index button 135ms

And Fill index form 7s 498ms

And Click ok button in index form 15s 134ms

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

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

And Expand index panel 130ms

Then Check are transport values equals 2s 131ms

Hooks

After Hooks.deleteProductAfterTest() 001ms

After Hooks.deleteTransportAfterTest() 098ms

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

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

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

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

And Add index to transport 26s 002ms

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

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

And Expand index panel 135ms

And Click delete index button 057ms

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

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

And Expand index panel 092ms

Then Verify that transport has no indexes 15s 014ms

Hooks

After Hooks.deleteProductAfterTest() 039ms

After Hooks.deleteTransportAfterTest() 077ms

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

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

And Show all transport "true" 072ms

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

And Add index to transport 22s 943ms

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

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

And Expand index panel 129ms

And Click delete index button 065ms

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

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

And Expand index panel 109ms

Then Verify that transport has no indexes 15s 005ms

Hooks

After Hooks.deleteProductAfterTest() 000ms

After Hooks.deleteTransportAfterTest() 072ms

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

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

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

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

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

And Add index to transport 24s 632ms

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

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

When Click on index details icon 105ms

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

Hooks

After Hooks.deleteProductAfterTest() 055ms

After Hooks.deleteTransportAfterTest() 122ms

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

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

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

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

And Show all transport types 1s 040ms

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

And Set advice window in schedule 2s 494ms

And Fill advice form 11s 928ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 183ms

After Hooks.deleteTransportAfterTest() 165ms

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

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

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

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

And Show all transport types 1s 053ms

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

And Set advice window in schedule 2s 601ms

And Fill advice form 8s 404ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 214ms

After Hooks.deleteTransportAfterTest() 141ms

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

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

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

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

And Show all transport types 1s 038ms

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

And Set advice window in schedule 2s 432ms

And Fill advice form 13s 212ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 225ms

After Hooks.deleteTransportAfterTest() 105ms

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

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

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

And Show all transport types 1s 050ms

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

And Go to "TRANSPORT_TABLE" 215ms

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

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

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

And Fill transport form 4s 730ms

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

And Expand advice panel 128ms

And Edit advice in transport details 12s 390ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 369ms

After Hooks.deleteTransportAfterTest() 137ms

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

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

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

And Show all transport types 1s 046ms

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

And Go to "TRANSPORT_TABLE" 246ms

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

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

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

And Fill transport form 1m 2s 566ms

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

And Expand advice panel 119ms

And Edit advice in transport details 6s 661ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 181ms

After Hooks.deleteTransportAfterTest() 135ms

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

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

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

And Show all transport types 1s 048ms

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

And Go to "TRANSPORT_TABLE" 207ms

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

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

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

And Fill transport form 24s 796ms

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

And Expand advice panel 117ms

And Edit advice in transport details 18s 643ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 273ms

After Hooks.deleteTransportAfterTest() 333ms

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 5s 289ms

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

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

Then Check if user got a mail 000ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 194ms

After Hooks.deleteTransportAfterTest() 133ms

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

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

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

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

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

And Wait "120" seconds 2m

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 294ms

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 008ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 222ms

After Hooks.deleteTransportAfterTest() 099ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 222ms

After Hooks.deleteTransportAfterTest() 076ms

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

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

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

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

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

And Wait till auction end 1m 58s 022ms

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

Then Check if user got a mail 000ms

Error message

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 563ms

After Hooks.deleteTransportAfterTest() 196ms

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

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

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

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

And Wait till auction end 1m 58s 022ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 355ms

After Hooks.deleteTransportAfterTest() 128ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 230ms

After Hooks.deleteTransportAfterTest() 081ms

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

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

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

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

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 32s 788ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 295ms

After Hooks.deleteTransportAfterTest() 062ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 249ms

After Hooks.deleteTransportAfterTest() 125ms

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

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

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

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

Error message

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

	at sun.reflect.GeneratedConstructorAccessor188.newInstance(Unknown Source)
	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() 215ms

After Hooks.deleteTransportAfterTest() 097ms

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

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

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

And Go to "TRANSPORT_TABLE" 140ms

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

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

And Fill transport form 35s 948ms

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

And Fill discrepancy report section 36s 253ms

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

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

And Generate discrepancy report 18s 809ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 545ms

After Hooks.deleteTransportAfterTest() 174ms

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

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

Error message

java.lang.NullPointerException
	at Utils.JsonApiUtil.getJSON(JsonApiUtil.java:128)
	at Utils.JsonApiUtil.getApiJson(JsonApiUtil.java:114)
	at CucumberTests.User.EditUserTest.prepareUserDetailsWithAllNotifications(EditUserTest.java:102)
	at CucumberTests.User.EditUserTest.prepareUserDetailsWithAllNotificationsAndByJSONFile(EditUserTest.java:90)
	at ✽.Prepare user "pha2-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file(file:Features/Atom/Mail/TransportMail.feature:6)

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 000ms

And Go to "WAREHOUSE_TAB" 000ms

And Select warehouse "Serownia" 000ms

And Set week view 000ms

And Show yesterday 000ms

And Move window into the past 000ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 000ms

Error message

java.lang.NullPointerException
	at Utils.JsonApiUtil.editJsonTextNode(JsonApiUtil.java:141)
	at CucumberTests.Hooks.cleanUserDetailsAfterTest(Hooks.java:296)
	at sun.reflect.GeneratedMethodAccessor240.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.deleteTransportAfterTest() 000ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 297ms

After Hooks.deleteTransportAfterTest() 070ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 273ms

After Hooks.deleteTransportAfterTest() 082ms

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

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

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 "true" 13s 761ms

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.9iALdo}, 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: 866ed84e0ec4ca228401960068e7b9da
	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() 217ms

After Hooks.deleteTransportAfterTest() 080ms

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

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

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

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

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.9iALdo}, 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: 866ed84e0ec4ca228401960068e7b9da
	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() 194ms

After Hooks.deleteTransportAfterTest() 080ms

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

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

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

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

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.9iALdo}, 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: 866ed84e0ec4ca228401960068e7b9da
	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() 249ms

After Hooks.deleteTransportAfterTest() 084ms

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

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

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

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

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

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

Then If user is login then logout 112ms

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

And Go to auction details 1s 205ms

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

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nie otrzymano zlecenia" 3m 14s 341ms

Then Check if user got a mail 000ms

Error message

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 354ms

After Hooks.deleteTransportAfterTest() 069ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 317ms

After Hooks.deleteTransportAfterTest() 076ms

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

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

And Fill transport form 41s 021ms

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

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

And Set advice window in schedule 2s 189ms

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

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

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

And Go to "TRANSPORT_TABLE" 260ms

And Show all transport "false" 008ms

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

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

And Click "save-transport" save button 1s 251ms

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

Hooks

After Hooks.deleteTransportAfterTest() 3s 926ms

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

And Set status of MOT to "AWAITING_VERIFICATION" 061ms

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

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

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

And Go to "TRANSPORT_TABLE" 194ms

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

And Set advice window in schedule 2s 807ms

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

Hooks

After Hooks.deleteTransportAfterTest() 105ms

After Hooks.deleteModeOfTransportationAfterTest() 080ms

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

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

And Set status of MOT to "DISABLED" 071ms

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

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

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

And Go to "TRANSPORT_TABLE" 210ms

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

And Set advice window in schedule 2s 761ms

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

Hooks

After Hooks.deleteTransportAfterTest() 096ms

After Hooks.deleteModeOfTransportationAfterTest() 074ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Set status of MOT to "ACCEPTED" 071ms

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

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

And Go to "TRANSPORT_TABLE" 206ms

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

And Set advice window in schedule 2s 772ms

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

Hooks

After Hooks.deleteTransportAfterTest() 089ms

After Hooks.deleteModeOfTransportationAfterTest() 065ms

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

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

And Set status of MOT to "UPDATED" 063ms

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

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

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

And Go to "TRANSPORT_TABLE" 217ms

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

And Set advice window in schedule 2s 757ms

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

Hooks

After Hooks.deleteTransportAfterTest() 095ms

After Hooks.deleteModeOfTransportationAfterTest() 081ms

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

And Set status of MOT to "REJECTED" 079ms

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

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

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

And Go to "TRANSPORT_TABLE" 179ms

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

And Set advice window in schedule 2s 766ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 083ms

After Hooks.deleteModeOfTransportationAfterTest() 082ms

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

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

And Set status of MOT to "BLOCKED" 065ms

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

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

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

And Go to "TRANSPORT_TABLE" 229ms

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

And Set advice window in schedule 2s 738ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 093ms

After Hooks.deleteModeOfTransportationAfterTest() 074ms

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

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

And Add transport by SKApi in "MGW" 150ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 51s 218ms

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

And Set advice window in schedule 2s 647ms

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

And Fill advice form 14s 849ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 234ms

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

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

When Add transport by SKApi in "MGW" 003ms

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

And Go to "TRANSPORT_TABLE" 118ms

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

Then Check are transport values equals 308ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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

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

When Add transport by SKApi in "MGW" 002ms

Then Check is transport "CONTAINER" created in transport table and set transport id 55s 002ms

And Go to "TRANSPORT_TABLE" 134ms

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

Then Check are transport values equals 300ms

Hooks

After Hooks.deleteTransportAfterTest() 164ms

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

When Add transport by SKApi in "MGW" 002ms

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

And Go to "TRANSPORT_TABLE" 149ms

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

Then Check are transport values equals 306ms

Hooks

After Hooks.deleteTransportAfterTest() 151ms

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

When Add transport by SKApi in "HRL" 002ms

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

And Go to "TRANSPORT_TABLE" 140ms

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

Then Check are transport values equals 309ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

When Add transport by SKApi in "HRL" 002ms

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

And Go to "TRANSPORT_TABLE" 126ms

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

Then Check are transport values equals 413ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

When Add transport by SKApi in "HRL" 003ms

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

And Go to "TRANSPORT_TABLE" 140ms

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

Then Check are transport values equals 317ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport by SKApi 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 127ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 082ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

When Add transport by SKApi in "" 003ms

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

And Go to "TRANSPORT_TABLE" 126ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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

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

And Add transport by SKApi in "MGW" 002ms

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

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

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

And Set advice window in schedule 2s 747ms

And Fill advice form 14s 822ms

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

And Go to "TRANSPORT_TABLE" 190ms

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

Then Check are advice values equals 2s 325ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

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

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

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

And Set advice window in schedule 2s 551ms

And Fill advice form 14s 656ms

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

And Go to "TRANSPORT_TABLE" 206ms

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

Then Check are advice values equals 2s 295ms

Hooks

After Hooks.deleteTransportAfterTest() 160ms

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

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

And Add transport by SKApi in "MGW" 002ms

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

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

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

And Set advice window in schedule 2s 547ms

And Fill advice form 14s 690ms

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

And Go to "TRANSPORT_TABLE" 238ms

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

Then Check are advice values equals 2s 341ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

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

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

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

And Set advice window in schedule 2s 543ms

And Fill advice form 14s 680ms

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

And Go to "TRANSPORT_TABLE" 205ms

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

Hooks

After Hooks.deleteTransportAfterTest() 140ms

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

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

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

And Set advice window in schedule 2s 522ms

And Fill advice form 14s 738ms

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

And Go to "TRANSPORT_TABLE" 216ms

Then Check advice data in SK API database "CONTAINER" 4s 113ms

Hooks

After Hooks.deleteTransportAfterTest() 148ms

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

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

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

And Set advice window in schedule 2s 518ms

And Fill advice form 14s 701ms

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

And Go to "TRANSPORT_TABLE" 253ms

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

Hooks

After Hooks.deleteTransportAfterTest() 108ms

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

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

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

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

And Fill advice form 14s 670ms

And Click advice save button to check error message 096ms

Then Check if possible advice alert is displayed 018ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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

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

And Add transport by SKApi in "MGW" 003ms

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

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

And Go to "TRANSPORT_TABLE" 221ms

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

And Expand advice panel 102ms

And Edit advice in transport details 14s 045ms

And Fill arrival date field 2s 285ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 166ms

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

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

And Add transport by SKApi in "MGW" 003ms

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

And Check is transport "CONTAINER" created in transport table and set transport id 27s 426ms

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

And Go to "TRANSPORT_TABLE" 196ms

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

And Expand advice panel 111ms

And Edit advice in transport details 14s 129ms

And Fill arrival date field 2s 298ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 217ms

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

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

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 33s 400ms

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

And Go to "TRANSPORT_TABLE" 239ms

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

And Expand advice panel 096ms

And Edit advice in transport details 14s 097ms

And Fill arrival date field 2s 299ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 136ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

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

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

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

When Go to "WAREHOUSE_TAB" 750ms

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

And Select view "DAYS_2" 2s 073ms

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

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

And Select view "DAYS_2" 2s 054ms

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

Hooks

After Hooks.deleteAllGrayWindowsAfterTest() 15s 200ms

After Hooks.deleteTransportAfterTest() 000ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

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

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

When Go to "WAREHOUSE_TAB" 805ms

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

And Select view "DAYS_2" 2s 097ms

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

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

And Select view "DAYS_2" 2s 055ms

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

Hooks

After Hooks.deleteAllGrayWindowsAfterTest() 15s 175ms

After Hooks.deleteTransportAfterTest() 000ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

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

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

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

When Go to "WAREHOUSE_TAB" 786ms

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

And Select view "DAYS_2" 2s 098ms

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

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

And Select view "DAYS_2" 2s 056ms

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

Hooks

After Hooks.deleteAllGrayWindowsAfterTest() 15s 180ms

After Hooks.deleteTransportAfterTest() 000ms

View Feature Schedule

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest @NIE_DZIAŁA_PRZEZ_A-7219

Scenario Outline Check if windows are visible after switching warehouse

Steps

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

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

And Select warehouse "MGW" 1s 164ms

And Select view "DAYS_2" 2s 082ms

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

And Select warehouse "HRL" 1s 413ms

And Select view "DAYS_2" 2s 062ms

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

Hooks

After Hooks.deleteAllGrayWindowsAfterTest() 15s 198ms

After Hooks.deleteTransportAfterTest() 000ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 144ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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

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

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

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

Then Check if transport has "departed" 027ms

Hooks

After Hooks.deleteTransportAfterTest() 144ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 113ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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

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

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

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

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

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

And Set advice window in schedule 2s 744ms

And Fill advice form 14s 758ms

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

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

And Go to "TRANSPORT_TABLE" 211ms

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

Hooks

After Hooks.deleteTransportAfterTest() 157ms

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

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

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

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

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

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

And Set advice window in schedule 2s 655ms

And Fill advice form 14s 678ms

And Click advice save button and wait for advice form to disappear 34s 971ms

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

And Go to "TRANSPORT_TABLE" 188ms

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

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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

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

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

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

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

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

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

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

Hooks

After Hooks.rollbackAddedActionAuthorities() 065ms

After Hooks.deleteTransportAfterTest() 114ms

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

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

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

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

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

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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

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

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

And Show all transport types 1s 028ms

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

And Set advice window in schedule 2s 555ms

And Fill advice form 8s 398ms

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

And Go to "TRANSPORT_TABLE" 228ms

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

And Confirm statuses until reach "left-the-area" 21s 541ms

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

Hooks

After Hooks.deleteTransportAfterTest() 212ms

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

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

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

And Show all transport types 1s 051ms

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

And Set advice window in schedule 2s 621ms

And Fill advice form 8s 444ms

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

And Go to "TRANSPORT_TABLE" 223ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 133ms

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

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

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

And Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 509ms

And Fill advice form 8s 449ms

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

And Go to "TRANSPORT_TABLE" 242ms

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

When Add file to transport by API 662ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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

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

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

And Show all transport types 1s 037ms

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

And Set advice window in schedule 2s 534ms

And Fill advice form 8s 412ms

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

And Go to "TRANSPORT_TABLE" 183ms

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

When Add file to transport by API 316ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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

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

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

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

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

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

And Show all transport types 1s 067ms

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

And Set advice window in schedule 6s 456ms

And Fill advice form 11s 934ms

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

And Go to "TRANSPORT_TABLE" 202ms

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

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

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

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:127)

Hooks

After Hooks.rollbackCustomFieldSettings() 066ms

After Hooks.deleteTransportAfterTest() 103ms

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

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

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

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

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

And Login as "keeeper-admin" 5s 872ms

And Show all transport types 1s 137ms

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

And Set advice window in schedule 2s 446ms

And Fill advice form 13s 263ms

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

And Go to "TRANSPORT_TABLE" 172ms

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

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

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

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:127)

Hooks

After Hooks.rollbackCustomFieldSettings() 051ms

After Hooks.deleteTransportAfterTest() 125ms

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

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

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

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

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

And Login as "keeeper-admin" 2s 107ms

And Show all transport types 1s 068ms

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

And Set advice window in schedule 2s 439ms

And Fill advice form 13s 213ms

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

And Go to "TRANSPORT_TABLE" 204ms

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

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

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

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:127)

Hooks

After Hooks.rollbackCustomFieldSettings() 048ms

After Hooks.deleteTransportAfterTest() 103ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 133ms

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

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

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

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:144)

Hooks

After Hooks.rollbackCustomFieldSettings() 046ms

After Hooks.deleteTransportAfterTest() 107ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 107ms

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

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

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

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:144)

Hooks

After Hooks.rollbackCustomFieldSettings() 048ms

After Hooks.deleteTransportAfterTest() 105ms

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" 092ms

And Get "Magazynier" settings from "hochland" in "DELIVERY" 027ms

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 138ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 621ms

And Login as "hochland-admin" 6s 003ms

And Go to "TRANSPORT_TABLE" 197ms

And Find transport in table with status "advice-added" 3s 192ms

And Confirm statuses until reach "during-unload" 6s 564ms

Then Check if next status is not possible to confirm 120ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:144)

Hooks

After Hooks.rollbackCustomFieldSettings() 114ms

After Hooks.deleteTransportAfterTest() 118ms

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 "LOAD" 021ms

And Get inputs from database "ADVICE_LOAD" "super-admin-keeeper" 002ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_LOAD_SANITARY_CONDITIONS_CFD" in "LOAD" - "keeeper" by "super-admin-keeeper" 047ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 161ms

And Login as "keeeper-admin" 1s 886ms

And Show all transport types 1s 121ms

And Click button advice in transport table "LOAD" 100ms

And Set advice window in schedule 2s 422ms

And Fill advice form 13s 230ms

And Click advice save button and wait for advice form to disappear 30s 736ms

And Go to "TRANSPORT_TABLE" 179ms

And Find transport in table with status "advice-added" 3s 225ms

When Confirm statuses until reach "arrived" 3s 841ms

And Check if next status is not possible to confirm 105ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:167)

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 000ms

And Go to transport details "LOAD" 000ms

And Open section: "advice-panel" 000ms

And Fill transport form 000ms

And Click "save-transport-and-close" save button and wait for form to disappear 000ms

And Go to transport details "LOAD" 000ms

And Open section: "advice-panel" 000ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 000ms

And Confirm statuses until reach "process-ended" 000ms

Then Check if transport has "process-ended" 000ms

Hooks

After Hooks.rollbackCustomFieldSettings() 044ms

After Hooks.deleteTransportAfterTest() 095ms

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" 097ms

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "CONTAINER" 023ms

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" 051ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 193ms

And Login as "keeeper-admin" 1s 953ms

And Show all transport types 1s 053ms

And Click button advice in transport table "CONTAINER" 100ms

And Set advice window in schedule 2s 381ms

And Fill advice form 13s 236ms

And Click advice save button and wait for advice form to disappear 30s 754ms

And Go to "TRANSPORT_TABLE" 200ms

And Find transport in table with status "advice-added" 3s 238ms

When Confirm statuses until reach "arrived" 3s 856ms

And Check if next status is not possible to confirm 107ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:167)

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 000ms

And Go to transport details "CONTAINER" 000ms

And Open section: "advice-panel" 000ms

And Fill transport form 000ms

And Click "save-transport-and-close" save button and wait for form to disappear 000ms

And Go to transport details "CONTAINER" 000ms

And Open section: "advice-panel" 000ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 000ms

And Confirm statuses until reach "process-ended" 000ms

Then Check if transport has "process-ended" 000ms

Hooks

After Hooks.rollbackCustomFieldSettings() 075ms

After Hooks.deleteTransportAfterTest() 094ms

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" 092ms

And Get "Magazynier (R)" settings from "hochland" in "TRANSFER_BETWEEN_WAREHOUSES" 021ms

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 166ms

And Login as "hochland-admin" 6s 342ms

And Show all transport types 1s 068ms

And Click button advice in transport table "TRANSFER_BETWEEN_WAREHOUSES" 142ms

And Set advice window in schedule 6s 506ms

And Fill advice form 11s 895ms

And Click advice save button and wait for advice form to disappear 30s 748ms

And Go to "TRANSPORT_TABLE" 216ms

And Find transport in table with status "advice-added" 3s 216ms

When Confirm statuses until reach "during-load" 6s 606ms

And Check if next status is not possible to confirm 110ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:167)

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 000ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 000ms

And Open section: "advice-panel" 000ms

And Fill transport form 000ms

And Click "save-transport-and-close" save button and wait for form to disappear 000ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 000ms

And Open section: "advice-panel" 000ms

And Fill "warehouseman-(u)" in transport form 000ms

And Confirm statuses until reach "process-ended" 000ms

Then Check if transport has "process-ended" 000ms

Hooks

After Hooks.rollbackCustomFieldSettings() 075ms

After Hooks.deleteTransportAfterTest() 120ms

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" 021ms

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" 047ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 360ms

And Login as "keeeper-admin" 2s 145ms

And Go to "TRANSPORT_TABLE" 136ms

And Find transport in table with status "planned" 3s 193ms

When Confirm statuses until reach "arrived" 3s 802ms

And Check if next status is not possible to confirm 107ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:195)

And Go to transport details "UNLOAD" 000ms

And Fill transport form 000ms

And Click "save-transport-and-close" save button and wait for form to disappear 000ms

And Confirm statuses until reach "process-ended" 000ms

Then Check if transport has "process-ended" 000ms

Hooks

After Hooks.rollbackCustomFieldSettings() 048ms

After Hooks.deleteTransportAfterTest() 098ms

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" 091ms

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "TANKER_GRANULATE_DELIVERY" 024ms

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" 051ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 291ms

And Login as "keeeper-admin" 1s 823ms

And Go to "TRANSPORT_TABLE" 104ms

And Find transport in table with status "planned" 3s 168ms

When Confirm statuses until reach "arrived" 3s 840ms

And Check if next status is not possible to confirm 111ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:195)

And Go to transport details "TANKER_GRANULATE_DELIVERY" 000ms

And Fill transport form 000ms

And Click "save-transport-and-close" save button and wait for form to disappear 000ms

And Confirm statuses until reach "process-ended" 000ms

Then Check if transport has "process-ended" 000ms

Hooks

After Hooks.rollbackCustomFieldSettings() 043ms

After Hooks.deleteTransportAfterTest() 095ms

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" 094ms

And Get "Magazynier" settings from "hochland" in "DELIVERY" 032ms

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" 100ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 375ms

And Login as "hochland-admin" 2s 379ms

And Go to "TRANSPORT_TABLE" 184ms

And Find transport in table with status "advice-added" 3s 188ms

When Confirm statuses until reach "during-unload" 6s 554ms

And Check if next status is not possible to confirm 124ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusIsNotPossibleToConfirm(ConfirmStatuses.java:104)
	at ✽.Check if next status is not possible to confirm(file:Features/Atom/Statuses/ConfirmStatuses.feature:195)

And Go to transport details "DELIVERY" 000ms

And Fill transport form 000ms

And Click "save-transport-and-close" save button and wait for form to disappear 000ms

And Confirm statuses until reach "process-ended" 000ms

Then Check if transport has "process-ended" 000ms

Hooks

After Hooks.rollbackCustomFieldSettings() 111ms

After Hooks.deleteTransportAfterTest() 164ms

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" 092ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 1s 285ms

And Confirm status "REPORTING" by Public API "v1" 099ms

And Confirm status "ARRIVAL" by Public API "v1" 122ms

And Login as "swiss-krono-delivery-guard" 5s 640ms

And Go to "TRANSPORT_TABLE" 201ms

When Confirm "Departure" status in transport row 3s 076ms

Then Verify that "Departure" has been confirmed 034ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

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" 095ms

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "UNLOAD" 020ms

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 295ms

When Login as "keeeper-admin" 1s 897ms

And Find transport in table with status "planned" 3s 209ms

And Confirm statuses until reach "arrived" 3s 816ms

And Go to transport details "UNLOAD" 4s 399ms

And Fill transport form 37s 939ms

Then Check if next status is not possible to confirm in transport details 068ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusInTransportDetailsIsNotPossibleToConfirm(ConfirmStatuses.java:119)
	at ✽.Check if next status is not possible to confirm in transport details(file:Features/Atom/Statuses/ConfirmStatuses.feature:236)

Hooks

After Hooks.rollbackCustomFieldSettings() 060ms

After Hooks.deleteTransportAfterTest() 113ms

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" 099ms

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "TANKER_GRANULATE_DELIVERY" 022ms

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" 045ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 361ms

When Login as "keeeper-admin" 1s 908ms

And Find transport in table with status "planned" 3s 210ms

And Confirm statuses until reach "arrived" 3s 837ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 380ms

And Fill transport form 36s 468ms

Then Check if next status is not possible to confirm in transport details 071ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusInTransportDetailsIsNotPossibleToConfirm(ConfirmStatuses.java:119)
	at ✽.Check if next status is not possible to confirm in transport details(file:Features/Atom/Statuses/ConfirmStatuses.feature:236)

Hooks

After Hooks.rollbackCustomFieldSettings() 049ms

After Hooks.deleteTransportAfterTest() 108ms

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" 095ms

And Get "Magazynier" settings from "hochland" in "DELIVERY" 023ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 003ms

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 135ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 334ms

When Login as "hochland-admin" 2s 355ms

And Find transport in table with status "advice-added" 3s 304ms

And Confirm statuses until reach "during-unload" 7s 547ms

And Go to transport details "DELIVERY" 4s 662ms

And Fill transport form 36s 020ms

Then Check if next status is not possible to confirm in transport details 058ms

Error message

java.lang.AssertionError: Klawisz potwierdzenia statusu jest aktywny!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfNextStatusInTransportDetailsIsNotPossibleToConfirm(ConfirmStatuses.java:119)
	at ✽.Check if next status is not possible to confirm in transport details(file:Features/Atom/Statuses/ConfirmStatuses.feature:236)

Hooks

After Hooks.rollbackCustomFieldSettings() 119ms

After Hooks.deleteTransportAfterTest() 082ms

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" 093ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 483ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 253ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 136ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 900ms

And Login as "bausch-admin" 1s 966ms

And Go to "TRANSPORT_TABLE" 200ms

And Find transport in table with status "advice-added" 3s 212ms

When Confirm statuses until reach "on-the-way" 9s 362ms

And Open statuses popup 063ms

And Toggle status date confirmation checkbox 293ms

And Confirm statuses until reach "process-ended" 18s 761ms

Then Check if transport has "process-ended" 028ms

Hooks

After Hooks.deleteTransportAfterTest() 145ms

After Hooks.deleteModeOfTransportationAfterTest() 098ms

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" 262ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 228ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 145ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 675ms

And Login as "bausch-admin" 1s 121ms

And Go to "TRANSPORT_TABLE" 222ms

And Find transport in table with status "advice-added" 3s 224ms

When Confirm statuses until reach "on-the-way" 9s 378ms

And Open statuses popup 048ms

And Toggle status date confirmation checkbox 275ms

And Change status execution date to "1" days from today 2s 190ms

Then Verify that status cannot be confirmed 1s 091ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

After Hooks.deleteModeOfTransportationAfterTest() 076ms

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" 4s 262ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 205ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 090ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 689ms

And Login as "bausch-admin" 1s 048ms

And Go to "TRANSPORT_TABLE" 218ms

And Find transport in table with status "advice-added" 3s 221ms

When Confirm statuses until reach "on-the-way" 9s 379ms

And Open statuses popup 052ms

And Toggle status date confirmation checkbox 265ms

And Change status execution date to "-1" days from today 2s 151ms

Then Verify that status cannot be confirmed 1s 087ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

After Hooks.deleteModeOfTransportationAfterTest() 079ms

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" 146ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 398ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 1s 030ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 021ms

When Login as "farmacol-admin" 2s 509ms

And Go to "TRANSPORT_TABLE" 209ms

And Confirm statuses until reach "during-unload" 9s 387ms

And Set actual confirmed transport status list 1s 371ms

And Disable task by API 2s 984ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 443ms

And Edit transport hours and recalculate statuses 16s 335ms

Then Verify that all confirmed statuses are still on transport status list 185ms

Hooks

After Hooks.deleteTransportAfterTest() 177ms

After Hooks.rollbackTaskChanges() 044ms

View Feature Status rejection

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it is possible to reject status by guard in transport table

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 978ms

And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 284ms

And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 1s 651ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 350ms

And Check if reject date is not visible 15s 024ms

When Reject status: Book of disinfection 060ms

And Check if reject date is visible 431ms

Then If user is login then logout 078ms

And Login as "lantmannen-admin" 1s 145ms

And Check if note was added to transport after status rejection 1s 233ms

And Check if history note was added to transport after status rejection - "LOAD" 5s 523ms

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nieaktualna księga mycia i dezynfekcji" 13s 229ms

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 190ms

After Hooks.deleteTransportAfterTest() 095ms

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 707ms

And Create transport "CREATE_LOAD_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 299ms

And Check if reject date is not visible 15s 055ms

When Reject status: Book of disinfection 084ms

And Check if reject date is visible 156ms

And Get rejection date 030ms

And Wait "60" seconds 1m

And Reject status: Book of disinfection 067ms

Then Check if reject date has changed 1s 086ms

Hooks

After Hooks.deleteTransportAfterTest() 253ms

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 206ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 716ms

And Go to transport details "LOAD" 4s 319ms

And Check if reject date is not visible 15s 032ms

When Reject status: Book of disinfection 073ms

Then Check if reject date is visible 146ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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" 999ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 341ms

And Open statuses popup 101ms

And Check if reject date is not visible 15s 028ms

When Reject status: Book of disinfection 085ms

Then Open statuses popup 055ms

And Check if reject date is visible 100ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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" 3s 146ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 414ms

And Confirm to the last status by API 300ms

When Find statuses for transport in table 2s 171ms

And Revoke statuses until reach "advice-added" 6s 829ms

Then Check if transport has "advice-added" 023ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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" 6s 155ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 351ms

And Confirm to the last status by API 186ms

When Find statuses for transport in table 1s 710ms

And Revoke statuses until reach "planned" 6s 795ms

Then Check if transport has "planned" 028ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

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 131ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 215ms

When Find transport in table with status "new" 3s 230ms

And Open statuses popup 096ms

Then Check if transport has checkpoints from list "Utworzenie zlecenia,Dodanie awizacji,Potwierdzenie okna czasowego" in "0" 075ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

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 067ms

And Get inputs from database "ADVICE_EXTERNAL_DELIVERY" "super-admin-farmacol" 001ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 188ms

And Click button advice in transport table "EXTERNAL_DELIVERY" 140ms

And Set advice window in schedule 2s 726ms

And Fill advice form 12s 226ms

And Click advice save button and wait for advice form to disappear 31s 246ms

And Go to "TRANSPORT_TABLE" 250ms

When Find transport in table with status "advice-added" 3s 187ms

And Open statuses popup 102ms

Then Check if transport has checkpoints from list "Zgłoszenie kierowcy,Rozpoczęcie rozładunku,Zakończenie rozładunku" in "1" 075ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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" 094ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 186ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 613ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 029ms

When Login as "farmacol-admin" 1s 044ms

And Go to "TRANSPORT_TABLE" 202ms

And Confirm statuses until reach "registered-katowice-przyjęcia" 6s 696ms

And Disable task by API 097ms

And Find transport pencil button in transports table 1s 256ms

And Click pencil and move transport to next day in schedule 3s 295ms

And Go to "TRANSPORT_TABLE" 250ms

Then Verify that "START_OF_UNLOADING" is not visible 122ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

After Hooks.rollbackTaskChanges() 037ms

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 372ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 5s 551ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 094ms

When Go to "WAREHOUSE_TAB" 762ms

And Select warehouse "Serownia" 1s 397ms

And Set week view 1s 098ms

And Show yesterday 1s 070ms

And Move window into the past 305ms

Then Check if window is "red" 2s 021ms

Hooks

After Hooks.rollbackAddedAuthorities() 132ms

After Hooks.deleteTransportAfterTest() 126ms

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 044ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 350ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "lantmannen-admin" 047ms

When Go to "WAREHOUSE_TAB" 293ms

And Select warehouse "Magazyn - Nowa Sól" 2s 222ms

And Set week view 1s 127ms

And Show yesterday 1s 061ms

And Move window into the past 441ms

Then Check if window is "red" 2s 022ms

Hooks

After Hooks.rollbackAddedAuthorities() 042ms

After Hooks.deleteTransportAfterTest() 096ms

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 224ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 182ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "piast-admin" 054ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 002ms

When Show all transport types 1s 042ms

And Click button advice in transport table "DELIVERY" 121ms

And Set advice window in schedule 2s 645ms

And Fill advice form 8s 465ms

And Click advice save button and wait for advice form to disappear 30s 721ms

And Select warehouse "Magazyn Hala A" 1s 206ms

And Set week view 2s 107ms

And Show yesterday 1s 175ms

And Move window into the past 583ms

Then Check if window is "red" 2s 058ms

Hooks

After Hooks.rollbackAddedAuthorities() 032ms

After Hooks.deleteTransportAfterTest() 089ms

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 859ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Set algorithm setting for "super-admin-hochland" in "Magazyn Zimny Kaźmierz" on "Magazyn Zimny" 458ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 521ms

When Go to "WAREHOUSE_TAB" 788ms

And Select warehouse "Magazyn Zimny Kaźmierz" 1s 723ms

And Set week view 1s 122ms

And Check if time window length is correct after "CREATE" 029ms

And Change number of pallets in transport 51s 485ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 636ms

And Check if time window length is correct after "EDIT" 030ms

Hooks

After Hooks.deleteTransportAfterTest() 150ms

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 223ms

And Get "UNLOAD" settings from "keeeper" 046ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 135ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;true" 130ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 402ms

When Go to "WAREHOUSE_TAB" 315ms

And Select warehouse "Magazyn Surowców" 1s 200ms

And Set week view 1s 099ms

Then Check if time window has proper "60" 017ms

Hooks

After Hooks.rollbackTransportTypeSettings() 068ms

After Hooks.clearAlgorithmSettings() 143ms

After Hooks.deleteTransportAfterTest() 108ms

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 125ms

And Get "UNLOAD" settings from "keeeper" 022ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 113ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;false" 066ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 342ms

When Go to "WAREHOUSE_TAB" 328ms

And Select warehouse "Magazyn Surowców" 1s 168ms

And Set week view 1s 108ms

Then Check if time window has proper "60" 015ms

Hooks

After Hooks.rollbackTransportTypeSettings() 060ms

After Hooks.clearAlgorithmSettings() 105ms

After Hooks.deleteTransportAfterTest() 085ms

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 107ms

And Get "LOAD" settings from "keeeper" 027ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 097ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;false" 071ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 178ms

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" 119ms

And Set advice window in schedule 2s 483ms

And Fill advice form 13s 279ms

And Click advice save button and wait for advice form to disappear 30s 662ms

Then Check if time window has proper "30" 027ms

Hooks

After Hooks.rollbackTransportTypeSettings() 101ms

After Hooks.clearAlgorithmSettings() 104ms

After Hooks.deleteTransportAfterTest() 112ms

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 213ms

And Get "CONTAINER" settings from "keeeper" 026ms

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", "20;false" 057ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 196ms

And Get inputs from database "ADVICE_CONTAINER" "super-admin-keeeper" 003ms

And Show all transport types 1s 046ms

And Click button advice in transport table "CONTAINER" 133ms

And Set advice window in schedule 2s 380ms

And Fill advice form 13s 244ms

And Click advice save button and wait for advice form to disappear 30s 677ms

Then Check if time window has proper "60" 026ms

Hooks

After Hooks.rollbackTransportTypeSettings() 065ms

After Hooks.clearAlgorithmSettings() 106ms

After Hooks.deleteTransportAfterTest() 102ms

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" 6s 601ms

And Set algorithm setting for "super-admin-hochland" in "Serownia" on "Magazyn Sera" 148ms

And Set token of apiUsername "dha1-supplier-2@qa.qa-test" 091ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 15s 623ms

And Set token of apiUsername "super-admin-hochland" 122ms

When Go to transport details "DELIVERY" 32s 665ms

And Change filled value in transport details "quantity" "number" "25" "0" 1s 346ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 094ms

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.9iALdo}, 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: 866ed84e0ec4ca228401960068e7b9da
	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() 198ms

After Hooks.deleteTransportAfterTest() 112ms

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 186ms

And Set basic authorities "ROLE_ACCESS_TO_NUMBER_OF_WINDOWS" to user "keeeper-admin" 048ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 235ms

When Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 46s 661ms

And Check if time window counter value equals "1" 073ms

And Select view "DAYS_2" 2s 089ms

And Move advice window "2" 1s 344ms

And Select view "DAY" 2s 056ms

Then Check if time window counter value equals "0" 078ms

And Delete created transport by API 105ms

And Check if time window counter value equals "0" 055ms

And Click in free spot in schedule page to create gray window 250ms

And Check if time window counter value equals "0" 059ms

And Click in free spot in schedule page to create dedicated window 049ms

And Check if time window counter value equals "0" 051ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.deleteTransportAfterTest() 091ms

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" 5s 958ms

When Go to new transport "DELIVERY" 256ms

And Fill transport form 11s 377ms

And Click "save-transport" save button and wait for form to disappear 15s 667ms

And Set advice window in schedule 2s 177ms

And Check is transport created in schedule and set transport id 611ms

And Go to "TRANSPORT_TABLE" 256ms

When Click on time window date 1s 314ms

And Open transport form when in schedule 1s 166ms

Then Check are transport values equals 156ms

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" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 430ms

When Go to new transport "DELIVERY" 340ms

And Fill transport form 38s 869ms

And Click "save-transport" save button and wait for form to disappear 15s 651ms

And Set advice window in schedule 2s 154ms

And Check is transport created in schedule and set transport id 629ms

And Go to "TRANSPORT_TABLE" 259ms

When Click on time window date 1s 268ms

And Open transport form when in schedule 1s 240ms

Then Check are transport values equals 19s 361ms

Hooks

After Hooks.deleteTransportAfterTest() 137ms

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 302ms

When Go to new transport "CISTERN_DELIVERY" 353ms

And Fill transport form 34s 911ms

And Click "save-transport" save button and wait for form to disappear 15s 940ms

And Set advice window in schedule 2s 218ms

And Check is transport created in schedule and set transport id 592ms

And Go to "TRANSPORT_TABLE" 216ms

When Click on time window date 1s 453ms

And Open transport form when in schedule 1s 250ms

Then Check are transport values equals 21s 414ms

Hooks

After Hooks.deleteTransportAfterTest() 132ms

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 525ms

When Go to new transport "CISTERN_COLLECTION" 349ms

And Fill transport form 28s 393ms

And Click "save-transport" save button and wait for form to disappear 15s 952ms

And Set advice window in schedule 2s 217ms

And Check is transport created in schedule and set transport id 861ms

And Go to "TRANSPORT_TABLE" 179ms

When Click on time window date 1s 437ms

And Open transport form when in schedule 1s 207ms

Then Check are transport values equals 21s 427ms

Hooks

After Hooks.deleteTransportAfterTest() 137ms

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 514ms

When Go to new transport "DELIVERY" 306ms

And Fill transport form 38s 028ms

And Click "save-transport" save button and wait for form to disappear 15s 650ms

And Set advice window in schedule 2s 162ms

And Check is transport created in schedule and set transport id 628ms

And Go to "TRANSPORT_TABLE" 204ms

When Click on time window date 1s 327ms

And Open transport form when in schedule 1s 166ms

Then Check are transport values equals 19s 398ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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" 002ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 127ms

When Go to new transport "LOAD" 298ms

And Fill transport form 38s 087ms

And Click "save-transport" save button and wait for form to disappear 15s 657ms

And Set advice window in schedule 2s 157ms

And Check is transport created in schedule and set transport id 599ms

And Go to "TRANSPORT_TABLE" 250ms

When Click on time window date 1s 339ms

And Open transport form when in schedule 1s 178ms

Then Check are transport values equals 19s 321ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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" 093ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 103ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 060ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 108ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 19s 222ms

And Login as "farmacol-admin" 2s 531ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 45s 905ms

And Go to "TRANSPORT_TABLE" 324ms

When Go to transport details "EXTERNAL_DELIVERY" 4s 461ms

And Add step "unload" 108ms

And Change filled value in transport details "warehouse-select-step-2" "select" "Mory Przyjęcia" "0" 3s 466ms

And Change filled value in transport details "weight-step-2" "number" "23" "0" 1s 360ms

And Change filled value in transport details "number-of-pallets-step-2" "number" "23" "0" 1s 356ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 329ms

Then Click "save-transport" save button 196ms

And Set advice window in schedule in "2" days 4s 946ms

And Click advice save button and wait for advice form to disappear 30s 980ms

And Go to "TRANSPORT_TABLE" 259ms

And Check if transport has "2" time windows 016ms

Hooks

After Hooks.rollbackTransportTypeSettings() 066ms

After Hooks.rollbackAddedActionAuthorities() 055ms

After Hooks.deleteTransportAfterTest() 130ms

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" 094ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 033ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 067ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 183ms

And Set double window advice 000ms

And Login as "farmacol-admin" 2s 194ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 50s 043ms

And Go to "TRANSPORT_TABLE" 304ms

And Get checkpoint colors for transport 008ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "true" 46s 272ms

Hooks

After Hooks.rollbackTransportTypeSettings() 145ms

After Hooks.deleteTransportAfterTest() 207ms

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" 092ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 035ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 078ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 351ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 146ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 50s 564ms

And Go to "TRANSPORT_TABLE" 297ms

And Get checkpoint colors for transport 003ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "false" 31s 170ms

Hooks

After Hooks.rollbackTransportTypeSettings() 147ms

After Hooks.deleteTransportAfterTest() 193ms

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" 112ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 031ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 080ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 346ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 036ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 50s 517ms

And Get checkpoint colors for transport 005ms

And Go to "TRANSPORT_TABLE" 301ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true" 5s 432ms

Error message

java.lang.AssertionError
	at org.junit.Assert.fail(Assert.java:86)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.junit.Assert.assertTrue(Assert.java:52)
	at CucumberTests.TimeWindow.TimeWindowTest.verifyThatTransportColorsOfWindowsChangeProperlyInScheduleWhenWindowColorDependsOnWarehouseIs(TimeWindowTest.java:118)
	at ✽.Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true"(file:Features/Atom/TimeWindow/TransportWindow.feature:250)

Hooks

After Hooks.rollbackTransportTypeSettings() 140ms

After Hooks.deleteTransportAfterTest() 113ms

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" 094ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 037ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 070ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 15s 202ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 231ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 50s 572ms

And Get checkpoint colors for transport 005ms

And Go to "TRANSPORT_TABLE" 339ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "false" 7s 712ms

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.9iALdo}, 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: 866ed84e0ec4ca228401960068e7b9da
	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.getCssValue(RemoteWebElement.java:165)
	at CucumberTests.TimeWindow.TimeWindowTest.checkIfWindowsHasProperColorsInSchedule(TimeWindowTest.java:177)
	at CucumberTests.TimeWindow.TimeWindowTest.verifyThatTransportColorsOfWindowsChangeProperlyInScheduleWhenWindowColorDependsOnWarehouseIs(TimeWindowTest.java:118)
	at ✽.Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "false"(file:Features/Atom/TimeWindow/TransportWindow.feature:250)

Hooks

After Hooks.rollbackTransportTypeSettings() 138ms

After Hooks.deleteTransportAfterTest() 130ms

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" 092ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 196ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 656ms

And Login as "super-admin-farmacol" 6s 636ms

And Show all transport types 1s 174ms

And Click on time window date 1s 627ms

Then Open transport form when in schedule 1s 296ms

And Click create similar button 15s 183ms

And Click cancel button in transport form 106ms

And Open transport form when in schedule 1s 186ms

Then Check if transport form modal is visible 046ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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" 094ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 198ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 630ms

And Login as "super-admin-farmacol" 1s 140ms

And Show all transport types 1s 161ms

And Click on time window date 1s 627ms

Then Open transport form when in schedule 1s 297ms

And Click create similar button 15s 160ms

And Click cancel button in transport form 114ms

And Open transport form when in schedule 1s 201ms

Then Check if transport form modal is visible 041ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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 267ms

And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 002ms

And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 062ms

And Set proper delay time to move order to archive after task timeout 135ms

When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 278ms

And Go to "WAREHOUSE_TAB" 4s 350ms

And Change warehouse in schedule to: "Katowice" 1s 095ms

And Wait "60" seconds 1m

And Verify that transport window is grey 034ms

And Verify that transport is in archive 1s 276ms

Then Restore transport from archive 1s 107ms

And Verify that transport has been successfully restored 15s 274ms

Hooks

After Hooks.rollbackSettings() 050ms

After Hooks.deleteTransportAfterTest() 111ms

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 104ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 219ms

And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 030ms

And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 003ms

When Go to "TRANSPORT_TABLE" 146ms

And Click button advice in transport table "OWN_COLLECTION" 1s 989ms

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 40s 379ms

And Go to "TRANSPORT_TABLE" 213ms

And Find transport in table with status "planned-magazyn-tychy" 3s 257ms

And Confirm statuses until reach "process-ended" 24s 342ms

And Wait "12" seconds 12s

Then Go to "ARCHIVE_TAB" 215ms

And Show "OWN_COLLECTION" 062ms

And Verify that created transport is "true" in transport table 15s 096ms

Hooks

After Hooks.rollbackSettings() 076ms

After Hooks.deleteTransportAfterTest() 107ms

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 026ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 275ms

When Fill auction form 15s 508ms

Then Verify that the auction has been added to transport 054ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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 274ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 223ms

When Fill auction form 15s 400ms

Then Verify that the auction has been added to transport 035ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

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 078ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 184ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 108ms

When If user is login then logout 114ms

And Login as "paa1-carrier@qa.qa-test" 2s 632ms

And Go to auction offer 1s 189ms

And Accept transport with minimum rate 15s 649ms

Then Check if carrier is assigned to transport 021ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject auction offer

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 069ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 289ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 107ms

When If user is login then logout 123ms

And Login as "paa1-carrier@qa.qa-test" 1s 251ms

And Go to auction offer 1s 286ms

And Reject auction offer 15s 624ms

Then Verify that offer has been removed from transport 15s 046ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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 263ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 250ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 108ms

When If user is login then logout 112ms

And Login as "pskza1-carrier@qa.qa-test" 1s 283ms

And Go to auction offer 1s 221ms

And Reject auction offer 15s 602ms

Then Verify that offer has been removed from transport 15s 065ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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 150ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 246ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 120ms

When If user is login then logout 114ms

And Login as "paa1-carrier@qa.qa-test" 1s 102ms

And Go to auction offer 1s 218ms

And Offer prize above maximum - "20000" 145ms

Then Verify that is not possible to add offer 209ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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 164ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 203ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 113ms

When If user is login then logout 089ms

And Login as "pskza1-carrier@qa.qa-test" 1s 086ms

And Go to auction offer 1s 217ms

And Offer prize above maximum - "20000" 128ms

Then Verify that is not possible to add offer 135ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

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 042ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 215ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 107ms

And Wait till auction end 1m 58s 018ms

Then Verify that is possible to add auction 050ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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 310ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 271ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 118ms

And Wait till auction end 1m 58s 017ms

Then Verify that is possible to add auction 052ms

Hooks

After Hooks.deleteTransportAfterTest() 235ms

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 230ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 486ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 128ms

And Go to auction offer 1s 210ms

When Offer "1000" 144ms

Then Verify that offer with "1000" has been added to auction 3s 043ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

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 052ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 241ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 108ms

And Go to auction offer 1s 205ms

When Offer "1000" 140ms

Then Verify that offer with "1000" has been added to auction 3s 034ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

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" 979ms

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 101ms

And Go to auction offer 1s 183ms

When Offer "1000" 103ms

And Verify that offer with "1000" has been added to auction 3s 037ms

Then Go to auction offer 1s 184ms

And Revoke current offer 573ms

And Verify that offer has been revoked 30s 598ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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 145ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 296ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 118ms

And Go to auction offer 1s 197ms

When Offer "1000" 152ms

And Verify that offer with "1000" has been added to auction 3s 043ms

Then Go to auction offer 1s 179ms

And Offer "1500" 108ms

And Verify that offer with "1500" has been added to auction 3s 022ms

Hooks

After Hooks.deleteTransportAfterTest() 068ms

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" 980ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 233ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 102ms

And Go to auction offer 1s 197ms

When Offer "1000" 148ms

And Verify that offer with "1000" has been added to auction 3s 035ms

Then Login as "swisskrono-admin" 1s 043ms

And Go to auction details 1s 208ms

And Finish active auction 060ms

And Verify that the transport has no active auction 147ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if carrier can see current place in auction depending on the "canSeeCurrentPlaceInAuction" role

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 088ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 213ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 104ms

And Go to auction offer 1s 197ms

When Offer "1000" 127ms

Then Verify that carrier can see current place in auction depending on the "true" role 101ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if carrier can see current place in auction depending on the "canSeeCurrentPlaceInAuction" role

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 060ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 237ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 091ms

And Go to auction offer 1s 193ms

When Offer "1000" 135ms

Then Verify that carrier can see current place in auction depending on the "false" role 15s 018ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

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 114ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 252ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 109ms

And Go to auction offer 1s 211ms

When Offer "300" 143ms

And Verify that carrier can't add offer to auction 027ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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 044ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 215ms

And Show all transport "false" 012ms

When Go to auction form 1s 288ms

Then Verify carrier selection value "false" 056ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

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 204ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 253ms

And Show all transport "true" 080ms

When Go to auction form 1s 193ms

Then Verify carrier selection value "true" 036ms

Hooks

After Hooks.deleteTransportAfterTest() 059ms

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 007ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 189ms

When Open transport auction form 173ms

And Select all companies checkbox in transport auction form 064ms

And Unselect company "PAA2" in transport auction form 071ms

And Put transport on auction 15s 213ms

And Open transport auction history 116ms

And Open participants section in transport auction history 050ms

Then Check if unselected "PAA2" is in transport auction history as participant 15s 038ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

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 218ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 388ms

When Open transport auction form 333ms

And Select all companies checkbox in transport auction form 063ms

And Unselect company "PSKZA2" in transport auction form 051ms

And Put transport on auction 15s 158ms

And Open transport auction history 096ms

And Open participants section in transport auction history 056ms

Then Check if unselected "PSKZA2" is in transport auction history as participant 15s 013ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

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 708ms

When Go to new transport "UNLOAD" 15s 314ms

And Fill transport form 24s 613ms

And Click "save-transport" save button and wait for form to disappear 16s 031ms

And Set advice window in schedule 2s 205ms

And Check is transport created in schedule and set transport id 633ms

And Go to "TRANSPORT_TABLE" 211ms

And Go to transport details "UNLOAD" 32s 418ms

Then Check are transport values equals 21s 378ms

Hooks

After Hooks.deleteTransportAfterTest() 132ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 149ms

When Go to new transport "DELIVERY" 298ms

And Fill transport form 11s 426ms

And Click "save-transport" save button and wait for form to disappear 15s 599ms

And Set advice window in schedule 2s 170ms

And Check is transport created in schedule and set transport id 521ms

And Go to "TRANSPORT_TABLE" 258ms

And Go to transport details "DELIVERY" 4s 351ms

Then Check are transport values equals 140ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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" 003ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 146ms

When Go to new transport "OWN_COLLECTION" 333ms

And Fill transport form 17s 994ms

And Click "save-transport" save button and wait for form to disappear 15s 703ms

And Set advice window in schedule 2s 186ms

And Check is transport created in schedule and set transport id 497ms

And Go to "TRANSPORT_TABLE" 196ms

And Go to transport details "OWN_COLLECTION" 4s 310ms

Then Check are transport values equals 150ms

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_DELIVERY" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 404ms

When Go to new transport "DELIVERY" 349ms

And Fill transport form 39s 025ms

And Click "save-transport" save button and wait for form to disappear 15s 610ms

And Set advice window in schedule 2s 164ms

And Check is transport created in schedule and set transport id 611ms

And Go to "TRANSPORT_TABLE" 280ms

And Go to transport details "DELIVERY" 4s 671ms

Then Check are transport values equals 19s 381ms

Hooks

After Hooks.deleteTransportAfterTest() 140ms

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" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 463ms

When Go to new transport "CISTERN_DELIVERY" 382ms

And Fill transport form 34s 934ms

And Click "save-transport" save button and wait for form to disappear 15s 930ms

And Set advice window in schedule 2s 224ms

And Check is transport created in schedule and set transport id 4s 754ms

And Go to "TRANSPORT_TABLE" 196ms

And Go to transport details "CISTERN_DELIVERY" 4s 392ms

Then Check are transport values equals 21s 385ms

Hooks

After Hooks.deleteTransportAfterTest() 210ms

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 469ms

When Go to new transport "CISTERN_COLLECTION" 349ms

And Fill transport form 28s 403ms

And Click "save-transport" save button and wait for form to disappear 15s 842ms

And Set advice window in schedule 2s 223ms

And Check is transport created in schedule and set transport id 624ms

And Go to "TRANSPORT_TABLE" 188ms

And Go to transport details "CISTERN_COLLECTION" 4s 386ms

Then Check are transport values equals 21s 387ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 476ms

When Go to new transport "OWN_COLLECTION" 343ms

And Fill transport form 32s 866ms

And Click "save-transport" save button and wait for form to disappear 15s 700ms

And Set advice window in schedule 2s 173ms

And Check is transport created in schedule and set transport id 610ms

And Go to "TRANSPORT_TABLE" 209ms

And Go to transport details "OWN_COLLECTION" 4s 572ms

Then Check are transport values equals 19s 360ms

Hooks

After Hooks.deleteTransportAfterTest() 287ms

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 483ms

When Go to new transport "OWN_COLLECTION_POWDER_FACTORY" 363ms

And Fill transport form 32s 911ms

And Click "save-transport" save button and wait for form to disappear 15s 773ms

And Set advice window in schedule 2s 178ms

And Check is transport created in schedule and set transport id 923ms

And Go to "TRANSPORT_TABLE" 170ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 431ms

Then Check are transport values equals 4s 323ms

Hooks

After Hooks.deleteTransportAfterTest() 146ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_EXPORT" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 442ms

When Go to new transport "EXPORT" 369ms

And Fill transport form 40s 739ms

And Click "save-transport" save button and wait for form to disappear 15s 632ms

And Set advice window in schedule 2s 165ms

And Check is transport created in schedule and set transport id 638ms

And Go to "TRANSPORT_TABLE" 199ms

And Go to transport details "EXPORT" 5s 140ms

Then Check are transport values equals 4s 323ms

Hooks

After Hooks.deleteTransportAfterTest() 201ms

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 585ms

When Go to new transport "DELIVERY" 15s 207ms

And Fill transport form 28s 422ms

And Click "save-transport" save button and wait for form to disappear 15s 623ms

And Set advice window in schedule 2s 160ms

And Check is transport created in schedule and set transport id 751ms

And Go to "TRANSPORT_TABLE" 241ms

And Go to transport details "DELIVERY" 32s 277ms

Then Check are transport values equals 36s 353ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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 100ms

When Go to new transport "DELIVERY" 317ms

And Fill transport form 38s 145ms

And Click "save-transport" save button and wait for form to disappear 15s 581ms

And Set advice window in schedule 2s 157ms

And Check is transport created in schedule and set transport id 582ms

And Go to "TRANSPORT_TABLE" 158ms

And Go to transport details "DELIVERY" 4s 320ms

Then Check are transport values equals 19s 312ms

Hooks

After Hooks.deleteTransportAfterTest() 364ms

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 129ms

When Go to new transport "LOAD" 311ms

And Fill transport form 37s 973ms

And Click "save-transport" save button and wait for form to disappear 15s 797ms

And Set advice window in schedule 2s 179ms

And Check is transport created in schedule and set transport id 878ms

And Go to "TRANSPORT_TABLE" 249ms

And Go to transport details "LOAD" 4s 339ms

Then Check are transport values equals 19s 307ms

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-keeeper" 002ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 286ms

When Go to new transport "UNLOAD" 309ms

And Fill transport form 37s 635ms

And Click "save-transport" save button and wait for form to disappear 15s 584ms

And Set advice window in schedule 2s 145ms

And Check is transport created in schedule and set transport id 617ms

And Go to "TRANSPORT_TABLE" 216ms

And Go to transport details "UNLOAD" 4s 372ms

Then Check are transport values equals 21s 415ms

Hooks

After Hooks.deleteTransportAfterTest() 197ms

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 176ms

When Go to new transport "TANKER_GRANULATE_DELIVERY" 327ms

And Fill transport form 37s 678ms

And Click "save-transport" save button and wait for form to disappear 15s 614ms

And Set advice window in schedule 2s 151ms

And Check is transport created in schedule and set transport id 539ms

And Go to "TRANSPORT_TABLE" 202ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 381ms

Then Check are transport values equals 21s 428ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

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 164ms

When Go to new transport "DELIVERY" 313ms

And Fill transport form 22s 962ms

And Click "save-transport" save button and wait for form to disappear 15s 583ms

And Set advice window in schedule 2s 157ms

And Check is transport created in schedule and set transport id 632ms

And Go to "TRANSPORT_TABLE" 186ms

And Go to transport details "DELIVERY" 4s 315ms

Then Check are transport values equals 17s 308ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

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 363ms

When Go to new transport "WEIGHING" 294ms

And Fill transport form 13s 586ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 604ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 161ms

And Go to transport details "WEIGHING" 6s 740ms

And Check are transport values equals 2s 162ms

Hooks

After Hooks.deleteTransportAfterTest() 137ms

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 179ms

When Go to new transport "TRANSPORT" 373ms

And Fill transport form 26s 824ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 649ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 134ms

And Go to transport details "TRANSPORT" 4s 455ms

And Check are transport values equals 6s 243ms

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_CONTAINER" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 162ms

When Go to new transport "CONTAINER" 295ms

And Fill transport form 11s 225ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 648ms

And Show all transport "false" 012ms

And Go to "TRANSPORT_TABLE" 125ms

And Go to transport details "CONTAINER" 4s 363ms

And Check are transport values equals 084ms

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_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 473ms

When Go to new transport "TRANSFER_BETWEEN_WAREHOUSES" 334ms

And Fill transport form 12s 954ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 626ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 155ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 612ms

And Check are transport values equals 4s 173ms

Hooks

After Hooks.deleteTransportAfterTest() 141ms

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 727ms

When Go to new transport "DELIVERY" 311ms

And Fill transport form 22s 610ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 649ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 144ms

And Go to transport details "DELIVERY" 4s 562ms

And Check are transport values equals 17s 222ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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 255ms

When Go to new transport "LOAD" 366ms

And Fill transport form 26s 410ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 631ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 136ms

And Go to transport details "LOAD" 4s 568ms

And Check are transport values equals 2s 161ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-keeeper" 002ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 164ms

When Go to new transport "LOAD" 306ms

And Fill transport form 24s 690ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 662ms

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 144ms

And Go to transport details "LOAD" 4s 363ms

And Check are transport values equals 19s 253ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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 171ms

When Go to new transport "CONTAINER" 310ms

And Fill transport form 24s 729ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 631ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 147ms

And Go to transport details "CONTAINER" 4s 359ms

And Check are transport values equals 19s 230ms

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_SMALLS_IMPORT" "super-admin-skz" 002ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 211ms

When Go to new transport "SMALLS_IMPORT" 419ms

And Fill transport form 36s 605ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 131ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 144ms

And Go to transport details "SMALLS_IMPORT" 4s 440ms

And Check are transport values equals 10s 394ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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 274ms

When Go to new transport "SMALLS_EXPORT" 421ms

And Fill transport form 36s 454ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 599ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 144ms

And Go to transport details "SMALLS_EXPORT" 4s 422ms

And Check are transport values equals 10s 418ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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 167ms

When Go to new transport "TRANSPORT_ORDER" 405ms

And Fill transport form 30s 077ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 615ms

And Show all transport "true" 096ms

And Go to "TRANSPORT_TABLE" 138ms

And Go to transport details "TRANSPORT_ORDER" 4s 428ms

And Check are transport values equals 19s 356ms

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 145ms

When Go to new transport "TRANSPORT" 384ms

And Fill transport form 37s 663ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 626ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 139ms

And Go to transport details "TRANSPORT" 4s 354ms

And Check are transport values equals 4s 219ms

Hooks

After Hooks.deleteTransportAfterTest() 161ms

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 165ms

When Go to new transport "INBOUND" 379ms

And Fill transport form 41s 192ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 646ms

And Show all transport "true" 096ms

And Go to "TRANSPORT_TABLE" 116ms

And Go to transport details "INBOUND" 4s 405ms

And Check are transport values equals 2s 272ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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" 003ms

And Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 164ms

When Go to new transport "EXTERNAL_DELIVERY" 316ms

And Fill transport form 53s 862ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 634ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 127ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 411ms

And Check are transport values equals 4s 512ms

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" "dfa1-supplier" 002ms

And Login as "dfa1-supplier" and set token of apiUsername "dfa1-supplier" 2s 766ms

When Go to new transport "EXTERNAL_DELIVERY" 15s 310ms

And Fill transport form 47s 426ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 608ms

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 129ms

And Go to transport details "EXTERNAL_DELIVERY" 32s 462ms

And Check are transport values equals 4s 504ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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 071ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 002ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 19s 600ms

And Show all transport "false" 007ms

When Go to transport details "UNLOAD" 32s 495ms

And Fill transport form 30s 504ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 164ms

And Go to transport details "UNLOAD" 32s 449ms

Then Check are transport values equals 4s 298ms

Hooks

After Hooks.deleteTransportAfterTest() 180ms

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 196ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 001ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 251ms

And Show all transport "false" 008ms

When Go to transport details "TRANSPORT" 4s 458ms

And Fill transport form 10s 349ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 603ms

And Go to transport details "TRANSPORT" 4s 445ms

Then Check are transport values equals 4s 148ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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 142ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 172ms

And Show all transport "false" 011ms

When Go to transport details "CONTAINER" 4s 355ms

And Fill transport form 4s 735ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 634ms

And Go to transport details "CONTAINER" 4s 377ms

Then Check are transport values equals 052ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

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 119ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 297ms

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 4s 309ms

And Fill transport form 11s 594ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 610ms

And Go to transport details "DELIVERY" 4s 366ms

Then Check are transport values equals 117ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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 078ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-adama" 002ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-adama" 1s 293ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION" 4s 410ms

And Fill transport form 21s 648ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 592ms

And Go to transport details "OWN_COLLECTION" 4s 342ms

Then Check are transport values equals 2s 229ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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 478ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 364ms

And Show all transport "false" 006ms

When Go to transport details "DELIVERY" 4s 728ms

And Fill transport form 36s 024ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 136ms

And Go to transport details "DELIVERY" 4s 437ms

Then Check are transport values equals 10s 578ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 485ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-hochland" 001ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 417ms

And Show all transport "false" 006ms

When Go to transport details "OWN_COLLECTION" 4s 688ms

And Fill transport form 36s 666ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 127ms

And Go to transport details "OWN_COLLECTION" 4s 442ms

Then Check are transport values equals 6s 400ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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 420ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 351ms

And Show all transport "false" 005ms

When Go to transport details "EXPORT" 5s 694ms

And Fill transport form 48s 150ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 144ms

And Go to transport details "EXPORT" 4s 520ms

Then Check are transport values equals 8s 519ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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 482ms

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 195ms

And Show all transport "false" 007ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 548ms

And Fill transport form 36s 307ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 671ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 462ms

Then Check are transport values equals 12s 497ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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 492ms

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 335ms

And Show all transport "false" 007ms

When Go to transport details "CISTERN_DELIVERY" 4s 469ms

And Fill transport form 27s 355ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 655ms

And Go to transport details "CISTERN_DELIVERY" 4s 371ms

Then Check are transport values equals 6s 312ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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 487ms

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 261ms

And Show all transport "false" 005ms

When Go to transport details "CISTERN_COLLECTION" 4s 460ms

And Fill transport form 25s 928ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 624ms

And Go to transport details "CISTERN_COLLECTION" 4s 404ms

Then Check are transport values equals 6s 272ms

Hooks

After Hooks.deleteTransportAfterTest() 176ms

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 454ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 001ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 300ms

And Show all transport "false" 006ms

When Go to transport details "WEIGHING" 4s 370ms

And Fill transport form 12s 341ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 597ms

And Go to transport details "WEIGHING" 4s 335ms

Then Check are transport values equals 2s 140ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

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 480ms

And Get inputs from database "EDIT_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 002ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 358ms

And Show all transport "false" 007ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 543ms

And Fill transport form 35s 259ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 165ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 448ms

Then Check are transport values equals 6s 362ms

Hooks

After Hooks.deleteTransportAfterTest() 143ms

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 304ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 32s 420ms

And Fill transport form 25s 738ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 611ms

And Go to transport details "DELIVERY" 32s 328ms

Then Check are transport values equals 2s 199ms

Hooks

After Hooks.deleteTransportAfterTest() 284ms

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 179ms

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 408ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 539ms

And Fill transport form 1m 2s 590ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 154ms

And Go to transport details "DELIVERY" 4s 440ms

Then Check are transport values equals 121ms

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() 103ms

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 211ms

And Get inputs from database "EDIT_LOAD" "super-admin-piast" 002ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 203ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 672ms

And Fill transport form 57s 415ms

And Click "save-transport-and-close" save button and wait for form to disappear 5s 424ms

And Go to transport details "LOAD" 4s 398ms

Then Check are transport values equals 24s 858ms

Hooks

After Hooks.deleteTransportAfterTest() 197ms

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 188ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 619ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 369ms

And Fill transport form 16s 500ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 644ms

And Go to transport details "DELIVERY" 4s 324ms

Then Check are transport values equals 076ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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 096ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 577ms

And Show all transport "false" 007ms

When Go to transport details "LOAD" 4s 317ms

And Fill transport form 28s 161ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 176ms

And Go to transport details "LOAD" 4s 339ms

Then Check are transport values equals 2s 255ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

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 137ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 369ms

And Show all transport "false" 009ms

When Go to transport details "UNLOAD" 4s 435ms

And Fill transport form 38s 017ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 141ms

And Go to transport details "UNLOAD" 4s 387ms

Then Check are transport values equals 6s 428ms

Hooks

After Hooks.deleteTransportAfterTest() 140ms

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 151ms

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 384ms

And Show all transport "false" 011ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 387ms

And Fill transport form 36s 310ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 619ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 391ms

Then Check are transport values equals 6s 401ms

Hooks

After Hooks.deleteTransportAfterTest() 4s 097ms

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 192ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 273ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 392ms

And Fill transport form 24s 808ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 614ms

And Go to transport details "LOAD" 4s 373ms

Then Check are transport values equals 4s 224ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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 182ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 177ms

And Show all transport "false" 011ms

When Go to transport details "CONTAINER" 4s 405ms

And Fill transport form 24s 755ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 602ms

And Go to transport details "CONTAINER" 4s 336ms

Then Check are transport values equals 4s 215ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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 259ms

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 261ms

And Show all transport "false" 009ms

When Go to transport details "SMALLS_IMPORT" 4s 530ms

And Fill transport form 33s 009ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 643ms

And Go to transport details "SMALLS_IMPORT" 4s 452ms

Then Check are transport values equals 8s 320ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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 247ms

And Get inputs from database "EDIT_SMALLS_EXPORT" "super-admin-skz" 002ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 254ms

And Show all transport "false" 010ms

When Go to transport details "SMALLS_EXPORT" 4s 532ms

And Fill transport form 33s 114ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 646ms

And Go to transport details "SMALLS_EXPORT" 4s 388ms

Then Check are transport values equals 8s 325ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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 178ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 417ms

And Show all transport "true" 077ms

When Go to transport details "DELIVERY" 4s 329ms

And Fill transport form 19s 653ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 638ms

And Go to transport details "DELIVERY" 4s 335ms

Then Check are transport values equals 197ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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 157ms

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 276ms

And Show all transport "true" 077ms

When Go to transport details "TRANSPORT_ORDER" 4s 461ms

And Fill transport form 26s 774ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 638ms

And Go to transport details "TRANSPORT_ORDER" 4s 388ms

Then Check are transport values equals 2s 277ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

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" 6s 572ms

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 280ms

And Show all transport "false" 007ms

When Go to transport details "CONTAINER" 4s 397ms

And Fill transport form 8s 879ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 617ms

And Go to transport details "CONTAINER" 4s 414ms

Then Check are transport values equals 4s 131ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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 449ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 475ms

And Show all transport "false" 008ms

When Delete transport 17s 895ms

Then Transport not displayed in table of transports 15s 017ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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 214ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 202ms

And Show all transport "false" 010ms

When Delete transport 17s 235ms

Then Transport not displayed in table of transports 15s 013ms

Hooks

After Hooks.deleteTransportAfterTest() 058ms

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 085ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 337ms

And Show all transport "false" 010ms

When Delete transport 17s 523ms

Then Transport not displayed in table of transports 15s 014ms

Hooks

After Hooks.deleteTransportAfterTest() 057ms

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 244ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 234ms

And Show all transport "false" 008ms

When Delete transport 16s 994ms

Then Transport not displayed in table of transports 15s 013ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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 239ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 268ms

And Show all transport "false" 009ms

When Delete transport 17s 677ms

Then Transport not displayed in table of transports 15s 047ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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 245ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 285ms

And Show all transport "false" 010ms

When Delete transport 17s 705ms

Then Transport not displayed in table of transports 15s 030ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 116ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 339ms

And Show all transport "true" 079ms

When Delete transport 19s 096ms

Then Transport not displayed in table of transports 15s 050ms

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 198ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 287ms

And Show all transport "true" 083ms

When Delete transport 17s 116ms

Then Transport not displayed in table of transports 15s 023ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 1s 079ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 002ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 700ms

And Show all transport "false" 010ms

When Go to transport details "UNLOAD" 32s 497ms

And Fill transport form 30s 526ms

And Click "save-transport" save button 1s 276ms

And Click cancel button in transport form 105ms

And Go to transport details "UNLOAD" 32s 386ms

Then Check are transport values equals 4s 290ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 143ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 002ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 231ms

And Show all transport "false" 010ms

When Go to transport details "TRANSPORT" 4s 476ms

And Fill transport form 10s 325ms

And Click "save-transport" save button 795ms

And Click cancel button in transport form 076ms

And Go to transport details "TRANSPORT" 4s 333ms

Then Check are transport values equals 4s 152ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 144ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 194ms

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 369ms

And Fill transport form 4s 716ms

And Click "save-transport" save button 723ms

And Click cancel button in transport form 074ms

And Go to transport details "CONTAINER" 4s 265ms

Then Check are transport values equals 041ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 124ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 325ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 356ms

And Fill transport form 11s 604ms

And Click "save-transport" save button 715ms

And Click cancel button in transport form 079ms

And Go to transport details "DELIVERY" 4s 265ms

Then Check are transport values equals 125ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 134ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-adama" 001ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-adama" 1s 317ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION" 4s 419ms

And Fill transport form 21s 633ms

And Click "save-transport" save button 713ms

And Click cancel button in transport form 070ms

And Go to transport details "OWN_COLLECTION" 4s 327ms

Then Check are transport values equals 2s 224ms

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 428ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 304ms

And Show all transport "false" 007ms

When Go to transport details "DELIVERY" 4s 746ms

And Fill transport form 35s 964ms

And Click "save-transport" save button 1s 240ms

And Click cancel button in transport form 090ms

And Go to transport details "DELIVERY" 4s 425ms

Then Check are transport values equals 10s 562ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

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 445ms

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 322ms

And Show all transport "false" 008ms

When Go to transport details "OWN_COLLECTION" 4s 592ms

And Fill transport form 36s 809ms

And Click "save-transport" save button 1s 255ms

And Click cancel button in transport form 075ms

And Go to transport details "OWN_COLLECTION" 4s 411ms

Then Check are transport values equals 6s 374ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 432ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 374ms

And Show all transport "false" 005ms

When Go to transport details "EXPORT" 5s 590ms

And Fill transport form 48s 093ms

And Click "save-transport" save button 808ms

And Click cancel button in transport form 087ms

And Go to transport details "EXPORT" 4s 418ms

Then Check are transport values equals 8s 499ms

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 462ms

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 168ms

And Show all transport "false" 009ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 697ms

And Fill transport form 36s 123ms

And Click "save-transport" save button 1s 272ms

And Click cancel button in transport form 090ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 428ms

Then Check are transport values equals 12s 486ms

Hooks

After Hooks.deleteTransportAfterTest() 060ms

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 420ms

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 368ms

And Show all transport "false" 005ms

When Go to transport details "CISTERN_DELIVERY" 4s 533ms

And Fill transport form 27s 433ms

And Click "save-transport" save button 778ms

And Click cancel button in transport form 074ms

And Go to transport details "CISTERN_DELIVERY" 4s 401ms

Then Check are transport values equals 6s 341ms

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 "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 511ms

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 292ms

And Show all transport "false" 007ms

When Go to transport details "CISTERN_COLLECTION" 4s 447ms

And Fill transport form 25s 890ms

And Click "save-transport" save button 712ms

And Click cancel button in transport form 080ms

And Go to transport details "CISTERN_COLLECTION" 4s 357ms

Then Check are transport values equals 6s 318ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

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 473ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 001ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 197ms

And Show all transport "false" 007ms

When Go to transport details "WEIGHING" 4s 376ms

And Fill transport form 12s 400ms

And Click "save-transport" save button 707ms

And Click cancel button in transport form 075ms

And Go to transport details "WEIGHING" 4s 305ms

Then Check are transport values equals 2s 172ms

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 "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 402ms

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 319ms

And Show all transport "false" 004ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 561ms

And Fill transport form 35s 277ms

And Click "save-transport" save button 1s 230ms

And Click cancel button in transport form 093ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 408ms

Then Check are transport values equals 6s 364ms

Hooks

After Hooks.deleteTransportAfterTest() 185ms

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 160ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 340ms

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 32s 416ms

And Fill transport form 25s 733ms

And Click "save-transport" save button 712ms

And Click cancel button in transport form 093ms

And Go to transport details "DELIVERY" 32s 320ms

Then Check are transport values equals 2s 210ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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 235ms

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 216ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 450ms

And Fill transport form 1m 2s 599ms

And Click "save-transport" save button 1s 227ms

And Click cancel button in transport form 058ms

And Go to transport details "DELIVERY" 4s 362ms

Then Check are transport values equals 125ms

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() 115ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 238ms

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 290ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 699ms

And Fill transport form 57s 453ms

And Click "save-transport" save button 1s 260ms

And Click cancel button in transport form 083ms

And Go to transport details "LOAD" 4s 439ms

Then Check are transport values equals 24s 784ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 099ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 537ms

And Show all transport "false" 009ms

When Go to transport details "DELIVERY" 5s 222ms

And Fill transport form 16s 462ms

And Click "save-transport" save button 733ms

And Click cancel button in transport form 085ms

And Go to transport details "DELIVERY" 4s 302ms

Then Check are transport values equals 065ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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 129ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 285ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 317ms

And Fill transport form 28s 325ms

And Click "save-transport" save button 1s 236ms

And Click cancel button in transport form 082ms

And Go to transport details "LOAD" 4s 329ms

Then Check are transport values equals 2s 243ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 174ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 365ms

And Show all transport "false" 010ms

When Go to transport details "UNLOAD" 4s 431ms

And Fill transport form 37s 939ms

And Click "save-transport" save button 1s 235ms

And Click cancel button in transport form 082ms

And Go to transport details "UNLOAD" 4s 353ms

Then Check are transport values equals 6s 358ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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 179ms

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 356ms

And Show all transport "false" 010ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 446ms

And Fill transport form 36s 399ms

And Click "save-transport" save button 773ms

And Click cancel button in transport form 081ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 325ms

Then Check are transport values equals 6s 358ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 838ms

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 149ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 247ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 410ms

And Fill transport form 24s 760ms

And Click "save-transport" save button 730ms

And Click cancel button in transport form 064ms

And Go to transport details "LOAD" 4s 316ms

Then Check are transport values equals 4s 204ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 178ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 002ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 194ms

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 404ms

And Fill transport form 24s 766ms

And Click "save-transport" save button 712ms

And Click cancel button in transport form 061ms

And Go to transport details "CONTAINER" 4s 325ms

Then Check are transport values equals 4s 204ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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 236ms

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 271ms

And Show all transport "false" 010ms

When Go to transport details "SMALLS_IMPORT" 4s 524ms

And Fill transport form 33s 082ms

And Click "save-transport" save button 774ms

And Click cancel button in transport form 062ms

And Go to transport details "SMALLS_IMPORT" 4s 344ms

Then Check are transport values equals 8s 355ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 214ms

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 232ms

And Show all transport "false" 009ms

When Go to transport details "SMALLS_EXPORT" 4s 509ms

And Fill transport form 33s 137ms

And Click "save-transport" save button 4s 938ms

And Click cancel button in transport form 076ms

And Go to transport details "SMALLS_EXPORT" 4s 346ms

Then Check are transport values equals 8s 357ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 195ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 473ms

And Show all transport "true" 070ms

When Go to transport details "DELIVERY" 4s 357ms

And Fill transport form 19s 587ms

And Click "save-transport" save button 742ms

And Click cancel button in transport form 070ms

And Go to transport details "DELIVERY" 4s 329ms

Then Check are transport values equals 175ms

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 "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 168ms

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 272ms

And Show all transport "true" 080ms

When Go to transport details "TRANSPORT_ORDER" 4s 456ms

And Fill transport form 26s 814ms

And Click "save-transport" save button 716ms

And Click cancel button in transport form 077ms

And Go to transport details "TRANSPORT_ORDER" 4s 336ms

Then Check are transport values equals 2s 243ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

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 168ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 242ms

And Create gray windows "CREATE_GRAY_WINDOW_MWG" on "PRZESYŁKI DROBNICOWE" in "Magazyn Wyrobów Gotowych" as "super-admin-keeeper" 266ms

And If user is login then logout 114ms

Then Login as "dka1-supplier" 2s 580ms

And Click button advice in transport table "LOAD" 205ms

And Check if moved to first possible start date in schedule 415ms

Hooks

After Hooks.deleteAllGrayWindowsAfterTest() 1m 34s 461ms

After Hooks.deleteTransportAfterTest() 206ms

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" 125ms

And Set "transport" inputs from JSON file "CREATE_LOAD_WITH_NEW_ADDRESS" "super-admin-piast" 004ms

When Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 315ms

Then Go to new transport "LOAD" 350ms

And Fill transport form 27s 436ms

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" 098ms

When Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 501ms

And Set "transport" inputs from JSON file "EDIT_TRANSPORT_ADDRESS" "super-admin-piast" 001ms

Then Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 142ms

And Go to transport details "LOAD" 4s 816ms

And Fill transport form 16s 056ms

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() 076ms

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 239ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 235ms

When Go to "TRANSPORT_TABLE" 146ms

And Show all transport types 1s 040ms

And Verify that transport has "0" files 038ms

Then Add file to transport by API 472ms

And Verify that transport has "1" files 556ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

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 081ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 220ms

When Go to "TRANSPORT_TABLE" 106ms

And Show all transport types 1s 039ms

And Verify that transport has "0" files 036ms

Then Add file to transport by API 242ms

And Verify that transport has "1" files 498ms

Hooks

After Hooks.deleteTransportAfterTest() 063ms

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 287ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 495ms

When Go to "TRANSPORT_TABLE" 128ms

And Show all transport types 1s 032ms

And Verify that transport has "0" files 038ms

Then Add file to transport by API 231ms

And Verify that transport has "1" files 265ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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 070ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 204ms

When Go to "TRANSPORT_TABLE" 126ms

And Show all transport types 1s 040ms

And Verify that transport has "0" files 040ms

Then Add file to transport by API 209ms

And Verify that transport has "1" files 914ms

Hooks

After Hooks.deleteTransportAfterTest() 048ms

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 073ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 200ms

And Delete transport 17s 724ms

When Go to "ARCHIVE_TAB" 265ms

And Show "DELIVERY" 073ms

And Verify that transport has "0" files 681ms

Then Add file to transport 148ms

And Verify that transport has "1" files 380ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

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 180ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 196ms

And Delete transport 17s 336ms

When Go to "ARCHIVE_TAB" 239ms

And Show "LOAD" 093ms

And Verify that transport has "0" files 1s 147ms

Then Add file to transport 156ms

And Verify that transport has "1" files 360ms

Hooks

After Hooks.deleteTransportAfterTest() 064ms

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 400ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 365ms

And Delete transport 17s 838ms

When Go to "ARCHIVE_TAB" 244ms

And Show "DELIVERY" 050ms

And Verify that transport has "0" files 1s 078ms

Then Add file to transport 151ms

And Verify that transport has "1" files 366ms

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 "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 137ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 206ms

And Delete transport 17s 558ms

When Go to "ARCHIVE_TAB" 215ms

And Show "CONTAINER" 085ms

And Verify that transport has "0" files 1s 052ms

Then Add file to transport 119ms

And Verify that transport has "1" files 4s 263ms

Hooks

After Hooks.deleteTransportAfterTest() 052ms

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" 093ms

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 121ms

And Set token of apiUsername "paa1-carrier@qa.qa-test" 099ms

And Accept transferred transport by Api 170ms

And Login as "paa1-carrier@qa.qa-test" 1s 061ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 15s 843ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

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 069ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 219ms

And Transfer transport to carrier by JSON file "super-admin-adama" "false" confirmation 108ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 807ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

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" 096ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 216ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 176ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 342ms

And Login as "paa1-carrier@qa.qa-test" 1s 161ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 16s 038ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

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 170ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 243ms

When Go to "TRANSPORT_TABLE" 136ms

And Show all transport "true" 079ms

Then Verify that transport has "1" CMR file 1s 196ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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 048ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 292ms

When Go to "TRANSPORT_TABLE" 104ms

And Show all transport "true" 060ms

Then Verify that transport has "2" CMR file 1s 170ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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 056ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 284ms

When Go to "TRANSPORT_TABLE" 132ms

And Show all transport "true" 063ms

Then Verify that "CMR" document can be downloaded 17s 434ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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 057ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 359ms

And Show all transport "true" 074ms

And Delete transport 17s 145ms

When Go to "ARCHIVE_TAB" 209ms

And Show "TRANSPORT_ORDER" 056ms

Then Verify that "CMR" document can be downloaded 16s 833ms

Hooks

After Hooks.deleteTransportAfterTest() 060ms

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 672ms

And Create default accepted mode of transportation by API with "pba1-carrier" 429ms

And If user is login then logout 075ms

And Login as "bausch-admin" and set token of apiUsername "super-admin-bausch" 1s 309ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 250ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 200ms

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-bausch" 010ms

And Click button advice in transport table "LOAD_PL" 1s 771ms

And Set advice window in schedule 2s 913ms

And Fill advice form 9s 307ms

And Click advice save button and wait for advice form to disappear 31s 241ms

And Find transport in table with status "advice-added" 3s 333ms

When Confirm statuses until reach "on-the-way" 13s 398ms

Then Verify that "delivery_document" document can be downloaded 16s 321ms

Hooks

After Hooks.deleteTransportAfterTest() 206ms

After Hooks.deleteModeOfTransportationAfterTest() 080ms

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 400ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 652ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 252ms

And Click pencil and move transport to next day in schedule 16s 958ms

Then Check if transport is in new location in schedule 2s 120ms

And Check if dates in transport form are correct 3s 461ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

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 196ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 318ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 260ms

And Click pencil and move transport to next day in schedule 16s 740ms

Then Check if transport is in new location in schedule 2s 129ms

And Check if dates in transport form are correct 3s 390ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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 089ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 391ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 255ms

And Click pencil and move transport to next day in schedule 20s 893ms

Then Check if transport is in new location in schedule 2s 130ms

And Check if dates in transport form are correct 3s 389ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

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 132ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 370ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 231ms

And Click pencil and move transport to next day in schedule 16s 297ms

Then Check if transport is in new location in schedule 2s 106ms

And Check if dates in transport form are correct 3s 331ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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 173ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 340ms

And Show all transport "false" 009ms

When Find transport pencil button in transports table 1s 251ms

And Click pencil and move transport to next day in schedule 16s 355ms

Then Check if transport is in new location in schedule 2s 122ms

And Check if dates in transport form are correct 3s 382ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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 138ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-alrec" 5s 418ms

And Show all transport "true" 088ms

When Find transport pencil button in transports table 1s 231ms

And Click pencil and move transport to next day in schedule 16s 507ms

Then Check if transport is in new location in schedule 2s 127ms

And Check if dates in transport form are correct 3s 455ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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 155ms

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" 002ms

When Show all transport types 1s 043ms

And Click button advice in transport table "DELIVERY" 132ms

And Set advice window in schedule 2s 580ms

And Fill advice form 8s 377ms

And Click advice save button and wait for advice form to disappear 30s 714ms

And Go to "TRANSPORT_TABLE" 246ms

And Find transport pencil button in transports table 1s 237ms

And Click pencil and move transport to next day in schedule 17s 536ms

Then Check if transport is in new location in schedule 2s 129ms

And Check if dates in transport form are correct 3s 467ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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 422ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 373ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 268ms

And Click pencil and move transport to next day in schedule 16s 402ms

And Move advice window "3" 1s 319ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 118ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 330ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 261ms

And Click pencil and move transport to next day in schedule 16s 719ms

And Move advice window "3" 1s 388ms

Then Check if advice window is in new location 039ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport after editing by pencil button

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 017ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 325ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 225ms

And Click pencil and move transport to next day in schedule 16s 799ms

And Move advice window "3" 1s 438ms

Then Check if advice window is in new location 028ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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 181ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 450ms

And Show all transport "false" 007ms

When Find transport pencil button in transports table 1s 230ms

And Click pencil and move transport to next day in schedule 16s 358ms

And Move advice window "3" 1s 326ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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 045ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 351ms

And Show all transport "false" 008ms

When Find transport pencil button in transports table 1s 203ms

And Click pencil and move transport to next day in schedule 16s 268ms

And Move advice window "3" 1s 303ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

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 157ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 297ms

And Show all transport "true" 088ms

When Find transport pencil button in transports table 1s 238ms

And Click pencil and move transport to next day in schedule 16s 423ms

And Move advice window "3" 1s 370ms

Then Check if advice window is in new location 023ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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 414ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 726ms

And Go to transport details "DELIVERY" 5s 644ms

When Open section: "discrepancy-report-panel" 1s 068ms

Then Verify that no discrepancies found label is visible in discrepancy report section 070ms

And Select "NIE" in the "insp.-accord.-with-ins." 2s 444ms

And Verify that discrepancy report custom fields are visible in discrepancy report section 116ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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 344ms

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 665ms

And Fill transport form 36s 053ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 119ms

When Go to transport details "DELIVERY" 4s 427ms

Then Select "NIE" in the "insp.-accord.-with-ins." 2s 415ms

And Click "save-transport" save button 728ms

And Wait "2" seconds 2s

And Verify that discrepancy report section is open 033ms

And Verify that discrepancy report section contains validation errors 021ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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 522ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 432ms

When Go to transport details "DELIVERY" 4s 775ms

Then Verify that discrepancy report section is available 042ms

And Open section: "discrepancy-report-panel" 1s 060ms

And Verify that generate new discrepancy report button is visible 045ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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 379ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 306ms

When Go to transport details "OWN_COLLECTION" 4s 653ms

Then Verify that discrepancy report section is available 033ms

And Open section: "discrepancy-report-panel" 1s 070ms

And Verify that generate new discrepancy report button is visible 034ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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 370ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 310ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 516ms

Then Verify that discrepancy report section is available 036ms

And Open section: "discrepancy-report-panel" 1s 056ms

And Verify that generate new discrepancy report button is visible 033ms

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 343ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 335ms

When Go to transport details "EXPORT" 5s 619ms

Then Verify that discrepancy report section is available 050ms

And Open section: "discrepancy-report-panel" 1s 048ms

And Verify that generate new discrepancy report button is visible 035ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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 214ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 195ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 466ms

Then Verify that discrepancy report section is available 041ms

And Open section: "discrepancy-report-panel" 1s 059ms

And Verify that generate new discrepancy report button is visible 030ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 032ms

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 342ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 294ms

When Go to transport details "CISTERN_DELIVERY" 4s 506ms

Then Verify that discrepancy report section is not available 15s 030ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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 482ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 1s 269ms

When Go to transport details "CISTERN_COLLECTION" 4s 445ms

Then Verify that discrepancy report section is not available 15s 027ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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 403ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 202ms

When Go to transport details "WEIGHING" 4s 373ms

Then Verify that discrepancy report section is not available 15s 041ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

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 483ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 379ms

When Go to "TRANSPORT_TABLE" 109ms

And Go to transport details "DELIVERY" 4s 731ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 525ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 330ms

And Open section: "discrepancy-report-panel" 1s 070ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 003ms

And Fill transport form 35s 979ms

And Fill discrepancy report section without closing the form 19s 615ms

And Generate discrepancy report 17s 255ms

And Download discrepancy report 164ms

Then Verify that discrepancy report file has correct values 15s 153ms

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:76)

Hooks

After Hooks.deleteTransportAfterTest() 150ms

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 488ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 465ms

When Go to "TRANSPORT_TABLE" 112ms

And Go to transport details "DELIVERY" 4s 745ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 002ms

And Fill transport form 35s 989ms

And Open section: "discrepancy-report-panel" 1s 077ms

And Fill discrepancy report section without closing the form 19s 591ms

And Generate discrepancy report 18s 820ms

And Download discrepancy report 165ms

And Verify that discrepancy report file has correct values 15s 175ms

Error message

java.nio.file.NoSuchFileException: /home/teamcity/Downloads/41_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() 153ms

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" 092ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 048ms

And Get "LOAD" settings from "piast" 041ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "false" 079ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-piast" 1s 256ms

And Login as "piast-admin" 1s 791ms

And Go to "TRANSPORT_TABLE" 215ms

When Go to transport details "LOAD" 4s 729ms

And Add step "unload" 118ms

And Change filled value in transport details "company-step-2" "autocomplete" "DPA2" "0" 6s 530ms

And Change filled value in transport details "recipient-step-2" "autocomplete" "Testowy" "0" 6s 512ms

Then Click "save-transport-and-close" save button and wait for form to disappear 15s 617ms

And Go to transport details "LOAD" 4s 562ms

And Verify that transport has "3" steps 022ms

Hooks

After Hooks.rollbackTransportTypeSettings() 071ms

After Hooks.rollbackAddedActionAuthorities() 056ms

After Hooks.deleteTransportAfterTest() 092ms

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 115ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 284ms

When Go to "TRANSPORT_TABLE" 139ms

And Go to transport details "SMALLS_IMPORT" 17s 128ms

Then Verify that user can't edit time range for load and unload 15s 025ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

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" 091ms

And Create transport "CREATE_DELIVERY_TWO_LOADS" by JSON file as "super-admin-neuca" 1s 623ms

And Login as "neuca-admin" 856ms

And Go to "TRANSPORT_TABLE" 190ms

And Show all transport types 15s 061ms

When Go to transport details "DELIVERY" 32s 576ms

Then Check if sum of number of pallets in transport form in "load" steps is correct 069ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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" 093ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 15s 383ms

And Login as "hochland-admin" 1s 499ms

And Go to "TRANSPORT_TABLE" 124ms

And Show all transport types 1s 048ms

When Go to transport details "EXPORT" 4s 515ms

Then Check if sum of number of pallets in transport form in "unload" steps is correct 867ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

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" 100ms

And Get "DELIVERY" settings from "neuca" 057ms

And Set transportType settings with values: "quantitySumCheckValue", "33" 127ms

And Login as "neuca-admin" 943ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 15s 396ms

When Go to "TRANSPORT_TABLE" 258ms

And Go to transport details "DELIVERY" 32s 461ms

And Set number of pallets in "load" step in transport - "32" 149ms

And Check if number of pallets check message is not visible in transport form 15s 061ms

And Set number of pallets in "load" step in transport - "34" 139ms

Then Check if number of pallets check message is visible in transport form 046ms

Hooks

After Hooks.rollbackTransportTypeSettings() 105ms

After Hooks.deleteTransportAfterTest() 101ms

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" 095ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 097ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 051ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 070ms

And Login as "farmacol-admin" 6s 223ms

And Go to new transport "EXTERNAL_DELIVERY" 283ms

And Add step "unload" 096ms

And Click "save-transport-and-close" save button 686ms

Then Verify that "time-range-from-date-2" has validation error 1s 037ms

Then Verify that "time-range-to-date-2" has validation error 1s 030ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 342ms

And Click "save-transport-and-close" save button 710ms

And Verify that "time-range-from-date-2" has no validation error 019ms

And Verify that "time-range-to-date-2" has no validation error 020ms

Hooks

After Hooks.rollbackTransportTypeSettings() 071ms

After Hooks.rollbackAddedActionAuthorities() 075ms

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" 092ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_LOAD_STEP_FROM_UNLOAD" "ACTIVE" 056ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 412ms

When Login as "piast-admin" 1s 963ms

And Go to transport details "LOAD" 4s 796ms

And Get inputs from database "PIAST_LOAD_ADD_UNLOAD_STEP" "super-admin-piast" 002ms

And Add step "unload" 127ms

And Fill step data 15s 069ms

And Get inputs from database "PIAST_LOAD_ADD_LOAD_STEP" "super-admin-piast" 002ms

And Add step "load" 131ms

And Fill step data 5s 485ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 625ms

Then Go to transport details "LOAD" 4s 563ms

And Check if "unload" step is added as "3" step in transport form 039ms

And Check if "load" step is added as "4" step in transport form 039ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 064ms

After Hooks.deleteTransportAfterTest() 067ms

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" 091ms

And Add action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_LOAD_STEPS" "UNLIMITED" 056ms

And Remove action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_UNLOAD_STEPS" "UNLIMITED" 007ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 246ms

When Login as "super-admin-skz" 2s 192ms

And Go to transport details "SMALLS_EXPORT" 4s 450ms

And Check if step is draggable "LOAD" 028ms

And Check if step is not draggable "UNLOAD" 021ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 2s 541ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

After Hooks.deleteTransportAfterTest() 071ms

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" 004ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 095ms

When Go to new transport "SMALLS_IMPORT" 375ms

And Fill transport form 19s 865ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 613ms

And Show all transport "false" 006ms

And Go to transport details "SMALLS_IMPORT" 4s 497ms

And Click create similar button 15s 194ms

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 623ms

And Open similar transport details 262ms

Then Check are transport values equals 2s 118ms

Hooks

After Hooks.deleteSimilarTransportAfterTest() 067ms

After Hooks.deleteTransportAfterTest() 069ms

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" 005ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 887ms

When Go to new transport "TRANSPORT_ORDER" 360ms

And Fill transport form 23s 925ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 154ms

And Show all transport "true" 092ms

And Go to transport details "TRANSPORT_ORDER" 4s 419ms

And Click create similar button 15s 196ms

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 608ms

And Open similar transport details 281ms

Then Check are transport values equals 2s 218ms

Hooks

After Hooks.deleteSimilarTransportAfterTest() 152ms

After Hooks.deleteTransportAfterTest() 067ms

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" 005ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 122ms

When Go to new transport "TRANSPORT" 365ms

And Fill transport form 26s 849ms

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 details "TRANSPORT" 4s 457ms

And Click create similar button 15s 196ms

And Fill "transport" form "CREATE_SIMILAR_TRANSPORT" by "super-admin-adama" 1s 336ms

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.9iALdo}, 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: 866ed84e0ec4ca228401960068e7b9da
	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.deleteSimilarTransportAfterTest() 000ms

After Hooks.deleteTransportAfterTest() 088ms

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" 005ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 6s 509ms

When Go to new transport "DELIVERY" 15s 269ms

And Fill transport form 35s 908ms

And Click "save-transport" save button and wait for form to disappear 15s 770ms

And Set advice window in schedule 2s 166ms

And Check is transport created in schedule and set transport id 1s 064ms

And Go to "TRANSPORT_TABLE" 188ms

And Go to transport details "DELIVERY" 32s 425ms

And Click create similar button 15s 150ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 9s 548ms

And Click "save-transport" save button and wait for form to disappear 15s 639ms

And Set advice window in schedule in "2" days 4s 232ms

And Go to "TRANSPORT_TABLE" 226ms

And Open similar transport details 4s 620ms

Then Check are transport values equals 23s 478ms

Hooks

After Hooks.deleteSimilarTransportAfterTest() 268ms

After Hooks.deleteTransportAfterTest() 114ms

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" 005ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 187ms

When Go to new transport "DELIVERY" 315ms

And Fill transport form 15s 515ms

And Click "save-transport" save button and wait for form to disappear 15s 739ms

And Set advice window in schedule 2s 172ms

And Check is transport created in schedule and set transport id 672ms

And Go to "TRANSPORT_TABLE" 257ms

And Go to transport details "DELIVERY" 4s 336ms

And Click create similar button 15s 133ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "super-admin-adama" 10s 917ms

And Click "save-transport" save button and wait for form to disappear 15s 623ms

And Set advice window in schedule in "2" days 4s 238ms

And Go to "TRANSPORT_TABLE" 173ms

And Open similar transport details 34s 888ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for visibility of element located by By.xpath: //button[@type='submit' and @data-field-name='save-transport-and-close'] (tried for 30 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:160)
	at CucumberTests.Transport.TransportFormTest.openSimilarTransportDetails(TransportFormTest.java:90)
	at ✽.Open similar transport details(file:Features/Atom/Transport/TransportForm/TransportForm.feature:39)
Caused by: org.openqa.selenium.NoSuchElementException: Cannot locate an element using By.xpath: //button[@type='submit' and @data-field-name='save-transport-and-close']
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:160)
	at CucumberTests.Transport.TransportFormTest.openSimilarTransportDetails(TransportFormTest.java:90)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.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)

Then Check are transport values equals 000ms

Hooks

After Hooks.deleteSimilarTransportAfterTest() 000ms

After Hooks.deleteTransportAfterTest() 156ms

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 078ms

When Go to new transport "DELIVERY" 15s 272ms

And Fill transport form 35s 877ms

And Click "save-transport" save button and wait for form to disappear 15s 775ms

And Set advice window in schedule 2s 184ms

And Check is transport created in schedule and set transport id 829ms

And Go to "TRANSPORT_TABLE" 267ms

And Go to transport details "DELIVERY" 32s 434ms

And Click create similar button 15s 167ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 9s 552ms

And Click "save-transport" save button and wait for form to disappear 15s 735ms

And Set advice window in schedule in "2" days 4s 210ms

And Go to "TRANSPORT_TABLE" 206ms

And Open similar transport details 960ms

Then Check is field "CARRIER" of type "autocomplete" equals "Przewoźnik Neuca Automat 1" 015ms

Hooks

After Hooks.deleteSimilarTransportAfterTest() 128ms

After Hooks.deleteTransportAfterTest() 085ms

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 206ms

When Go to new transport "SMALLS_IMPORT" 379ms

And Fill transport form 33s 005ms

And Click "save-transport-and-close" save button and wait for form to disappear 682ms

And Go to transport details "SMALLS_IMPORT" 4s 440ms

And Go to transport print details form 3s 110ms

Then Check are transport values equals 8s 361ms

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 256ms

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 252ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 177ms

And Go to transport details "SMALLS_IMPORT" 4s 487ms

Then Verify that the transport can be edited 1s 314ms

And Close transport details 15s 103ms

And If user is login then logout 090ms

And Login as "pskza1-carrier@qa.qa-test" 1s 285ms

And Go to transport details "SMALLS_IMPORT" 4s 432ms

And Verify that the transport cannot be edited 46s 298ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is not possible to edit transport when auction is active

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 266ms

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 256ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 144ms

And Go to transport details "SMALLS_EXPORT" 4s 457ms

Then Verify that the transport can be edited 1s 298ms

And Close transport details 15s 145ms

And If user is login then logout 127ms

And Login as "pskza1-carrier@qa.qa-test" 1s 315ms

And Go to transport details "SMALLS_EXPORT" 4s 468ms

And Verify that the transport cannot be edited 46s 294ms

Hooks

After Hooks.deleteTransportAfterTest() 134ms

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 151ms

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 236ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 116ms

And Go to transport details "SMALLS_IMPORT" 4s 459ms

Then Verify that the hidden data in transport are not visible 1s 052ms

And Close transport details 15s 135ms

And If user is login then logout 113ms

And Login as "swisskrono-admin" 1s 391ms

And Go to transport details "SMALLS_IMPORT" 4s 520ms

And Verify that the hidden data in transport are visible 1s 220ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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" 974ms

And Get inputs from database "HIDDEN_DATA_SMALLS_EXPORT" "super-admin-skz" 002ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 221ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 102ms

And Go to transport details "SMALLS_EXPORT" 4s 441ms

Then Verify that the hidden data in transport are not visible 1s 040ms

And Close transport details 15s 130ms

And If user is login then logout 121ms

And Login as "swisskrono-admin" 5s 296ms

And Go to transport details "SMALLS_EXPORT" 4s 519ms

And Verify that the hidden data in transport are visible 1s 247ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is possible use 'save' and 'save transport and close' buttons after editing transport and fill discrepancy report panel

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 538ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 423ms

When Go to transport details "DELIVERY" 4s 747ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 324ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 533ms

And Change filled value in transport details "insp.-accord.-with-ins." "select" "NIE" "1" 3s 513ms

And Fill discrepancy report section without closing the form 19s 542ms

And Click "save-transport" save button 1s 263ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 600ms

And Check if transport details form is disappeared 15s 061ms

Hooks

After Hooks.deleteTransportAfterTest() 146ms

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" 093ms

And Add action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 109ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 279ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 405ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 7s 565ms

When Go to "TRANSPORT_TABLE" 212ms

And Go to transport details "DELIVERY" 4s 691ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 346ms

Then Verify that "transport-description" in transport has value "opis" 019ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 053ms

After Hooks.rollbackWarehousesAccess() 172ms

After Hooks.deleteTransportAfterTest() 089ms

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" 093ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 318ms

And Remove action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 067ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 156ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 2s 501ms

When Go to "TRANSPORT_TABLE" 200ms

And Go to transport details "DELIVERY" 4s 658ms

Then Verify that "transport-description" in transport form is disabled 030ms

Hooks

After Hooks.rollbackRemovedActionAuthorities() 062ms

After Hooks.rollbackWarehousesAccess() 164ms

After Hooks.deleteTransportAfterTest() 130ms

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" 092ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 062ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 378ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 760ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 191ms

And Go to transport details "DELIVERY" 4s 759ms

Then Verify that "CARRIER" in transport form is visible 034ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 050ms

After Hooks.deleteTransportAfterTest() 114ms

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" 091ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 057ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 249ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 5s 993ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 167ms

And Go to transport details "TRANSPORT" 4s 477ms

Then Verify that "CARRIER" in transport form is visible 042ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 053ms

After Hooks.deleteTransportAfterTest() 080ms

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" 099ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 053ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 260ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 149ms

And Show all transport "true" 096ms

When Go to "TRANSPORT_TABLE" 112ms

And Go to transport details "TRANSPORT_ORDER" 4s 452ms

Then Verify that "CARRIER" in transport form is visible 035ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 056ms

After Hooks.deleteTransportAfterTest() 088ms

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" 094ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 053ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 374ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 599ms

And Show all transport "false" 004ms

When Go to "TRANSPORT_TABLE" 179ms

And Go to transport details "DELIVERY" 4s 716ms

Then Verify that "CARRIER" in transport form is not visible 15s 067ms

Hooks

After Hooks.rollbackRemovedActionAuthorities() 059ms

After Hooks.deleteTransportAfterTest() 124ms

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" 095ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 055ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 207ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 125ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 209ms

And Go to transport details "TRANSPORT" 4s 480ms

Then Verify that "CARRIER" in transport form is not visible 15s 054ms

Hooks

After Hooks.rollbackRemovedActionAuthorities() 064ms

After Hooks.deleteTransportAfterTest() 075ms

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" 093ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 052ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 238ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 6s 123ms

And Show all transport "true" 072ms

When Go to "TRANSPORT_TABLE" 100ms

And Go to transport details "TRANSPORT_ORDER" 4s 462ms

Then Verify that "CARRIER" in transport form is not visible 15s 009ms

Hooks

After Hooks.rollbackRemovedActionAuthorities() 059ms

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-hochland" 093ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 061ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 058ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 480ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 647ms

And Show all transport "false" 004ms

When Go to "TRANSPORT_TABLE" 209ms

And Go to transport details "DELIVERY" 4s 714ms

Then Verify that "CARRIER" in transport form is not disabled 035ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 111ms

After Hooks.deleteTransportAfterTest() 111ms

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" 097ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 059ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 065ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 210ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 995ms

And Show all transport "false" 003ms

When Go to "TRANSPORT_TABLE" 163ms

And Go to transport details "TRANSPORT" 4s 498ms

Then Verify that "CARRIER" in transport form is not disabled 021ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 078ms

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" 099ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 066ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 042ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 213ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 10s 585ms

And Show all transport "true" 077ms

When Go to "TRANSPORT_TABLE" 129ms

And Go to transport details "TRANSPORT_ORDER" 4s 506ms

Then Verify that "CARRIER" in transport form is not disabled 030ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 082ms

After Hooks.deleteTransportAfterTest() 061ms

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" 086ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 056ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 042ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 373ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 463ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 189ms

And Go to transport details "DELIVERY" 4s 520ms

Then Verify that "CARRIER" in transport form is disabled 027ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 1s 893ms

After Hooks.rollbackRemovedActionAuthorities() 066ms

After Hooks.deleteTransportAfterTest() 123ms

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" 086ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 051ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 006ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 193ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 024ms

And Show all transport "false" 004ms

When Go to "TRANSPORT_TABLE" 179ms

And Go to transport details "TRANSPORT" 4s 440ms

Then Verify that "CARRIER" in transport form is disabled 028ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 061ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

After Hooks.deleteTransportAfterTest() 104ms

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" 091ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 062ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 006ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 227ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 867ms

And Show all transport "true" 091ms

When Go to "TRANSPORT_TABLE" 096ms

And Go to transport details "TRANSPORT_ORDER" 4s 428ms

Then Verify that "CARRIER" in transport form is disabled 027ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 052ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

After Hooks.deleteTransportAfterTest() 073ms

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" 089ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 310ms

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" 052ms

And Add action authority with: "adama" "adama-admin" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 065ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 813ms

When Find transport in table with status "planned" 3s 362ms

And Confirm statuses until reach "process-ended" 21s 554ms

And Wait "90" seconds 1m 30s

And Go to "ARCHIVE_TAB" 285ms

And Show "DELIVERY" 075ms

And Go to transport details "DELIVERY" 32s 405ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 345ms

And Click "save-transport-and-close" save button and wait for form to disappear 19s 852ms

And Wait "7" seconds 7s

And Go to transport details "DELIVERY" 32s 348ms

Then Verify that "transport-description" in transport has value "opis" 031ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 113ms

After Hooks.rollbackRemovedActionAuthorities() 128ms

After Hooks.deleteTransportAfterTest() 117ms

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 664ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 582ms

When Go to transport details "DELIVERY" 4s 435ms

And Fill transport form 32s 693ms

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for visibility of element located by By.xpath: //div[@aria-expanded='true'] (tried for 30 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:160)
	at CucumberTests.Transport.Transport.selectValue(Transport.java:226)
	at CucumberTests.Transport.Transport.fillSelectInput(Transport.java:214)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:166)
	at CucumberTests.Transport.CreateTransport.fillTransportForm(CreateTransport.java:170)
	at ✽.Fill transport form(file:Features/Atom/Transport/TransportForm/TransportForm.feature:259)
Caused by: org.openqa.selenium.NoSuchElementException: Cannot locate an element using By.xpath: //div[@aria-expanded='true']
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:160)
	at CucumberTests.Transport.Transport.selectValue(Transport.java:226)
	at CucumberTests.Transport.Transport.fillSelectInput(Transport.java:214)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:166)
	at CucumberTests.Transport.CreateTransport.fillTransportForm(CreateTransport.java:170)
	at sun.reflect.GeneratedMethodAccessor269.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 Change filled value in transport details "driver-name" "text" "XXX ZZZ" "0" 000ms

And Click "save-transport-and-close" save button and wait for form to disappear 000ms

And Go to new transport "DELIVERY" 000ms

Then Verify that driver "XXX ZZZ" is in list 000ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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 308ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 242ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 250ms

And If user is login then logout 106ms

And Login as "pskza1-carrier@qa.qa-test" 4s 315ms

Then Verify that the transport has been transferred 1s 114ms

And Accept or reject "accept" transferred transport 15s 859ms

And Go to transport details "SMALLS_IMPORT" 4s 551ms

And Verify that "transaction-price" in transport form is visible 034ms

And Verify that transaction price field has correct value 020ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_IMPORT" 023ms

Hooks

After Hooks.deleteTransportAfterTest() 072ms

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 246ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 342ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 187ms

And If user is login then logout 111ms

And Login as "pskza1-carrier@qa.qa-test" 1s 190ms

Then Verify that the transport has been transferred 1s 135ms

And Accept or reject "accept" transferred transport 15s 784ms

And Go to transport details "SMALLS_EXPORT" 4s 520ms

And Verify that "transaction-price" in transport form is visible 037ms

And Verify that transaction price field has correct value 019ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_EXPORT" 022ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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 833ms

And Create transport "CREATE_DELIVERY_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 646ms

And Show all transport types 1s 045ms

Then Check if transport number is visible "DELIVERY" 15s 067ms

And Check if transport details is not visible 15s 008ms

Hooks

After Hooks.deleteTransportAfterTest() 134ms

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" 7s 015ms

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 129ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 398ms

When Click on transport row 069ms

Then Verify if transport row is selected 033ms

Hooks

After Hooks.deleteTransportAfterTest() 132ms

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" 2s 040ms

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 157ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 226ms

When Click on transport row 1s 874ms

Then Verify if transport row is selected 022ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 874ms

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 097ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 296ms

When Click on transport row 067ms

Then Verify if transport row is selected 024ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

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 877ms

And Show all transport "false" 008ms

And Go to "TRANSPORT_TABLE" 114ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 280ms

When Click on transport row 047ms

Then Verify if transport row is selected 025ms

Hooks

After Hooks.deleteTransportAfterTest() 216ms

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 968ms

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 104ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 305ms

When Click on transport row 052ms

Then Verify if transport row is selected 023ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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 800ms

And Show all transport "true" 077ms

And Go to "TRANSPORT_TABLE" 113ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 279ms

When Click on transport row 066ms

Then Verify if transport row is selected 022ms

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 "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 3s 013ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 511ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 107ms

When Accept or reject "accept" transferred transport 17s 383ms

Then Verify that transport is accept or reject "accept" 022ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

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 158ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 250ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 099ms

When Accept or reject "reject" transferred transport 17s 651ms

Then Verify that transport is accept or reject "reject" 15s 040ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 575ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 228ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 070ms

When Accept or reject "accept" transferred transport 18s 055ms

Then Verify that transport is accept or reject "accept" 018ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

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 097ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 264ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 084ms

When Accept or reject "reject" transferred transport 17s 410ms

Then Verify that transport is accept or reject "reject" 15s 065ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

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" 5s 014ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 376ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 100ms

When Accept or reject "accept" transferred transport 18s 143ms

Then Verify that transport is accept or reject "accept" 025ms

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 160ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 249ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 085ms

When Accept or reject "reject" transferred transport 18s 028ms

Then Verify that transport is accept or reject "reject" 15s 059ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - with confirmation checkbox

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 130ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 292ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 173ms

And If user is login then logout 117ms

And Login as "paa1-carrier@qa.qa-test" 1s 187ms

Then Verify that the transport has been transferred with "true" 1s 204ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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 010ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 296ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 19s 294ms

And If user is login then logout 108ms

And Login as "paa1-carrier@qa.qa-test" 1s 147ms

Then Verify that the transport has been transferred with "false" 1s 089ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - without confirmation checkbox

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 7s 318ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 248ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 171ms

And If user is login then logout 111ms

And Login as "pskza1-carrier@qa.qa-test" 1s 481ms

Then Verify that the transport has been transferred 1s 134ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

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 165ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 226ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 279ms

And If user is login then logout 100ms

And Login as "pskza1-carrier@qa.qa-test" 1s 148ms

Then Verify that the transport has been transferred 1s 118ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

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 071ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 229ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 167ms

And Go to auction offer 1s 214ms

When Offer "1000" 143ms

And Verify that offer with "1000" has been added to auction 3s 039ms

And If user is login then logout 087ms

And Login as "swisskrono-admin" 1s 260ms

Then Go to auction details 1s 181ms

And Pass transport to carrier from auction details 4s 281ms

And If user is login then logout 553ms

And Login as "pskza1-carrier@qa.qa-test" 1s 280ms

And Verify that the transport has been transferred 1s 141ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to pass transport to carrier when auction is finished

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 067ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 221ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 102ms

And Go to auction offer 1s 207ms

When Offer "1000" 138ms

And Verify that offer with "1000" has been added to auction 3s 042ms

And Wait till auction end 1m 54s 016ms

And If user is login then logout 085ms

Then Login as "swisskrono-admin" 1s 381ms

And Go to auction details 1s 228ms

And Pass transport to carrier from auction details 1s 273ms

And If user is login then logout 451ms

And Login as "pskza1-carrier@qa.qa-test" 1s 243ms

And Verify that the transport has been transferred 1s 125ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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 157ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 213ms

And Go to "TRANSPORT_TABLE" 121ms

When Open transport transfer modal 1s 241ms

Then Verify that all enabled companies from "swisskrono" are shown in select 130ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

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 462ms

And Login as "adama-admin" 1s 008ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 200ms

And Go to "TRANSPORT_TABLE" 129ms

When Open transport transfer modal 1s 259ms

Then Verify that "Przewoźnik Adama Automat 1" is blocked in select 093ms

Hooks

After Hooks.deleteTransportAfterTest() 066ms

After Hooks.rollbackRejectedSections() 103ms

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 010ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 222ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" with "120" seconds to accept transport 19s 219ms

And If user is login then logout 117ms

When Login as "paa1-carrier@qa.qa-test" 7s 174ms

And Verify that the transport has been transferred with "true" 1s 193ms

And Wait "120" seconds 2m

Then Verify if transport is not visible to carrier after expiring time to accept transport 15s 044ms

Hooks

After Hooks.deleteTransportAfterTest() 234ms

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 023ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 746ms

When Go to "TRANSPORT_TABLE" 146ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 415ms

Then Check if new assortment group is disabled in transport form 029ms

Hooks

After Hooks.deleteTransportAfterTest() 161ms

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 016ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 495ms

And Get inputs from database "CREATE_ADVICE_CONTAINER" "super-admin-adama" 001ms

When Show all transport types 1s 037ms

And Click button advice in transport table "CONTAINER" 129ms

And Set advice window in schedule 2s 358ms

And Click button cancel in advice form 15s 365ms

And Set advice window in schedule 2s 157ms

And Click button cancel in advice form 15s 275ms

And Set advice window in schedule 2s 131ms

And Fill advice form 15s 825ms

And Click advice save button and wait for advice form to disappear 31s 695ms

And Go to "TRANSPORT_TABLE" 205ms

And Go to transport details "CONTAINER" 4s 425ms

Then Check are advice values equals 2s 397ms

Hooks

After Hooks.deleteTransportAfterTest() 138ms

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 164ms

And Get inputs from database "CREATE_TRANSPOSRT_ORDER" "super-admin-adama" 001ms

When Go to new transport "TRANSPORT" 442ms

And Fill transport form 26s 814ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 648ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 23s 325ms

And Check is transport "TRANSPORT" created in transport table and set transport id 1s 123ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 159ms

And Accept or reject "reject" transferred transport 15s 268ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 093ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 305ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 137ms

And Accept or reject "accept" transferred transport 16s 103ms

Then Verify that transport is accept or reject "accept" 022ms

Hooks

After Hooks.deleteTransportAfterTest() 144ms

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 085ms

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 225ms

When Show all transport types 1s 047ms

And Click button advice in transport table "DELIVERY" 134ms

And Set advice window in schedule 2s 691ms

And Click button cancel in advice form 15s 409ms

And Go to "TRANSPORT_TABLE" 216ms

When Go to transport details "DELIVERY" 4s 381ms

And Fill transport form 1m 4s 205ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 150ms

And Go to transport details "DELIVERY" 4s 523ms

Then Check are transport values equals 24s 834ms

Hooks

After Hooks.deleteTransportAfterTest() 137ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@deleteTransportAfterTest	3643	37	92	0	0	3772	368	37	405	5h 37m 17s 798ms	Failed

Tag Report