Cucumber-JVM Reports - Feature: Advice transport

Project	Number	Date
ApolloFullRunnerReport	after_release_3_6_0.326	28 lut 2021, 13:03

	Steps	Scenarios	Features
Advice transport	421	6	6	0	0	433	35	6	41	31m 3s 704ms	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 407ms

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

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

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

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

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

And Fill advice form 16s 319ms

And Click advice save button to check error message 086ms

Then Check if possible advice alert is displayed 020ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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

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

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

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

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

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

And Fill advice form 8s 467ms

And Click advice save button to check error message 090ms

Then Check if possible advice alert is displayed 033ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

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

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

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

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

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

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

And Fill advice form 8s 518ms

And Click advice save button to check error message 101ms

Then Check if possible advice alert is displayed 027ms

Hooks

After Hooks.deleteTransportAfterTest() 087ms

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

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

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

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

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

And Fill advice form 13s 321ms

And Click advice save button to check error message 090ms

Then Check if possible advice alert is displayed 025ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

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

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

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

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

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

And Fill advice form 13s 203ms

And Click advice save button to check error message 091ms

Then Check if possible advice alert is displayed 020ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

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

And Show all transport types 1s 044ms

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

And Go to "TRANSPORT_TABLE" 170ms

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

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

And Fill transport form 4s 747ms

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

And Expand advice panel 110ms

And Edit advice in transport details 12s 564ms

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

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

And Expand advice panel 117ms

Then Check are advice values equals after edition 203ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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

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

And Show all transport types 1s 049ms

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

And Go to "TRANSPORT_TABLE" 233ms

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

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

And Fill transport form 1m 2s 605ms

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

And Expand advice panel 122ms

And Edit advice in transport details 6s 650ms

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

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

And Expand advice panel 111ms

Then Check are advice values equals after edition 114ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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

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

And Show all transport types 1s 047ms

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

And Go to "TRANSPORT_TABLE" 191ms

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

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

And Fill transport form 57s 639ms

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

And Expand advice panel 121ms

And Edit advice in transport details 6s 694ms

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

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

And Expand advice panel 128ms

Then Check are advice values equals after edition 102ms

Hooks

After Hooks.deleteTransportAfterTest() 152ms

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

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

And Show all transport types 1s 052ms

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

And Go to "TRANSPORT_TABLE" 153ms

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

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

And Fill transport form 24s 781ms

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

And Expand advice panel 119ms

And Edit advice in transport details 18s 570ms

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

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

And Expand advice panel 112ms

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

Hooks

After Hooks.deleteTransportAfterTest() 118ms

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

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

And Show all transport types 1s 050ms

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

And Go to "TRANSPORT_TABLE" 190ms

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

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

And Fill transport form 24s 722ms

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

And Expand advice panel 120ms

And Edit advice in transport details 18s 607ms

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

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

And Expand advice panel 116ms

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

Hooks

After Hooks.deleteTransportAfterTest() 126ms

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

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

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

When Show all transport types 1s 048ms

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

And Set advice window in schedule 2s 367ms

And Fill advice form 12s 508ms

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

And Go to "TRANSPORT_TABLE" 182ms

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

Then Check are advice values equals 346ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

@deleteTransportAfterTest

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

Steps

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

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

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

When Show all transport types 1s 051ms

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

And Set advice window in schedule 6s 419ms

And Fill advice form 11s 955ms

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

And Go to "TRANSPORT_TABLE" 206ms

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

Then Check are advice values equals 2s 336ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

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

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

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

When Show all transport types 1s 048ms

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

And Set advice window in schedule 2s 582ms

And Fill advice form 8s 430ms

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

And Go to "TRANSPORT_TABLE" 223ms

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

Then Check are advice values equals 212ms

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

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

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

When Show all transport types 1s 051ms

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

And Set advice window in schedule 2s 539ms

And Fill advice form 8s 436ms

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

And Go to "TRANSPORT_TABLE" 169ms

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

Then Check are advice values equals 238ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

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

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

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

When Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 387ms

And Fill advice form 13s 302ms

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

And Go to "TRANSPORT_TABLE" 146ms

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

Then Check are advice values equals 2s 350ms

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

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

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

When Show all transport types 1s 056ms

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

And Set advice window in schedule 2s 401ms

And Fill advice form 13s 272ms

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

And Go to "TRANSPORT_TABLE" 172ms

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

Then Check are advice values equals 2s 328ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

@deleteTransportAfterTest

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

Steps

Given Get inputs from database "CREATE_DELIVERY" "super-admin-neuca" 005ms

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

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

And Fill transport form 37s 621ms

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

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

Error message

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for element to no longer be visible: By.xpath: //button[@type='submit' and @data-field-name='save-transport'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'ns3112421', ip: '94.23.29.183', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-136-generic', java.version: '1.8.0_201'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=88.0.4324.96 (68dba2d8a0b149a1d3afac56fa74648032bcf46b-refs/branch-heads/4324@{#1784}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.gwR4g0}, 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: c4feda8e8a8d7520e72db51802c422be
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:82)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:231)
	at Pages.BasePage.waitUntilElementDisappear(BasePage.java:197)
	at Pages.Transport.TransportFormPage.clickSaveButtonAndWaitForFormToDisappear(TransportFormPage.java:254)
	at CucumberTests.Transport.CreateTransport.clickSaveButtonAndWaitForFormToDisappear(CreateTransport.java:188)
	at ✽.Click "save-transport" save button and wait for form to disappear(file:Features/Atom/Advice/AdviceTransport.feature:77)

When Change warehouse in schedule to: "Ołtarzew" 000ms

Then Set advice window in schedule 000ms

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

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

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

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

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

And Accept transferred transport by Api 261ms

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

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

When Show all transport types 1s 039ms

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

And Set advice window in schedule 2s 345ms

And Fill advice form 11s 888ms

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

And Go to "TRANSPORT_TABLE" 209ms

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

Then Check are advice values equals 2s 279ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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

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

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

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

And Accept transferred transport by Api 110ms

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

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

When Show all transport types 1s 039ms

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

And Set advice window in schedule 2s 605ms

And Fill advice form 14s 673ms

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

And Go to "TRANSPORT_TABLE" 189ms

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

Then Check are advice values equals 2s 318ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

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

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

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

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

And Accept transferred transport by Api 095ms

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

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

When Show all transport types 1s 039ms

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

And Set advice window in schedule 2s 590ms

And Fill advice form 14s 645ms

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

And Go to "TRANSPORT_TABLE" 184ms

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

Then Check are advice values equals 2s 302ms

Hooks

After Hooks.deleteTransportAfterTest() 173ms

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

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

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

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

And Accept transferred transport by Api 093ms

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

When Show all transport types 1s 035ms

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

And Set week view 1s 554ms

And Show yesterday 1s 128ms

Then Check if advice restriction blockade windows are visible 021ms

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

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

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

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

And Accept transferred transport by Api 097ms

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

And Set week view 2s 031ms

And Show yesterday 1s 099ms

Then Check if advice restriction blockade windows are visible 030ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

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

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

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

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

And Accept transferred transport by Api 076ms

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

When Show all transport types 1s 039ms

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

And Set week view 2s 049ms

And Show yesterday 1s 110ms

Then Check if advice restriction blockade windows are visible 033ms

Hooks

After Hooks.deleteTransportAfterTest() 107ms

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

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

And Show all transport "false" 027ms

And Click on time window date 1s 268ms

And Select view "DAYS_4" 2s 067ms

And Move advice window "3" 1s 320ms

Then Check if advice window is in new location 027ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

@deleteTransportAfterTest

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

Steps

Given Login as "pgf-admin" and set token of apiUsername "super-admin-pgf" 1s 007ms

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

And Show all transport "false" 016ms

And Click on time window date 15s 682ms

And Select view "DAYS_4" 2s 073ms

And Move advice window "3" 1s 492ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport "false" 020ms

And Click on time window date 15s 478ms

And Select view "DAYS_4" 2s 079ms

And Move advice window "3" 1s 401ms

Then Check if advice window is in new location 024ms

Hooks

After Hooks.deleteTransportAfterTest() 106ms

@deleteTransportAfterTest

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

Steps

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

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

And Show all transport "false" 016ms

And Click on time window date 1s 425ms

And Select view "DAYS_4" 2s 065ms

And Move advice window "3" 1s 407ms

Then Check if advice window is in new location 027ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

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

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

And Show all transport "false" 019ms

And Click on time window date 1s 286ms

And Select view "DAYS_4" 2s 058ms

And Move advice window "3" 1s 306ms

Then Check if advice window is in new location 025ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

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

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

And Show all transport "true" 072ms

And Click on time window date 1s 338ms

And Select view "DAYS_4" 2s 074ms

And Move advice window "3" 1s 346ms

Then Check if advice window is in new location 028ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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

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

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

When Show all transport types 1s 042ms

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

And Set advice window in schedule 2s 537ms

And Fill advice form 8s 478ms

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

And Go to "TRANSPORT_TABLE" 231ms

And Click on time window date 1s 457ms

And Select view "DAYS_4" 2s 052ms

And Move advice window "3" 1s 427ms

Then Check if advice window is in new location 031ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

@deleteTransportAfterTest

Scenario Outline Check if late advice is red

Steps

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

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

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

Error message

java.lang.AssertionError
	at org.junit.Assert.fail(Assert.java:86)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at org.junit.Assert.assertTrue(Assert.java:52)
	at CucumberTests.Transport.TransportUtilTest.checkIfTransportRowIs(TransportUtilTest.java:35)
	at ✽.Check if transport row is "red"(file:Features/Atom/Advice/AdviceTransport.feature:171)

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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

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

And Go to "TRANSPORT_TABLE" 123ms

And Show all transport types 1s 045ms

And Click on time window date 1s 306ms

And Scroll to time window "adviceWindow" 053ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 107ms

And Show all transport types 1s 041ms

And Click on time window date 1s 406ms

And Scroll to time window "adviceWindow" 049ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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

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

And Go to "TRANSPORT_TABLE" 123ms

And Show all transport types 1s 045ms

And Click on time window date 1s 306ms

And Scroll to time window "adviceWindow" 041ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 291ms

And Show all transport types 15s 054ms

And Click on time window date 15s 824ms

And Scroll to time window "adviceWindow" 049ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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

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

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

When Show all transport types 1s 048ms

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

And Set advice window in schedule 2s 526ms

And Fill advice form 8s 414ms

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

And Go to "TRANSPORT_TABLE" 216ms

And Click on time window date 1s 425ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 088ms

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

And Go to "WAREHOUSE_TAB" 769ms

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

When Go to new transport "DELIVERY" 394ms

And Fill transport form 40s 254ms

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

And Click previous page button in browser 027ms

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

Hooks

After Hooks.deleteTransportAfterTest() 002ms

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

And Go to "WAREHOUSE_TAB" 720ms

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

When Go to new transport "DELIVERY" 418ms

And Fill transport form 40s 295ms

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

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

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

Hooks

After Hooks.deleteTransportAfterTest() 002ms

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

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

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

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

When Show all transport types 1s 041ms

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

And Fill advice form 11s 669ms

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

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

And Open statuses popup 104ms

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

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

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

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

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

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

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

And Set advice window in schedule 2s 738ms

And Fill advice form 9s 237ms

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

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

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

When Go to "TRANSPORT_TABLE" 216ms

And Show all transport types 1s 046ms

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

And Set advice window in schedule 2s 636ms

And Select driver "Marek Kanarek" from suggestions 967ms

Then Verify if mode of transportation select is empty 036ms

Hooks

After Hooks.deleteAllTransports() 1m 1s 773ms

After Hooks.deleteModeOfTransportationAfterTest() 108ms

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

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

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

And Go to "WAREHOUSE_TAB" 561ms

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

And Set week view 2s 345ms

And Move cursor over time window element 392ms

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

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

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

Feature Report