Cucumber-JVM Reports - Feature: Advice transport

Project	Number	Date
ApolloFullRunnerReport	develop.332	04 mar 2021, 16:41

	Steps	Scenarios	Features
Advice transport	425	5	3	0	0	433	35	6	41	31m 43s 660ms	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" 4s 744ms

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

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

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

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

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

And Fill advice form 16s 490ms

And Click advice save button to check error message 085ms

Then Check if possible advice alert is displayed 021ms

Hooks

After Hooks.deleteTransportAfterTest() 343ms

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

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

And Fill advice form 8s 599ms

And Click advice save button to check error message 105ms

Then Check if possible advice alert is displayed 022ms

Hooks

After Hooks.deleteTransportAfterTest() 159ms

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

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

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

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

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

And Fill advice form 8s 547ms

And Click advice save button to check error message 101ms

Then Check if possible advice alert is displayed 030ms

Hooks

After Hooks.deleteTransportAfterTest() 142ms

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

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

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

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

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

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

And Fill advice form 13s 325ms

And Click advice save button to check error message 087ms

Then Check if possible advice alert is displayed 028ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

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

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

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

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

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

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

And Fill advice form 13s 341ms

And Click advice save button to check error message 087ms

Then Check if possible advice alert is displayed 030ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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

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

And Show all transport types 1s 042ms

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

And Go to "TRANSPORT_TABLE" 190ms

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

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

And Fill transport form 4s 734ms

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

And Expand advice panel 098ms

And Edit advice in transport details 12s 579ms

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

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

And Expand advice panel 110ms

Then Check are advice values equals after edition 240ms

Hooks

After Hooks.deleteTransportAfterTest() 147ms

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

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

And Show all transport types 1s 052ms

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

And Go to "TRANSPORT_TABLE" 268ms

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

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

And Fill transport form 1m 2s 597ms

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

And Expand advice panel 109ms

And Edit advice in transport details 6s 642ms

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

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

And Expand advice panel 108ms

Then Check are advice values equals after edition 076ms

Hooks

After Hooks.deleteTransportAfterTest() 177ms

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

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

And Show all transport types 1s 053ms

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

And Go to "TRANSPORT_TABLE" 192ms

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

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

And Fill transport form 57s 364ms

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

And Expand advice panel 122ms

And Edit advice in transport details 6s 707ms

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

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

And Expand advice panel 104ms

Then Check are advice values equals after edition 095ms

Hooks

After Hooks.deleteTransportAfterTest() 241ms

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

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

And Show all transport types 1s 049ms

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

And Go to "TRANSPORT_TABLE" 178ms

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

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

And Fill transport form 24s 703ms

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

And Expand advice panel 111ms

And Edit advice in transport details 18s 550ms

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

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

And Expand advice panel 107ms

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

Hooks

After Hooks.deleteTransportAfterTest() 194ms

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

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

And Show all transport types 1s 053ms

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

And Go to "TRANSPORT_TABLE" 201ms

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

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

And Fill transport form 24s 749ms

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

And Expand advice panel 131ms

And Edit advice in transport details 18s 715ms

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

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

And Expand advice panel 115ms

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

Hooks

After Hooks.deleteTransportAfterTest() 170ms

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

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

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

When Show all transport types 1s 049ms

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

And Set advice window in schedule 2s 373ms

And Fill advice form 12s 578ms

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

And Go to "TRANSPORT_TABLE" 169ms

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

Then Check are advice values equals 350ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

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

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

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

When Show all transport types 1s 034ms

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

And Set advice window in schedule 6s 431ms

And Fill advice form 11s 923ms

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

And Go to "TRANSPORT_TABLE" 186ms

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

Then Check are advice values equals 2s 315ms

Hooks

After Hooks.deleteTransportAfterTest() 161ms

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

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

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

When Show all transport types 1s 042ms

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

And Set advice window in schedule 2s 526ms

And Fill advice form 8s 504ms

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

And Go to "TRANSPORT_TABLE" 251ms

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

Then Check are advice values equals 218ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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

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

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

When Show all transport types 1s 048ms

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

And Set advice window in schedule 2s 560ms

And Fill advice form 8s 485ms

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

And Go to "TRANSPORT_TABLE" 209ms

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

Then Check are advice values equals 227ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

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

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

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

When Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 419ms

And Fill advice form 13s 263ms

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

And Go to "TRANSPORT_TABLE" 155ms

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

Then Check are advice values equals 2s 327ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

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

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

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

When Show all transport types 1s 046ms

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

And Set advice window in schedule 2s 437ms

And Fill advice form 13s 286ms

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

And Go to "TRANSPORT_TABLE" 193ms

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

Then Check are advice values equals 2s 353ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

@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" 009ms

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

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

And Fill transport form 41s 090ms

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

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

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

Then Set advice window in schedule 2s 245ms

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

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[@id='slot-115377329-2021-03-05-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.8xFbl4}, 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: d536f7a566882c9c9f151fa88c617b68
*** Element info: {Using=xpath, value=//div[@id='slot-115377329-2021-03-05-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() 001ms

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

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

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

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

And Accept transferred transport by Api 364ms

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

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

When Show all transport types 1s 058ms

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

And Set advice window in schedule 2s 374ms

And Fill advice form 11s 968ms

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

And Go to "TRANSPORT_TABLE" 246ms

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

Then Check are advice values equals 2s 279ms

Hooks

After Hooks.deleteTransportAfterTest() 169ms

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

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

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

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

And Accept transferred transport by Api 147ms

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

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

When Show all transport types 1s 038ms

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

And Set advice window in schedule 2s 644ms

And Fill advice form 14s 632ms

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

And Go to "TRANSPORT_TABLE" 182ms

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

Then Check are advice values equals 2s 343ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

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

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

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

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

And Accept transferred transport by Api 121ms

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

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

And Set advice window in schedule 2s 636ms

And Fill advice form 14s 647ms

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

And Go to "TRANSPORT_TABLE" 186ms

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

Then Check are advice values equals 2s 349ms

Hooks

After Hooks.deleteTransportAfterTest() 172ms

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

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

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

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

And Accept transferred transport by Api 105ms

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

When Show all transport types 1s 038ms

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

And Set week view 1s 520ms

And Show yesterday 1s 131ms

Then Check if advice restriction blockade windows are visible 025ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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

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

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

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

And Accept transferred transport by Api 112ms

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

When Show all transport types 1s 039ms

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

And Set week view 2s 065ms

And Show yesterday 1s 118ms

Then Check if advice restriction blockade windows are visible 031ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

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

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

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

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

And Accept transferred transport by Api 093ms

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

When Show all transport types 1s 043ms

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

And Set week view 2s 052ms

And Show yesterday 1s 129ms

Then Check if advice restriction blockade windows are visible 031ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

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

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

And Show all transport "false" 034ms

And Click on time window date 1s 294ms

And Select view "DAYS_4" 2s 062ms

And Move advice window "3" 1s 326ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 139ms

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport "false" 021ms

And Click on time window date 15s 854ms

And Select view "DAYS_4" 2s 060ms

And Move advice window "3" 1s 479ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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

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

And Show all transport "false" 016ms

And Click on time window date 15s 548ms

And Select view "DAYS_4" 2s 073ms

And Move advice window "3" 1s 427ms

Then Check if advice window is in new location 029ms

Hooks

After Hooks.deleteTransportAfterTest() 132ms

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

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

And Show all transport "false" 018ms

And Click on time window date 1s 454ms

And Select view "DAYS_4" 2s 052ms

And Move advice window "3" 1s 381ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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

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

And Show all transport "false" 014ms

And Click on time window date 1s 293ms

And Select view "DAYS_4" 2s 055ms

And Move advice window "3" 1s 302ms

Then Check if advice window is in new location 040ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

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

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

And Show all transport "true" 093ms

And Click on time window date 1s 384ms

And Select view "DAYS_4" 2s 071ms

And Move advice window "3" 1s 333ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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

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

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

When Show all transport types 1s 046ms

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

And Set advice window in schedule 2s 551ms

And Fill advice form 8s 475ms

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

And Go to "TRANSPORT_TABLE" 224ms

And Click on time window date 1s 426ms

And Select view "DAYS_4" 2s 051ms

And Move advice window "3" 1s 424ms

Then Check if advice window is in new location 021ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

@deleteTransportAfterTest

Scenario Outline Check if late advice is red

Steps

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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

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

And Go to "TRANSPORT_TABLE" 149ms

And Show all transport types 1s 046ms

And Click on time window date 1s 304ms

And Scroll to time window "adviceWindow" 048ms

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

Then Check height of the time window after expanding by "80" 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 "80" in "adviceWindow"(file:Features/Atom/Advice/AdviceTransport.feature:186)

Hooks

After Hooks.deleteTransportAfterTest() 156ms

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

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

And Go to "TRANSPORT_TABLE" 135ms

And Show all transport types 1s 043ms

And Click on time window date 1s 375ms

And Scroll to time window "adviceWindow" 033ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 167ms

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

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

And Go to "TRANSPORT_TABLE" 145ms

And Show all transport types 1s 040ms

And Click on time window date 1s 292ms

And Scroll to time window "adviceWindow" 039ms

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

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

Error message

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

Hooks

After Hooks.deleteTransportAfterTest() 097ms

@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" 995ms

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

And Go to "TRANSPORT_TABLE" 306ms

And Show all transport types 15s 054ms

And Click on time window date 15s 823ms

And Scroll to time window "adviceWindow" 034ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 101ms

@deleteTransportAfterTest

Scenario Outline Check if it is possible to resize advice window in schedule after add advice by advice button in transport table

Steps

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

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

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

And Set advice window in schedule 2s 537ms

And Fill advice form 8s 467ms

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

And Go to "TRANSPORT_TABLE" 242ms

And Click on time window date 1s 432ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 127ms

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

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

And Go to "WAREHOUSE_TAB" 757ms

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

When Go to new transport "DELIVERY" 438ms

And Fill transport form 40s 224ms

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

And Click previous page button in browser 028ms

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

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

And Go to "WAREHOUSE_TAB" 780ms

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

When Go to new transport "DELIVERY" 384ms

And Fill transport form 40s 248ms

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

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

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

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

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

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

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

When Show all transport types 1s 045ms

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

And Fill advice form 11s 642ms

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

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

And Open statuses popup 100ms

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

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

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

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

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

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

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

And Set advice window in schedule 2s 756ms

And Fill advice form 9s 261ms

And Click advice save button and wait for advice form to disappear 15s 908ms

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

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

When Go to "TRANSPORT_TABLE" 262ms

And Show all transport types 1s 050ms

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

And Set advice window in schedule 2s 694ms

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

Then Verify if mode of transportation select is empty 036ms

Hooks

After Hooks.deleteAllTransports() 15s 050ms

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.8xFbl4}, 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: d536f7a566882c9c9f151fa88c617b68
*** 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() 172ms

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

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

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

And Go to "WAREHOUSE_TAB" 598ms

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

And Set week view 2s 364ms

And Move cursor over time window element 416ms

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

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

	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 43s 660ms	Failed

Feature Report