Cucumber-JVM Reports - Tag: @deleteTransportAfterTest

Project	Number	Date
ApolloFullRunnerReport	develop.367	03 kwi 2021, 05:45

	Steps	Scenarios	Features
@deleteTransportAfterTest	3705	21	46	0	0	3772	384	21	405	5h 42m 12s 717ms	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 542ms

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

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

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

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

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

And Fill advice form 16s 444ms

And Click advice save button to check error message 079ms

Then Check if possible advice alert is displayed 017ms

Hooks

After Hooks.deleteTransportAfterTest() 375ms

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

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

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

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

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

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

And Fill advice form 8s 392ms

And Click advice save button to check error message 080ms

Then Check if possible advice alert is displayed 017ms

Hooks

After Hooks.deleteTransportAfterTest() 151ms

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

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

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

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

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

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

And Fill advice form 8s 366ms

And Click advice save button to check error message 089ms

Then Check if possible advice alert is displayed 022ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

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

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

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

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

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

And Fill advice form 13s 173ms

And Click advice save button to check error message 082ms

Then Check if possible advice alert is displayed 019ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

And Fill advice form 13s 135ms

And Click advice save button to check error message 074ms

Then Check if possible advice alert is displayed 023ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

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

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

And Show all transport types 1s 046ms

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

And Go to "TRANSPORT_TABLE" 157ms

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

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

And Fill transport form 4s 696ms

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

And Expand advice panel 108ms

And Edit advice in transport details 12s 404ms

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

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

And Expand advice panel 105ms

Then Check are advice values equals after edition 204ms

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

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

And Show all transport types 1s 049ms

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

And Go to "TRANSPORT_TABLE" 209ms

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

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

And Fill transport form 1m 1s 973ms

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

And Expand advice panel 104ms

And Edit advice in transport details 6s 579ms

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

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

And Expand advice panel 093ms

Then Check are advice values equals after edition 085ms

Hooks

After Hooks.deleteTransportAfterTest() 171ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport types 1s 050ms

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

And Go to "TRANSPORT_TABLE" 189ms

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

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

And Fill transport form 56s 945ms

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

And Expand advice panel 126ms

And Edit advice in transport details 6s 604ms

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

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

And Expand advice panel 091ms

Then Check are advice values equals after edition 085ms

Hooks

After Hooks.deleteTransportAfterTest() 174ms

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

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

And Show all transport types 1s 039ms

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

And Go to "TRANSPORT_TABLE" 167ms

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

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

And Fill transport form 24s 610ms

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

And Expand advice panel 102ms

And Edit advice in transport details 18s 462ms

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

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

And Expand advice panel 096ms

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

Hooks

After Hooks.deleteTransportAfterTest() 143ms

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

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

And Show all transport types 1s 044ms

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

And Go to "TRANSPORT_TABLE" 158ms

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

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

And Fill transport form 24s 579ms

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

And Expand advice panel 111ms

And Edit advice in transport details 18s 507ms

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

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

And Expand advice panel 090ms

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

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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

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

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

When Show all transport types 1s 044ms

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

And Set advice window in schedule 2s 370ms

And Fill advice form 12s 313ms

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

And Go to "TRANSPORT_TABLE" 178ms

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

Then Check are advice values equals 303ms

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 "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 464ms

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

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

When Show all transport types 1s 040ms

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

And Set advice window in schedule 6s 424ms

And Fill advice form 11s 686ms

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

And Go to "TRANSPORT_TABLE" 178ms

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

Then Check are advice values equals 2s 272ms

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

Steps

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

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

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

When Show all transport types 1s 039ms

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

And Set advice window in schedule 2s 550ms

And Fill advice form 8s 325ms

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

And Go to "TRANSPORT_TABLE" 219ms

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

Then Check are advice values equals 191ms

Hooks

After Hooks.deleteTransportAfterTest() 152ms

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

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

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

When Show all transport types 1s 036ms

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

And Set advice window in schedule 2s 576ms

And Fill advice form 8s 262ms

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

And Go to "TRANSPORT_TABLE" 179ms

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

Then Check are advice values equals 193ms

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

Steps

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

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

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

When Show all transport types 1s 047ms

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

And Set advice window in schedule 2s 399ms

And Fill advice form 13s 069ms

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

And Go to "TRANSPORT_TABLE" 163ms

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

Then Check are advice values equals 2s 302ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

When Show all transport types 1s 040ms

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

And Set advice window in schedule 2s 385ms

And Fill advice form 13s 092ms

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

And Go to "TRANSPORT_TABLE" 173ms

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

Then Check are advice values equals 2s 277ms

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 after passing it on to the carrier

Steps

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

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

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

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

And Accept transferred transport by Api 595ms

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

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

When Show all transport types 1s 038ms

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

And Set advice window in schedule 2s 537ms

And Fill advice form 11s 779ms

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

And Go to "TRANSPORT_TABLE" 212ms

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

Then Check are advice values equals 2s 272ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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

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

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

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

And Accept transferred transport by Api 110ms

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

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

And Set advice window in schedule 2s 589ms

And Fill advice form 14s 369ms

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

And Go to "TRANSPORT_TABLE" 183ms

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

Then Check are advice values equals 2s 294ms

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

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

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

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

And Accept transferred transport by Api 102ms

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

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

When Show all transport types 1s 039ms

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

And Set advice window in schedule 2s 592ms

And Fill advice form 14s 520ms

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

And Go to "TRANSPORT_TABLE" 158ms

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

Then Check are advice values equals 2s 282ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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

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

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

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

And Accept transferred transport by Api 102ms

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

When Show all transport types 1s 039ms

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

And Set week view 1s 512ms

And Show yesterday 1s 062ms

Then Check if advice restriction blockade windows are visible 018ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

View Feature Advice transport

@deleteTransportAfterTest

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

Steps

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

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

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

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

And Accept transferred transport by Api 108ms

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

When Show all transport types 1s 030ms

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

And Set week view 2s 057ms

And Show yesterday 1s 111ms

Then Check if advice restriction blockade windows are visible 030ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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

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

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

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

And Accept transferred transport by Api 100ms

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

When Show all transport types 1s 039ms

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

And Set week view 2s 062ms

And Show yesterday 1s 149ms

Then Check if advice restriction blockade windows are visible 029ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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

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

And Show all transport "false" 026ms

And Click on time window date 1s 266ms

And Select view "DAYS_4" 2s 055ms

And Move advice window "3" 1s 315ms

Then Check if advice window is in new location 023ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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

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

And Show all transport "false" 010ms

And Click on time window date 15s 769ms

And Select view "DAYS_4" 2s 069ms

And Move advice window "3" 15s 062ms

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.cTgIHr}, 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: 1968d0bcafa471a25cdc53a4d1bd1dd3
*** 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() 093ms

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

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

And Show all transport "false" 014ms

And Click on time window date 15s 546ms

And Select view "DAYS_4" 2s 067ms

And Move advice window "3" 1s 378ms

Then Check if advice window is in new location 023ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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

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

And Show all transport "false" 018ms

And Click on time window date 1s 417ms

And Select view "DAYS_4" 2s 060ms

And Move advice window "3" 1s 343ms

Then Check if advice window is in new location 020ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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

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

And Show all transport "false" 012ms

And Click on time window date 1s 302ms

And Select view "DAYS_4" 2s 062ms

And Move advice window "3" 1s 300ms

Then Check if advice window is in new location 019ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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

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

And Show all transport "true" 067ms

And Click on time window date 1s 322ms

And Select view "DAYS_4" 2s 057ms

And Move advice window "3" 1s 329ms

Then Check if advice window is in new location 024ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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

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

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

When Show all transport types 1s 030ms

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

And Set advice window in schedule 2s 561ms

And Fill advice form 8s 292ms

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

And Go to "TRANSPORT_TABLE" 229ms

And Click on time window date 1s 390ms

And Select view "DAYS_4" 2s 051ms

And Move advice window "3" 1s 416ms

Then Check if advice window is in new location 024ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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

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

And Go to "TRANSPORT_TABLE" 113ms

And Show all transport types 1s 039ms

And Click on time window date 1s 310ms

And Scroll to time window "adviceWindow" 046ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 114ms

And Show all transport types 1s 036ms

And Click on time window date 1s 439ms

And Scroll to time window "adviceWindow" 032ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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

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

And Go to "TRANSPORT_TABLE" 125ms

And Show all transport types 1s 033ms

And Click on time window date 1s 310ms

And Scroll to time window "adviceWindow" 035ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 283ms

And Show all transport types 15s 044ms

And Click on time window date 15s 818ms

And Scroll to time window "adviceWindow" 028ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 177ms

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

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

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

When Show all transport types 1s 044ms

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

And Set advice window in schedule 2s 555ms

And Fill advice form 8s 281ms

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

And Go to "TRANSPORT_TABLE" 226ms

And Click on time window date 1s 405ms

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

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

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

And Go to "WAREHOUSE_TAB" 866ms

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

When Go to new transport "DELIVERY" 323ms

And Fill transport form 39s 291ms

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

And Click previous page button in browser 030ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

View Feature Advice transport

@deleteTransportAfterTest

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

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

And Go to "WAREHOUSE_TAB" 731ms

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

When Go to new transport "DELIVERY" 337ms

And Fill transport form 39s 352ms

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

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

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

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

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

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

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

When Show all transport types 1s 035ms

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

And Fill advice form 11s 495ms

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

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

And Open statuses popup 099ms

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

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Advice transport

@deleteTransportAfterTest

Scenario Outline Check if time window details preview displays correctly

Steps

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

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

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

And Login as "farmacol-admin" 3s 605ms

And Go to "WAREHOUSE_TAB" 668ms

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

And Set week view 2s 195ms

And Move cursor over time window element 385ms

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

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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

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

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

And Fill transport form 34s 217ms

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

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

And Set advice window in schedule 2s 150ms

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

Then Go to "OWN_COMPANY_TAB" 250ms

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

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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

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

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

And Fill transport form 16s 244ms

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

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

And Set advice window in schedule 2s 147ms

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

Then Go to "OWN_COMPANY_TAB" 268ms

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

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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

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

When Go to "TRANSPORT_TABLE" 110ms

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

And Show all transport types 1s 037ms

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

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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

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

When Go to "TRANSPORT_TABLE" 119ms

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

And Show all transport types 1s 045ms

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

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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

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

When Go to "TRANSPORT_TABLE" 107ms

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

And Show all transport types 1s 054ms

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

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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

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

When Go to "TRANSPORT_TABLE" 124ms

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

And Show all transport types 1s 051ms

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

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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

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

And Delete created transport by API 099ms

When Go to "ARCHIVE_TAB" 206ms

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

And Show "SMALLS_IMPORT" 085ms

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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

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

And Delete created transport by API 091ms

When Go to "ARCHIVE_TAB" 177ms

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

And Show "SMALLS_IMPORT" 080ms

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

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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

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

And Delete created transport by API 100ms

When Go to "ARCHIVE_TAB" 230ms

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

And Show "SMALLS_IMPORT" 084ms

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

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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

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

And Delete created transport by API 086ms

When Go to "ARCHIVE_TAB" 202ms

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

And Show "SMALLS_IMPORT" 072ms

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

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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

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

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

And Go to "TRANSPORT_TABLE" 139ms

And Show all transport "true" 088ms

And Select transportType "TRANSPORT_ORDER" 1s 133ms

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

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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

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

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

And Go to "TRANSPORT_TABLE" 214ms

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

And Toggle transport table days limit filter 093ms

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

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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

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

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

When Go to "TRANSPORT_TABLE" 116ms

And Go to auction form 1s 393ms

And Select contractors group "Kraj" 093ms

Then Verify that carrier "PSKZA1" is selected 022ms

Hooks

After Hooks.removeContractorsGroup() 087ms

After Hooks.deleteTransportAfterTest() 086ms

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

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

When Go to "TRANSPORT_TABLE" 121ms

And Go to auction form 1s 221ms

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

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

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

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

When Go to "TRANSPORT_TABLE" 120ms

And Go to auction form 1s 224ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 068ms

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

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

And Show all transport "false" 011ms

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

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

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

And Expand index panel 103ms

And Click add index button 121ms

And Fill index form 10s 548ms

And Click ok button in index form 15s 135ms

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

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

And Expand index panel 125ms

Then Check are transport values equals 116ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

After Hooks.deleteProductAfterTest() 075ms

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

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

And Show all transport "true" 085ms

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

And Expand index panel 101ms

And Click add index button 117ms

And Fill index form 7s 507ms

And Click ok button in index form 15s 148ms

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

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

And Expand index panel 127ms

Then Check are transport values equals 2s 130ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.deleteProductAfterTest() 000ms

View Feature Crud index

@deleteProductAfterTest @deleteTransportAfterTest

Scenario Outline Check if it possible to delete index in transport

Steps

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

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

And Show all transport "false" 012ms

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

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

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

And Add index to transport 25s 882ms

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

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

And Expand index panel 128ms

And Click delete index button 068ms

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

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

And Expand index panel 100ms

Then Verify that transport has no indexes 15s 061ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

After Hooks.deleteProductAfterTest() 056ms

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

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

And Show all transport "true" 077ms

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

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

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

And Add index to transport 22s 945ms

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

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

And Expand index panel 122ms

And Click delete index button 064ms

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

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

And Expand index panel 092ms

Then Verify that transport has no indexes 15s 052ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

After Hooks.deleteProductAfterTest() 000ms

View Feature Index

@deleteProductAfterTest @deleteTransportAfterTest

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

Steps

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

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

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

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

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

And Add index to transport 24s 616ms

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

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

When Click on index details icon 111ms

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

Hooks

After Hooks.deleteTransportAfterTest() 100ms

After Hooks.deleteProductAfterTest() 034ms

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

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

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

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

And Show all transport types 1s 042ms

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

And Set advice window in schedule 2s 476ms

And Fill advice form 11s 907ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 217ms

After Hooks.deleteTransportAfterTest() 153ms

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

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

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

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

And Show all transport types 1s 042ms

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

And Set advice window in schedule 2s 563ms

And Fill advice form 8s 430ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 176ms

After Hooks.deleteTransportAfterTest() 118ms

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

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

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

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

And Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 437ms

And Fill advice form 13s 238ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 243ms

After Hooks.deleteTransportAfterTest() 095ms

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

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

And Show all transport types 1s 049ms

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

And Go to "TRANSPORT_TABLE" 198ms

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

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

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

And Fill transport form 4s 749ms

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

And Expand advice panel 116ms

And Edit advice in transport details 12s 534ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 202ms

After Hooks.deleteTransportAfterTest() 108ms

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" 6s 356ms

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

And Show all transport types 1s 048ms

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

And Go to "TRANSPORT_TABLE" 238ms

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

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

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

And Expand advice panel 092ms

And Edit advice in transport details 6s 636ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 195ms

After Hooks.deleteTransportAfterTest() 119ms

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

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

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

And Show all transport types 1s 054ms

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

And Go to "TRANSPORT_TABLE" 188ms

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

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

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

And Fill transport form 24s 797ms

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

And Expand advice panel 102ms

And Edit advice in transport details 18s 649ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 280ms

After Hooks.deleteTransportAfterTest() 120ms

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

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

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

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

Then Check if user got a mail 000ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 173ms

After Hooks.deleteTransportAfterTest() 141ms

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

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

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

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

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

And Wait "120" seconds 2m

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 271ms

After Hooks.deleteTransportAfterTest() 100ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 006ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating a new auction

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 221ms

After Hooks.deleteTransportAfterTest() 096ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 227ms

After Hooks.deleteTransportAfterTest() 100ms

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

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

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

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

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

And Wait till auction end 1m 58s 023ms

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

Then Check if user got a mail 000ms

Error message

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 487ms

After Hooks.deleteTransportAfterTest() 194ms

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

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

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

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

And Wait till auction end 1m 58s 022ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 184ms

After Hooks.deleteTransportAfterTest() 078ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 213ms

After Hooks.deleteTransportAfterTest() 091ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 251ms

After Hooks.deleteTransportAfterTest() 069ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 197ms

After Hooks.deleteTransportAfterTest() 085ms

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

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

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

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

Error message

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

	at sun.reflect.GeneratedConstructorAccessor186.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() 174ms

After Hooks.deleteTransportAfterTest() 090ms

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

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

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

And Go to "TRANSPORT_TABLE" 132ms

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

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

And Fill transport form 35s 942ms

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

And Fill discrepancy report section 35s 924ms

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

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

And Generate discrepancy report 19s 327ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 355ms

After Hooks.deleteTransportAfterTest() 103ms

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

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:293)
	at sun.reflect.GeneratedMethodAccessor239.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 103ms

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 308ms

After Hooks.deleteTransportAfterTest() 061ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 293ms

After Hooks.deleteTransportAfterTest() 057ms

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

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

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

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

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.cTgIHr}, 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: 1968d0bcafa471a25cdc53a4d1bd1dd3
	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() 194ms

After Hooks.deleteTransportAfterTest() 073ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

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

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.cTgIHr}, 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: 1968d0bcafa471a25cdc53a4d1bd1dd3
	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() 193ms

After Hooks.deleteTransportAfterTest() 088ms

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

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

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

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

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.cTgIHr}, 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: 1968d0bcafa471a25cdc53a4d1bd1dd3
	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() 278ms

After Hooks.deleteTransportAfterTest() 095ms

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

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

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

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

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

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

Then If user is login then logout 109ms

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

And Go to auction details 1s 180ms

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

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

Then Check if user got a mail 000ms

Error message

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 294ms

After Hooks.deleteTransportAfterTest() 085ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 271ms

After Hooks.deleteTransportAfterTest() 090ms

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

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

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

And Fill transport form 41s 116ms

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

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

And Set advice window in schedule 2s 181ms

Then Verify that the error is visible after exceeding the pallet limit 1s 729ms

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

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

And Go to "TRANSPORT_TABLE" 286ms

And Show all transport "false" 007ms

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

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

And Click "save-transport" save button 717ms

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

Hooks

After Hooks.deleteTransportAfterTest() 145ms

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

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

And Set status of MOT to "AWAITING_VERIFICATION" 078ms

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

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

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

And Go to "TRANSPORT_TABLE" 210ms

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

And Set advice window in schedule 2s 767ms

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

Hooks

After Hooks.deleteTransportAfterTest() 087ms

After Hooks.deleteModeOfTransportationAfterTest() 075ms

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

And Set status of MOT to "DISABLED" 056ms

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

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

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

And Go to "TRANSPORT_TABLE" 215ms

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

And Set advice window in schedule 2s 772ms

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

Hooks

After Hooks.deleteTransportAfterTest() 116ms

After Hooks.deleteModeOfTransportationAfterTest() 072ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Set status of MOT to "ACCEPTED" 058ms

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

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

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

And Go to "TRANSPORT_TABLE" 237ms

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

And Set advice window in schedule 2s 794ms

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

Hooks

After Hooks.deleteTransportAfterTest() 079ms

After Hooks.deleteModeOfTransportationAfterTest() 072ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Set status of MOT to "UPDATED" 067ms

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

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

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

And Go to "TRANSPORT_TABLE" 197ms

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

And Set advice window in schedule 2s 718ms

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

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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

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

And Set status of MOT to "REJECTED" 063ms

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

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

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

And Go to "TRANSPORT_TABLE" 208ms

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

And Set advice window in schedule 2s 750ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.deleteModeOfTransportationAfterTest() 076ms

View Feature Mode of transportation - Advice

@deleteModeOfTransportationAfterTest @deleteTransportAfterTest

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

Steps

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

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

And Set status of MOT to "BLOCKED" 065ms

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

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

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

And Go to "TRANSPORT_TABLE" 209ms

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

And Set advice window in schedule 2s 806ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 088ms

After Hooks.deleteModeOfTransportationAfterTest() 072ms

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

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

And Add transport by SKApi in "MGW" 156ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 24s 903ms

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

And Set advice window in schedule 2s 749ms

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

And Fill advice form 18s 260ms

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 211ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

When Add transport by SKApi in "MGW" 002ms

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

And Go to "TRANSPORT_TABLE" 112ms

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

Then Check are transport values equals 427ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

When Add transport by SKApi in "MGW" 003ms

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

And Go to "TRANSPORT_TABLE" 130ms

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

Then Check are transport values equals 421ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

When Add transport by SKApi in "MGW" 002ms

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

And Go to "TRANSPORT_TABLE" 124ms

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

Then Check are transport values equals 427ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

When Add transport by SKApi in "HRL" 002ms

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

And Go to "TRANSPORT_TABLE" 124ms

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

Then Check are transport values equals 405ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

When Add transport by SKApi in "HRL" 002ms

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

And Go to "TRANSPORT_TABLE" 139ms

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

Then Check are transport values equals 435ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

When Add transport by SKApi in "HRL" 003ms

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

And Go to "TRANSPORT_TABLE" 109ms

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

Then Check are transport values equals 398ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

View Feature SK API - Creation of the Transport

@deleteTransportAfterTest

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

Steps

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

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

And Set another client name "Pepsi" 000ms

When Add transport by SKApi in "MGW" 003ms

Then Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 54s 338ms

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

Hooks

After Hooks.deleteTransportAfterTest() 072ms

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

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

When Add transport by SKApi in "" 002ms

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

And Go to "TRANSPORT_TABLE" 136ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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

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

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

And Set advice window in schedule 2s 790ms

And Fill advice form 14s 887ms

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

And Go to "TRANSPORT_TABLE" 207ms

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

Then Check are advice values equals 2s 285ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

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

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

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

And Set advice window in schedule 2s 589ms

And Fill advice form 14s 707ms

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

And Go to "TRANSPORT_TABLE" 227ms

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

Then Check are advice values equals 2s 302ms

Hooks

After Hooks.deleteTransportAfterTest() 138ms

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

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

And Add transport by SKApi in "MGW" 002ms

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

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

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

And Set advice window in schedule 2s 513ms

And Fill advice form 14s 725ms

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

And Go to "TRANSPORT_TABLE" 228ms

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

Then Check are advice values equals 2s 280ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Steps

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

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

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

And Set advice window in schedule 2s 533ms

And Fill advice form 14s 703ms

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

And Go to "TRANSPORT_TABLE" 191ms

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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

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

And Add transport by SKApi in "MGW" 003ms

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

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

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

And Set advice window in schedule 2s 539ms

And Fill advice form 14s 737ms

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

And Go to "TRANSPORT_TABLE" 226ms

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

Hooks

After Hooks.deleteTransportAfterTest() 131ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Steps

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

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

And Add transport by SKApi in "MGW" 003ms

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

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

And Set advice window in schedule 2s 533ms

And Fill advice form 14s 707ms

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

And Go to "TRANSPORT_TABLE" 251ms

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

Hooks

After Hooks.deleteTransportAfterTest() 109ms

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

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

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

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

And Fill advice form 14s 756ms

And Click advice save button to check error message 098ms

Then Check if possible advice alert is displayed 027ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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

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

And Add transport by SKApi in "MGW" 002ms

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

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

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

And Go to "TRANSPORT_TABLE" 226ms

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

And Expand advice panel 098ms

And Edit advice in transport details 14s 130ms

And Fill arrival date field 2s 299ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 134ms

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

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

And Add transport by SKApi in "MGW" 002ms

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

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

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

And Go to "TRANSPORT_TABLE" 222ms

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

And Expand advice panel 104ms

And Edit advice in transport details 14s 159ms

And Fill arrival date field 2s 298ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 230ms

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

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

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

And Go to "TRANSPORT_TABLE" 244ms

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

And Expand advice panel 103ms

And Edit advice in transport details 14s 159ms

And Fill arrival date field 2s 278ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 155ms

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

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

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

When Go to "WAREHOUSE_TAB" 864ms

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

And Select view "DAYS_2" 2s 089ms

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

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

And Select view "DAYS_2" 2s 052ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 203ms

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

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

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

When Go to "WAREHOUSE_TAB" 772ms

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

And Select view "DAYS_2" 2s 086ms

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

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

And Select view "DAYS_2" 2s 051ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 191ms

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

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

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

When Go to "WAREHOUSE_TAB" 724ms

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

And Select view "DAYS_2" 2s 086ms

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

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

And Select view "DAYS_2" 2s 059ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 169ms

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

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

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

When Go to "WAREHOUSE_TAB" 455ms

And Select warehouse "MGW" 1s 182ms

And Select view "DAYS_2" 2s 076ms

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

And Select warehouse "HRL" 1s 387ms

And Select view "DAYS_2" 2s 060ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

After Hooks.deleteAllGrayWindowsAfterTest() 15s 151ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 134ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 141ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 110ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

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

Then Check if transport has "departed" 027ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Status confirmation

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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" 5s 610ms

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

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

When Accept or reject "accept" transferred transport 17s 990ms

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

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

And Set advice window in schedule 2s 794ms

And Fill advice form 14s 633ms

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

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

And Go to "TRANSPORT_TABLE" 218ms

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

Hooks

After Hooks.deleteTransportAfterTest() 139ms

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

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

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

When Accept or reject "accept" transferred transport 17s 982ms

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

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

And Set advice window in schedule 2s 677ms

And Fill advice form 14s 710ms

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

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

And Go to "TRANSPORT_TABLE" 194ms

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

Hooks

After Hooks.deleteTransportAfterTest() 148ms

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

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

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

When Login as "hochland-admin" 3s 012ms

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

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

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

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

Hooks

After Hooks.rollbackAddedActionAuthorities() 070ms

After Hooks.deleteTransportAfterTest() 104ms

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

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

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

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

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

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

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

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

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

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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

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

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

And Show all transport types 1s 047ms

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

And Set advice window in schedule 2s 578ms

And Fill advice form 8s 428ms

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

And Go to "TRANSPORT_TABLE" 254ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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

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

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

And Show all transport types 1s 050ms

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

And Set advice window in schedule 2s 555ms

And Fill advice form 8s 425ms

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

And Go to "TRANSPORT_TABLE" 216ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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

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

And Show all transport types 1s 047ms

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

And Set advice window in schedule 2s 544ms

And Fill advice form 8s 425ms

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

And Go to "TRANSPORT_TABLE" 215ms

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

When Add file to transport by API 568ms

And Confirm statuses until reach "process-ended" 38s 290ms

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

Hooks

After Hooks.deleteTransportAfterTest() 148ms

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

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

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

And Show all transport types 1s 042ms

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

And Set advice window in schedule 2s 574ms

And Fill advice form 8s 408ms

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

And Go to "TRANSPORT_TABLE" 211ms

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

When Add file to transport by API 232ms

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

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

Hooks

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 - with advice step

Steps

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

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

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

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

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

And Show all transport types 1s 061ms

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

And Set advice window in schedule 6s 439ms

And Fill advice form 11s 915ms

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

And Go to "TRANSPORT_TABLE" 216ms

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

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

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

Hooks

After Hooks.rollbackCustomFieldSettings() 071ms

After Hooks.deleteTransportAfterTest() 126ms

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

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

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

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

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

And Login as "keeeper-admin" 2s 034ms

And Show all transport types 1s 139ms

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

And Set advice window in schedule 2s 402ms

And Fill advice form 13s 260ms

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

And Go to "TRANSPORT_TABLE" 195ms

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

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

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

Hooks

After Hooks.rollbackCustomFieldSettings() 042ms

After Hooks.deleteTransportAfterTest() 082ms

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

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

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

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

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

And Login as "keeeper-admin" 2s 123ms

And Show all transport types 1s 074ms

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

And Set advice window in schedule 2s 405ms

And Fill advice form 13s 268ms

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

And Go to "TRANSPORT_TABLE" 206ms

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

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

Then Check if next status is not possible to confirm 109ms

Hooks

After Hooks.rollbackCustomFieldSettings() 044ms

After Hooks.deleteTransportAfterTest() 099ms

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 "UNLOAD" 022ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_DELIVERY_SANITARY_CONDITIONS_CFD" in "UNLOAD" - "keeeper" by "super-admin-keeeper" 042ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 293ms

And Login as "keeeper-admin" 2s 051ms

And Go to "TRANSPORT_TABLE" 102ms

And Find transport in table with status "planned" 3s 201ms

And Confirm statuses until reach "arrived" 3s 782ms

Then Check if next status is not possible to confirm 105ms

Hooks

After Hooks.rollbackCustomFieldSettings() 048ms

After Hooks.deleteTransportAfterTest() 128ms

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" 095ms

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "TANKER_GRANULATE_DELIVERY" 022ms

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" 042ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 323ms

And Login as "keeeper-admin" 2s 152ms

And Go to "TRANSPORT_TABLE" 121ms

And Find transport in table with status "planned" 3s 157ms

And Confirm statuses until reach "arrived" 3s 833ms

Then Check if next status is not possible to confirm 113ms

Hooks

After Hooks.rollbackCustomFieldSettings() 043ms

After Hooks.deleteTransportAfterTest() 117ms

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" 022ms

And Set custom field "Magazynier" with "EDIT_DELIVERY_WAREHOUSEMAN_CFD" in "DELIVERY" - "hochland" by "super-admin-hochland" 152ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 354ms

And Login as "hochland-admin" 2s 256ms

And Go to "TRANSPORT_TABLE" 240ms

And Find transport in table with status "advice-added" 3s 201ms

And Confirm statuses until reach "during-unload" 6s 553ms

Then Check if next status is not possible to confirm 109ms

Hooks

After Hooks.rollbackCustomFieldSettings() 101ms

After Hooks.deleteTransportAfterTest() 086ms

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" 089ms

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "LOAD" 021ms

And Get inputs from database "ADVICE_LOAD" "super-admin-keeeper" 001ms

And Set custom field "Spełnienie warunków sanitarno-technicznych" with "EDIT_LOAD_SANITARY_CONDITIONS_CFD" in "LOAD" - "keeeper" by "super-admin-keeeper" 038ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 141ms

And Login as "keeeper-admin" 2s 068ms

And Show all transport types 1s 124ms

And Click button advice in transport table "LOAD" 137ms

And Set advice window in schedule 2s 391ms

And Fill advice form 13s 186ms

And Click advice save button and wait for advice form to disappear 30s 723ms

And Go to "TRANSPORT_TABLE" 179ms

And Find transport in table with status "advice-added" 3s 243ms

When Confirm statuses until reach "arrived" 3s 815ms

And Check if next status is not possible to confirm 107ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 002ms

And Go to transport details "LOAD" 4s 382ms

And Open section: "advice-panel" 1s 079ms

And Fill transport form 24s 842ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 662ms

And Go to transport details "LOAD" 4s 380ms

And Open section: "advice-panel" 1s 065ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 15s 784ms

And Confirm statuses until reach "process-ended" 24s 278ms

Then Check if transport has "process-ended" 027ms

Hooks

After Hooks.rollbackCustomFieldSettings() 095ms

After Hooks.deleteTransportAfterTest() 140ms

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" 093ms

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "CONTAINER" 024ms

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" 045ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 267ms

And Login as "keeeper-admin" 2s 415ms

And Show all transport types 1s 054ms

And Click button advice in transport table "CONTAINER" 144ms

And Set advice window in schedule 2s 456ms

And Fill advice form 13s 274ms

And Click advice save button and wait for advice form to disappear 30s 693ms

And Go to "TRANSPORT_TABLE" 196ms

And Find transport in table with status "advice-added" 3s 226ms

When Confirm statuses until reach "arrived" 3s 836ms

And Check if next status is not possible to confirm 114ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 002ms

And Go to transport details "CONTAINER" 4s 390ms

And Open section: "advice-panel" 1s 062ms

And Fill transport form 24s 743ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 642ms

And Go to transport details "CONTAINER" 4s 358ms

And Open section: "advice-panel" 1s 060ms

And Fill "meeting-sanitary-and-technical-conditions" in transport form 15s 806ms

And Confirm statuses until reach "process-ended" 24s 286ms

Then Check if transport has "process-ended" 027ms

Hooks

After Hooks.rollbackCustomFieldSettings() 057ms

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 - with advice step

Steps

Given Set token of apiUsername "super-admin-hochland" 093ms

And Get "Magazynier (R)" settings from "hochland" in "TRANSFER_BETWEEN_WAREHOUSES" 017ms

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" 059ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 168ms

And Login as "hochland-admin" 2s 901ms

And Show all transport types 1s 058ms

And Click button advice in transport table "TRANSFER_BETWEEN_WAREHOUSES" 130ms

And Set advice window in schedule 6s 475ms

And Fill advice form 11s 907ms

And Click advice save button and wait for advice form to disappear 30s 712ms

And Go to "TRANSPORT_TABLE" 213ms

And Find transport in table with status "advice-added" 3s 219ms

When Confirm statuses until reach "during-load" 6s 581ms

And Check if next status is not possible to confirm 105ms

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 002ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 614ms

And Open section: "advice-panel" 1s 074ms

And Fill transport form 36s 329ms

And Click "save-transport-and-close" save button and wait for form to disappear 754ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 583ms

And Open section: "advice-panel" 1s 081ms

And Fill "warehouseman-(u)" in transport form 15s 837ms

And Confirm statuses until reach "process-ended" 32s 560ms

Then Check if transport has "process-ended" 025ms

Hooks

After Hooks.rollbackCustomFieldSettings() 068ms

After Hooks.deleteTransportAfterTest() 116ms

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 "UNLOAD" 019ms

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" 045ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 377ms

And Login as "keeeper-admin" 2s 484ms

And Go to "TRANSPORT_TABLE" 140ms

And Find transport in table with status "planned" 3s 179ms

When Confirm statuses until reach "arrived" 3s 804ms

And Check if next status is not possible to confirm 111ms

And Go to transport details "UNLOAD" 4s 433ms

And Fill transport form 37s 969ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 165ms

And Confirm statuses until reach "process-ended" 24s 279ms

Then Check if transport has "process-ended" 026ms

Hooks

After Hooks.rollbackCustomFieldSettings() 078ms

After Hooks.deleteTransportAfterTest() 142ms

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" 095ms

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" 043ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 364ms

And Login as "keeeper-admin" 1s 988ms

And Go to "TRANSPORT_TABLE" 141ms

And Find transport in table with status "planned" 3s 182ms

When Confirm statuses until reach "arrived" 3s 812ms

And Check if next status is not possible to confirm 114ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 426ms

And Fill transport form 36s 391ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 642ms

And Confirm statuses until reach "process-ended" 24s 306ms

Then Check if transport has "process-ended" 026ms

Hooks

After Hooks.rollbackCustomFieldSettings() 052ms

After Hooks.deleteTransportAfterTest() 113ms

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" 103ms

And Get "Magazynier" settings from "hochland" in "DELIVERY" 019ms

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" 098ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 322ms

And Login as "hochland-admin" 2s 570ms

And Go to "TRANSPORT_TABLE" 237ms

And Find transport in table with status "advice-added" 3s 200ms

When Confirm statuses until reach "during-unload" 6s 572ms

And Check if next status is not possible to confirm 117ms

And Go to transport details "DELIVERY" 4s 669ms

And Fill transport form 36s 108ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 154ms

And Confirm statuses until reach "process-ended" 21s 563ms

Then Check if transport has "process-ended" 024ms

Hooks

After Hooks.rollbackCustomFieldSettings() 120ms

After Hooks.deleteTransportAfterTest() 102ms

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" 098ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 1s 293ms

And Confirm status "REPORTING" by Public API "v1" 110ms

And Confirm status "ARRIVAL" by Public API "v1" 111ms

And Login as "swiss-krono-delivery-guard" 1s 745ms

And Go to "TRANSPORT_TABLE" 173ms

When Confirm "Departure" status in transport row 3s 079ms

Then Verify that "Departure" has been confirmed 034ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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" 093ms

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "UNLOAD" 018ms

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" 040ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 15s 328ms

When Login as "keeeper-admin" 1s 980ms

And Find transport in table with status "planned" 3s 243ms

And Confirm statuses until reach "arrived" 3s 817ms

And Go to transport details "UNLOAD" 4s 394ms

And Fill transport form 38s 012ms

Then Check if next status is not possible to confirm in transport details 071ms

Hooks

After Hooks.rollbackCustomFieldSettings() 050ms

After Hooks.deleteTransportAfterTest() 092ms

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" 091ms

And Get "Spełnienie warunków sanitarno-technicznych" settings from "keeeper" in "TANKER_GRANULATE_DELIVERY" 023ms

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" 037ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 273ms

When Login as "keeeper-admin" 2s 009ms

And Find transport in table with status "planned" 3s 237ms

And Confirm statuses until reach "arrived" 3s 824ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 459ms

And Fill transport form 36s 324ms

Then Check if next status is not possible to confirm in transport details 071ms

Hooks

After Hooks.rollbackCustomFieldSettings() 047ms

After Hooks.deleteTransportAfterTest() 100ms

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" 093ms

And Get "Magazynier" settings from "hochland" in "DELIVERY" 018ms

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" 125ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 341ms

When Login as "hochland-admin" 2s 357ms

And Find transport in table with status "advice-added" 3s 330ms

And Confirm statuses until reach "during-unload" 6s 600ms

And Go to transport details "DELIVERY" 4s 689ms

And Fill transport form 36s 086ms

Then Check if next status is not possible to confirm in transport details 069ms

Hooks

After Hooks.rollbackCustomFieldSettings() 120ms

After Hooks.deleteTransportAfterTest() 110ms

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" 097ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 448ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 275ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 137ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 3s 994ms

And Login as "bausch-admin" 2s 193ms

And Go to "TRANSPORT_TABLE" 215ms

And Find transport in table with status "advice-added" 3s 195ms

When Confirm statuses until reach "on-the-way" 9s 361ms

And Open statuses popup 065ms

And Toggle status date confirmation checkbox 275ms

And Confirm statuses until reach "process-ended" 18s 743ms

Then Check if transport has "process-ended" 029ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

After Hooks.deleteModeOfTransportationAfterTest() 102ms

View Feature Status confirmation

@deleteTransportAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline Check if it is not possible to confirm status with invalid confirmation date [A-7159]

Steps

Given Set token of apiUsername "super-admin-bausch" 094ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 308ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 229ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 111ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 720ms

And Login as "bausch-admin" 1s 087ms

And Go to "TRANSPORT_TABLE" 232ms

And Find transport in table with status "advice-added" 3s 225ms

When Confirm statuses until reach "on-the-way" 9s 308ms

And Open statuses popup 067ms

And Toggle status date confirmation checkbox 276ms

And Change status execution date to "1" days from today 2s 205ms

Then Verify that status cannot be confirmed 1s 084ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

After Hooks.deleteModeOfTransportationAfterTest() 080ms

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" 093ms

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 288ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 230ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 099ms

When Create advice by JSON file "CREATE_ADVICE_FOR_LOAD_PL" as "super-admin-bausch" 708ms

And Login as "bausch-admin" 1s 029ms

And Go to "TRANSPORT_TABLE" 204ms

And Find transport in table with status "advice-added" 3s 226ms

When Confirm statuses until reach "on-the-way" 9s 326ms

And Open statuses popup 067ms

And Toggle status date confirmation checkbox 285ms

And Change status execution date to "-1" days from today 2s 194ms

Then Verify that status cannot be confirmed 1s 099ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

After Hooks.deleteModeOfTransportationAfterTest() 069ms

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" 104ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 259ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 651ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 026ms

When Login as "farmacol-admin" 2s 537ms

And Go to "TRANSPORT_TABLE" 117ms

And Confirm statuses until reach "during-unload" 9s 984ms

And Set actual confirmed transport status list 1s 387ms

And Disable task by API 035ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 468ms

And Edit transport hours and recalculate statuses 16s 356ms

Then Verify that all confirmed statuses are still on transport status list 187ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

After Hooks.rollbackTaskChanges() 046ms

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" 5s 226ms

And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 277ms

And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 1s 900ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 401ms

And Check if reject date is not visible 15s 018ms

When Reject status: Book of disinfection 081ms

And Check if reject date is visible 391ms

Then If user is login then logout 068ms

And Login as "lantmannen-admin" 1s 130ms

And Check if note was added to transport after status rejection 1s 228ms

And Check if history note was added to transport after status rejection - "LOAD" 5s 522ms

And Get mail "apolloautomattest@gmail.com" message from mail account with "Nieaktualna księga mycia i dezynfekcji" 13s 840ms

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 185ms

After Hooks.deleteTransportAfterTest() 099ms

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 756ms

And Create transport "CREATE_LOAD_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 289ms

And Check if reject date is not visible 15s 027ms

When Reject status: Book of disinfection 071ms

And Check if reject date is visible 153ms

And Get rejection date 026ms

And Wait "60" seconds 1m

And Reject status: Book of disinfection 061ms

Then Check if reject date has changed 1s 085ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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 133ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 296ms

And Go to transport details "LOAD" 4s 328ms

And Check if reject date is not visible 15s 063ms

When Reject status: Book of disinfection 069ms

Then Check if reject date is visible 158ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

View Feature Status rejection

@deleteTransportAfterTest

Scenario Outline Check if it is possible to reject status by admin in statuses popup

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 035ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 300ms

And Open statuses popup 091ms

And Check if reject date is not visible 15s 042ms

When Reject status: Book of disinfection 088ms

Then Open statuses popup 052ms

And Check if reject date is visible 092ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

View Feature Status revocation

@deleteTransportAfterTest

Scenario Outline Check if it is possible to revoke statuses by user

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 647ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 407ms

And Confirm to the last status by API 169ms

When Find statuses for transport in table 2s 021ms

And Revoke statuses until reach "advice-added" 6s 817ms

Then Check if transport has "advice-added" 027ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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" 2s 062ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 283ms

And Confirm to the last status by API 182ms

When Find statuses for transport in table 1s 702ms

And Revoke statuses until reach "planned" 6s 760ms

Then Check if transport has "planned" 026ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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 120ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 193ms

When Find transport in table with status "new" 3s 232ms

And Open statuses popup 087ms

Then Check if transport has checkpoints from list "Utworzenie zlecenia,Dodanie awizacji,Potwierdzenie okna czasowego" in "0" 069ms

Hooks

After Hooks.deleteTransportAfterTest() 063ms

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 147ms

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 197ms

And Click button advice in transport table "EXTERNAL_DELIVERY" 135ms

And Set advice window in schedule 2s 703ms

And Fill advice form 12s 194ms

And Click advice save button and wait for advice form to disappear 30s 734ms

And Go to "TRANSPORT_TABLE" 247ms

When Find transport in table with status "advice-added" 3s 215ms

And Open statuses popup 104ms

Then Check if transport has checkpoints from list "Zgłoszenie kierowcy,Rozpoczęcie rozładunku,Zakończenie rozładunku" in "1" 059ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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" 095ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 1s 193ms

And Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 658ms

And Get "START_OF_UNLOADING" data for transport type "EXTERNAL_DELIVERY" and principal "farmacol" 022ms

When Login as "farmacol-admin" 1s 475ms

And Go to "TRANSPORT_TABLE" 223ms

And Confirm statuses until reach "registered-katowice-przyjęcia" 6s 637ms

And Disable task by API 055ms

And Find transport pencil button in transports table 1s 265ms

And Click pencil and move transport to next day in schedule 18s 182ms

And Go to "TRANSPORT_TABLE" 219ms

Then Verify that "START_OF_UNLOADING" is not visible 141ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

After Hooks.rollbackTaskChanges() 031ms

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 392ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 713ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 087ms

When Go to "WAREHOUSE_TAB" 746ms

And Select warehouse "Serownia" 1s 377ms

And Set week view 1s 096ms

And Show yesterday 1s 072ms

And Move window into the past 308ms

Then Check if window is "red" 2s 029ms

Hooks

After Hooks.rollbackAddedAuthorities() 059ms

After Hooks.deleteTransportAfterTest() 146ms

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 033ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 341ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "lantmannen-admin" 047ms

When Go to "WAREHOUSE_TAB" 312ms

And Select warehouse "Magazyn - Nowa Sól" 2s 202ms

And Set week view 1s 140ms

And Show yesterday 1s 056ms

And Move window into the past 398ms

Then Check if window is "red" 2s 031ms

Hooks

After Hooks.rollbackAddedAuthorities() 043ms

After Hooks.deleteTransportAfterTest() 108ms

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 191ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 191ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "piast-admin" 043ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 002ms

When Show all transport types 1s 040ms

And Click button advice in transport table "DELIVERY" 119ms

And Set advice window in schedule 2s 686ms

And Fill advice form 8s 432ms

And Click advice save button and wait for advice form to disappear 30s 765ms

And Select warehouse "Magazyn Hala A" 1s 207ms

And Set week view 2s 055ms

And Show yesterday 1s 133ms

And Move window into the past 567ms

Then Check if window is "red" 2s 055ms

Hooks

After Hooks.rollbackAddedAuthorities() 054ms

After Hooks.deleteTransportAfterTest() 101ms

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" 3s 091ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 002ms

And Set algorithm setting for "super-admin-hochland" in "Magazyn Zimny Kaźmierz" on "Magazyn Zimny" 442ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 362ms

When Go to "WAREHOUSE_TAB" 827ms

And Select warehouse "Magazyn Zimny Kaźmierz" 1s 706ms

And Set week view 1s 124ms

And Check if time window length is correct after "CREATE" 030ms

And Change number of pallets in transport 51s 150ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 219ms

And Check if time window length is correct after "EDIT" 029ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackTransportTypeSettings

Scenario Outline Check if time window has valid length with restriction to algorithm settings when quantity is set in transport form

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 205ms

And Get "UNLOAD" settings from "keeeper" 042ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 098ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;true" 161ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 335ms

When Go to "WAREHOUSE_TAB" 313ms

And Select warehouse "Magazyn Surowców" 1s 172ms

And Set week view 1s 091ms

Then Check if time window has proper "60" 018ms

Hooks

After Hooks.rollbackTransportTypeSettings() 072ms

After Hooks.clearAlgorithmSettings() 143ms

After Hooks.deleteTransportAfterTest() 117ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings @rollbackTransportTypeSettings

Scenario Outline Check if time window has valid length with restriction to algorithm settings when quantity is set from default quantity value and quantity field is not visible in transport form

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 105ms

And Get "UNLOAD" settings from "keeeper" 030ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Surowców" on "Magazyn Surowców" 099ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;false" 065ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 343ms

When Go to "WAREHOUSE_TAB" 319ms

And Select warehouse "Magazyn Surowców" 1s 163ms

And Set week view 1s 091ms

Then Check if time window has proper "60" 028ms

Hooks

After Hooks.rollbackTransportTypeSettings() 061ms

After Hooks.clearAlgorithmSettings() 101ms

After Hooks.deleteTransportAfterTest() 098ms

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 115ms

And Get "LOAD" settings from "keeeper" 028ms

And Set algorithm setting for "super-admin-keeeper" in "Magazyn Wyrobów Gotowych" on "Magazyn Wyrobów Gotowych" 092ms

And Set transportType settings with values: "defaultQuantityValue;requiresStepsQuantity", "4;false" 066ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 197ms

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 467ms

And Fill advice form 13s 211ms

And Click advice save button and wait for advice form to disappear 30s 686ms

Then Check if time window has proper "30" 025ms

Hooks

After Hooks.rollbackTransportTypeSettings() 117ms

After Hooks.clearAlgorithmSettings() 097ms

After Hooks.deleteTransportAfterTest() 086ms

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 188ms

And Get "CONTAINER" settings from "keeeper" 034ms

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", "20;false" 062ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 217ms

And Get inputs from database "ADVICE_CONTAINER" "super-admin-keeeper" 003ms

And Show all transport types 1s 044ms

And Click button advice in transport table "CONTAINER" 136ms

And Set advice window in schedule 2s 419ms

And Fill advice form 13s 232ms

And Click advice save button and wait for advice form to disappear 30s 721ms

Then Check if time window has proper "60" 028ms

Hooks

After Hooks.rollbackTransportTypeSettings() 082ms

After Hooks.clearAlgorithmSettings() 110ms

After Hooks.deleteTransportAfterTest() 104ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest @clearAlgorithmSettings

Scenario Outline Check if supplier can change time window size by change number of pallets

Steps

Given Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "super-admin-hochland" 2s 709ms

And Set algorithm setting for "super-admin-hochland" in "Serownia" on "Magazyn Sera" 130ms

And Set token of apiUsername "dha1-supplier-2@qa.qa-test" 102ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 15s 488ms

And Set token of apiUsername "super-admin-hochland" 102ms

When Go to transport details "DELIVERY" 32s 703ms

And Change filled value in transport details "quantity" "number" "25" "0" 1s 348ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 077ms

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.cTgIHr}, 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: 1968d0bcafa471a25cdc53a4d1bd1dd3
	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() 136ms

After Hooks.deleteTransportAfterTest() 180ms

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 211ms

And Set basic authorities "ROLE_ACCESS_TO_NUMBER_OF_WINDOWS" to user "keeeper-admin" 052ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 195ms

When Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 46s 572ms

And Check if time window counter value equals "1" 074ms

And Select view "DAYS_2" 2s 085ms

And Move advice window "2" 1s 325ms

And Select view "DAY" 2s 067ms

Then Check if time window counter value equals "0" 072ms

And Delete created transport by API 110ms

And Check if time window counter value equals "0" 055ms

And Click in free spot in schedule page to create gray window 178ms

And Check if time window counter value equals "0" 053ms

And Click in free spot in schedule page to create dedicated window 048ms

And Check if time window counter value equals "0" 045ms

Hooks

After Hooks.rollbackAddedAuthorities() 000ms

After Hooks.deleteTransportAfterTest() 080ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 122ms

When Go to new transport "DELIVERY" 281ms

And Fill transport form 11s 446ms

And Click "save-transport" save button and wait for form to disappear 15s 638ms

And Set advice window in schedule 2s 168ms

And Check is transport created in schedule and set transport id 491ms

And Go to "TRANSPORT_TABLE" 266ms

When Click on time window date 1s 342ms

And Open transport form when in schedule 1s 167ms

Then Check are transport values equals 155ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 428ms

When Go to new transport "DELIVERY" 305ms

And Fill transport form 38s 920ms

And Click "save-transport" save button and wait for form to disappear 15s 635ms

And Set advice window in schedule 2s 159ms

And Check is transport created in schedule and set transport id 630ms

And Go to "TRANSPORT_TABLE" 267ms

When Click on time window date 1s 279ms

And Open transport form when in schedule 1s 353ms

Then Check are transport values equals 19s 377ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_CISTERN_DELIVERY" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 394ms

When Go to new transport "CISTERN_DELIVERY" 355ms

And Fill transport form 34s 978ms

And Click "save-transport" save button and wait for form to disappear 15s 875ms

And Set advice window in schedule 2s 195ms

And Check is transport created in schedule and set transport id 545ms

And Go to "TRANSPORT_TABLE" 195ms

When Click on time window date 1s 420ms

And Open transport form when in schedule 1s 185ms

Then Check are transport values equals 21s 446ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if transport form can be opened in schedule

Steps

Given Get inputs from database "CREATE_CISTERN_COLLECTION" "super-admin-hochland" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 462ms

When Go to new transport "CISTERN_COLLECTION" 354ms

And Fill transport form 28s 492ms

And Click "save-transport" save button and wait for form to disappear 19s 037ms

And Set advice window in schedule 2s 209ms

And Check is transport created in schedule and set transport id 951ms

And Go to "TRANSPORT_TABLE" 173ms

When Click on time window date 1s 389ms

And Open transport form when in schedule 1s 201ms

Then Check are transport values equals 21s 416ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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" 003ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 2s 518ms

When Go to new transport "DELIVERY" 297ms

And Fill transport form 38s 059ms

And Click "save-transport" save button and wait for form to disappear 15s 609ms

And Set advice window in schedule 2s 170ms

And Check is transport created in schedule and set transport id 644ms

And Go to "TRANSPORT_TABLE" 205ms

When Click on time window date 1s 338ms

And Open transport form when in schedule 1s 159ms

Then Check are transport values equals 19s 348ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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 081ms

When Go to new transport "LOAD" 292ms

And Fill transport form 38s 047ms

And Click "save-transport" save button and wait for form to disappear 15s 644ms

And Set advice window in schedule 2s 167ms

And Check is transport created in schedule and set transport id 539ms

And Go to "TRANSPORT_TABLE" 258ms

When Click on time window date 1s 335ms

And Open transport form when in schedule 1s 177ms

Then Check are transport values equals 19s 326ms

Hooks

After Hooks.deleteTransportAfterTest() 132ms

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" 105ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 050ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 114ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 194ms

And Login as "farmacol-admin" 2s 569ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 45s 839ms

And Go to "TRANSPORT_TABLE" 310ms

When Go to transport details "EXTERNAL_DELIVERY" 4s 480ms

And Add step "unload" 106ms

And Change filled value in transport details "warehouse-select-step-2" "select" "Mory Przyjęcia" "0" 3s 455ms

And Change filled value in transport details "weight-step-2" "number" "23" "0" 1s 367ms

And Change filled value in transport details "number-of-pallets-step-2" "number" "23" "0" 1s 370ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 327ms

Then Click "save-transport" save button 187ms

And Set advice window in schedule in "2" days 4s 964ms

And Click advice save button and wait for advice form to disappear 31s 002ms

And Go to "TRANSPORT_TABLE" 237ms

And Check if transport has "2" time windows 012ms

Hooks

After Hooks.rollbackTransportTypeSettings() 069ms

After Hooks.rollbackAddedActionAuthorities() 051ms

After Hooks.deleteTransportAfterTest() 135ms

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" 040ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 065ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 201ms

And Set double window advice 000ms

And Login as "farmacol-admin" 2s 095ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 993ms

And Go to "TRANSPORT_TABLE" 262ms

And Get checkpoint colors for transport 004ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "true" 43s 161ms

Hooks

After Hooks.rollbackTransportTypeSettings() 117ms

After Hooks.deleteTransportAfterTest() 138ms

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" 097ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 030ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 081ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 192ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 074ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 883ms

And Go to "TRANSPORT_TABLE" 346ms

And Get checkpoint colors for transport 004ms

Then Verify that transport colors change in column "UNLOAD_TIME_WINDOW" properly when windowColorDependsOnWarehouse is "false" 45s 805ms

Hooks

After Hooks.rollbackTransportTypeSettings() 125ms

After Hooks.deleteTransportAfterTest() 163ms

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" 090ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 031ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "true" 054ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 1s 279ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 120ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 50s 012ms

And Get checkpoint colors for transport 004ms

And Go to "TRANSPORT_TABLE" 311ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "true" 5s 699ms

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() 138ms

After Hooks.deleteTransportAfterTest() 136ms

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" 093ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 032ms

And Set transportType settings with values: "windowColorDependsOnWarehouse", "false" 067ms

And Create transport "CREATE_EXTERNAL_DELIVERY_2_WINDOWS" by JSON file as "super-admin-farmacol" 15s 170ms

And Set double window advice 000ms

And Login as "farmacol-admin" 1s 220ms

And Create advice "CREATE_ADVICE_EXTERNAL_DELIVERY" "EXTERNAL_DELIVERY" "super-admin-farmacol" 49s 922ms

And Get checkpoint colors for transport 006ms

And Go to "TRANSPORT_TABLE" 280ms

Then Verify that transport colors of windows "UNLOAD_TIME_WINDOW" change properly in schedule when windowColorDependsOnWarehouse is "false" 9s 909ms

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.cTgIHr}, 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: 1968d0bcafa471a25cdc53a4d1bd1dd3
	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() 065ms

After Hooks.deleteTransportAfterTest() 127ms

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" 096ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 163ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 592ms

And Login as "super-admin-farmacol" 2s 589ms

And Show all transport types 1s 171ms

And Click on time window date 1s 615ms

Then Open transport form when in schedule 1s 277ms

And Click create similar button 15s 125ms

And Click cancel button in transport form 103ms

And Open transport form when in schedule 1s 176ms

Then Check if transport form modal is visible 041ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

View Feature TransportWindow atom tests

@deleteTransportAfterTest

Scenario Outline Check if window is active after using "create similar" on that window [A-7009]

Steps

Given Set token of apiUsername "super-admin-farmacol" 093ms

And Create transport "CREATE_EXTERNAL_DELIVERY" by JSON file as "super-admin-farmacol" 15s 151ms

When Create advice by JSON file "CREATE_ADVICE_FOR_EXTERNAL_DELIVERY" as "super-admin-farmacol" 566ms

And Login as "super-admin-farmacol" 1s 142ms

And Show all transport types 1s 154ms

And Click on time window date 1s 615ms

Then Open transport form when in schedule 1s 273ms

And Click create similar button 15s 206ms

And Click cancel button in transport form 100ms

And Open transport form when in schedule 1s 222ms

Then Check if transport form modal is visible 045ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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 204ms

And Check expected date interval for principal "neuca" in transport type "DELIVERY" and task "ARRIVE" 001ms

And Get setting "DELAY_TIME_TO_MOVE_ORDER_TO_ARCHIVE_AFTER_TASK_TIMEOUT" for "neuca" 022ms

And Set proper delay time to move order to archive after task timeout 048ms

When Create transport with time window start at closest full hour "CREATE_DELIVERY" by API as "super-admin-neuca" 315ms

And Go to "WAREHOUSE_TAB" 603ms

And Change warehouse in schedule to: "Katowice" 1s 067ms

And Wait "60" seconds 1m

And Verify that transport window is grey 037ms

And Verify that transport is in archive 1s 134ms

Then Restore transport from archive 1s 156ms

And Verify that transport has been successfully restored 15s 318ms

Hooks

After Hooks.rollbackSettings() 032ms

After Hooks.deleteTransportAfterTest() 106ms

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 161ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-dayco" 1s 217ms

And Get setting "ARCHIVING_JOB_INTERVAL" for "dayco" 033ms

And Prepare setting: "ARCHIVING_JOB_INTERVAL" with value: "10s" with "super-admin-dayco" 003ms

When Go to "TRANSPORT_TABLE" 134ms

And Click button advice in transport table "OWN_COLLECTION" 2s

And Create advice "ADVICE_OWN_COLLECTION" "OWN_COLLECTION" "super-admin-dayco" 40s 244ms

And Go to "TRANSPORT_TABLE" 192ms

And Find transport in table with status "planned-magazyn-tychy" 3s 241ms

And Confirm statuses until reach "process-ended" 36s 774ms

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.cTgIHr}, 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: 1968d0bcafa471a25cdc53a4d1bd1dd3
	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.getAttribute(RemoteWebElement.java:128)
	at Utils.StatusUtil.waitUntilAttributeOfWebElementChangeValue(StatusUtil.java:38)
	at Pages.Transport.TransportsPage.confirmNextStatus(TransportsPage.java:296)
	at Pages.Transport.TransportsPage.confirmStatuses(TransportsPage.java:283)
	at CucumberTests.StatusTests.ConfirmStatuses.confirmStatusesUntilReach(ConfirmStatuses.java:84)
	at ✽.Confirm statuses until reach "process-ended"(file:Features/Atom/Transport/Archive.feature:45)

And Wait "12" seconds 000ms

Then Go to "ARCHIVE_TAB" 000ms

And Show "OWN_COLLECTION" 000ms

And Verify that created transport is "true" in transport table 000ms

Hooks

After Hooks.rollbackSettings() 064ms

After Hooks.deleteTransportAfterTest() 100ms

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 054ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 283ms

When Fill auction form 15s 497ms

Then Verify that the auction has been added to transport 047ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

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 260ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 204ms

When Fill auction form 15s 419ms

Then Verify that the auction has been added to transport 051ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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 052ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 188ms

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 118ms

And Login as "paa1-carrier@qa.qa-test" 2s 581ms

And Go to auction offer 1s 261ms

And Accept transport with minimum rate 15s 665ms

Then Check if carrier is assigned to transport 020ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

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 148ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 218ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 102ms

When If user is login then logout 093ms

And Login as "paa1-carrier@qa.qa-test" 1s 100ms

And Go to auction offer 1s 310ms

And Reject auction offer 15s 609ms

Then Verify that offer has been removed from transport 15s 048ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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 278ms

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 101ms

When If user is login then logout 108ms

And Login as "pskza1-carrier@qa.qa-test" 1s 106ms

And Go to auction offer 1s 212ms

And Reject auction offer 15s 585ms

Then Verify that offer has been removed from transport 15s 034ms

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 085ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 187ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 087ms

When If user is login then logout 095ms

And Login as "paa1-carrier@qa.qa-test" 1s 108ms

And Go to auction offer 1s 301ms

And Offer prize above maximum - "20000" 145ms

Then Verify that is not possible to add offer 158ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

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 154ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 228ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 115ms

When If user is login then logout 097ms

And Login as "pskza1-carrier@qa.qa-test" 1s 074ms

And Go to auction offer 1s 207ms

And Offer prize above maximum - "20000" 142ms

Then Verify that is not possible to add offer 151ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to add auction again after previous auction end

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 021ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 210ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 093ms

And Wait till auction end 1m 58s 018ms

Then Verify that is possible to add auction 053ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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 325ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 278ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 117ms

And Wait till auction end 1m 58s 018ms

Then Verify that is possible to add auction 051ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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 232ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 279ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 120ms

And Go to auction offer 1s 222ms

When Offer "1000" 138ms

Then Verify that offer with "1000" has been added to auction 3s 031ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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 019ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 198ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 100ms

And Go to auction offer 1s 209ms

When Offer "1000" 139ms

Then Verify that offer with "1000" has been added to auction 3s 037ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to revoke an offer

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 068ms

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 093ms

And Go to auction offer 1s 190ms

When Offer "1000" 145ms

And Verify that offer with "1000" has been added to auction 3s 034ms

Then Go to auction offer 1s 173ms

And Revoke current offer 570ms

And Verify that offer has been revoked 30s 613ms

Hooks

After Hooks.deleteTransportAfterTest() 132ms

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 117ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 256ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 112ms

And Go to auction offer 1s 199ms

When Offer "1000" 148ms

And Verify that offer with "1000" has been added to auction 3s 042ms

Then Go to auction offer 1s 185ms

And Offer "1500" 150ms

And Verify that offer with "1500" has been added to auction 3s 027ms

Hooks

After Hooks.deleteTransportAfterTest() 088ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if it is possible to finish active auction

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 496ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 224ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 100ms

And Go to auction offer 1s 203ms

When Offer "1000" 135ms

And Verify that offer with "1000" has been added to auction 3s 032ms

Then Login as "swisskrono-admin" 1s 034ms

And Go to auction details 1s 215ms

And Finish active auction 044ms

And Verify that the transport has no active auction 144ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

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 013ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 218ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 103ms

And Go to auction offer 1s 201ms

When Offer "1000" 139ms

Then Verify that carrier can see current place in auction depending on the "true" role 149ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

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 047ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 244ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 113ms

And Go to auction offer 1s 204ms

When Offer "1000" 143ms

Then Verify that carrier can see current place in auction depending on the "false" role 15s 060ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

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 107ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 194ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 097ms

And Go to auction offer 1s 206ms

When Offer "300" 148ms

And Verify that carrier can't add offer to auction 030ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check carrier selection in create auction form

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 221ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 4s 268ms

And Show all transport "false" 011ms

When Go to auction form 1s 279ms

Then Verify carrier selection value "false" 041ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

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 061ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 252ms

And Show all transport "true" 083ms

When Go to auction form 1s 194ms

Then Verify carrier selection value "true" 044ms

Hooks

After Hooks.deleteTransportAfterTest() 075ms

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 039ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 212ms

When Open transport auction form 178ms

And Select all companies checkbox in transport auction form 061ms

And Unselect company "PAA2" in transport auction form 074ms

And Put transport on auction 15s 174ms

And Open transport auction history 106ms

And Open participants section in transport auction history 054ms

Then Check if unselected "PAA2" is in transport auction history as participant 15s 066ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

View Feature Set transport order on auction

@deleteTransportAfterTest

Scenario Outline Check if auction is available to correct participants

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 259ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 222ms

When Open transport auction form 169ms

And Select all companies checkbox in transport auction form 067ms

And Unselect company "PSKZA2" in transport auction form 074ms

And Put transport on auction 15s 223ms

And Open transport auction history 104ms

And Open participants section in transport auction history 053ms

Then Check if unselected "PSKZA2" is in transport auction history as participant 15s 012ms

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_UNLOAD" "super-admin-pgf" 003ms

And Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 2s 509ms

When Go to new transport "UNLOAD" 15s 276ms

And Fill transport form 24s 527ms

And Click "save-transport" save button and wait for form to disappear 16s 009ms

And Set advice window in schedule 2s 204ms

And Check is transport created in schedule and set transport id 648ms

And Go to "TRANSPORT_TABLE" 246ms

And Go to transport details "UNLOAD" 32s 392ms

Then Check are transport values equals 21s 367ms

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-adama" 004ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 145ms

When Go to new transport "DELIVERY" 312ms

And Fill transport form 11s 445ms

And Click "save-transport" save button and wait for form to disappear 15s 639ms

And Set advice window in schedule 2s 169ms

And Check is transport created in schedule and set transport id 437ms

And Go to "TRANSPORT_TABLE" 225ms

And Go to transport details "DELIVERY" 4s 324ms

Then Check are transport values equals 123ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 102ms

When Go to new transport "OWN_COLLECTION" 290ms

And Fill transport form 17s 973ms

And Click "save-transport" save button and wait for form to disappear 15s 640ms

And Set advice window in schedule 2s 177ms

And Check is transport created in schedule and set transport id 456ms

And Go to "TRANSPORT_TABLE" 206ms

And Go to transport details "OWN_COLLECTION" 4s 330ms

Then Check are transport values equals 145ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-hochland" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 474ms

When Go to new transport "DELIVERY" 375ms

And Fill transport form 38s 979ms

And Click "save-transport" save button and wait for form to disappear 15s 590ms

And Set advice window in schedule 2s 159ms

And Check is transport created in schedule and set transport id 614ms

And Go to "TRANSPORT_TABLE" 248ms

And Go to transport details "DELIVERY" 4s 638ms

Then Check are transport values equals 19s 370ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_CISTERN_DELIVERY" "super-admin-hochland" 002ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 427ms

When Go to new transport "CISTERN_DELIVERY" 362ms

And Fill transport form 34s 972ms

And Click "save-transport" save button and wait for form to disappear 15s 918ms

And Set advice window in schedule 2s 203ms

And Check is transport created in schedule and set transport id 646ms

And Go to "TRANSPORT_TABLE" 219ms

And Go to transport details "CISTERN_DELIVERY" 4s 409ms

Then Check are transport values equals 21s 403ms

Hooks

After Hooks.deleteTransportAfterTest() 148ms

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" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 429ms

When Go to new transport "CISTERN_COLLECTION" 335ms

And Fill transport form 28s 420ms

And Click "save-transport" save button and wait for form to disappear 15s 896ms

And Set advice window in schedule 2s 225ms

And Check is transport created in schedule and set transport id 603ms

And Go to "TRANSPORT_TABLE" 190ms

And Go to transport details "CISTERN_COLLECTION" 6s 369ms

Then Check are transport values equals 21s 366ms

Hooks

After Hooks.deleteTransportAfterTest() 198ms

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 474ms

When Go to new transport "OWN_COLLECTION" 407ms

And Fill transport form 32s 899ms

And Click "save-transport" save button and wait for form to disappear 15s 695ms

And Set advice window in schedule 2s 160ms

And Check is transport created in schedule and set transport id 619ms

And Go to "TRANSPORT_TABLE" 219ms

And Go to transport details "OWN_COLLECTION" 4s 524ms

Then Check are transport values equals 19s 378ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_OWN_COLLECTION_POWDER_FACTORY" "super-admin-hochland" 003ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 357ms

When Go to new transport "OWN_COLLECTION_POWDER_FACTORY" 337ms

And Fill transport form 32s 849ms

And Click "save-transport" save button and wait for form to disappear 15s 682ms

And Set advice window in schedule 2s 169ms

And Check is transport created in schedule and set transport id 663ms

And Go to "TRANSPORT_TABLE" 191ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 462ms

Then Check are transport values equals 4s 320ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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 387ms

When Go to new transport "EXPORT" 393ms

And Fill transport form 40s 893ms

And Click "save-transport" save button and wait for form to disappear 15s 596ms

And Set advice window in schedule 2s 163ms

And Check is transport created in schedule and set transport id 638ms

And Go to "TRANSPORT_TABLE" 193ms

And Go to transport details "EXPORT" 4s 650ms

Then Check are transport values equals 4s 402ms

Hooks

After Hooks.deleteTransportAfterTest() 144ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-skd" 003ms

And Login as "swiss-krono-delivery-admin" and set token of apiUsername "super-admin-skd" 2s 490ms

When Go to new transport "DELIVERY" 15s 214ms

And Fill transport form 28s 418ms

And Click "save-transport" save button and wait for form to disappear 15s 615ms

And Set advice window in schedule 2s 169ms

And Check is transport created in schedule and set transport id 729ms

And Go to "TRANSPORT_TABLE" 238ms

And Go to transport details "DELIVERY" 32s 348ms

Then Check are transport values equals 36s 398ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-lantmannen" 002ms

And Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 135ms

When Go to new transport "DELIVERY" 323ms

And Fill transport form 38s 085ms

And Click "save-transport" save button and wait for form to disappear 15s 596ms

And Set advice window in schedule 2s 168ms

And Check is transport created in schedule and set transport id 599ms

And Go to "TRANSPORT_TABLE" 199ms

And Go to transport details "DELIVERY" 4s 337ms

Then Check are transport values equals 19s 337ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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 132ms

When Go to new transport "LOAD" 339ms

And Fill transport form 38s 070ms

And Click "save-transport" save button and wait for form to disappear 15s 668ms

And Set advice window in schedule 2s 170ms

And Check is transport created in schedule and set transport id 560ms

And Go to "TRANSPORT_TABLE" 246ms

And Go to transport details "LOAD" 4s 344ms

Then Check are transport values equals 19s 331ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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 214ms

When Go to new transport "UNLOAD" 319ms

And Fill transport form 37s 753ms

And Click "save-transport" save button and wait for form to disappear 15s 578ms

And Set advice window in schedule 2s 174ms

And Check is transport created in schedule and set transport id 590ms

And Go to "TRANSPORT_TABLE" 203ms

And Go to transport details "UNLOAD" 4s 331ms

Then Check are transport values equals 21s 478ms

Hooks

After Hooks.deleteTransportAfterTest() 147ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport with advice

Steps

Given Get inputs from database "CREATE_TANKER_GRANULATE_DELIVERY" "super-admin-keeeper" 002ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 207ms

When Go to new transport "TANKER_GRANULATE_DELIVERY" 337ms

And Fill transport form 37s 643ms

And Click "save-transport" save button and wait for form to disappear 15s 652ms

And Set advice window in schedule 2s 181ms

And Check is transport created in schedule and set transport id 603ms

And Go to "TRANSPORT_TABLE" 220ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 365ms

Then Check are transport values equals 21s 451ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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 142ms

When Go to new transport "DELIVERY" 325ms

And Fill transport form 22s 916ms

And Click "save-transport" save button and wait for form to disappear 15s 585ms

And Set advice window in schedule 2s 147ms

And Check is transport created in schedule and set transport id 574ms

And Go to "TRANSPORT_TABLE" 203ms

And Go to transport details "DELIVERY" 4s 355ms

Then Check are transport values equals 17s 279ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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 398ms

When Go to new transport "WEIGHING" 273ms

And Fill transport form 13s 549ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 599ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 135ms

And Go to transport details "WEIGHING" 4s 399ms

And Check are transport values equals 2s 187ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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" 001ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 124ms

When Go to new transport "TRANSPORT" 365ms

And Fill transport form 26s 833ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 633ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 144ms

And Go to transport details "TRANSPORT" 4s 453ms

And Check are transport values equals 6s 276ms

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_CONTAINER" "super-admin-adama" 002ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 198ms

When Go to new transport "CONTAINER" 349ms

And Fill transport form 11s 215ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 603ms

And Show all transport "false" 008ms

And Go to "TRANSPORT_TABLE" 134ms

And Go to transport details "CONTAINER" 4s 380ms

And Check are transport values equals 072ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

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 413ms

When Go to new transport "TRANSFER_BETWEEN_WAREHOUSES" 340ms

And Fill transport form 12s 992ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 598ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 141ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 604ms

And Check are transport values equals 4s 193ms

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_DELIVERY" "super-admin-piast" 002ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 703ms

When Go to new transport "DELIVERY" 345ms

And Fill transport form 22s 627ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 644ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 149ms

And Go to transport details "DELIVERY" 4s 531ms

And Check are transport values equals 17s 204ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-piast" 002ms

And Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 211ms

When Go to new transport "LOAD" 348ms

And Fill transport form 26s 338ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 628ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 150ms

And Go to transport details "LOAD" 4s 522ms

And Check are transport values equals 2s 170ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_LOAD" "super-admin-keeeper" 002ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 213ms

When Go to new transport "LOAD" 288ms

And Fill transport form 24s 683ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 171ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 148ms

And Go to transport details "LOAD" 4s 388ms

And Check are transport values equals 19s 230ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_CONTAINER" "super-admin-keeeper" 002ms

And Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 143ms

When Go to new transport "CONTAINER" 288ms

And Fill transport form 24s 710ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 640ms

And Show all transport "false" 011ms

And Go to "TRANSPORT_TABLE" 159ms

And Go to transport details "CONTAINER" 4s 384ms

And Check are transport values equals 19s 258ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

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 161ms

When Go to new transport "SMALLS_IMPORT" 400ms

And Fill transport form 36s 471ms

And Click "save-transport-and-close" save button and wait for form to disappear 678ms

And Show all transport "false" 006ms

And Go to "TRANSPORT_TABLE" 112ms

And Go to transport details "SMALLS_IMPORT" 4s 440ms

And Check are transport values equals 10s 403ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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" 001ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 348ms

When Go to new transport "SMALLS_EXPORT" 393ms

And Fill transport form 36s 476ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 608ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 132ms

And Go to transport details "SMALLS_EXPORT" 4s 434ms

And Check are transport values equals 10s 413ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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 181ms

When Go to new transport "TRANSPORT_ORDER" 394ms

And Fill transport form 30s 149ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 198ms

And Show all transport "true" 093ms

And Go to "TRANSPORT_TABLE" 141ms

And Go to transport details "TRANSPORT_ORDER" 4s 414ms

And Check are transport values equals 19s 409ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_TRANSPORT_ORDER_WITHOUT_WAREHOUSES" "super-admin-adama" 003ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 143ms

When Go to new transport "TRANSPORT" 378ms

And Fill transport form 37s 771ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 611ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 151ms

And Go to transport details "TRANSPORT" 4s 432ms

And Check are transport values equals 4s 245ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_INBOUND_WITHOUT_WAREHOUSES" "super-admin-alrec" 003ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 175ms

When Go to new transport "INBOUND" 375ms

And Fill transport form 41s 145ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 676ms

And Show all transport "true" 080ms

And Go to "TRANSPORT_TABLE" 126ms

And Go to transport details "INBOUND" 4s 456ms

And Check are transport values equals 2s 309ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" "super-admin-farmacol" 002ms

And Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 1s 269ms

When Go to new transport "EXTERNAL_DELIVERY" 338ms

And Fill transport form 53s 819ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 598ms

And Show all transport "false" 009ms

And Go to "TRANSPORT_TABLE" 135ms

And Go to transport details "EXTERNAL_DELIVERY" 4s 441ms

And Check are transport values equals 4s 504ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it possible to create new transport without advice

Steps

Given Get inputs from database "CREATE_EXTERNAL_DELIVERY_WITH_TWO_UNLOAD" "dfa1-supplier" 002ms

And Login as "dfa1-supplier" and set token of apiUsername "dfa1-supplier" 6s 065ms

When Go to new transport "EXTERNAL_DELIVERY" 15s 260ms

And Fill transport form 47s 473ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 119ms

And Show all transport "false" 010ms

And Go to "TRANSPORT_TABLE" 146ms

And Go to transport details "EXTERNAL_DELIVERY" 32s 431ms

And Check are transport values equals 4s 502ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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 150ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 001ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 791ms

And Show all transport "false" 009ms

When Go to transport details "UNLOAD" 32s 493ms

And Fill transport form 30s 472ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 190ms

And Go to transport details "UNLOAD" 32s 466ms

Then Check are transport values equals 4s 307ms

Hooks

After Hooks.deleteTransportAfterTest() 179ms

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 122ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 001ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 221ms

And Show all transport "false" 007ms

When Go to transport details "TRANSPORT" 4s 502ms

And Fill transport form 10s 338ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 622ms

And Go to transport details "TRANSPORT" 4s 455ms

Then Check are transport values equals 4s 157ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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 198ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 189ms

And Show all transport "false" 009ms

When Go to transport details "CONTAINER" 4s 361ms

And Fill transport form 4s 723ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 591ms

And Go to transport details "CONTAINER" 4s 357ms

Then Check are transport values equals 054ms

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 646ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 279ms

And Show all transport "false" 012ms

When Go to transport details "DELIVERY" 4s 375ms

And Fill transport form 11s 571ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 583ms

And Go to transport details "DELIVERY" 4s 363ms

Then Check are transport values equals 135ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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 187ms

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 288ms

And Show all transport "false" 011ms

When Go to transport details "OWN_COLLECTION" 4s 357ms

And Fill transport form 21s 657ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 648ms

And Go to transport details "OWN_COLLECTION" 4s 355ms

Then Check are transport values equals 2s 222ms

Hooks

After Hooks.deleteTransportAfterTest() 141ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 334ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 451ms

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 4s 489ms

And Fill transport form 36s 119ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 151ms

And Go to transport details "DELIVERY" 4s 473ms

Then Check are transport values equals 10s 534ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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 389ms

And Get inputs from database "EDIT_OWN_COLLECTION" "super-admin-hochland" 002ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 352ms

And Show all transport "false" 008ms

When Go to transport details "OWN_COLLECTION" 4s 667ms

And Fill transport form 36s 746ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 143ms

And Go to transport details "OWN_COLLECTION" 4s 443ms

Then Check are transport values equals 6s 423ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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 318ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 486ms

And Show all transport "false" 010ms

When Go to transport details "EXPORT" 5s 723ms

And Fill transport form 48s 206ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 654ms

And Go to transport details "EXPORT" 4s 517ms

Then Check are transport values equals 8s 516ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 460ms

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 174ms

And Show all transport "false" 010ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 702ms

And Fill transport form 36s 179ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 706ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 447ms

Then Check are transport values equals 12s 519ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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 459ms

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 307ms

And Show all transport "false" 010ms

When Go to transport details "CISTERN_DELIVERY" 4s 503ms

And Fill transport form 27s 327ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 676ms

And Go to transport details "CISTERN_DELIVERY" 4s 391ms

Then Check are transport values equals 6s 329ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 469ms

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 269ms

And Show all transport "false" 010ms

When Go to transport details "CISTERN_COLLECTION" 4s 491ms

And Fill transport form 25s 823ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 626ms

And Go to transport details "CISTERN_COLLECTION" 4s 396ms

Then Check are transport values equals 6s 279ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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 465ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 001ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 200ms

And Show all transport "false" 008ms

When Go to transport details "WEIGHING" 4s 399ms

And Fill transport form 12s 390ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 611ms

And Go to transport details "WEIGHING" 4s 335ms

Then Check are transport values equals 2s 160ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 377ms

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 321ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 533ms

And Fill transport form 35s 183ms

And Click "save-transport-and-close" save button and wait for form to disappear 704ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 452ms

Then Check are transport values equals 6s 350ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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 148ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 310ms

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 32s 456ms

And Fill transport form 25s 720ms

And Click "save-transport-and-close" save button and wait for form to disappear 18s 801ms

And Go to transport details "DELIVERY" 32s 336ms

Then Check are transport values equals 2s 207ms

Hooks

After Hooks.deleteTransportAfterTest() 194ms

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 194ms

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 251ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 578ms

And Fill transport form 1m 2s 543ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 168ms

And Go to transport details "DELIVERY" 4s 395ms

Then Check are transport values equals 137ms

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() 094ms

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 182ms

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 222ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 705ms

And Fill transport form 57s 459ms

And Click "save-transport-and-close" save button and wait for form to disappear 695ms

And Go to transport details "LOAD" 4s 495ms

Then Check are transport values equals 24s 852ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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 168ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 384ms

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 4s 391ms

And Fill transport form 16s 441ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 656ms

And Go to transport details "DELIVERY" 4s 329ms

Then Check are transport values equals 070ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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 138ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 344ms

And Show all transport "false" 011ms

When Go to transport details "LOAD" 4s 357ms

And Fill transport form 28s 206ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 134ms

And Go to transport details "LOAD" 4s 343ms

Then Check are transport values equals 2s 234ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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 187ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 390ms

And Show all transport "false" 010ms

When Go to transport details "UNLOAD" 4s 450ms

And Fill transport form 37s 946ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 595ms

And Go to transport details "UNLOAD" 4s 340ms

Then Check are transport values equals 6s 399ms

Hooks

After Hooks.deleteTransportAfterTest() 137ms

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 326ms

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 362ms

And Show all transport "false" 013ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 437ms

And Fill transport form 36s 345ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 628ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 397ms

Then Check are transport values equals 6s 418ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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 218ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 223ms

And Show all transport "false" 011ms

When Go to transport details "LOAD" 4s 407ms

And Fill transport form 24s 735ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 636ms

And Go to transport details "LOAD" 4s 371ms

Then Check are transport values equals 4s 220ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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 202ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 190ms

And Show all transport "false" 012ms

When Go to transport details "CONTAINER" 4s 391ms

And Fill transport form 24s 758ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 606ms

And Go to transport details "CONTAINER" 4s 349ms

Then Check are transport values equals 4s 210ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

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 266ms

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 309ms

And Show all transport "false" 011ms

When Go to transport details "SMALLS_IMPORT" 4s 528ms

And Fill transport form 33s 095ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 657ms

And Go to transport details "SMALLS_IMPORT" 4s 422ms

Then Check are transport values equals 8s 350ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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 230ms

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 241ms

And Show all transport "false" 010ms

When Go to transport details "SMALLS_EXPORT" 4s 523ms

And Fill transport form 33s 104ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 626ms

And Go to transport details "SMALLS_EXPORT" 4s 413ms

Then Check are transport values equals 8s 359ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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 183ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 418ms

And Show all transport "true" 089ms

When Go to transport details "DELIVERY" 4s 362ms

And Fill transport form 19s 596ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 612ms

And Go to transport details "DELIVERY" 4s 365ms

Then Check are transport values equals 193ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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_TRANSPORT_ORDER" "super-admin-alrec" 001ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 321ms

And Show all transport "true" 077ms

When Go to transport details "TRANSPORT_ORDER" 4s 484ms

And Fill transport form 26s 825ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 638ms

And Go to transport details "TRANSPORT_ORDER" 4s 401ms

Then Check are transport values equals 2s 253ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to edit transport

Steps

Given Login as "keeeper-warehouseman" and set token of apiUsername "super-admin-keeeper" 2s 734ms

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 206ms

And Show all transport "false" 011ms

When Go to transport details "CONTAINER" 4s 409ms

And Fill transport form 8s 908ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 601ms

And Go to transport details "CONTAINER" 4s 420ms

Then Check are transport values equals 4s 113ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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 432ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 405ms

And Show all transport "false" 010ms

When Delete transport 17s 969ms

Then Transport not displayed in table of transports 15s 039ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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 236ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 203ms

And Show all transport "false" 010ms

When Delete transport 17s 208ms

Then Transport not displayed in table of transports 15s 071ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

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 162ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 392ms

And Show all transport "false" 009ms

When Delete transport 17s 490ms

Then Transport not displayed in table of transports 15s 068ms

Hooks

After Hooks.deleteTransportAfterTest() 065ms

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 202ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 195ms

And Show all transport "false" 010ms

When Delete transport 17s 081ms

Then Transport not displayed in table of transports 15s 054ms

Hooks

After Hooks.deleteTransportAfterTest() 064ms

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 284ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 439ms

And Show all transport "false" 012ms

When Delete transport 17s 649ms

Then Transport not displayed in table of transports 15s 018ms

Hooks

After Hooks.deleteTransportAfterTest() 080ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 261ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 242ms

And Show all transport "false" 010ms

When Delete transport 17s 696ms

Then Transport not displayed in table of transports 15s 060ms

Hooks

After Hooks.deleteTransportAfterTest() 079ms

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 186ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 399ms

And Show all transport "true" 071ms

When Delete transport 19s 089ms

Then Transport not displayed in table of transports 15s 053ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to delete transport

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 132ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 320ms

And Show all transport "true" 082ms

When Delete transport 17s 132ms

Then Transport not displayed in table of transports 15s 058ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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 041ms

And Get inputs from database "EDIT_UNLOAD" "super-admin-pgf" 001ms

And Create transport "CREATE_UNLOAD" by JSON file as "super-admin-pgf" 15s 665ms

And Show all transport "false" 010ms

When Go to transport details "UNLOAD" 32s 494ms

And Fill transport form 30s 533ms

And Click "save-transport" save button 1s 276ms

And Click cancel button in transport form 098ms

And Go to transport details "UNLOAD" 32s 388ms

Then Check are transport values equals 4s 280ms

Hooks

After Hooks.deleteTransportAfterTest() 148ms

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 149ms

And Get inputs from database "EDIT_TRANSPORT" "super-admin-adama" 001ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 274ms

And Show all transport "false" 011ms

When Go to transport details "TRANSPORT" 4s 479ms

And Fill transport form 10s 297ms

And Click "save-transport" save button 751ms

And Click cancel button in transport form 083ms

And Go to transport details "TRANSPORT" 4s 346ms

Then Check are transport values equals 4s 142ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 171ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-adama" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 190ms

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 379ms

And Fill transport form 4s 740ms

And Click "save-transport" save button 718ms

And Click cancel button in transport form 070ms

And Go to transport details "CONTAINER" 4s 282ms

Then Check are transport values equals 046ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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 202ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-adama" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 308ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 388ms

And Fill transport form 11s 653ms

And Click "save-transport" save button 704ms

And Click cancel button in transport form 076ms

And Go to transport details "DELIVERY" 4s 256ms

Then Check are transport values equals 125ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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 136ms

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 296ms

And Show all transport "false" 009ms

When Go to transport details "OWN_COLLECTION" 4s 352ms

And Fill transport form 21s 670ms

And Click "save-transport" save button 717ms

And Click cancel button in transport form 074ms

And Go to transport details "OWN_COLLECTION" 4s 307ms

Then Check are transport values equals 2s 219ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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 448ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 313ms

And Show all transport "false" 011ms

When Go to transport details "DELIVERY" 4s 546ms

And Fill transport form 36s 029ms

And Click "save-transport" save button 1s 249ms

And Click cancel button in transport form 120ms

And Go to transport details "DELIVERY" 4s 426ms

Then Check are transport values equals 10s 597ms

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 "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 486ms

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 286ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION" 4s 682ms

And Fill transport form 36s 697ms

And Click "save-transport" save button 1s 255ms

And Click cancel button in transport form 105ms

And Go to transport details "OWN_COLLECTION" 4s 403ms

Then Check are transport values equals 6s 383ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 502ms

And Get inputs from database "EDIT_EXPORT" "super-admin-hochland" 001ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 342ms

And Show all transport "false" 006ms

When Go to transport details "EXPORT" 5s 649ms

And Fill transport form 48s 103ms

And Click "save-transport" save button 1s 259ms

And Click cancel button in transport form 098ms

And Go to transport details "EXPORT" 4s 443ms

Then Check are transport values equals 8s 462ms

Hooks

After Hooks.deleteTransportAfterTest() 167ms

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 536ms

And Get inputs from database "EDIT_TRANSFER_BETWEEN_WAREHOUSES" "super-admin-hochland" 001ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 175ms

And Show all transport "false" 010ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 692ms

And Fill transport form 36s 142ms

And Click "save-transport" save button 882ms

And Click cancel button in transport form 079ms

And Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 407ms

Then Check are transport values equals 12s 501ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 484ms

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 299ms

And Show all transport "false" 010ms

When Go to transport details "CISTERN_DELIVERY" 4s 531ms

And Fill transport form 27s 263ms

And Click "save-transport" save button 768ms

And Click cancel button in transport form 089ms

And Go to transport details "CISTERN_DELIVERY" 4s 368ms

Then Check are transport values equals 6s 318ms

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 "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 537ms

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 280ms

And Show all transport "false" 010ms

When Go to transport details "CISTERN_COLLECTION" 4s 471ms

And Fill transport form 25s 915ms

And Click "save-transport" save button 761ms

And Click cancel button in transport form 077ms

And Go to transport details "CISTERN_COLLECTION" 4s 323ms

Then Check are transport values equals 6s 286ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 409ms

And Get inputs from database "EDIT_WEIGHING" "super-admin-hochland" 001ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 216ms

And Show all transport "false" 008ms

When Go to transport details "WEIGHING" 4s 402ms

And Fill transport form 12s 399ms

And Click "save-transport" save button 709ms

And Click cancel button in transport form 085ms

And Go to transport details "WEIGHING" 4s 314ms

Then Check are transport values equals 2s 164ms

Hooks

After Hooks.deleteTransportAfterTest() 056ms

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 399ms

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 306ms

And Show all transport "false" 010ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 534ms

And Fill transport form 35s 261ms

And Click "save-transport" save button 898ms

And Click cancel button in transport form 097ms

And Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 399ms

Then Check are transport values equals 6s 352ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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 152ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-skd" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 297ms

And Show all transport "false" 005ms

When Go to transport details "DELIVERY" 32s 416ms

And Fill transport form 25s 712ms

And Click "save-transport" save button 728ms

And Click cancel button in transport form 084ms

And Go to transport details "DELIVERY" 32s 388ms

Then Check are transport values equals 2s 212ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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 178ms

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 187ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 567ms

And Fill transport form 1m 2s 638ms

And Click "save-transport" save button 1s 235ms

And Click cancel button in transport form 084ms

And Go to transport details "DELIVERY" 4s 375ms

Then Check are transport values equals 133ms

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() 169ms

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 256ms

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 266ms

And Show all transport "false" 012ms

When Go to transport details "LOAD" 4s 699ms

And Fill transport form 57s 442ms

And Click "save-transport" save button 1s 248ms

And Click cancel button in transport form 067ms

And Go to transport details "LOAD" 4s 413ms

Then Check are transport values equals 24s 805ms

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 109ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-lantmannen" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 426ms

And Show all transport "false" 010ms

When Go to transport details "DELIVERY" 4s 385ms

And Fill transport form 16s 478ms

And Click "save-transport" save button 715ms

And Click cancel button in transport form 076ms

And Go to transport details "DELIVERY" 4s 295ms

Then Check are transport values equals 072ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 1s 026ms

And Get inputs from database "EDIT_LOAD" "super-admin-lantmannen" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 286ms

And Show all transport "false" 010ms

When Go to transport details "LOAD" 4s 333ms

And Fill transport form 28s 227ms

And Click "save-transport" save button 1s 246ms

And Click cancel button in transport form 081ms

And Go to transport details "LOAD" 4s 340ms

Then Check are transport values equals 2s 244ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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 262ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-keeeper" 002ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 357ms

And Show all transport "false" 007ms

When Go to transport details "UNLOAD" 4s 423ms

And Fill transport form 38s

And Click "save-transport" save button 757ms

And Click cancel button in transport form 078ms

And Go to transport details "UNLOAD" 4s 335ms

Then Check are transport values equals 6s 408ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 178ms

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 353ms

And Show all transport "false" 007ms

When Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 421ms

And Fill transport form 36s 334ms

And Click "save-transport" save button 771ms

And Click cancel button in transport form 109ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 306ms

Then Check are transport values equals 6s 396ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 176ms

And Get inputs from database "EDIT_LOAD" "super-admin-keeeper" 001ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 194ms

And Show all transport "false" 009ms

When Go to transport details "LOAD" 4s 412ms

And Fill transport form 24s 833ms

And Click "save-transport" save button 726ms

And Click cancel button in transport form 071ms

And Go to transport details "LOAD" 4s 314ms

Then Check are transport values equals 4s 213ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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 199ms

And Get inputs from database "EDIT_CONTAINER" "super-admin-keeeper" 001ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 219ms

And Show all transport "false" 010ms

When Go to transport details "CONTAINER" 4s 398ms

And Fill transport form 24s 736ms

And Click "save-transport" save button 726ms

And Click cancel button in transport form 067ms

And Go to transport details "CONTAINER" 4s 322ms

Then Check are transport values equals 4s 193ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 238ms

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 255ms

And Show all transport "false" 011ms

When Go to transport details "SMALLS_IMPORT" 4s 515ms

And Fill transport form 33s 114ms

And Click "save-transport" save button 763ms

And Click cancel button in transport form 074ms

And Go to transport details "SMALLS_IMPORT" 4s 361ms

Then Check are transport values equals 8s 345ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

View Feature Crud Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible use save and cancel combination after editing transport

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 379ms

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 259ms

And Show all transport "false" 009ms

When Go to transport details "SMALLS_EXPORT" 4s 524ms

And Fill transport form 33s 155ms

And Click "save-transport" save button 723ms

And Click cancel button in transport form 085ms

And Go to transport details "SMALLS_EXPORT" 4s 349ms

Then Check are transport values equals 8s 341ms

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 "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 169ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-alrec" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 394ms

And Show all transport "true" 074ms

When Go to transport details "DELIVERY" 4s 369ms

And Fill transport form 19s 627ms

And Click "save-transport" save button 711ms

And Click cancel button in transport form 094ms

And Go to transport details "DELIVERY" 4s 314ms

Then Check are transport values equals 156ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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 163ms

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 264ms

And Show all transport "true" 071ms

When Go to transport details "TRANSPORT_ORDER" 4s 443ms

And Fill transport form 26s 831ms

And Click "save-transport" save button 733ms

And Click cancel button in transport form 079ms

And Go to transport details "TRANSPORT_ORDER" 4s 313ms

Then Check are transport values equals 2s 258ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Crud Transport

@deleteTransportAfterTest @deleteAllGrayWindowsAfterTest

Scenario Outline Check if firstPossibleStart algorithm works properly when creating transport advice

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 201ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 1s 248ms

And Create gray windows "CREATE_GRAY_WINDOW_MWG" on "PRZESYŁKI DROBNICOWE" in "Magazyn Wyrobów Gotowych" as "super-admin-keeeper" 275ms

And If user is login then logout 108ms

Then Login as "dka1-supplier" 2s 557ms

And Click button advice in transport table "LOAD" 215ms

And Check if moved to first possible start date in schedule 420ms

Hooks

After Hooks.deleteTransportAfterTest() 062ms

After Hooks.deleteAllGrayWindowsAfterTest() 1m 30s 492ms

View Feature Crud Transport

@deleteTransportAfterTest @deleteAddressAfterTest

Scenario Outline Check if it is possible to create transport with new address [A-7158]

Steps

Given Set token of apiUsername "super-admin-piast" 097ms

And Set "transport" inputs from JSON file "CREATE_LOAD_WITH_NEW_ADDRESS" "super-admin-piast" 007ms

When Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 337ms

Then Go to new transport "LOAD" 345ms

And Fill transport form 27s 431ms

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" 094ms

When Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 262ms

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 201ms

And Go to transport details "LOAD" 4s 851ms

And Fill transport form 16s 094ms

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() 000ms

After Hooks.deleteTransportAfterTest() 064ms

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 223ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 213ms

When Go to "TRANSPORT_TABLE" 134ms

And Show all transport types 1s 042ms

And Verify that transport has "0" files 035ms

Then Add file to transport by API 405ms

And Verify that transport has "1" files 623ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

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 088ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 191ms

When Go to "TRANSPORT_TABLE" 122ms

And Show all transport types 1s 044ms

And Verify that transport has "0" files 040ms

Then Add file to transport by API 209ms

And Verify that transport has "1" files 568ms

Hooks

After Hooks.deleteTransportAfterTest() 071ms

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 357ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 339ms

When Go to "TRANSPORT_TABLE" 133ms

And Show all transport types 1s 043ms

And Verify that transport has "0" files 040ms

Then Add file to transport by API 235ms

And Verify that transport has "1" files 388ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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 078ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 200ms

When Go to "TRANSPORT_TABLE" 132ms

And Show all transport types 1s 043ms

And Verify that transport has "0" files 036ms

Then Add file to transport by API 233ms

And Verify that transport has "1" files 870ms

Hooks

After Hooks.deleteTransportAfterTest() 061ms

View Feature Transport files

@deleteTransportAfterTest

Scenario Outline Check if it possible to add file to transport in archive

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 1s 087ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 176ms

And Delete transport 17s 225ms

When Go to "ARCHIVE_TAB" 245ms

And Show "DELIVERY" 056ms

And Verify that transport has "0" files 710ms

Then Add file to transport 153ms

And Verify that transport has "1" files 370ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

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 237ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 199ms

And Delete transport 17s 355ms

When Go to "ARCHIVE_TAB" 278ms

And Show "LOAD" 087ms

And Verify that transport has "0" files 1s 170ms

Then Add file to transport 158ms

And Verify that transport has "1" files 368ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

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 389ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 434ms

And Delete transport 17s 890ms

When Go to "ARCHIVE_TAB" 215ms

And Show "DELIVERY" 061ms

And Verify that transport has "0" files 1s 002ms

Then Add file to transport 159ms

And Verify that transport has "1" files 380ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

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 155ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-keeeper" 1s 194ms

And Delete transport 17s 608ms

When Go to "ARCHIVE_TAB" 262ms

And Show "CONTAINER" 089ms

And Verify that transport has "0" files 1s 100ms

Then Add file to transport 139ms

And Verify that transport has "1" files 343ms

Hooks

After Hooks.deleteTransportAfterTest() 070ms

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" 102ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 15s 226ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 110ms

And Set token of apiUsername "paa1-carrier@qa.qa-test" 093ms

And Accept transferred transport by Api 210ms

And Login as "paa1-carrier@qa.qa-test" 1s 018ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 16s 248ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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 184ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 185ms

And Transfer transport to carrier by JSON file "super-admin-adama" "false" confirmation 105ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 17s 881ms

Hooks

After Hooks.deleteTransportAfterTest() 3s 216ms

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" 104ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 220ms

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 170ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 410ms

And Login as "paa1-carrier@qa.qa-test" 1s 092ms

Then Verify that "large_entrepreneur_declaration" document can be downloaded 16s 144ms

Hooks

After Hooks.deleteTransportAfterTest() 112ms

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 221ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 301ms

When Go to "TRANSPORT_TABLE" 139ms

And Show all transport "true" 075ms

Then Verify that transport has "1" CMR file 1s 195ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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 107ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 244ms

When Go to "TRANSPORT_TABLE" 125ms

And Show all transport "true" 066ms

Then Verify that transport has "2" CMR file 1s 193ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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 065ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 277ms

When Go to "TRANSPORT_TABLE" 118ms

And Show all transport "true" 076ms

Then Verify that "CMR" document can be downloaded 17s 559ms

Hooks

After Hooks.deleteTransportAfterTest() 064ms

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 172ms

And Create transport "CREATE_TRANSPORT_TWO_UNLOAD_STEPS" by JSON file as "super-admin-alrec" 1s 263ms

And Show all transport "true" 087ms

And Delete transport 17s 173ms

When Go to "ARCHIVE_TAB" 219ms

And Show "TRANSPORT_ORDER" 052ms

Then Verify that "CMR" document can be downloaded 16s 785ms

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 701ms

And Create default accepted mode of transportation by API with "pba1-carrier" 406ms

And If user is login then logout 090ms

And Login as "bausch-admin" and set token of apiUsername "super-admin-bausch" 1s 343ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 257ms

And Transfer transport to carrier by JSON file "super-admin-bausch" "false" confirmation 104ms

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-bausch" 009ms

And Click button advice in transport table "LOAD_PL" 1s 842ms

And Set advice window in schedule 2s 861ms

And Fill advice form 9s 255ms

And Click advice save button and wait for advice form to disappear 16s 013ms

And Find transport in table with status "advice-added" 3s 335ms

When Confirm statuses until reach "on-the-way" 9s 372ms

Then Verify that "delivery_document" document can be downloaded 16s 444ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

After Hooks.deleteModeOfTransportationAfterTest() 078ms

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 527ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 423ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 256ms

And Click pencil and move transport to next day in schedule 16s 394ms

Then Check if transport is in new location in schedule 2s 121ms

And Check if dates in transport form are correct 3s 454ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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 174ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 256ms

And Show all transport "false" 007ms

When Find transport pencil button in transports table 1s 225ms

And Click pencil and move transport to next day in schedule 16s 715ms

Then Check if transport is in new location in schedule 2s 130ms

And Check if dates in transport form are correct 3s 344ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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 115ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 281ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 265ms

And Click pencil and move transport to next day in schedule 16s 917ms

Then Check if transport is in new location in schedule 2s 125ms

And Check if dates in transport form are correct 3s 407ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 174ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 366ms

And Show all transport "false" 009ms

When Find transport pencil button in transports table 1s 262ms

And Click pencil and move transport to next day in schedule 16s 361ms

Then Check if transport is in new location in schedule 2s 119ms

And Check if dates in transport form are correct 3s 314ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

View Feature Edit transport using pencil

@deleteTransportAfterTest

Scenario Outline Check if it possible to edit transport by pencil

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 150ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 366ms

And Show all transport "false" 005ms

When Find transport pencil button in transports table 1s 214ms

And Click pencil and move transport to next day in schedule 16s 361ms

Then Check if transport is in new location in schedule 2s 108ms

And Check if dates in transport form are correct 3s 374ms

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 "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 166ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-alrec" 1s 400ms

And Show all transport "true" 086ms

When Find transport pencil button in transports table 1s 237ms

And Click pencil and move transport to next day in schedule 16s 502ms

Then Check if transport is in new location in schedule 2s 131ms

And Check if dates in transport form are correct 3s 454ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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 209ms

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 1s 198ms

And Get inputs from database "ADVICE_DELIVERY" "super-admin-piast" 002ms

When Show all transport types 1s 035ms

And Click button advice in transport table "DELIVERY" 137ms

And Set advice window in schedule 2s 604ms

And Fill advice form 8s 470ms

And Click advice save button and wait for advice form to disappear 30s 722ms

And Go to "TRANSPORT_TABLE" 251ms

And Find transport pencil button in transports table 1s 241ms

And Click pencil and move transport to next day in schedule 17s 630ms

Then Check if transport is in new location in schedule 2s 124ms

And Check if dates in transport form are correct 3s 467ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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 945ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 369ms

And Show all transport "false" 009ms

When Find transport pencil button in transports table 1s 256ms

And Click pencil and move transport to next day in schedule 16s 352ms

And Move advice window "3" 1s 360ms

Then Check if advice window is in new location 018ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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 157ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 267ms

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 676ms

And Move advice window "3" 1s 356ms

Then Check if advice window is in new location 027ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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 055ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 299ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 213ms

And Click pencil and move transport to next day in schedule 16s 947ms

And Move advice window "3" 1s 551ms

Then Check if advice window is in new location 030ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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 219ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 330ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 245ms

And Click pencil and move transport to next day in schedule 16s 289ms

And Move advice window "3" 1s 314ms

Then Check if advice window is in new location 026ms

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 096ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 315ms

And Show all transport "false" 010ms

When Find transport pencil button in transports table 1s 240ms

And Click pencil and move transport to next day in schedule 16s 283ms

And Move advice window "3" 1s 326ms

Then Check if advice window is in new location 026ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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 147ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 302ms

And Show all transport "true" 065ms

When Find transport pencil button in transports table 1s 213ms

And Click pencil and move transport to next day in schedule 16s 416ms

And Move advice window "3" 1s 357ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

View Feature Transport Form - Discrepancy Report scenarios

@deleteTransportAfterTest

Scenario Outline Check if discrepancy report custom fields are visible in proper section

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 1s 452ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 393ms

And Go to transport details "DELIVERY" 4s 751ms

When Open section: "discrepancy-report-panel" 1s 075ms

Then Verify that no discrepancies found label is visible in discrepancy report section 076ms

And Select "NIE" in the "insp.-accord.-with-ins." 2s 447ms

And Verify that discrepancy report custom fields are visible in discrepancy report section 113ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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 354ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 410ms

And Go to transport details "DELIVERY" 4s 624ms

And Fill transport form 35s 893ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 136ms

When Go to transport details "DELIVERY" 4s 432ms

Then Select "NIE" in the "insp.-accord.-with-ins." 2s 438ms

And Click "save-transport" save button 725ms

And Wait "2" seconds 2s

And Verify that discrepancy report section is open 030ms

And Verify that discrepancy report section contains validation errors 019ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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_DELIVERY" by JSON file as "super-admin-hochland" 1s 378ms

When Go to transport details "DELIVERY" 4s 760ms

Then Verify that discrepancy report section is available 045ms

And Open section: "discrepancy-report-panel" 1s 066ms

And Verify that generate new discrepancy report button is visible 037ms

Hooks

After Hooks.deleteTransportAfterTest() 150ms

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 230ms

And Create transport "CREATE_OWN_COLLECTION" by JSON file as "super-admin-hochland" 1s 298ms

When Go to transport details "OWN_COLLECTION" 4s 617ms

Then Verify that discrepancy report section is available 037ms

And Open section: "discrepancy-report-panel" 1s 068ms

And Verify that generate new discrepancy report button is visible 034ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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 402ms

And Create transport "CREATE_OWN_COLLECTION_POWDER_FACTORY" by JSON file as "super-admin-hochland" 1s 320ms

When Go to transport details "OWN_COLLECTION_POWDER_FACTORY" 4s 554ms

Then Verify that discrepancy report section is available 032ms

And Open section: "discrepancy-report-panel" 1s 059ms

And Verify that generate new discrepancy report button is visible 028ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

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 350ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 1s 363ms

When Go to transport details "EXPORT" 5s 676ms

Then Verify that discrepancy report section is available 032ms

And Open section: "discrepancy-report-panel" 1s 064ms

And Verify that generate new discrepancy report button is visible 034ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

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 298ms

And Create transport "CREATE_TRANSFER_BETWEEN_WAREHOUSES" by JSON file as "super-admin-hochland" 1s 186ms

When Go to transport details "TRANSFER_BETWEEN_WAREHOUSES" 4s 695ms

Then Verify that discrepancy report section is available 040ms

And Open section: "discrepancy-report-panel" 1s 066ms

And Verify that generate new discrepancy report button is visible 034ms

Hooks

After Hooks.deleteTransportAfterTest() 062ms

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 327ms

And Create transport "CREATE_CISTERN_DELIVERY" by JSON file as "super-admin-hochland" 1s 323ms

When Go to transport details "CISTERN_DELIVERY" 4s 491ms

Then Verify that discrepancy report section is not available 15s 025ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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 399ms

And Create transport "CREATE_CISTERN_COLLECTION" by JSON file as "super-admin-hochland" 1s 329ms

When Go to transport details "CISTERN_COLLECTION" 4s 458ms

Then Verify that discrepancy report section is not available 15s 031ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

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 419ms

And Create transport "CREATE_WEIGHING" by JSON file as "super-admin-hochland" 1s 202ms

When Go to transport details "WEIGHING" 4s 387ms

Then Verify that discrepancy report section is not available 15s 039ms

Hooks

After Hooks.deleteTransportAfterTest() 055ms

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 461ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 349ms

When Go to "TRANSPORT_TABLE" 165ms

And Go to transport details "DELIVERY" 4s 746ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 516ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 328ms

And Open section: "discrepancy-report-panel" 1s 077ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 002ms

And Fill transport form 36s 056ms

And Fill discrepancy report section without closing the form 19s 675ms

And Generate discrepancy report 16s 746ms

And Download discrepancy report 175ms

Then Verify that discrepancy report file has correct values 15s 135ms

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() 120ms

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 615ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 361ms

When Go to "TRANSPORT_TABLE" 156ms

And Go to transport details "DELIVERY" 4s 734ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 002ms

And Fill transport form 36s 112ms

And Open section: "discrepancy-report-panel" 1s 082ms

And Fill discrepancy report section without closing the form 19s 670ms

And Generate discrepancy report 16s 213ms

And Download discrepancy report 173ms

And Verify that discrepancy report file has correct values 15s 155ms

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() 113ms

View Feature Transport Form - Steps section scenarios

@deleteTransportAfterTest @rollbackAddedActionAuthorities @rollbackTransportTypeSettings

Scenario Outline Check if added step is saved with transport

Steps

Given Set token of apiUsername "super-admin-piast" 091ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 048ms

And Get "LOAD" settings from "piast" 030ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "false" 064ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-piast" 1s 183ms

And Login as "piast-admin" 1s 787ms

And Go to "TRANSPORT_TABLE" 199ms

When Go to transport details "LOAD" 4s 679ms

And Add step "unload" 131ms

And Change filled value in transport details "company-step-2" "autocomplete" "DPA2" "0" 6s 509ms

And Change filled value in transport details "recipient-step-2" "autocomplete" "Testowy" "0" 6s 544ms

Then Click "save-transport-and-close" save button and wait for form to disappear 15s 601ms

And Go to transport details "LOAD" 4s 576ms

And Verify that transport has "3" steps 022ms

Hooks

After Hooks.rollbackTransportTypeSettings() 062ms

After Hooks.rollbackAddedActionAuthorities() 053ms

After Hooks.deleteTransportAfterTest() 061ms

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 173ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 252ms

When Go to "TRANSPORT_TABLE" 125ms

And Go to transport details "SMALLS_IMPORT" 17s 123ms

Then Verify that user can't edit time range for load and unload 15s 043ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

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" 090ms

And Create transport "CREATE_DELIVERY_TWO_LOADS" by JSON file as "super-admin-neuca" 1s 505ms

And Login as "neuca-admin" 901ms

And Go to "TRANSPORT_TABLE" 210ms

And Show all transport types 15s 026ms

When Go to transport details "DELIVERY" 32s 527ms

Then Check if sum of number of pallets in transport form in "load" steps is correct 072ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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" 094ms

And Create transport "CREATE_EXPORT" by JSON file as "super-admin-hochland" 15s 404ms

And Login as "hochland-admin" 1s 491ms

And Go to "TRANSPORT_TABLE" 124ms

And Show all transport types 1s 048ms

When Go to transport details "EXPORT" 5s 605ms

Then Check if sum of number of pallets in transport form in "unload" steps is correct 068ms

Hooks

After Hooks.deleteTransportAfterTest() 156ms

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" 106ms

And Get "DELIVERY" settings from "neuca" 042ms

And Set transportType settings with values: "quantitySumCheckValue", "33" 123ms

And Login as "neuca-admin" 869ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-neuca" 15s 290ms

When Go to "TRANSPORT_TABLE" 233ms

And Go to transport details "DELIVERY" 32s 451ms

And Set number of pallets in "load" step in transport - "32" 127ms

And Check if number of pallets check message is not visible in transport form 15s 025ms

And Set number of pallets in "load" step in transport - "34" 141ms

Then Check if number of pallets check message is visible in transport form 047ms

Hooks

After Hooks.rollbackTransportTypeSettings() 091ms

After Hooks.deleteTransportAfterTest() 104ms

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" 100ms

And Add action authority with: "farmacol" "farmacol-admin" "EXTERNAL_DELIVERY" "ADD_UNLOAD_STEP_FROM_UNLOAD" "ACTIVE" 091ms

And Get "EXTERNAL_DELIVERY" settings from "farmacol" 051ms

And Set transportType settings with values: "isUnloadStepInWarehouseByDefault", "true" 068ms

And Login as "farmacol-admin" 2s 261ms

And Go to new transport "EXTERNAL_DELIVERY" 316ms

And Add step "unload" 107ms

And Click "save-transport-and-close" save button 684ms

Then Verify that "time-range-from-date-2" has validation error 1s 029ms

Then Verify that "time-range-to-date-2" has validation error 1s 027ms

And Change filled value in transport details "time-range-from-date-2" "date" "" "0" 3s 326ms

And Click "save-transport-and-close" save button 698ms

And Verify that "time-range-from-date-2" has no validation error 018ms

And Verify that "time-range-to-date-2" has no validation error 019ms

Hooks

After Hooks.rollbackTransportTypeSettings() 074ms

After Hooks.rollbackAddedActionAuthorities() 069ms

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" 094ms

And Add action authority with: "piast" "piast-admin" "LOAD" "ADD_LOAD_STEP_FROM_UNLOAD" "ACTIVE" 058ms

And Create transport "CREATE_LOAD_FRONT" by JSON file as "super-admin-piast" 1s 202ms

When Login as "piast-admin" 1s 842ms

And Go to transport details "LOAD" 4s 782ms

And Get inputs from database "PIAST_LOAD_ADD_UNLOAD_STEP" "super-admin-piast" 002ms

And Add step "unload" 117ms

And Fill step data 15s 107ms

And Get inputs from database "PIAST_LOAD_ADD_LOAD_STEP" "super-admin-piast" 002ms

And Add step "load" 125ms

And Fill step data 5s 460ms

And Click "save-transport-and-close" save button and wait for form to disappear 703ms

Then Go to transport details "LOAD" 4s 541ms

And Check if "unload" step is added as "3" step in transport form 042ms

And Check if "load" step is added as "4" step in transport form 032ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 056ms

After Hooks.deleteTransportAfterTest() 094ms

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" 087ms

And Add action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_LOAD_STEPS" "UNLIMITED" 049ms

And Remove action authority with: "swisskrono" "super-admin-skz" "SMALLS_EXPORT" "MOVE_UNLOAD_STEPS" "UNLIMITED" 005ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 206ms

When Login as "super-admin-skz" 2s 118ms

And Go to transport details "SMALLS_EXPORT" 4s 485ms

And Check if step is draggable "LOAD" 032ms

And Check if step is not draggable "UNLOAD" 025ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 052ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

After Hooks.deleteTransportAfterTest() 086ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest @ADAMA_NIE_DZIAŁA_PRZEZ_A-7134

Scenario Outline Check if transport created without advice by similar button has correct values

Steps

Given Set "transport" inputs from JSON file "CREATE_SMALLS_IMPORT" "super-admin-skz" 005ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 098ms

When Go to new transport "SMALLS_IMPORT" 355ms

And Fill transport form 19s 901ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 633ms

And Show all transport "false" 011ms

And Go to transport details "SMALLS_IMPORT" 4s 435ms

And Click create similar button 15s 185ms

And Fill "transport" form "CREATE_SIMILAR_SMALLS_IMPORT" by "super-admin-skz" 001ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 598ms

And Open similar transport details 282ms

Then Check are transport values equals 2s 119ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

After Hooks.deleteSimilarTransportAfterTest() 072ms

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" 007ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 970ms

When Go to new transport "TRANSPORT_ORDER" 364ms

And Fill transport form 23s 970ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 642ms

And Show all transport "true" 087ms

And Go to transport details "TRANSPORT_ORDER" 4s 422ms

And Click create similar button 15s 182ms

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 639ms

And Open similar transport details 272ms

Then Check are transport values equals 2s 199ms

Hooks

After Hooks.deleteTransportAfterTest() 1s 045ms

After Hooks.deleteSimilarTransportAfterTest() 074ms

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 140ms

When Go to new transport "TRANSPORT" 399ms

And Fill transport form 26s 716ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 651ms

And Show all transport "false" 008ms

And Go to transport details "TRANSPORT" 4s 461ms

And Click create similar button 15s 212ms

And Fill "transport" form "CREATE_SIMILAR_TRANSPORT" by "super-admin-adama" 1s 341ms

And Click "save-transport-and-close" save button and wait for form to disappear 10s 186ms

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.cTgIHr}, 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: 1968d0bcafa471a25cdc53a4d1bd1dd3
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:198)
	at Pages.Transport.TransportFormPage.clickSaveButtonAndWaitForFormToDisappear(TransportFormPage.java:192)
	at CucumberTests.Transport.CreateTransport.clickSaveButtonAndWaitForFormToDisappear(CreateTransport.java:188)
	at ✽.Click "save-transport-and-close" save button and wait for form to disappear(file:Features/Atom/Transport/TransportForm/TransportForm.feature:14)

And Open similar transport details 000ms

Then Check are transport values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

After Hooks.deleteSimilarTransportAfterTest() 000ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

Scenario Outline Check if transport created with advice by similar button has correct values

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "pna1-carrier" 006ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 2s 659ms

When Go to new transport "DELIVERY" 15s 342ms

And Fill transport form 35s 946ms

And Click "save-transport" save button and wait for form to disappear 15s 727ms

And Set advice window in schedule 2s 167ms

And Check is transport created in schedule and set transport id 914ms

And Go to "TRANSPORT_TABLE" 212ms

And Go to transport details "DELIVERY" 32s 344ms

And Click create similar button 15s 181ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 9s 546ms

And Click "save-transport" save button and wait for form to disappear 15s 586ms

And Set advice window in schedule in "2" days 4s 206ms

And Go to "TRANSPORT_TABLE" 221ms

And Open similar transport details 496ms

Then Check are transport values equals 23s 483ms

Hooks

After Hooks.deleteTransportAfterTest() 162ms

After Hooks.deleteSimilarTransportAfterTest() 111ms

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 219ms

When Go to new transport "DELIVERY" 308ms

And Fill transport form 15s 521ms

And Click "save-transport" save button and wait for form to disappear 15s 631ms

And Set advice window in schedule 2s 166ms

And Check is transport created in schedule and set transport id 568ms

And Go to "TRANSPORT_TABLE" 206ms

And Go to transport details "DELIVERY" 4s 333ms

And Click create similar button 15s 165ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "super-admin-adama" 10s 904ms

And Click "save-transport" save button and wait for form to disappear 15s 591ms

And Set advice window in schedule in "2" days 4s 201ms

And Go to "TRANSPORT_TABLE" 155ms

And Open similar transport details 329ms

Then Check are transport values equals 183ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.deleteSimilarTransportAfterTest() 000ms

View Feature Transport form

@deleteTransportAfterTest @deleteSimilarTransportAfterTest

Scenario Outline Check if transport created with advice by similar button has correct carrier

Steps

Given Set "transport" inputs from JSON file "CREATE_DELIVERY" "pna1-carrier" 002ms

And Login as "pna1-carrier" and set token of apiUsername "pna1-carrier" 1s 051ms

When Go to new transport "DELIVERY" 15s 282ms

And Fill transport form 35s 940ms

And Click "save-transport" save button and wait for form to disappear 15s 746ms

And Set advice window in schedule 2s 178ms

And Check is transport created in schedule and set transport id 4s 031ms

And Go to "TRANSPORT_TABLE" 190ms

And Go to transport details "DELIVERY" 32s 401ms

And Click create similar button 15s 204ms

And Fill "transport" form "CREATE_SIMILAR_DELIVERY" by "pna1-carrier" 9s 506ms

And Click "save-transport" save button and wait for form to disappear 15s 603ms

And Set advice window in schedule in "2" days 4s 238ms

And Go to "TRANSPORT_TABLE" 223ms

And Open similar transport details 543ms

Then Check is field "CARRIER" of type "autocomplete" equals "Przewoźnik Neuca Automat 1" 019ms

Hooks

After Hooks.deleteTransportAfterTest() 175ms

After Hooks.deleteSimilarTransportAfterTest() 105ms

View Feature Transport form

@deleteTransportAfterTest

Scenario Outline Check if it is possible to show transport details print form

Steps

Given Get inputs from database "CREATE_SMALLS_IMPORT_FOR_PRINT" "super-admin-skz" 002ms

And Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 275ms

When Go to new transport "SMALLS_IMPORT" 403ms

And Fill transport form 33s 029ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 623ms

And Go to transport details "SMALLS_IMPORT" 4s 451ms

And Go to transport print details form 3s 095ms

Then Check are transport values equals 8s 365ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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 279ms

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 273ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 165ms

And Go to transport details "SMALLS_IMPORT" 4s 487ms

Then Verify that the transport can be edited 1s 321ms

And Close transport details 15s 127ms

And If user is login then logout 103ms

And Login as "pskza1-carrier@qa.qa-test" 1s 277ms

And Go to transport details "SMALLS_IMPORT" 4s 503ms

And Verify that the transport cannot be edited 46s 313ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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 260ms

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 230ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 125ms

And Go to transport details "SMALLS_EXPORT" 4s 505ms

Then Verify that the transport can be edited 1s 325ms

And Close transport details 15s 139ms

And If user is login then logout 118ms

And Login as "pskza1-carrier@qa.qa-test" 1s 259ms

And Go to transport details "SMALLS_EXPORT" 4s 488ms

And Verify that the transport cannot be edited 46s 374ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

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 140ms

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 238ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 089ms

And Go to transport details "SMALLS_IMPORT" 4s 464ms

Then Verify that the hidden data in transport are not visible 1s 038ms

And Close transport details 15s 077ms

And If user is login then logout 109ms

And Login as "swisskrono-admin" 1s 407ms

And Go to transport details "SMALLS_IMPORT" 4s 526ms

And Verify that the hidden data in transport are visible 1s 245ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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 144ms

And Get inputs from database "HIDDEN_DATA_SMALLS_EXPORT" "super-admin-skz" 001ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 267ms

When Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 117ms

And Go to transport details "SMALLS_EXPORT" 4s 443ms

Then Verify that the hidden data in transport are not visible 1s 043ms

And Close transport details 15s 098ms

And If user is login then logout 122ms

And Login as "swisskrono-admin" 1s 431ms

And Go to transport details "SMALLS_EXPORT" 4s 499ms

And Verify that the hidden data in transport are visible 1s 256ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

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 404ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 458ms

When Go to transport details "DELIVERY" 4s 734ms

And Change filled value in transport details "unloaded-stere" "text" "3" "0" 1s 330ms

And Change filled value in transport details "warehouseman" "select" "Dorosz Mieczysław" "0" 3s 526ms

And Change filled value in transport details "insp.-accord.-with-ins." "select" "NIE" "1" 3s 518ms

And Fill discrepancy report section without closing the form 19s 659ms

And Click "save-transport" save button 1s 249ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 614ms

And Check if transport details form is disappeared 15s 046ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

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" 094ms

And Add action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 112ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 264ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 402ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 3s 547ms

When Go to "TRANSPORT_TABLE" 172ms

And Go to transport details "DELIVERY" 4s 731ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 334ms

Then Verify that "transport-description" in transport has value "opis" 026ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 059ms

After Hooks.rollbackWarehousesAccess() 175ms

After Hooks.deleteTransportAfterTest() 101ms

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" 095ms

And Create transport "CREATE_DELIVERY_WARM_KAZMIERZ" by JSON file as "super-admin-hochland" 1s 375ms

And Remove action authority with: "hochland" "hochland-warehouseman" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 059ms

And Add access to the warehouse "Magazyn Ciepły Kaźmierz" to the user "hochland-warehouseman" by JSON file 118ms

And Login as "hochland-warehouseman" and set token of apiUsername "super-admin-hochland" 2s 624ms

When Go to "TRANSPORT_TABLE" 169ms

And Go to transport details "DELIVERY" 4s 698ms

Then Verify that "transport-description" in transport form is disabled 028ms

Hooks

After Hooks.rollbackRemovedActionAuthorities() 061ms

After Hooks.rollbackWarehousesAccess() 177ms

After Hooks.deleteTransportAfterTest() 104ms

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" 098ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 055ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 402ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 614ms

And Show all transport "false" 004ms

When Go to "TRANSPORT_TABLE" 220ms

And Go to transport details "DELIVERY" 4s 708ms

Then Verify that "CARRIER" in transport form is visible 043ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 053ms

After Hooks.deleteTransportAfterTest() 120ms

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 200ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 085ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 176ms

And Go to transport details "TRANSPORT" 4s 476ms

Then Verify that "CARRIER" in transport form is visible 036ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 061ms

After Hooks.deleteTransportAfterTest() 076ms

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" 098ms

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 252ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 055ms

And Show all transport "true" 068ms

When Go to "TRANSPORT_TABLE" 098ms

And Go to transport details "TRANSPORT_ORDER" 4s 450ms

Then Verify that "CARRIER" in transport form is visible 034ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 049ms

After Hooks.deleteTransportAfterTest() 080ms

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" 090ms

And Remove action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 055ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 382ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 600ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 203ms

And Go to transport details "DELIVERY" 4s 753ms

Then Verify that "CARRIER" in transport form is not visible 15s 054ms

Hooks

After Hooks.rollbackRemovedActionAuthorities() 059ms

After Hooks.deleteTransportAfterTest() 091ms

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" 094ms

And Remove action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 051ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 224ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 937ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 215ms

And Go to transport details "TRANSPORT" 4s 473ms

Then Verify that "CARRIER" in transport form is not visible 15s 061ms

Hooks

After Hooks.rollbackRemovedActionAuthorities() 053ms

After Hooks.deleteTransportAfterTest() 080ms

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" 092ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 045ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 187ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 978ms

And Show all transport "true" 067ms

When Go to "TRANSPORT_TABLE" 107ms

And Go to transport details "TRANSPORT_ORDER" 4s 462ms

Then Verify that "CARRIER" in transport form is not visible 15s 022ms

Hooks

After Hooks.rollbackRemovedActionAuthorities() 051ms

After Hooks.deleteTransportAfterTest() 087ms

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" 094ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 053ms

And Add action authority with: "hochland" "hochland-admin" "DELIVERY" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 055ms

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 618ms

And Show all transport "false" 004ms

When Go to "TRANSPORT_TABLE" 231ms

And Go to transport details "DELIVERY" 4s 711ms

Then Verify that "CARRIER" in transport form is not disabled 034ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 092ms

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" 092ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 058ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 055ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 215ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 053ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 199ms

And Go to transport details "TRANSPORT" 4s 471ms

Then Verify that "CARRIER" in transport form is not disabled 024ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 082ms

After Hooks.deleteTransportAfterTest() 052ms

View Feature Transport form

@rollbackAddedActionAuthorities @deleteTransportAfterTest

Scenario Outline Check if user can edit `carrierCompany` field in transport form

Steps

Given Set token of apiUsername "super-admin-alrec" 113ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 049ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 040ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 223ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 2s 663ms

And Show all transport "true" 066ms

When Go to "TRANSPORT_TABLE" 105ms

And Go to transport details "TRANSPORT_ORDER" 5s 192ms

Then Verify that "CARRIER" in transport form is not disabled 029ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 096ms

After Hooks.deleteTransportAfterTest() 070ms

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" 092ms

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" 039ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 389ms

And Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 420ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 184ms

And Go to transport details "DELIVERY" 4s 703ms

Then Verify that "CARRIER" in transport form is disabled 028ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 049ms

After Hooks.rollbackRemovedActionAuthorities() 060ms

After Hooks.deleteTransportAfterTest() 106ms

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" 097ms

And Add action authority with: "adama" "adama-admin" "TRANSPORT" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 057ms

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 216ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 984ms

And Show all transport "false" 005ms

When Go to "TRANSPORT_TABLE" 219ms

And Go to transport details "TRANSPORT" 4s 480ms

Then Verify that "CARRIER" in transport form is disabled 031ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 045ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

After Hooks.deleteTransportAfterTest() 077ms

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" 090ms

And Add action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "ACCESS_CARRIER_COMPANY_FIELD" "UNLIMITED" 053ms

And Remove action authority with: "alrec" "alrec-admin" "TRANSPORT_ORDER" "UPDATE_CARRIER_COMPANY_FIELD" "UNLIMITED" 008ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-alrec" 1s 226ms

And Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 805ms

And Show all transport "true" 074ms

When Go to "TRANSPORT_TABLE" 107ms

And Go to transport details "TRANSPORT_ORDER" 4s 467ms

Then Verify that "CARRIER" in transport form is disabled 024ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 048ms

After Hooks.rollbackRemovedActionAuthorities() 000ms

After Hooks.deleteTransportAfterTest() 062ms

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" 092ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 261ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_MAIN_DATA_SECTION" "UNLIMITED" 050ms

And Remove action authority with: "adama" "adama-admin" "DELIVERY" "UPDATE_ADVICE" "UNLIMITED" 050ms

And Add action authority with: "adama" "adama-admin" "DELIVERY" "EDIT_DESCRIPTION_FIELD" "UNLIMITED" 058ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 852ms

When Find transport in table with status "planned" 3s 331ms

And Confirm statuses until reach "process-ended" 21s 522ms

And Wait "90" seconds 1m 30s

And Go to "ARCHIVE_TAB" 266ms

And Show "DELIVERY" 074ms

And Go to transport details "DELIVERY" 32s 399ms

And Change filled value in transport details "transport-description" "text" "opis" "0" 1s 332ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 652ms

And Wait "7" seconds 7s

And Go to transport details "DELIVERY" 32s 382ms

Then Verify that "transport-description" in transport has value "opis" 030ms

Hooks

After Hooks.rollbackAddedActionAuthorities() 065ms

After Hooks.rollbackRemovedActionAuthorities() 105ms

After Hooks.deleteTransportAfterTest() 092ms

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 400ms

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 570ms

When Go to transport details "DELIVERY" 4s 698ms

And Fill transport form 35s 856ms

And Change filled value in transport details "driver-name" "text" "XXX ZZZ" "0" 1s 384ms

And Click "save-transport-and-close" save button and wait for form to disappear 19s 316ms

And Go to new transport "DELIVERY" 303ms

Then Verify that driver "XXX ZZZ" is in list 626ms

Hooks

After Hooks.deleteTransportAfterTest() 164ms

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 230ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 256ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 228ms

And If user is login then logout 109ms

And Login as "pskza1-carrier@qa.qa-test" 1s 141ms

Then Verify that the transport has been transferred 1s 120ms

And Accept or reject "accept" transferred transport 15s 830ms

And Go to transport details "SMALLS_IMPORT" 4s 525ms

And Verify that "transaction-price" in transport form is visible 038ms

And Verify that transaction price field has correct value 021ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_IMPORT" 028ms

Hooks

After Hooks.deleteTransportAfterTest() 099ms

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 303ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 227ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 186ms

And If user is login then logout 112ms

And Login as "pskza1-carrier@qa.qa-test" 1s 237ms

Then Verify that the transport has been transferred 1s 141ms

And Accept or reject "accept" transferred transport 15s 781ms

And Go to transport details "SMALLS_EXPORT" 4s 519ms

And Verify that "transaction-price" in transport form is visible 039ms

And Verify that transaction price field has correct value 024ms

And Verify that transaction currency field has correct value: "swisskrono" "SMALLS_EXPORT" 028ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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 897ms

And Create transport "CREATE_DELIVERY_NIEPORET_WAREHOUSE" by JSON file as "super-admin-lantmannen" 1s 606ms

And Show all transport types 1s 048ms

Then Check if transport number is visible "DELIVERY" 15s 083ms

And Check if transport details is not visible 15s 039ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 974ms

And Show all transport "false" 006ms

And Go to "TRANSPORT_TABLE" 132ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 1s 499ms

When Click on transport row 069ms

Then Verify if transport row is selected 031ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

View Feature Transport table

@deleteTransportAfterTest

Scenario Outline Check if transport table row is selected

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 988ms

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 208ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-adama" 1s 291ms

When Click on transport row 1s 760ms

Then Verify if transport row is selected 034ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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 882ms

And Show all transport "false" 004ms

And Go to "TRANSPORT_TABLE" 106ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 15s 261ms

When Click on transport row 089ms

Then Verify if transport row is selected 043ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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 902ms

And Show all transport "false" 004ms

And Go to "TRANSPORT_TABLE" 124ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-lantmannen" 1s 245ms

When Click on transport row 056ms

Then Verify if transport row is selected 026ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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 910ms

And Show all transport "false" 005ms

And Go to "TRANSPORT_TABLE" 112ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 326ms

When Click on transport row 065ms

Then Verify if transport row is selected 033ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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 990ms

And Show all transport "true" 080ms

And Go to "TRANSPORT_TABLE" 099ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-alrec" 1s 236ms

When Click on transport row 069ms

Then Verify if transport row is selected 028ms

Hooks

After Hooks.deleteTransportAfterTest() 092ms

View Feature Reject Transport

@deleteTransportAfterTest

Scenario Outline Check if it is possible to accept and reject transport by carrier

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 2s 810ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 264ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 114ms

When Accept or reject "accept" transferred transport 17s 698ms

Then Verify that transport is accept or reject "accept" 023ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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 118ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 220ms

And Transfer transport to carrier by JSON file "super-admin-adama" "true" confirmation 075ms

When Accept or reject "reject" transferred transport 17s 629ms

Then Verify that transport is accept or reject "reject" 15s 058ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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 392ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 247ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 060ms

When Accept or reject "accept" transferred transport 18s 017ms

Then Verify that transport is accept or reject "accept" 024ms

Hooks

After Hooks.deleteTransportAfterTest() 062ms

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 120ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 240ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 060ms

When Accept or reject "reject" transferred transport 18s 017ms

Then Verify that transport is accept or reject "reject" 15s 016ms

Hooks

After Hooks.deleteTransportAfterTest() 085ms

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 170ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 246ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 084ms

When Accept or reject "accept" transferred transport 18s 115ms

Then Verify that transport is accept or reject "accept" 018ms

Hooks

After Hooks.deleteTransportAfterTest() 094ms

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 008ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 210ms

And Transfer transport to carrier by JSON file "super-admin-skz" "true" confirmation 078ms

When Accept or reject "reject" transferred transport 18s 049ms

Then Verify that transport is accept or reject "reject" 15s 015ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

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 184ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 247ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 276ms

And If user is login then logout 115ms

And Login as "paa1-carrier@qa.qa-test" 1s 165ms

Then Verify that the transport has been transferred with "true" 1s 207ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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 068ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 231ms

When Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 19s 227ms

And If user is login then logout 091ms

And Login as "paa1-carrier@qa.qa-test" 1s 184ms

Then Verify that the transport has been transferred with "false" 1s 162ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

View Feature Transfer transport to carrier

@deleteTransportAfterTest

Scenario Outline Check if it is possible to transfer transport to carrier - without confirmation checkbox

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 948ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 285ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 178ms

And If user is login then logout 114ms

And Login as "pskza1-carrier@qa.qa-test" 1s 213ms

Then Verify that the transport has been transferred 1s 136ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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 147ms

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 1s 215ms

When Transfer transport to carrier "Przewoźnik SKZ Automat 1" 19s 164ms

And If user is login then logout 108ms

And Login as "pskza1-carrier@qa.qa-test" 1s 178ms

Then Verify that the transport has been transferred 1s 133ms

Hooks

After Hooks.deleteTransportAfterTest() 103ms

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 028ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 479ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 4s 324ms

And Go to auction offer 1s 312ms

When Offer "1000" 137ms

And Verify that offer with "1000" has been added to auction 3s 037ms

And If user is login then logout 088ms

And Login as "swisskrono-admin" 1s 280ms

Then Go to auction details 1s 212ms

And Pass transport to carrier from auction details 1s 257ms

And If user is login then logout 444ms

And Login as "pskza1-carrier@qa.qa-test" 1s 223ms

And Verify that the transport has been transferred 1s 129ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

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 025ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 244ms

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-skz" 2s 109ms

And Go to auction offer 1s 192ms

When Offer "1000" 122ms

And Verify that offer with "1000" has been added to auction 3s 040ms

And Wait till auction end 1m 54s 018ms

And If user is login then logout 130ms

Then Login as "swisskrono-admin" 1s 391ms

And Go to auction details 1s 197ms

And Pass transport to carrier from auction details 1s 258ms

And If user is login then logout 373ms

And Login as "pskza1-carrier@qa.qa-test" 1s 183ms

And Verify that the transport has been transferred 1s 142ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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 172ms

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 1s 219ms

And Go to "TRANSPORT_TABLE" 135ms

When Open transport transfer modal 1s 234ms

Then Verify that all enabled companies from "swisskrono" are shown in select 130ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

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 416ms

And Login as "adama-admin" 979ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 237ms

And Go to "TRANSPORT_TABLE" 129ms

When Open transport transfer modal 1s 279ms

Then Verify that "Przewoźnik Adama Automat 1" is blocked in select 107ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

After Hooks.rollbackRejectedSections() 108ms

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 025ms

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 1s 230ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" with "120" seconds to accept transport 19s 237ms

And If user is login then logout 115ms

When Login as "paa1-carrier@qa.qa-test" 3s 015ms

And Verify that the transport has been transferred with "true" 1s 220ms

And Wait "120" seconds 2m

Then Verify if transport is not visible to carrier after expiring time to accept transport 15s 033ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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 068ms

And Create transport "CREATE_TANKER_GRANULATE_DELIVERY" by JSON file as "super-admin-keeeper" 1s 583ms

When Go to "TRANSPORT_TABLE" 138ms

And Go to transport details "TANKER_GRANULATE_DELIVERY" 4s 400ms

Then Check if new assortment group is disabled in transport form 031ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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 050ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 1s 231ms

And Get inputs from database "CREATE_ADVICE_CONTAINER" "super-admin-adama" 002ms

When Show all transport types 1s 049ms

And Click button advice in transport table "CONTAINER" 115ms

And Set advice window in schedule 2s 387ms

And Click button cancel in advice form 15s 382ms

And Set advice window in schedule 2s 126ms

And Click button cancel in advice form 15s 281ms

And Set advice window in schedule 2s 152ms

And Fill advice form 15s 885ms

And Click advice save button and wait for advice form to disappear 30s 768ms

And Go to "TRANSPORT_TABLE" 165ms

And Go to transport details "CONTAINER" 4s 427ms

Then Check are advice values equals 2s 386ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

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 118ms

And Get inputs from database "CREATE_TRANSPOSRT_ORDER" "super-admin-adama" 001ms

When Go to new transport "TRANSPORT" 430ms

And Fill transport form 26s 810ms

And Click "save-transport-and-close" save button and wait for form to disappear 15s 602ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 21s 900ms

And Check is transport "TRANSPORT" created in transport table and set transport id 1s 106ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 110ms

And Accept or reject "reject" transferred transport 15s 916ms

And Login as "adama-admin" and set token of apiUsername "super-admin-adama" 1s 145ms

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 19s 289ms

And Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 016ms

And Accept or reject "accept" transferred transport 16s 020ms

Then Verify that transport is accept or reject "accept" 027ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

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 189ms

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 209ms

When Show all transport types 1s 051ms

And Click button advice in transport table "DELIVERY" 135ms

And Set advice window in schedule 2s 631ms

And Click button cancel in advice form 15s 412ms

And Go to "TRANSPORT_TABLE" 233ms

When Go to transport details "DELIVERY" 4s 566ms

And Fill transport form 1m 2s 499ms

And Click "save-transport-and-close" save button and wait for form to disappear 16s 158ms

And Go to transport details "DELIVERY" 4s 440ms

Then Check are transport values equals 24s 829ms

Hooks

After Hooks.deleteTransportAfterTest() 165ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@deleteTransportAfterTest	3705	21	46	0	0	3772	384	21	405	5h 42m 12s 717ms	Failed

Tag Report