Cucumber-JVM Reports - Feature: Advice Mail

Project	Number	Date
ApolloFullRunnerReport	develop.360	27 mar 2021, 05:51

	Steps	Scenarios	Features
Advice Mail	95	1	2	0	0	98	7	1	8	13m 56s 397ms	Failed

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after creating advice

Steps

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

And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 127ms

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

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

And Show all transport types 1s 042ms

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

And Set advice window in schedule 2s 485ms

And Fill advice form 11s 903ms

And Click advice save button and wait for advice form to disappear 31s 266ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zapisano awizację! | Advice has been saved!" 37s 833ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 135ms

After Hooks.cleanUserDetailsAfterTest() 176ms

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after creating advice

Steps

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

And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 147ms

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

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

And Show all transport types 1s 045ms

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

And Set advice window in schedule 2s 599ms

And Fill advice form 8s 431ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zapisano awizację! | Advice has been saved!" 7s 279ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 116ms

After Hooks.cleanUserDetailsAfterTest() 178ms

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after creating advice

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 1s 127ms

And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 230ms

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

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

And Show all transport types 1s 047ms

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

And Set advice window in schedule 2s 441ms

And Fill advice form 13s 309ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zapisano awizację! | Time window has been saved!" 7s 276ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

After Hooks.cleanUserDetailsAfterTest() 228ms

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 2s 036ms

And Prepare user "adama-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 182ms

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

And Show all transport types 1s 042ms

And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 45s 161ms

And Go to "TRANSPORT_TABLE" 201ms

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

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

When Go to transport details "CONTAINER" 3s 206ms

And Fill transport form 4s 726ms

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

And Expand advice panel 119ms

And Edit advice in transport details 12s 471ms

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

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-and-close'] (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=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.tUpg08}, 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=89.0.4389.90, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: cedfeacbb839d0235adddd16b68a5978
	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:192)
	at CucumberTests.Transport.CreateTransport.clickSaveButtonAndWaitForFormToDisappear(CreateTransport.java:188)
	at ✽.Click "save-transport-and-close" save button and wait for form to disappear(file:Features/Atom/Mail/AdviceMail.feature:37)

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zmiana w awizacji numer" 000ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

After Hooks.cleanUserDetailsAfterTest() 176ms

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Steps

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

And Prepare user "piast-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 152ms

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

And Show all transport types 1s 050ms

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

And Go to "TRANSPORT_TABLE" 233ms

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

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

When Go to transport details "DELIVERY" 3s 206ms

And Fill transport form 1m 2s 619ms

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

And Expand advice panel 094ms

And Edit advice in transport details 6s 638ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zmiana w awizacji numer" 32s 368ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 152ms

After Hooks.cleanUserDetailsAfterTest() 181ms

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Steps

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

And Prepare user "keeeper-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 246ms

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

And Show all transport types 1s 037ms

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

And Go to "TRANSPORT_TABLE" 198ms

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

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

When Go to transport details "LOAD" 3s 227ms

And Fill transport form 24s 780ms

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

And Expand advice panel 123ms

And Edit advice in transport details 18s 692ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zmiana w awizacji numer" 20s 003ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

After Hooks.cleanUserDetailsAfterTest() 203ms

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after status confirmation

Steps

Given Set token of apiUsername "super-admin-skd" 096ms

And Prepare user "swiss-krono-delivery-admin" details with all notifications and "apolloautomattest@gmail.com" by JSON file 218ms

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 1s 380ms

And Confirm status "ARRIVAL" by Public API "v1" 331ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Potwierdzono status Wjazd na teren zakładu" 12s 746ms

Then Check if user got a mail 000ms

And Confirm status "DEPARTURE" by Public API "v1" 155ms

When Get mail "apolloautomattest@gmail.com" message from mail account with "Potwierdzono status Wyjazd" 1m 19s 892ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

After Hooks.cleanUserDetailsAfterTest() 154ms

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackVerificationEmailSettingAfterTest

Scenario Outline Check if verification mail was sent to transport creator

Steps

Given Set token of apiUsername "super-admin-hochland" 100ms

And Prepare company "Dostawca Hochland Automat 1" verification email setting "48h" 013ms

And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 169ms

And Login as "dha1-supplier-2@qa.qa-test" and set token of apiUsername "dha1-supplier-2@qa.qa-test" 3s 427ms

And Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2@qa.qa-test" 15s 420ms

And Wait "120" seconds 2m

When Get mail "apolloautomattest@gmail.com" message from mail account with "Weryfikacja danych awizacji" 7s 303ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 134ms

After Hooks.cleanUserDetailsAfterTest() 233ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 007ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Advice Mail	95	1	2	0	0	98	7	1	8	13m 56s 397ms	Failed

Feature Report