Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	2021.AT1.64	17 sie 2021, 05:48

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	432	1	5	0	0	438	44	1	45	46m 33s 766ms	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" 093ms

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

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

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

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

Then Go to "INVITATIONS_TAB" 188ms

And Go to invitation details 055ms

Then Reject invitation by button as user 098ms

When If user is login then logout 304ms

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

And Go to "INVITATIONS_TAB" 191ms

And Go to "REJECTED_TAB" invitation status tab 102ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 022ms

After Hooks.cleanUserDetailsAfterTest() 161ms

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

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

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

And Go to "INVITATIONS_TAB" 173ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 039ms

Hooks

After Hooks.deleteInvitationAfterTest() 039ms

After Hooks.cleanUserDetailsAfterTest() 223ms

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

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

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

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

And Show all transport types 1s 045ms

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

And Set advice window in schedule 2s 477ms

And Fill advice form 13s 896ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

After Hooks.cleanUserDetailsAfterTest() 183ms

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

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

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

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

And Show all transport types 1s 038ms

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

And Set advice window in schedule 2s 670ms

And Fill advice form 10s 518ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 117ms

After Hooks.cleanUserDetailsAfterTest() 135ms

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

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

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

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

And Show all transport types 1s 046ms

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

And Set advice window in schedule 2s 474ms

And Fill advice form 15s 294ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 110ms

After Hooks.cleanUserDetailsAfterTest() 206ms

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

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

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

And Show all transport types 1s 044ms

And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 47s 113ms

And Go to "TRANSPORT_TABLE" 195ms

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

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

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

And Fill transport form 4s 724ms

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

And Expand advice panel 103ms

And Edit advice in transport details 14s 467ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

After Hooks.cleanUserDetailsAfterTest() 164ms

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

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

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

And Show all transport types 1s 044ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 44s 040ms

And Go to "TRANSPORT_TABLE" 240ms

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

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

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

And Fill transport form 1m 2s 262ms

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

And Expand advice panel 112ms

And Edit advice in transport details 6s 566ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 147ms

After Hooks.cleanUserDetailsAfterTest() 178ms

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

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

And Show all transport types 1s 044ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 48s 648ms

And Go to "TRANSPORT_TABLE" 168ms

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

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

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

And Fill transport form 25s 987ms

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

And Expand advice panel 115ms

And Edit advice in transport details 20s 687ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 127ms

After Hooks.cleanUserDetailsAfterTest() 194ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

After Hooks.cleanUserDetailsAfterTest() 130ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackVerificationEmailSettingAfterTest

Scenario Outline Check if verification mail was sent to transport creator

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 120ms

After Hooks.cleanUserDetailsAfterTest() 254ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 133ms

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

And Prepare user "paa1-carrier@qa.qa-test" 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 247ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 091ms

After Hooks.cleanUserDetailsAfterTest() 255ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 078ms

After Hooks.cleanUserDetailsAfterTest() 292ms

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

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

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

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

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

And Wait till auction end 1m 58s 017ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 093ms

After Hooks.cleanUserDetailsAfterTest() 303ms

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

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

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

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

And Wait till auction end 1m 58s 017ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 100ms

After Hooks.cleanUserDetailsAfterTest() 171ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 111ms

After Hooks.cleanUserDetailsAfterTest() 261ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after winning an auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 084ms

After Hooks.cleanUserDetailsAfterTest() 286ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 082ms

After Hooks.cleanUserDetailsAfterTest() 235ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail two hours before auction ends

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 101ms

After Hooks.cleanUserDetailsAfterTest() 289ms

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

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

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

And Go to "TRANSPORT_TABLE" 119ms

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

And Get inputs from database "EDIT_DELIVERY" "super-admin-hochland" 037ms

And Fill transport form 38s 023ms

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

And Fill discrepancy report section 49s 537ms

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

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

And Generate discrepancy report 3s 289ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 124ms

After Hooks.cleanUserDetailsAfterTest() 394ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 283ms

After Hooks.deleteModeOfTransportationAfterTest() 115ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 319ms

After Hooks.deleteModeOfTransportationAfterTest() 063ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 809ms

And Select warehouse "Serownia" 1s 452ms

And Set week view 1s 097ms

And Show yesterday 1s 066ms

And Move window into the past 304ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "spóźnił się na" 1m 7s 876ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 115ms

After Hooks.cleanUserDetailsAfterTest() 312ms

After Hooks.rollbackAddedAuthorities() 023ms

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" 2s 226ms

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 069ms

After Hooks.cleanUserDetailsAfterTest() 292ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 090ms

After Hooks.cleanUserDetailsAfterTest() 295ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 108ms

After Hooks.cleanUserDetailsAfterTest() 283ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 077ms

After Hooks.cleanUserDetailsAfterTest() 268ms

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

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

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

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

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

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

Then If user is login then logout 325ms

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

And Go to auction details 1s 218ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 105ms

After Hooks.cleanUserDetailsAfterTest() 386ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating new inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 086ms

After Hooks.cleanUserDetailsAfterTest() 368ms

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 169ms

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) 000ms

Steps

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

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

And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 037ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms

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

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

And Set advice window in schedule 2s 614ms

And Fill advice form 16s 809ms

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

And Go to "TRANSPORT_TABLE" 206ms

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

Then Check are advice values equals 4s 334ms

Hooks

After Hooks.deleteTransportAfterTest() 098ms

After Hooks.cleanUserDetailsAfterTest() 263ms

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

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

And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 039ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 037ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 399ms

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

And Set advice window in schedule 2s 573ms

And Fill advice form 16s 781ms

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

And Go to "TRANSPORT_TABLE" 173ms

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

Then Check are advice values equals 4s 349ms

Hooks

After Hooks.deleteTransportAfterTest() 113ms

After Hooks.cleanUserDetailsAfterTest() 295ms

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

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

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 037ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms

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

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

And Set advice window in schedule 2s 578ms

And Fill advice form 16s 792ms

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

And Go to "TRANSPORT_TABLE" 203ms

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

Then Check are advice values equals 4s 326ms

Hooks

After Hooks.deleteTransportAfterTest() 095ms

After Hooks.cleanUserDetailsAfterTest() 274ms

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

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

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 037ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 3s 832ms

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

And Set advice window in schedule 2s 557ms

And Fill advice form 16s 709ms

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

And Go to "TRANSPORT_TABLE" 242ms

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

Then Check are advice values equals 4s 317ms

Hooks

After Hooks.deleteTransportAfterTest() 128ms

After Hooks.cleanUserDetailsAfterTest() 352ms

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

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

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 037ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms

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

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

And Set advice window in schedule 30s 115ms

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.tQWkKe}, 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: 8750bd19a17fb9d97045e3531768dee5
*** 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:325)
	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() 081ms

After Hooks.cleanUserDetailsAfterTest() 222ms

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) 000ms

Steps

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

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

And Get inputs from database "CREATE_OWN_COLLECTION" "super-admin-skz" 037ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 3s 394ms

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

And Set advice window in schedule 2s 540ms

And Fill advice form 16s 699ms

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

And Go to "TRANSPORT_TABLE" 197ms

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

Hooks

After Hooks.deleteTransportAfterTest() 106ms

After Hooks.cleanUserDetailsAfterTest() 274ms

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

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

And Get inputs from database "CREATE_CONTAINER" "super-admin-skz" 039ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms

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

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

And Set advice window in schedule 2s 574ms

And Fill advice form 16s 771ms

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

And Go to "TRANSPORT_TABLE" 198ms

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

Hooks

After Hooks.deleteTransportAfterTest() 115ms

After Hooks.cleanUserDetailsAfterTest() 286ms

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

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

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 037ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 034ms

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

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

And Set advice window in schedule 2s 585ms

And Fill advice form 16s 797ms

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

And Go to "TRANSPORT_TABLE" 217ms

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

Hooks

After Hooks.deleteTransportAfterTest() 091ms

After Hooks.cleanUserDetailsAfterTest() 264ms

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) 000ms

Steps

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

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

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 036ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 1s 140ms

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

And Set advice window in schedule 2s 585ms

And Fill advice form 16s 738ms

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

And Go to "TRANSPORT_TABLE" 246ms

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

Hooks

After Hooks.deleteTransportAfterTest() 120ms

After Hooks.cleanUserDetailsAfterTest() 366ms

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

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

And Get inputs from database "CREATE_TRANSPORT_ORDER" "super-admin-skz" 038ms

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

And Get inputs from database "CREATE_ADVICE" "super-admin-skz" 033ms

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

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

And Set advice window in schedule 2s 568ms

And Fill advice form 16s 845ms

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

And Go to "TRANSPORT_TABLE" 199ms

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

Hooks

After Hooks.deleteTransportAfterTest() 129ms

After Hooks.cleanUserDetailsAfterTest() 232ms

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

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

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

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

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

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

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

When Reject status: Book of disinfection 093ms

And Check if reject date is visible 306ms

Then If user is login then logout 297ms

And Login as "lantmannen-admin" 893ms

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

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

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

And Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 142ms

After Hooks.cleanUserDetailsAfterTest() 170ms

After Hooks.rollbackWarehousesAccess() 131ms

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

And Prepare login page 228ms

And Click remind password button 087ms

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

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

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

And Extract password from mailgun mail 4s 349ms

And Reset password from link 727ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 139ms

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

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

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

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

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

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

Then Save user details 279ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 104ms

After Hooks.rollbackAddedAuthorities() 080ms

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

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

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

And Expand "other" notification section 479ms

And Select all notifications in "other" section 093ms

Then Save user details 353ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 132ms

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

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

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

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

And Go to "USERS_TAB" 908ms

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

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

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

Then Save user details 249ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 109ms

After Hooks.rollbackAddedAuthorities() 041ms

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

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

And Go to "USERS_TAB" 775ms

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

And Expand "GLUE_FACTORY" notification section 215ms

And Select all notifications in "GLUE_FACTORY" section 524ms

Then Save user details 484ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 148ms

After Hooks.rollbackAddedAuthorities() 037ms

	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	46m 33s 766ms	Failed

Tag Report