Cucumber-JVM Reports - Feature: Advice Mail

Project	Number	Date
ApolloFullRunnerReport	after_release_3_6_0.318	24 lut 2021, 23:40

	Steps	Scenarios	Features
Advice Mail	97	1	0	0	0	98	7	1	8	16m 1s 146ms	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 123ms

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

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

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

And Show all transport types 1s 045ms

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

And Set advice window in schedule 2s 441ms

And Fill advice form 11s 839ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 144ms

After Hooks.cleanUserDetailsAfterTest() 189ms

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

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

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

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

And Show all transport types 1s 048ms

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

And Set advice window in schedule 2s 618ms

And Fill advice form 8s 494ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

After Hooks.cleanUserDetailsAfterTest() 184ms

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

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

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

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

And Show all transport types 1s 045ms

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

And Set advice window in schedule 2s 371ms

And Fill advice form 13s 287ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 131ms

After Hooks.cleanUserDetailsAfterTest() 257ms

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

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

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

And Show all transport types 1s 043ms

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

And Go to "TRANSPORT_TABLE" 185ms

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

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

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

And Fill transport form 4s 746ms

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

And Expand advice panel 120ms

And Edit advice in transport details 12s 510ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 104ms

After Hooks.cleanUserDetailsAfterTest() 153ms

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

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

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

And Show all transport types 1s 052ms

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

And Go to "TRANSPORT_TABLE" 247ms

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

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

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

And Fill transport form 1m 2s 551ms

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

And Expand advice panel 133ms

And Edit advice in transport details 6s 666ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Zmiana w awizacji numer" 3m 15s 657ms

Then Check if user got a mail 000ms

Error message

java.lang.AssertionError: Użytkownik nie otrzymał maila. Actual: 
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failEquals(Assert.java:185)
	at org.junit.Assert.assertNotEquals(Assert.java:161)
	at CucumberTests.Mail.MailTest.checkIfUseGotMail(MailTest.java:33)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/AdviceMail.feature:39)

Hooks

After Hooks.deleteTransportAfterTest() 207ms

After Hooks.cleanUserDetailsAfterTest() 197ms

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

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

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

And Show all transport types 1s 051ms

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

And Go to "TRANSPORT_TABLE" 186ms

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

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

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

And Fill transport form 24s 773ms

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

And Expand advice panel 117ms

And Edit advice in transport details 18s 687ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 165ms

After Hooks.cleanUserDetailsAfterTest() 251ms

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

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

When Get mail "apolloautomattest@gmail.com" message from mail account with "Potwierdzono status Wyjazd" 37s 329ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 182ms

After Hooks.cleanUserDetailsAfterTest() 164ms

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackVerificationEmailSettingAfterTest

Scenario Outline Check if verification mail was sent to transport creator

Steps

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

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

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

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

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

And Wait "120" seconds 2m

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 139ms

After Hooks.cleanUserDetailsAfterTest() 237ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 010ms

	Steps						Scenarios			Features
Feature	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
Advice Mail	97	1	0	0	0	98	7	1	8	16m 1s 146ms	Failed

Feature Report