Cucumber-JVM Reports - Feature: Advice transport

Project	Number	Date
ApolloFullRunnerReport	develop.326	09 mar 2021, 03:54

	Steps	Scenarios	Features
Advice transport	425	5	3	0	0	433	35	6	41	31m 54s 944ms	Failed

@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 "adama-admin" and set token of apiUsername "super-admin-adama" 2s 696ms

And Create transport "CREATE_CONTAINER" by JSON file as "super-admin-adama" 2s 594ms

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

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

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

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

And Fill advice form 16s 266ms

And Click advice save button to check error message 092ms

Then Check if possible advice alert is displayed 026ms

Hooks

After Hooks.deleteTransportAfterTest() 278ms

@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 244ms

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

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

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

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

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

And Fill advice form 8s 536ms

And Click advice save button to check error message 097ms

Then Check if possible advice alert is displayed 025ms

Hooks

After Hooks.deleteTransportAfterTest() 167ms

@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 152ms

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

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

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

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

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

And Fill advice form 8s 527ms

And Click advice save button to check error message 116ms

Then Check if possible advice alert is displayed 024ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

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

And Fill advice form 13s 397ms

And Click advice save button to check error message 086ms

Then Check if possible advice alert is displayed 024ms

Hooks

After Hooks.deleteTransportAfterTest() 148ms

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

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

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

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

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

And Fill advice form 13s 343ms

And Click advice save button to check error message 091ms

Then Check if possible advice alert is displayed 027ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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

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

And Show all transport types 1s 050ms

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

And Go to "TRANSPORT_TABLE" 214ms

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

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

And Fill transport form 4s 705ms

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

And Expand advice panel 098ms

And Edit advice in transport details 12s 591ms

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

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

And Expand advice panel 120ms

Then Check are advice values equals after edition 234ms

Hooks

After Hooks.deleteTransportAfterTest() 148ms

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

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

And Show all transport types 1s 043ms

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

And Go to "TRANSPORT_TABLE" 261ms

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

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

And Fill transport form 1m 2s 636ms

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

And Expand advice panel 120ms

And Edit advice in transport details 6s 652ms

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

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

And Expand advice panel 115ms

Then Check are advice values equals after edition 104ms

Hooks

After Hooks.deleteTransportAfterTest() 221ms

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

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

And Show all transport types 1s 053ms

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

And Go to "TRANSPORT_TABLE" 215ms

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

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

And Fill transport form 57s 555ms

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

And Expand advice panel 125ms

And Edit advice in transport details 6s 648ms

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

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

And Expand advice panel 112ms

Then Check are advice values equals after edition 094ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

@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 153ms

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

And Show all transport types 1s 050ms

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

And Go to "TRANSPORT_TABLE" 215ms

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

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

And Fill transport form 24s 754ms

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

And Expand advice panel 122ms

And Edit advice in transport details 18s 696ms

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

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

And Expand advice panel 140ms

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

Hooks

After Hooks.deleteTransportAfterTest() 135ms

@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 153ms

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

And Show all transport types 1s 049ms

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

And Go to "TRANSPORT_TABLE" 205ms

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

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

And Fill transport form 24s 804ms

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

And Expand advice panel 115ms

And Edit advice in transport details 18s 673ms

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

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

And Expand advice panel 105ms

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

Hooks

After Hooks.deleteTransportAfterTest() 192ms

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

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

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

When Show all transport types 1s 051ms

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

And Set advice window in schedule 2s 387ms

And Fill advice form 12s 569ms

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

And Go to "TRANSPORT_TABLE" 190ms

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

Then Check are advice values equals 330ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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

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

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

When Show all transport types 1s 047ms

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

And Set advice window in schedule 6s 473ms

And Fill advice form 11s 953ms

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

And Go to "TRANSPORT_TABLE" 209ms

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

Then Check are advice values equals 2s 323ms

Hooks

After Hooks.deleteTransportAfterTest() 167ms

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

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

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

And Set advice window in schedule 2s 556ms

And Fill advice form 8s 438ms

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

And Go to "TRANSPORT_TABLE" 256ms

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

Then Check are advice values equals 219ms

Hooks

After Hooks.deleteTransportAfterTest() 146ms

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

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

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

When Show all transport types 1s 041ms

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

And Set advice window in schedule 2s 561ms

And Fill advice form 8s 465ms

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

And Go to "TRANSPORT_TABLE" 191ms

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

Then Check are advice values equals 204ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

@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 148ms

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

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

When Show all transport types 1s 046ms

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

And Set advice window in schedule 2s 394ms

And Fill advice form 13s 252ms

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

And Go to "TRANSPORT_TABLE" 187ms

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

Then Check are advice values equals 2s 340ms

Hooks

After Hooks.deleteTransportAfterTest() 121ms

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

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

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

When Show all transport types 1s 047ms

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

And Set advice window in schedule 2s 413ms

And Fill advice form 13s 270ms

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

And Go to "TRANSPORT_TABLE" 209ms

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

Then Check are advice values equals 2s 346ms

Hooks

After Hooks.deleteTransportAfterTest() 139ms

@deleteTransportAfterTest

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

Steps

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

And Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 3s 021ms

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

And Fill transport form 41s 104ms

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

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

When Change warehouse in schedule to: "Ołtarzew" 1s 335ms

Then Set advice window in schedule 2s 241ms

And Check is transport created in schedule and set transport id 15s 030ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[@id='slot-115377329-2021-03-09-00-00']//div[@data-transport-id]"}
  (Session info: headless chrome=88.0.4324.182)
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=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.RR2DSL}, 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=88.0.4324.182, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 266f32a0015a6459d97ec7248dbe68f9
*** Element info: {Using=xpath, value=//div[@id='slot-115377329-2021-03-09-00-00']//div[@data-transport-id]}
	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.Schedule.SchedulePage.getTransportId(SchedulePage.java:161)
	at CucumberTests.Transport.AdviceTransport.checkIsTransportCreatedInScheduleAndSetTransportId(AdviceTransport.java:158)
	at ✽.Check is transport created in schedule and set transport id(file:Features/Atom/Advice/AdviceTransport.feature:80)

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "DELIVERY" 000ms

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

Hooks

After Hooks.deleteTransportAfterTest() 002ms

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

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

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

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

And Accept transferred transport by Api 389ms

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

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

When Show all transport types 1s 036ms

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

And Set advice window in schedule 2s 395ms

And Fill advice form 11s 903ms

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

And Go to "TRANSPORT_TABLE" 241ms

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

Then Check are advice values equals 2s 313ms

Hooks

After Hooks.deleteTransportAfterTest() 146ms

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

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

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

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

And Accept transferred transport by Api 113ms

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

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

When Show all transport types 1s 044ms

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

And Set advice window in schedule 2s 610ms

And Fill advice form 14s 688ms

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

And Go to "TRANSPORT_TABLE" 194ms

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

Then Check are advice values equals 2s 327ms

Hooks

After Hooks.deleteTransportAfterTest() 176ms

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

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

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

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

And Accept transferred transport by Api 125ms

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

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

When Show all transport types 1s 036ms

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

And Set advice window in schedule 2s 610ms

And Fill advice form 14s 732ms

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

And Go to "TRANSPORT_TABLE" 192ms

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

Then Check are advice values equals 2s 306ms

Hooks

After Hooks.deleteTransportAfterTest() 148ms

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

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

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

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

And Accept transferred transport by Api 113ms

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

When Show all transport types 1s 038ms

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

And Set week view 1s 505ms

And Show yesterday 1s 114ms

Then Check if advice restriction blockade windows are visible 025ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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

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

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

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

And Accept transferred transport by Api 103ms

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

When Show all transport types 1s 048ms

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

And Set week view 2s 052ms

And Show yesterday 1s 120ms

Then Check if advice restriction blockade windows are visible 031ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

@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 133ms

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

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

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

And Accept transferred transport by Api 075ms

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

When Show all transport types 1s 037ms

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

And Set week view 2s 040ms

And Show yesterday 1s 123ms

Then Check if advice restriction blockade windows are visible 032ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

@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 520ms

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

And Show all transport "false" 028ms

And Click on time window date 1s 294ms

And Select view "DAYS_4" 2s 057ms

And Move advice window "3" 1s 328ms

Then Check if advice window is in new location 028ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport "false" 017ms

And Click on time window date 15s 787ms

And Select view "DAYS_4" 2s 071ms

And Move advice window "3" 1s 466ms

Then Check if advice window is in new location 129ms

Hooks

After Hooks.deleteTransportAfterTest() 083ms

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

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

And Show all transport "false" 013ms

And Click on time window date 15s 481ms

And Select view "DAYS_4" 2s 061ms

And Move advice window "3" 1s 396ms

Then Check if advice window is in new location 027ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport "false" 017ms

And Click on time window date 1s 432ms

And Select view "DAYS_4" 2s 068ms

And Move advice window "3" 1s 407ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

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

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

And Show all transport "false" 018ms

And Click on time window date 1s 320ms

And Select view "DAYS_4" 2s 065ms

And Move advice window "3" 1s 319ms

Then Check if advice window is in new location 026ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport "true" 085ms

And Click on time window date 1s 320ms

And Select view "DAYS_4" 2s 057ms

And Move advice window "3" 1s 335ms

Then Check if advice window is in new location 045ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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

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

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

When Show all transport types 1s 042ms

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

And Set advice window in schedule 2s 546ms

And Fill advice form 8s 409ms

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

And Go to "TRANSPORT_TABLE" 235ms

And Click on time window date 1s 413ms

And Select view "DAYS_4" 2s 063ms

And Move advice window "3" 1s 438ms

Then Check if advice window is in new location 027ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

@deleteTransportAfterTest

Scenario Outline Check if late advice is red

Steps

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 118ms

@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 296ms

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

And Go to "TRANSPORT_TABLE" 147ms

And Show all transport types 1s 048ms

And Click on time window date 1s 306ms

And Scroll to time window "adviceWindow" 051ms

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

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

Error message

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

Hooks

After Hooks.deleteTransportAfterTest() 125ms

@deleteTransportAfterTest

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

Steps

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

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

And Go to "TRANSPORT_TABLE" 139ms

And Show all transport types 1s 044ms

And Click on time window date 1s 416ms

And Scroll to time window "adviceWindow" 038ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 130ms

@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 517ms

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

And Go to "TRANSPORT_TABLE" 145ms

And Show all transport types 1s 042ms

And Click on time window date 1s 303ms

And Scroll to time window "adviceWindow" 037ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 099ms

@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 040ms

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

And Go to "TRANSPORT_TABLE" 243ms

And Show all transport types 15s 036ms

And Click on time window date 15s 798ms

And Scroll to time window "adviceWindow" 040ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 117ms

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

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

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

When Show all transport types 1s 056ms

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

And Set advice window in schedule 2s 527ms

And Fill advice form 8s 426ms

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

And Go to "TRANSPORT_TABLE" 242ms

And Click on time window date 1s 441ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 137ms

@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 379ms

And Go to "WAREHOUSE_TAB" 736ms

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

When Go to new transport "DELIVERY" 384ms

And Fill transport form 40s 017ms

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

And Click previous page button in browser 024ms

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

@deleteTransportAfterTest

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

Steps

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

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

And Go to "WAREHOUSE_TAB" 784ms

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

When Go to new transport "DELIVERY" 382ms

And Fill transport form 40s 316ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 000ms

@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 144ms

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

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

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

And Fill advice form 11s 628ms

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

When Find transport in table with status "no-advice-undefined" 1s 260ms

And Open statuses popup 112ms

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" 15s 034ms

Error message

org.junit.ComparisonFailure: Lista statusów jest niepoprawna expected:<[Zgłoszenie się kierowcy,Zakończenie załadunku,Dostarczenie do klienta]> but was:<[]>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at CucumberTests.StatusTests.ConfirmStatuses.checkIfTransportHasCheckpointsFromListInGroup(ConfirmStatuses.java:103)
	at ✽.Check if transport has checkpoints from list "Zgłoszenie się kierowcy,Zakończenie załadunku,Dostarczenie do klienta" in "1"(file:Features/Atom/Advice/AdviceTransport.feature:255)

Hooks

After Hooks.deleteTransportAfterTest() 088ms

@deleteAllTransportsAfterTest @deleteModeOfTransportationAfterTest

Scenario Outline Check if mode of transportation select is still empty after selecting driver in advice form

Steps

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

And Create accepted mode of transportation by API with "pba1-carrier": "AAAA0000" "Model" "Marka" "BBBB0000" 1s 536ms

And Create transport "CREATE_LOAD_PL" by JSON file as "super-admin-bausch" 1s 269ms

And Set "advice" inputs from JSON file "ADVICE_LOAD_PL" "super-admin-bausch" 003ms

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

And Click button advice in transport table "LOAD_PL" 2s 178ms

And Set advice window in schedule 2s 717ms

And Fill advice form 9s 235ms

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

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

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

When Go to "TRANSPORT_TABLE" 251ms

And Show all transport types 1s 046ms

And Click button advice in transport table "LOAD_PL" 2s 078ms

And Set advice window in schedule 2s 719ms

And Select driver "Marek Kanarek" from suggestions 1s 038ms

Then Verify if mode of transportation select is empty 044ms

Hooks

After Hooks.deleteAllTransports() 15s 054ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//button[@type='button' and @data-field-name='cancel-create']"}
  (Session info: headless chrome=88.0.4324.182)
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=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.RR2DSL}, 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=88.0.4324.182, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 266f32a0015a6459d97ec7248dbe68f9
*** Element info: {Using=xpath, value=//button[@type='button' and @data-field-name='cancel-create']}
	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:305)
	at CucumberTests._PerformanceTests.TransportTableTest.deleteAllTransport(TransportTableTest.java:122)
	at CucumberTests.Hooks.deleteAllTransports(Hooks.java:475)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at cucumber.runtime.Utils$1.call(Utils.java:26)
	at cucumber.runtime.Timeout.timeout(Timeout.java:16)
	at cucumber.runtime.Utils.invoke(Utils.java:20)
	at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60)
	at cucumber.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:16)
	at cucumber.runner.TestStep.executeStep(TestStep.java:63)
	at cucumber.runner.TestStep.run(TestStep.java:49)
	at cucumber.runner.TestCase.run(TestCase.java:49)
	at cucumber.runner.Runner.runPickle(Runner.java:40)
	at cucumber.runtime.junit.PickleRunners$WithStepDescriptions.run(PickleRunners.java:97)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
	at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
	at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)

After Hooks.deleteModeOfTransportationAfterTest() 145ms

@deleteTransportAfterTest

Scenario Outline Check if time window details preview displays correctly

Steps

Given Login as "farmacol-admin" and set token of apiUsername "super-admin-farmacol" 3s 059ms

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

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

And Go to "WAREHOUSE_TAB" 645ms

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

And Set week view 2s 366ms

And Move cursor over time window element 435ms

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

Error message

org.junit.ComparisonFailure: W polu 'Status' są widoczne nie poprawne dane expected:<[Now]y> but was:<[Zaawizowan]y>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at CucumberTests.Schedule.ScheduleTest.checkIfTransportPopupDetailsAreVisible(ScheduleTest.java:177)
	at ✽.Check if "Zaawizowany" "31415" "06:00" "GDA12345" are visible on time window popup details(file:Features/Atom/Advice/AdviceTransport.feature:292)

Hooks

After Hooks.deleteTransportAfterTest() 094ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Advice transport	425	5	3	0	0	433	35	6	41	31m 54s 944ms	Failed

Feature Report