Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.71	17 sie 2021, 09:11

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	432	1	5	0	0	438	44	1	45	56m 30s 713ms	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" 222ms

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

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

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

When Login as "piast-admin" 4s 977ms

Then Go to "INVITATIONS_TAB" 645ms

And Go to invitation details 148ms

Then Reject invitation by button as user 303ms

When If user is login then logout 713ms

Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 4s 922ms

And Go to "INVITATIONS_TAB" 492ms

And Go to "REJECTED_TAB" invitation status tab 324ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 166ms

After Hooks.cleanUserDetailsAfterTest() 1s 295ms

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

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

When Login as "neuca-admin" and set token of apiUsername "super-admin-neuca" 2s 389ms

And Go to "INVITATIONS_TAB" 446ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 109ms

Hooks

After Hooks.deleteInvitationAfterTest() 184ms

After Hooks.cleanUserDetailsAfterTest() 1s 327ms

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

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

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

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

And Show all transport types 1s 168ms

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

And Set advice window in schedule 3s 321ms

And Fill advice form 17s 123ms

And Click advice save button and wait for advice form to disappear 33s 812ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 772ms

After Hooks.cleanUserDetailsAfterTest() 1s 281ms

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

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

And Create transport "CREATE_DELIVERY_FRONT" by JSON file as "super-admin-piast" 2s 051ms

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

And Show all transport types 1s 177ms

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

And Set advice window in schedule 3s 416ms

And Fill advice form 13s 026ms

And Click advice save button and wait for advice form to disappear 33s 324ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 800ms

After Hooks.cleanUserDetailsAfterTest() 1s 032ms

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

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 2s 102ms

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

And Show all transport types 1s 153ms

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

And Set advice window in schedule 3s 247ms

And Fill advice form 18s 646ms

And Click advice save button and wait for advice form to disappear 33s 271ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 724ms

After Hooks.cleanUserDetailsAfterTest() 1s 594ms

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" 5s 054ms

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

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

And Show all transport types 1s 158ms

And Create advice "ADVICE_CONTAINER" "CONTAINER" "super-admin-adama" 53s 591ms

And Go to "TRANSPORT_TABLE" 424ms

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

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

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

And Fill transport form 5s 152ms

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

And Expand advice panel 284ms

And Edit advice in transport details 17s 518ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 840ms

After Hooks.cleanUserDetailsAfterTest() 1s 369ms

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" 5s 687ms

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

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

And Show all transport types 1s 137ms

And Create advice "ADVICE_DELIVERY" "DELIVERY" "super-admin-piast" 49s 977ms

And Go to "TRANSPORT_TABLE" 501ms

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

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

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

And Fill transport form 1m 8s 861ms

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

And Expand advice panel 282ms

And Edit advice in transport details 8s 092ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 988ms

After Hooks.cleanUserDetailsAfterTest() 1s 123ms

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" 6s 017ms

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-keeeper" 2s 059ms

And Show all transport types 1s 164ms

And Create advice "ADVICE_LOAD" "LOAD" "super-admin-keeeper" 55s 430ms

And Go to "TRANSPORT_TABLE" 455ms

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

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

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

And Fill transport form 28s 827ms

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

And Expand advice panel 275ms

And Edit advice in transport details 23s 776ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 801ms

After Hooks.cleanUserDetailsAfterTest() 1s 659ms

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-skd" 2s 759ms

And Confirm status "ARRIVAL" by Public API "v1" 1s 193ms

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

Then Check if user got a mail 000ms

And Confirm status "DEPARTURE" by Public API "v1" 1s 202ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 834ms

After Hooks.cleanUserDetailsAfterTest() 993ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 792ms

After Hooks.cleanUserDetailsAfterTest() 1s 719ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 429ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating a new auction

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Login as "adama-admin" and set token of apiUsername "super-admin-adama" 4s 995ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 078ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 718ms

After Hooks.cleanUserDetailsAfterTest() 2s 140ms

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 081ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 588ms

After Hooks.cleanUserDetailsAfterTest() 2s 046ms

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" 12s 364ms

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 133ms

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

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

And Wait till auction end 1m 57s 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 674ms

After Hooks.cleanUserDetailsAfterTest() 2s 431ms

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 111ms

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

And Wait till auction end 1m 57s 014ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 644ms

After Hooks.cleanUserDetailsAfterTest() 1s 368ms

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" 4s 873ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 123ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 543ms

After Hooks.cleanUserDetailsAfterTest() 2s 079ms

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 059ms

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

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Otrzymano zlecenie" 1m 54s 089ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 567ms

After Hooks.cleanUserDetailsAfterTest() 2s 335ms

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 110ms

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 604ms

After Hooks.cleanUserDetailsAfterTest() 2s 261ms

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" 5s 371ms

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 094ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zakończenie aukcji" 1m 18s 055ms

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 671ms

After Hooks.cleanUserDetailsAfterTest() 2s 117ms

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" 3s 308ms

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 182ms

And Go to "TRANSPORT_TABLE" 364ms

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

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

And Fill transport form 43s 088ms

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

And Fill discrepancy report section 52s 566ms

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

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

And Generate discrepancy report 21s 632ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 967ms

After Hooks.cleanUserDetailsAfterTest() 3s 377ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 585ms

After Hooks.deleteModeOfTransportationAfterTest() 353ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 477ms

After Hooks.deleteModeOfTransportationAfterTest() 287ms

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" 9s 484ms

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

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

And Create transport "CREATE_DELIVERY" by JSON file as "super-admin-hochland" 3s 138ms

And Go to "WAREHOUSE_TAB" 1s 296ms

And Select warehouse "Serownia" 1s 751ms

And Set week view 1s 266ms

And Show yesterday 1s 152ms

And Move window into the past 382ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 829ms

After Hooks.cleanUserDetailsAfterTest() 2s 400ms

After Hooks.rollbackAddedAuthorities() 168ms

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" 9s 316ms

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

And Wait "60" seconds 1m

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 179ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 583ms

After Hooks.cleanUserDetailsAfterTest() 2s 334ms

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" 7s 710ms

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

And Wait "60" seconds 1m

And Create transport "CREATE_SMALLS_EXPORT" by JSON file as "super-admin-skz" 2s 145ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 601ms

After Hooks.cleanUserDetailsAfterTest() 2s 284ms

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 084ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 760ms

After Hooks.cleanUserDetailsAfterTest() 2s 071ms

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

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

And Create transport "CREATE_TRANSPORT" by JSON file as "super-admin-adama" 2s 130ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 555ms

After Hooks.cleanUserDetailsAfterTest() 2s 028ms

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" 7s 579ms

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 228ms

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

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

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

Then If user is login then logout 248ms

And Login as "swisskrono-admin" 2s 770ms

And Go to auction details 1s 816ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 818ms

After Hooks.cleanUserDetailsAfterTest() 2s 733ms

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

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

And Create transport "CREATE_SMALLS_IMPORT" by JSON file as "super-admin-skz" 2s 140ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 666ms

After Hooks.cleanUserDetailsAfterTest() 2s 737ms

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 309ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 335ms

And Fill advice form 20s 396ms

And Click advice save button and wait for advice form to disappear 33s 248ms

And Go to "TRANSPORT_TABLE" 494ms

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

Then Check are advice values equals 5s 001ms

Hooks

After Hooks.deleteTransportAfterTest() 846ms

After Hooks.cleanUserDetailsAfterTest() 2s 292ms

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" 7s 615ms

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

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

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

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

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 170ms

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

And Set advice window in schedule 3s 378ms

And Fill advice form 20s 344ms

And Click advice save button and wait for advice form to disappear 33s 244ms

And Go to "TRANSPORT_TABLE" 481ms

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

Then Check are advice values equals 5s 007ms

Hooks

After Hooks.deleteTransportAfterTest() 777ms

After Hooks.cleanUserDetailsAfterTest() 2s 145ms

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" 7s 350ms

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

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

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

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

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 153ms

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

And Set advice window in schedule 3s 357ms

And Fill advice form 20s 551ms

And Click advice save button and wait for advice form to disappear 33s 291ms

And Go to "TRANSPORT_TABLE" 505ms

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

Then Check are advice values equals 4s 895ms

Hooks

After Hooks.deleteTransportAfterTest() 806ms

After Hooks.cleanUserDetailsAfterTest() 2s 299ms

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" 8s 700ms

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

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

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

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

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 717ms

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

And Set advice window in schedule 3s 528ms

And Fill advice form 20s 469ms

And Click advice save button and wait for advice form to disappear 33s 201ms

And Go to "TRANSPORT_TABLE" 489ms

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

Then Check are advice values equals 5s 023ms

Hooks

After Hooks.deleteTransportAfterTest() 795ms

After Hooks.cleanUserDetailsAfterTest() 2s 731ms

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" 7s 589ms

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

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

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

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

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 623ms

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

And Set advice window in schedule 30s 183ms

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-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-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/temp/buildTmp/.com.google.Chrome.R7BaJQ}, 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: 54f7e2e06dcf601f80c66fa6cd4b793a
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	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() 552ms

After Hooks.cleanUserDetailsAfterTest() 1s 803ms

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" 7s 557ms

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

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

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

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

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 7s 171ms

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

And Set advice window in schedule 3s 410ms

And Fill advice form 20s 412ms

And Click advice save button and wait for advice form to disappear 33s 290ms

And Go to "TRANSPORT_TABLE" 450ms

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

Hooks

After Hooks.deleteTransportAfterTest() 820ms

After Hooks.cleanUserDetailsAfterTest() 2s 161ms

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" 7s 439ms

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

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

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

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

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

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

And Set advice window in schedule 3s 498ms

And Fill advice form 20s 433ms

And Click advice save button and wait for advice form to disappear 33s 294ms

And Go to "TRANSPORT_TABLE" 490ms

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

Hooks

After Hooks.deleteTransportAfterTest() 871ms

After Hooks.cleanUserDetailsAfterTest() 2s 241ms

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" 7s 688ms

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

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

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

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

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 182ms

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

And Set advice window in schedule 3s 405ms

And Fill advice form 20s 547ms

And Click advice save button and wait for advice form to disappear 33s 270ms

And Go to "TRANSPORT_TABLE" 465ms

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

Hooks

After Hooks.deleteTransportAfterTest() 838ms

After Hooks.cleanUserDetailsAfterTest() 2s 174ms

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" 6s 434ms

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

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

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

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

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 4s 099ms

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

And Set advice window in schedule 3s 365ms

And Fill advice form 20s 465ms

And Click advice save button and wait for advice form to disappear 33s 817ms

And Go to "TRANSPORT_TABLE" 496ms

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

Hooks

After Hooks.deleteTransportAfterTest() 823ms

After Hooks.cleanUserDetailsAfterTest() 2s 942ms

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" 8s 673ms

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

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

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

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

And Check is transport "TRANSPORT_ORDER" created in transport table and set transport id 7s 548ms

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

And Set advice window in schedule 3s 414ms

And Fill advice form 20s 503ms

And Click advice save button and wait for advice form to disappear 33s 876ms

And Go to "TRANSPORT_TABLE" 440ms

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

Hooks

After Hooks.deleteTransportAfterTest() 856ms

After Hooks.cleanUserDetailsAfterTest() 1s 640ms

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" 4s 556ms

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

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

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

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

And Create transport "CREATE_LOAD" by JSON file as "super-admin-lantmannen" 2s 875ms

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

When Reject status: Book of disinfection 249ms

And Check if reject date is visible 977ms

Then If user is login then logout 760ms

And Login as "lantmannen-admin" 2s 180ms

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

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

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

And Check if user got a mail 000ms

Hooks

After Hooks.deleteTransportAfterTest() 832ms

After Hooks.cleanUserDetailsAfterTest() 1s 265ms

After Hooks.rollbackWarehousesAccess() 753ms

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

And Prepare login page 461ms

And Click remind password button 270ms

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

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

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

And Extract password from mailgun mail 4s 338ms

And Reset password from link 1s 620ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 962ms

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

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

When Login as "oaa1-receiver-2@qa.qa-test" 4s 339ms

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

And Change user details "email" to "newEmailAddress@newEmail.com" 1s 127ms

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

Then Save user details 1s 027ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 653ms

After Hooks.rollbackAddedAuthorities() 251ms

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

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

When Login as "pskza1-carrier-2@qa.qa-test" 7s 291ms

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

And Expand "other" notification section 2s 516ms

And Select all notifications in "other" section 299ms

Then Save user details 1s 488ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 967ms

After Hooks.rollbackAddedAuthorities() 144ms

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

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

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

When Login as "adama-buyer@qa.qa-test" 5s 133ms

And Go to "USERS_TAB" 2s 954ms

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

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

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

Then Save user details 1s 046ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 641ms

After Hooks.rollbackAddedAuthorities() 242ms

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

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

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

When Login as "swisskrono-tradesman@qa.qa-test" 9s 240ms

And Go to "USERS_TAB" 1s 579ms

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

And Expand "GLUE_FACTORY" notification section 609ms

And Select all notifications in "GLUE_FACTORY" section 1s 306ms

Then Save user details 1s 822ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 069ms

After Hooks.rollbackAddedAuthorities() 222ms

	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	56m 30s 713ms	Failed

Tag Report