Cucumber-JVM Reports - Feature: Advice transport

Project	Number	Date
ApolloFullRunnerReport	develop.320	26 lut 2021, 04:26

	Steps	Scenarios	Features
Advice transport	398	4	6	0	0	408	35	4	39	29m 39s 058ms	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" 1s 886ms

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

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

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

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

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

And Fill advice form 16s 446ms

And Click advice save button to check error message 081ms

Then Check if possible advice alert is displayed 024ms

Hooks

After Hooks.deleteTransportAfterTest() 193ms

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

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

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

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

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

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

Then Check if possible advice alert is displayed 019ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

@deleteTransportAfterTest

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

Steps

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

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

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

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

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

And Fill advice form 8s 535ms

And Click advice save button to check error message 111ms

Then Check if possible advice alert is displayed 024ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

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

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

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

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

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

And Fill advice form 13s 302ms

And Click advice save button to check error message 098ms

Then Check if possible advice alert is displayed 024ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

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

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

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

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

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

And Fill advice form 13s 350ms

And Click advice save button to check error message 108ms

Then Check if possible advice alert is displayed 028ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

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

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

And Show all transport types 1s 054ms

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

And Go to "TRANSPORT_TABLE" 153ms

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

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

And Fill transport form 4s 740ms

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

And Expand advice panel 124ms

And Edit advice in transport details 12s 546ms

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

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

And Expand advice panel 123ms

Then Check are advice values equals after edition 234ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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

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

And Show all transport types 1s 046ms

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

And Go to "TRANSPORT_TABLE" 237ms

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

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

And Fill transport form 1m 2s 576ms

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

And Expand advice panel 115ms

And Edit advice in transport details 6s 689ms

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

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

And Expand advice panel 097ms

Then Check are advice values equals after edition 096ms

Hooks

After Hooks.deleteTransportAfterTest() 182ms

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

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

And Show all transport types 1s 030ms

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

And Go to "TRANSPORT_TABLE" 188ms

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

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

And Fill transport form 57s 591ms

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

And Expand advice panel 117ms

And Edit advice in transport details 6s 694ms

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

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

And Expand advice panel 116ms

Then Check are advice values equals after edition 100ms

Hooks

After Hooks.deleteTransportAfterTest() 167ms

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

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

And Show all transport types 1s 046ms

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

And Go to "TRANSPORT_TABLE" 184ms

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

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

And Fill transport form 24s 768ms

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

And Expand advice panel 125ms

And Edit advice in transport details 18s 719ms

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

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

And Expand advice panel 119ms

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

Hooks

After Hooks.deleteTransportAfterTest() 160ms

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

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

And Show all transport types 1s 046ms

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

And Go to "TRANSPORT_TABLE" 170ms

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

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

And Fill transport form 24s 813ms

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

And Expand advice panel 116ms

And Edit advice in transport details 18s 664ms

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

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

And Expand advice panel 114ms

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

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

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

When Show all transport types 1s 053ms

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

And Set advice window in schedule 2s 390ms

And Fill advice form 12s 486ms

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

And Go to "TRANSPORT_TABLE" 166ms

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

Then Check are advice values equals 357ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

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

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

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

When Show all transport types 1s 036ms

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

And Set advice window in schedule 6s 479ms

And Fill advice form 11s 899ms

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

And Go to "TRANSPORT_TABLE" 195ms

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

Then Check are advice values equals 2s 325ms

Hooks

After Hooks.deleteTransportAfterTest() 169ms

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

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

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

When Show all transport types 1s 049ms

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

And Set advice window in schedule 2s 600ms

And Fill advice form 8s 462ms

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

And Go to "TRANSPORT_TABLE" 229ms

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

Then Check are advice values equals 234ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

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

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

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

And Set advice window in schedule 2s 531ms

And Fill advice form 8s 438ms

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

And Go to "TRANSPORT_TABLE" 197ms

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

Then Check are advice values equals 202ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

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

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

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

When Show all transport types 1s 045ms

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

And Set advice window in schedule 2s 408ms

And Fill advice form 13s 283ms

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

And Go to "TRANSPORT_TABLE" 168ms

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

Then Check are advice values equals 2s 345ms

Hooks

After Hooks.deleteTransportAfterTest() 109ms

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

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

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

When Show all transport types 1s 052ms

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

And Set advice window in schedule 2s 408ms

And Fill advice form 13s 340ms

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

And Go to "TRANSPORT_TABLE" 127ms

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

Then Check are advice values equals 2s 364ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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

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

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

And Fill transport form 37s 625ms

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

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

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-128-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.R7AwbA}, 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: be60914cafc82ac1cdc6c57659be12fc
	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 148ms

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

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

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

And Accept transferred transport by Api 355ms

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

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

When Show all transport types 1s 039ms

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

And Set advice window in schedule 2s 346ms

And Fill advice form 11s 861ms

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

And Go to "TRANSPORT_TABLE" 214ms

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

Then Check are advice values equals 2s 321ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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

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

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

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

And Accept transferred transport by Api 117ms

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

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

And Set advice window in schedule 2s 622ms

And Fill advice form 14s 732ms

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

And Go to "TRANSPORT_TABLE" 173ms

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

Then Check are advice values equals 2s 325ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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

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

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

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

And Accept transferred transport by Api 084ms

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

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

When Show all transport types 1s 043ms

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

And Set advice window in schedule 2s 638ms

And Fill advice form 14s 626ms

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

And Go to "TRANSPORT_TABLE" 167ms

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

Then Check are advice values equals 2s 337ms

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

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

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

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

And Accept transferred transport by Api 089ms

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

When Show all transport types 1s 051ms

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

And Set week view 1s 512ms

And Show yesterday 1s 127ms

Then Check if advice restriction blockade windows are visible 025ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

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

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

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

And Accept transferred transport by Api 092ms

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

When Show all transport types 1s 025ms

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

And Set week view 2s 046ms

And Show yesterday 1s 113ms

Then Check if advice restriction blockade windows are visible 034ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

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

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

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

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

And Accept transferred transport by Api 097ms

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

When Show all transport types 1s 046ms

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

And Set week view 2s 066ms

And Show yesterday 1s 109ms

Then Check if advice restriction blockade windows are visible 030ms

Hooks

After Hooks.deleteTransportAfterTest() 076ms

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

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

And Show all transport "false" 031ms

And Click on time window date 1s 311ms

And Select view "DAYS_4" 2s 075ms

And Move advice window "3" 1s 315ms

Then Check if advice window is in new location 030ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

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

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

And Show all transport "false" 014ms

And Click on time window date 15s 700ms

And Select view "DAYS_4" 2s 076ms

And Move advice window "3" 1s 487ms

Then Check if advice window is in new location 097ms

Hooks

After Hooks.deleteTransportAfterTest() 097ms

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

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

And Show all transport "false" 016ms

And Click on time window date 15s 606ms

And Select view "DAYS_4" 2s 120ms

And Move advice window "3" 1s 402ms

Then Check if advice window is in new location 028ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

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

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

And Show all transport "false" 020ms

And Click on time window date 1s 421ms

And Select view "DAYS_4" 2s 058ms

And Move advice window "3" 1s 422ms

Then Check if advice window is in new location 026ms

Hooks

After Hooks.deleteTransportAfterTest() 158ms

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

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

And Show all transport "false" 015ms

And Click on time window date 1s 297ms

And Select view "DAYS_4" 2s 064ms

And Move advice window "3" 1s 316ms

Then Check if advice window is in new location 024ms

Hooks

After Hooks.deleteTransportAfterTest() 129ms

@deleteTransportAfterTest

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

Steps

Given Login as "alrec-admin" and set token of apiUsername "super-admin-alrec" 1s 091ms

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

And Show all transport "true" 075ms

And Click on time window date 1s 376ms

And Select view "DAYS_4" 2s 070ms

And Move advice window "3" 1s 338ms

Then Check if advice window is in new location 018ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

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

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

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

When Show all transport types 1s 046ms

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

And Set advice window in schedule 2s 532ms

And Fill advice form 8s 460ms

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

And Go to "TRANSPORT_TABLE" 217ms

And Click on time window date 1s 399ms

And Select view "DAYS_4" 2s 052ms

And Move advice window "3" 1s 431ms

Then Check if advice window is in new location 026ms

Hooks

After Hooks.deleteTransportAfterTest() 136ms

@deleteTransportAfterTest

Scenario Outline Check if late advice is red

Steps

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 095ms

And Show all transport types 1s 032ms

And Click on time window date 1s 326ms

And Scroll to time window "adviceWindow" 047ms

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

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

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

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

And Go to "TRANSPORT_TABLE" 113ms

And Show all transport types 1s 046ms

And Click on time window date 1s 413ms

And Scroll to time window "adviceWindow" 053ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 108ms

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

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

And Go to "TRANSPORT_TABLE" 107ms

And Show all transport types 1s 038ms

And Click on time window date 1s 307ms

And Scroll to time window "adviceWindow" 055ms

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 241ms

And Show all transport types 15s 006ms

And Click on time window date 15s 825ms

And Scroll to time window "adviceWindow" 054ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 140ms

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

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

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

When Show all transport types 1s 047ms

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

And Set advice window in schedule 2s 562ms

And Fill advice form 8s 493ms

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

And Go to "TRANSPORT_TABLE" 216ms

And Click on time window date 1s 426ms

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

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

Hooks

After Hooks.deleteTransportAfterTest() 092ms

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

And Go to "WAREHOUSE_TAB" 766ms

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

When Go to new transport "DELIVERY" 407ms

And Fill transport form 40s 329ms

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

And Click previous page button in browser 025ms

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

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

And Go to "WAREHOUSE_TAB" 747ms

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

When Go to new transport "DELIVERY" 407ms

And Fill transport form 40s 181ms

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

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

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

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

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

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

When Show all transport types 1s 034ms

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

And Fill advice form 11s 643ms

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

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

And Open statuses popup 121ms

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

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

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Advice transport	398	4	6	0	0	408	35	4	39	29m 39s 058ms	Failed

Feature Report