Cucumber-JVM Reports - Feature: Advice transport

Project	Number	Date
ApolloFullRunnerReport	after_release_3_8_0.327	09 mar 2021, 17:43

	Steps	Scenarios	Features
Advice transport	425	5	3	0	0	433	35	6	41	31m 59s 525ms	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 262ms

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

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

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

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

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

And Fill advice form 16s 363ms

And Click advice save button to check error message 088ms

Then Check if possible advice alert is displayed 019ms

Hooks

After Hooks.deleteTransportAfterTest() 291ms

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

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

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

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

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

And Fill advice form 8s 519ms

And Click advice save button to check error message 098ms

Then Check if possible advice alert is displayed 025ms

Hooks

After Hooks.deleteTransportAfterTest() 169ms

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

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

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

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

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

And Fill advice form 8s 515ms

And Click advice save button to check error message 089ms

Then Check if possible advice alert is displayed 026ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

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

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

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

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

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

And Fill advice form 13s 377ms

And Click advice save button to check error message 097ms

Then Check if possible advice alert is displayed 022ms

Hooks

After Hooks.deleteTransportAfterTest() 185ms

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

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

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

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

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

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

And Fill advice form 13s 265ms

And Click advice save button to check error message 086ms

Then Check if possible advice alert is displayed 023ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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

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

And Show all transport types 1s 049ms

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

And Go to "TRANSPORT_TABLE" 194ms

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

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

And Fill transport form 4s 751ms

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

And Expand advice panel 100ms

And Edit advice in transport details 12s 580ms

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

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

And Expand advice panel 115ms

Then Check are advice values equals after edition 245ms

Hooks

After Hooks.deleteTransportAfterTest() 159ms

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

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

And Show all transport types 1s 044ms

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

And Go to "TRANSPORT_TABLE" 227ms

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

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

And Fill transport form 1m 2s 610ms

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

And Expand advice panel 113ms

And Edit advice in transport details 6s 681ms

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

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

And Expand advice panel 110ms

Then Check are advice values equals after edition 114ms

Hooks

After Hooks.deleteTransportAfterTest() 160ms

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

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

And Show all transport types 1s 053ms

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

And Go to "TRANSPORT_TABLE" 218ms

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

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

And Fill transport form 57s 450ms

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

And Expand advice panel 121ms

And Edit advice in transport details 6s 690ms

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

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

And Expand advice panel 123ms

Then Check are advice values equals after edition 108ms

Hooks

After Hooks.deleteTransportAfterTest() 179ms

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

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

And Show all transport types 1s 044ms

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

And Go to "TRANSPORT_TABLE" 188ms

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

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

And Fill transport form 24s 796ms

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

And Expand advice panel 112ms

And Edit advice in transport details 18s 701ms

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

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

And Expand advice panel 128ms

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

Hooks

After Hooks.deleteTransportAfterTest() 169ms

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

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

And Show all transport types 1s 051ms

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

And Go to "TRANSPORT_TABLE" 210ms

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

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

And Fill transport form 24s 824ms

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

And Expand advice panel 125ms

And Edit advice in transport details 18s 701ms

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

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

And Expand advice panel 095ms

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

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

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

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

When Show all transport types 1s 049ms

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

And Set advice window in schedule 2s 391ms

And Fill advice form 12s 522ms

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

And Go to "TRANSPORT_TABLE" 222ms

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

Then Check are advice values equals 307ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

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

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

When Show all transport types 1s 051ms

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

And Set advice window in schedule 6s 461ms

And Fill advice form 11s 962ms

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

And Go to "TRANSPORT_TABLE" 208ms

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

Then Check are advice values equals 2s 271ms

Hooks

After Hooks.deleteTransportAfterTest() 172ms

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

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

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

When Show all transport types 1s 053ms

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

And Set advice window in schedule 2s 566ms

And Fill advice form 8s 448ms

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

And Go to "TRANSPORT_TABLE" 241ms

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

Then Check are advice values equals 215ms

Hooks

After Hooks.deleteTransportAfterTest() 125ms

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

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

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

When Show all transport types 1s 046ms

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

And Set advice window in schedule 2s 603ms

And Fill advice form 8s 469ms

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

And Go to "TRANSPORT_TABLE" 183ms

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

Then Check are advice values equals 244ms

Hooks

After Hooks.deleteTransportAfterTest() 137ms

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

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

When Show all transport types 1s 044ms

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

And Set advice window in schedule 2s 390ms

And Fill advice form 13s 251ms

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

And Go to "TRANSPORT_TABLE" 191ms

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

Then Check are advice values equals 2s 275ms

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

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

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

When Show all transport types 1s 046ms

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

And Set advice window in schedule 2s 436ms

And Fill advice form 13s 215ms

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

And Go to "TRANSPORT_TABLE" 201ms

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

Then Check are advice values equals 2s 340ms

Hooks

After Hooks.deleteTransportAfterTest() 148ms

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

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

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

And Fill transport form 41s 179ms

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

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

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

Then Set advice window in schedule 2s 255ms

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

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[@id='slot-115377329-2021-03-10-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.VrsAKg}, 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: 45c1be08725a83b295951a89998878c6
*** Element info: {Using=xpath, value=//div[@id='slot-115377329-2021-03-10-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 072ms

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

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

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

And Accept transferred transport by Api 347ms

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

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

When Show all transport types 1s 036ms

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

And Set advice window in schedule 2s 379ms

And Fill advice form 11s 983ms

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

And Go to "TRANSPORT_TABLE" 235ms

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

Then Check are advice values equals 2s 265ms

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

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

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

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

And Accept transferred transport by Api 111ms

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

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

And Set advice window in schedule 2s 652ms

And Fill advice form 14s 753ms

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

And Go to "TRANSPORT_TABLE" 232ms

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

Then Check are advice values equals 2s 333ms

Hooks

After Hooks.deleteTransportAfterTest() 180ms

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

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

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

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

And Accept transferred transport by Api 124ms

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

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

When Show all transport types 1s 047ms

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

And Set advice window in schedule 2s 638ms

And Fill advice form 14s 717ms

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

And Go to "TRANSPORT_TABLE" 185ms

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

Then Check are advice values equals 2s 336ms

Hooks

After Hooks.deleteTransportAfterTest() 158ms

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

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

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

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

And Accept transferred transport by Api 100ms

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

When Show all transport types 1s 038ms

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

And Set week view 1s 515ms

And Show yesterday 1s 117ms

Then Check if advice restriction blockade windows are visible 024ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

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

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

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

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

And Accept transferred transport by Api 105ms

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

When Show all transport types 1s 039ms

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

And Set week view 2s 108ms

And Show yesterday 1s 081ms

Then Check if advice restriction blockade windows are visible 034ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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

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

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

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

And Accept transferred transport by Api 100ms

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

When Show all transport types 1s 042ms

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

And Set week view 1s 933ms

And Show yesterday 1s 129ms

Then Check if advice restriction blockade windows are visible 030ms

Hooks

After Hooks.deleteTransportAfterTest() 130ms

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

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

And Show all transport "false" 032ms

And Click on time window date 1s 314ms

And Select view "DAYS_4" 2s 058ms

And Move advice window "3" 1s 335ms

Then Check if advice window is in new location 027ms

Hooks

After Hooks.deleteTransportAfterTest() 133ms

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

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

And Show all transport "false" 018ms

And Click on time window date 15s 756ms

And Select view "DAYS_4" 2s 072ms

And Move advice window "3" 1s 496ms

Then Check if advice window is in new location 130ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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

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

And Show all transport "false" 018ms

And Click on time window date 15s 539ms

And Select view "DAYS_4" 2s 071ms

And Move advice window "3" 1s 395ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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

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

And Show all transport "false" 020ms

And Click on time window date 1s 429ms

And Select view "DAYS_4" 2s 067ms

And Move advice window "3" 1s 412ms

Then Check if advice window is in new location 023ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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

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

And Show all transport "false" 016ms

And Click on time window date 1s 283ms

And Select view "DAYS_4" 2s 063ms

And Move advice window "3" 1s 298ms

Then Check if advice window is in new location 026ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

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

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

And Show all transport "true" 081ms

And Click on time window date 1s 351ms

And Select view "DAYS_4" 2s 074ms

And Move advice window "3" 1s 357ms

Then Check if advice window is in new location 026ms

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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

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

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

And Set advice window in schedule 2s 562ms

And Fill advice form 8s 444ms

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

And Go to "TRANSPORT_TABLE" 243ms

And Click on time window date 1s 414ms

And Select view "DAYS_4" 2s 051ms

And Move advice window "3" 1s 413ms

Then Check if advice window is in new location 028ms

Hooks

After Hooks.deleteTransportAfterTest() 145ms

@deleteTransportAfterTest

Scenario Outline Check if late advice is red

Steps

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

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

Hooks

After Hooks.deleteTransportAfterTest() 134ms

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

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

And Go to "TRANSPORT_TABLE" 142ms

And Show all transport types 1s 044ms

And Click on time window date 1s 284ms

And Scroll to time window "adviceWindow" 038ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 136ms

And Show all transport types 1s 046ms

And Click on time window date 1s 427ms

And Scroll to time window "adviceWindow" 038ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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

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

And Go to "TRANSPORT_TABLE" 137ms

And Show all transport types 1s 047ms

And Click on time window date 1s 320ms

And Scroll to time window "adviceWindow" 039ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 278ms

And Show all transport types 15s 042ms

And Click on time window date 15s 794ms

And Scroll to time window "adviceWindow" 041ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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

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

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

When Show all transport types 1s 045ms

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

And Set advice window in schedule 2s 548ms

And Fill advice form 8s 439ms

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

And Go to "TRANSPORT_TABLE" 241ms

And Click on time window date 1s 431ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 145ms

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

And Go to "WAREHOUSE_TAB" 770ms

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

When Go to new transport "DELIVERY" 404ms

And Fill transport form 40s 043ms

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

And Click previous page button in browser 025ms

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

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

And Go to "WAREHOUSE_TAB" 740ms

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

When Go to new transport "DELIVERY" 392ms

And Fill transport form 40s 290ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 001ms

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

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

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

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

When Show all transport types 1s 038ms

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

And Fill advice form 11s 660ms

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

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

And Open statuses popup 110ms

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

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

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

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

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

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

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

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

And Set advice window in schedule 2s 720ms

And Fill advice form 9s 354ms

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

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

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

When Go to "TRANSPORT_TABLE" 247ms

And Show all transport types 1s 045ms

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

And Set advice window in schedule 2s 682ms

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

Then Verify if mode of transportation select is empty 073ms

Hooks

After Hooks.deleteAllTransports() 15s 061ms

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.VrsAKg}, 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: 45c1be08725a83b295951a89998878c6
*** 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() 154ms

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

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

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

And Go to "WAREHOUSE_TAB" 602ms

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

And Set week view 2s 360ms

And Move cursor over time window element 435ms

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

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

	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 59s 525ms	Failed

Feature Report