Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.66	19 sie 2021, 05:10

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	432	1	5	0	0	438	44	1	45	47m 59s 443ms	Failed

View Feature Invitation

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if rejected invitation is visible in rejected tab

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Delete invitations with email "automaty31415@test.pl" 015ms

Then Create invitation by JSON file "super-admin-alrec" for "automaty31415@test.pl" "CREATE_SUPPLIER_INVITATION" 765ms

And Prepare user "piast-admin" details with all notifications and "automaty31415@test.pl" by JSON file 196ms

When Login as "piast-admin" 1s 279ms

Then Go to "INVITATIONS_TAB" 194ms

And Go to invitation details 058ms

Then Reject invitation by button as user 114ms

When If user is login then logout 264ms

Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 1s 430ms

And Go to "INVITATIONS_TAB" 187ms

And Go to "REJECTED_TAB" invitation status tab 079ms

Then Invitation is displayed on list "automaty31415@test.pl" 148ms

Hooks

After Hooks.deleteInvitationAfterTest() 021ms

After Hooks.cleanUserDetailsAfterTest() 179ms

View Feature Invitation

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it is possible to invite existing user in order to associate him with principal company [A-7315]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-alrec" 097ms

And Prepare user "dha1-supplier-2@qa.qa-test" details with all notifications and "automatyy3333@test.pl" by JSON file 219ms

When Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 980ms

And Go to "INVITATIONS_TAB" 174ms

And Create invitation for "existing" user "SUPPLIER" "SUPPLIER" "automatyy3333@test.pl" "PL" 1s 144ms

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 043ms

Hooks

After Hooks.deleteInvitationAfterTest() 037ms

After Hooks.cleanUserDetailsAfterTest() 217ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 987ms

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

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

And Set "advice" inputs from JSON file "ADVICE_CONTAINER" "super-admin-adama" 002ms

And Show all transport types 1s 034ms

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

And Set advice window in schedule 2s 519ms

And Fill advice form 14s 014ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

After Hooks.cleanUserDetailsAfterTest() 145ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Show all transport types 1s 037ms

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

And Set advice window in schedule 2s 642ms

And Fill advice form 10s 493ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zapisano awizację! | Advice has been saved!" 5s 972ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

After Hooks.cleanUserDetailsAfterTest() 157ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Set "advice" inputs from JSON file "ADVICE_LOAD" "super-admin-keeeper" 001ms

And Show all transport types 1s 045ms

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

And Set advice window in schedule 2s 483ms

And Fill advice form 15s 396ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

After Hooks.cleanUserDetailsAfterTest() 210ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Show all transport types 1s 033ms

And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama" 588ms

And Go to "TRANSPORT_TABLE" 135ms

And Go to transport details "CONTAINER" 2s 461ms

And Set "transport" inputs from JSON file "EDIT_CONTAINER" "super-admin-adama" 001ms

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

And Fill transport form 4s 697ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_CONTAINER" "super-admin-adama" 001ms

And Expand advice panel 119ms

And Edit advice in transport details 14s 675ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 31s 555ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 123ms

After Hooks.cleanUserDetailsAfterTest() 192ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Show all transport types 1s 044ms

And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 587ms

And Go to "TRANSPORT_TABLE" 133ms

And Go to transport details "DELIVERY" 2s 581ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-piast" 001ms

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

And Fill transport form 1m 2s 391ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_DELIVERY" "super-admin-piast" 001ms

And Expand advice panel 124ms

And Edit advice in transport details 6s 594ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 140ms

After Hooks.cleanUserDetailsAfterTest() 165ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

And Show all transport types 1s 042ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper" 606ms

And Go to "TRANSPORT_TABLE" 149ms

And Go to transport details "LOAD" 2s 427ms

And Set "transport" inputs from JSON file "EDIT_LOAD" "super-admin-keeeper" 001ms

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

And Fill transport form 26s 069ms

And Set "advice" inputs from JSON file "EDIT_ADVICE_LOAD" "super-admin-keeeper" 001ms

And Expand advice panel 140ms

And Edit advice in transport details 20s 498ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 3m 896ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

After Hooks.cleanUserDetailsAfterTest() 221ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu" 5s 176ms

Then Check if user got a mail 000ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wyjazd" 26s 150ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

After Hooks.cleanUserDetailsAfterTest() 160ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackVerificationEmailSettingAfterTest

Scenario Outline Check if verification mail was sent to transport creator

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Weryfikacja danych awizacji" 1m 19s 608ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

After Hooks.cleanUserDetailsAfterTest() 226ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 137ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating a new auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 210ms

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

And Set transport on auction with "500" and "20000" by JSON file as "super-admin-adama" 2s 542ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowa aukcja" 10s 390ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

After Hooks.cleanUserDetailsAfterTest() 273ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 339ms

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

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 128ms

And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 463ms

And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 408ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 5s 183ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 074ms

After Hooks.cleanUserDetailsAfterTest() 287ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after bid has been added to auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-producer" and set token of apiUsername "super-admin-skz" 2s 538ms

And Prepare user "swisskrono-producer" details with all notifications and "apolloautomattest@gmail.com" by JSON file 367ms

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

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 112ms

And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 196ms

And Wait till auction end 1m 58s 018ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Dodano nową ofertę" 2m 42s 822ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.cleanUserDetailsAfterTest() 305ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after auction without bids

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 142ms

And Wait till auction end 1m 58s 017ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Aukcja zakończona bez ofert" 22s 086ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

After Hooks.cleanUserDetailsAfterTest() 178ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing first place in auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 327ms

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

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 145ms

And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 176ms

And Add a bid "500" to an auction by JSON file as "paa2-carrier@qa.qa-test" for "super-admin-adama" 281ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Oferta przelicytowana" 37s 679ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

After Hooks.cleanUserDetailsAfterTest() 242ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after winning an auction

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 325ms

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

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 137ms

And Add a bid "1500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 170ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 2m 9s 070ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

After Hooks.cleanUserDetailsAfterTest() 301ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after accepting minimal price

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 327ms

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

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" 2s 107ms

And Add a bid "500" to an auction by JSON file as "paa1-carrier@qa.qa-test" for "super-admin-adama" 333ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 5s 507ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

After Hooks.cleanUserDetailsAfterTest() 299ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail two hours before auction ends

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "paa1-carrier@qa.qa-test" and set token of apiUsername "super-admin-adama" 1s 733ms

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 333ms

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

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-adama" and finish of auction in "121" minutes 2s 184ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji" 31s 826ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

After Hooks.cleanUserDetailsAfterTest() 268ms

View Feature Discrepancy Report Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after discrepancy report generation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Go to "TRANSPORT_TABLE" 131ms

And Go to transport details "DELIVERY" 2s 733ms

And Set "transport" inputs from JSON file "EDIT_DELIVERY" "super-admin-hochland" 001ms

And Fill transport form 37s 910ms

And Open section: "discrepancy-report-panel" 1s 067ms

And Fill discrepancy report section 49s 616ms

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

And Change filled value in details "rodo-acceptance" "checkbox" "true" "0" 1s 287ms

And Generate discrepancy report 18s 826ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Utworzono protokół niezgodności" 5s 494ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 146ms

After Hooks.cleanUserDetailsAfterTest() 444ms

View Feature Mode of transportation mail

@deleteModeOfTransportationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent after updating mode of transportation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 093ms

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

When Create default mode of transportation by API with "pba1-carrier" 181ms

Then Update mode of transportation by API with "pba1-carrier": "BBBB0000" "Model2" "Marka2" "CCCC0000" 073ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Środek transportu BBBB0000 został zaktualizowany" 10s 352ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 303ms

After Hooks.deleteModeOfTransportationAfterTest() 105ms

View Feature Mode of transportation mail

@deleteModeOfTransportationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent after creating mode of transportation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

When Create default mode of transportation by API with "pba1-carrier" 081ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowy środek transportu" 5s 254ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 296ms

After Hooks.deleteModeOfTransportationAfterTest() 056ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackAddedAuthorities

Scenario Outline Check if mail was sent to after transport delay

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 2s 424ms

And Prepare user "pha2-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 380ms

And Set basic authorities "ROLE_CAN_PLAN_ADVICE_IN_THE_PAST" to user "hochland-admin" 024ms

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

And Go to "WAREHOUSE_TAB" 829ms

And Select warehouse "Serownia" 1s 368ms

And Set week view 1s 096ms

And Show yesterday 1s 067ms

And Move window into the past 299ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 36s 390ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

After Hooks.cleanUserDetailsAfterTest() 308ms

After Hooks.rollbackAddedAuthorities() 021ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 207ms

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

And Wait "60" seconds 1m

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import" 52s 457ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 081ms

After Hooks.cleanUserDetailsAfterTest() 306ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 873ms

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

And Wait "60" seconds 1m

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica eksport" 58s 783ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

After Hooks.cleanUserDetailsAfterTest() 312ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @FLAKY-A-7913

Scenario Outline Check if mail was sent to carrier after transport transfer

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 325ms

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

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true" 33s 786ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zlecenie czeka na akceptację" 5s 534ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 089ms

After Hooks.cleanUserDetailsAfterTest() 265ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @FLAKY-A-7913

Scenario Outline Check if mail was sent to carrier after transport transfer with no confirmation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "paa1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 338ms

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

And Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false" 33s 770ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zostało przekazane nowe zlecenie" 5s 447ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 073ms

After Hooks.cleanUserDetailsAfterTest() 269ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 871ms

And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 426ms

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

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 170ms

And Add a bid "1500" to an auction by JSON file as "pskza1-carrier@qa.qa-test" for "pskza1-carrier@qa.qa-test" 234ms

And Add a bid "500" to an auction by JSON file as "pskza2-carrier-2@qa.qa-test" for "pskza2-carrier-2@qa.qa-test" 235ms

Then If user is login then logout 303ms

And Login as "swisskrono-admin" 1s 006ms

And Go to auction details 1s 208ms

And Pass transport to carrier from auction details 1s 281ms

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 20s 992ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 114ms

After Hooks.cleanUserDetailsAfterTest() 353ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating new inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 272ms

And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "apolloautomattest@gmail.com" by JSON file 456ms

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

And Set transport on auction with "500" and "1500" by JSON file as "super-admin-skz" 2s 145ms

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nowe zapytanie ofertowe" 5s 387ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

After Hooks.cleanUserDetailsAfterTest() 346ms

View Feature Remind password

@cleanUserDetailsAfterTest

Scenario Outline Check if remind password http status is ok

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-adama" 090ms

And Prepare user "adama-admin" details with all notifications and "automaty10@o2.pl" by JSON file 219ms

Then Send password remind email "automaty10@o2.pl" and check if status is ok 161ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 166ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it possible to advice transport when transport is created by sk API

The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 155ms

And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 000ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 378ms

And Add transport by SKApi in "MGW" assigned to "" 002ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "CONTAINER" created in transport table and set transport id 6s 311ms

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

And Set advice window in schedule 2s 606ms

And Fill advice form 16s 804ms

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

And Go to "TRANSPORT_TABLE" 183ms

And Go to transport details "CONTAINER" 2s 496ms

Then Check are advice values equals 4s 330ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

After Hooks.cleanUserDetailsAfterTest() 261ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it possible to advice transport when transport is created by sk API

The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 2s 215ms

And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 000ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 332ms

And Add transport by SKApi in "MGW" assigned to "" 003ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 6s 381ms

When Click button advice in transport table "OWN_COLLECTION" 098ms

And Set advice window in schedule 2s 577ms

And Fill advice form 16s 738ms

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

And Go to "TRANSPORT_TABLE" 220ms

And Go to transport details "OWN_COLLECTION" 2s 469ms

Then Check are advice values equals 4s 357ms

Hooks

After Hooks.deleteTransportAfterTest() 149ms

After Hooks.cleanUserDetailsAfterTest() 314ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it possible to advice transport when transport is created by sk API

The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 888ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 314ms

And Add transport by SKApi in "MGW" assigned to "" 002ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 2s 919ms

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

And Set advice window in schedule 2s 559ms

And Fill advice form 16s 706ms

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

And Go to "TRANSPORT_TABLE" 228ms

And Go to transport details "TRANSPORT_ORDER" 2s 484ms

Then Check are advice values equals 4s 321ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.cleanUserDetailsAfterTest() 287ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it possible to advice transport when transport is created by sk API

The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 168ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 000ms

And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 469ms

And Add transport by SKApi in "MGW" assigned to "" 003ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 908ms

When Click button advice in transport table "TRANSPORT_ORDER" 093ms

And Set advice window in schedule 2s 569ms

And Fill advice form 16s 878ms

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

And Go to "TRANSPORT_TABLE" 225ms

And Go to transport details "TRANSPORT_ORDER" 2s 411ms

Then Check are advice values equals 4s 357ms

Hooks

After Hooks.deleteTransportAfterTest() 119ms

After Hooks.cleanUserDetailsAfterTest() 371ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it possible to advice transport when transport is created by sk API

The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 892ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 253ms

And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 003ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 962ms

When Click button advice in transport table "TRANSPORT_ORDER" 095ms

And Set advice window in schedule 30s 083ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//button[@data-button-name='SHIFT_RIGHT_DAY']"}
  (Session info: headless chrome=92.0.4515.131)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-63-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=92.0.4515.107 (87a818b10553a07434ea9e2b6dccf3cbe7895134-refs/branch-heads/4515@{#1634}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.NPWs6k}, timeouts={implicit=0, pageLoad=300000, script=30000}, pageLoadStrategy=normal, unhandledPromptBehavior=dismiss and notify, strictFileInteractability=false, platform=LINUX, proxy=Proxy(), goog:chromeOptions={debuggerAddress=localhost:9222}, webauthn:extension:credBlob=true, acceptInsecureCerts=false, browserVersion=92.0.4515.131, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 78025d07d5c75dd1bb40551e02dce894
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.GeneratedConstructorAccessor214.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at Pages.BasePage.getWebElementByXpath(BasePage.java:323)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:91)
	at ✽.Set advice window in schedule(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:13)

And Fill advice form 000ms

And Click advice save button and wait for advice form to disappear 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "TRANSPORT_ORDER" 000ms

Then Check are advice values equals 000ms

Hooks

After Hooks.deleteTransportAfterTest() 067ms

After Hooks.cleanUserDetailsAfterTest() 224ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 918ms

And Set "transport" inputs from JSON file "CREATE_OWN_COLLECTION" "super-admin-skz" 000ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 336ms

And Add transport by SKApi in "MGW" assigned to "" 003ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 6s 384ms

When Click button advice in transport table "OWN_COLLECTION" 084ms

And Set advice window in schedule 2s 591ms

And Fill advice form 16s 888ms

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

And Go to "TRANSPORT_TABLE" 192ms

Then Check advice data in SK API database "OWN_COLLECTION" 150ms

Hooks

After Hooks.deleteTransportAfterTest() 122ms

After Hooks.cleanUserDetailsAfterTest() 271ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 919ms

And Set "transport" inputs from JSON file "CREATE_CONTAINER" "super-admin-skz" 000ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 352ms

And Add transport by SKApi in "MGW" assigned to "" 003ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "CONTAINER" created in transport table and set transport id 3s 334ms

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

And Set advice window in schedule 2s 592ms

And Fill advice form 16s 736ms

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

And Go to "TRANSPORT_TABLE" 250ms

Then Check advice data in SK API database "CONTAINER" 100ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

After Hooks.cleanUserDetailsAfterTest() 279ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-admin" and set token of apiUsername "super-admin-skz" 1s 895ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

And Prepare user "swisskrono-admin" details with all notifications and "" by JSON file 361ms

And Add transport by SKApi in "MGW" assigned to "" 002ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 000ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 872ms

When Click button advice in transport table "TRANSPORT_ORDER" 084ms

And Set advice window in schedule 2s 571ms

And Fill advice form 16s 740ms

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

And Go to "TRANSPORT_TABLE" 211ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 041ms

Hooks

After Hooks.deleteTransportAfterTest() 102ms

After Hooks.cleanUserDetailsAfterTest() 294ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 1s 735ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

And Prepare user "pskza1-carrier@qa.qa-test" details with all notifications and "" by JSON file 507ms

And Add transport by SKApi in "MGW" assigned to "" 003ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 5s 839ms

When Click button advice in transport table "TRANSPORT_ORDER" 098ms

And Set advice window in schedule 2s 578ms

And Fill advice form 16s 690ms

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

And Go to "TRANSPORT_TABLE" 237ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 041ms

Hooks

After Hooks.deleteTransportAfterTest() 096ms

After Hooks.cleanUserDetailsAfterTest() 327ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 2s 055ms

And Set "transport" inputs from JSON file "CREATE_TRANSPORT_ORDER" "super-admin-skz" 001ms

And Prepare user "swisskrono-tradesman@qa.qa-test" details with all notifications and "automaty@test.pl" by JSON file 278ms

And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 003ms

And Set "advice" inputs from JSON file "CREATE_ADVICE" "super-admin-skz" 001ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 2s 950ms

When Click button advice in transport table "TRANSPORT_ORDER" 096ms

And Set advice window in schedule 2s 583ms

And Fill advice form 16s 806ms

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

And Go to "TRANSPORT_TABLE" 176ms

Then Check advice data in SK API database "TRANSPORT_ORDER" 081ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

After Hooks.cleanUserDetailsAfterTest() 245ms

View Feature Status rejection

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackWarehousesAccess

Scenario Outline Check if it is possible to reject status by guard in transport table

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare user "lantmannen-guard" details with all notifications and "apolloautomattest@gmail.com" by JSON file 259ms

And Prepare user "pla1-carrier" details with all notifications and "apolloautomattest@gmail.com" by JSON file 195ms

And Add access to the warehouse "Magazyn - Nowa Sól" to the user "lantmannen-guard" by JSON file 133ms

And Login as "lantmannen-guard" and set token of apiUsername "super-admin-lantmannen" 1s 242ms

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 1s 296ms

And Check if reject date is not visible 15s 009ms

When Reject status: Book of disinfection 099ms

And Check if reject date is visible 261ms

Then If user is login then logout 253ms

And Login as "lantmannen-admin" 897ms

And Check if note was added to transport after status rejection 1s 230ms

And Check if history note was added to transport after status rejection - "LOAD" 6s 546ms

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji" 2m 46s 861ms

And Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 141ms

After Hooks.cleanUserDetailsAfterTest() 191ms

After Hooks.rollbackWarehousesAccess() 135ms

View Feature User

@cleanUserDetailsAfterTest @TmsLink=A-8005.1

Scenario Outline Check if it is not possible to use the previous password when editing it - remind password [A-8005]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Prepare login page 202ms

And Click remind password button 088ms

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

And Send remind password form with email "apolloautomattest@gmail.com" 177ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Restart hasła! | Password reset!" 32s 616ms

And Extract password from mailgun mail 4s 176ms

And Reset password from link 705ms

Then Check if alert is displayed "Hasło nie może być takie samo jak aktualne hasło użytkownika." in remind password page 154ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 156ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7965

Scenario Outline Permission - Edit user main data [A-7965]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2@qa.qa-test" 047ms

When Login as "oaa1-receiver-2@qa.qa-test" 1s 279ms

And Go to user "oaa1-receiver@qa.qa-test" details edition by prepared link 019ms

And Change user details "email" to "newEmailAddress@newEmail.com" 260ms

And Change user details "phone" to "123456789" 153ms

Then Save user details 251ms

And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 056ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 105ms

After Hooks.rollbackAddedAuthorities() 036ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user notifications [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_USERS_TAB;EDIT_USERS_NOTIFICATION" to user "pskza1-carrier-2@qa.qa-test" 025ms

When Login as "pskza1-carrier-2@qa.qa-test" 1s 778ms

And Go to user "pskza1-carrier@qa.qa-test" details edition by prepared link 036ms

And Expand "other" notification section 410ms

And Select all notifications in "other" section 095ms

Then Save user details 382ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 142ms

After Hooks.rollbackAddedAuthorities() 022ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user main data from other company [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;ROLE_EDIT_USERS_MAIN_DATA" to user "adama-buyer@qa.qa-test" 063ms

And Set user details json of user "oaa1-receiver@qa.qa-test" 001ms

When Login as "adama-buyer@qa.qa-test" 1s 395ms

And Go to "USERS_TAB" 908ms

And Find user "oaa1-receiver@qa.qa-test" 2s 286ms

And Change user details "email" to "newEmailAddress@newEmail.com" 241ms

And Change user details "phone" to "123456789" 140ms

Then Save user details 234ms

And Verify if "newEmailAddress@newEmail.com" and "123456789" are visible in user details page 055ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 095ms

After Hooks.rollbackAddedAuthorities() 040ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

Scenario Outline Permission - Edit user notifications from other company [A-7887]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman@qa.qa-test" 052ms

And Set user details json of user "pskza1-carrier@qa.qa-test" 000ms

When Login as "swisskrono-tradesman@qa.qa-test" 1s 929ms

And Go to "USERS_TAB" 808ms

And Find user "pskza1-carrier@qa.qa-test" 2s 246ms

And Expand "GLUE_FACTORY" notification section 265ms

And Select all notifications in "GLUE_FACTORY" section 510ms

Then Save user details 521ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 143ms

After Hooks.rollbackAddedAuthorities() 036ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@cleanUserDetailsAfterTest	432	1	5	0	0	438	44	1	45	47m 59s 443ms	Failed

Tag Report