Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.119	15 sie 2021, 05:58

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	426	3	9	0	0	438	42	3	45	55m 46s 899ms	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" 231ms

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

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

When Login as "piast-admin" 5s 063ms

Then Go to "INVITATIONS_TAB" 708ms

And Go to invitation details 156ms

Then Reject invitation by button as user 298ms

When If user is login then logout 666ms

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

And Go to "INVITATIONS_TAB" 502ms

And Go to "REJECTED_TAB" invitation status tab 338ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 172ms

After Hooks.cleanUserDetailsAfterTest() 1s 358ms

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

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

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

And Go to "INVITATIONS_TAB" 480ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 114ms

Hooks

After Hooks.deleteInvitationAfterTest() 180ms

After Hooks.cleanUserDetailsAfterTest() 1s 310ms

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

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

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

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

And Show all transport types 1s 158ms

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

And Set advice window in schedule 3s 436ms

And Fill advice form 17s 386ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 355ms

After Hooks.deleteTransportAfterTest() 759ms

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

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

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

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

And Show all transport types 1s 222ms

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

And Set advice window in schedule 3s 439ms

And Fill advice form 12s 933ms

And Click advice save button and wait for advice form to disappear 18s 418ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 054ms

After Hooks.deleteTransportAfterTest() 772ms

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

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

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

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

And Show all transport types 1s 148ms

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

And Set advice window in schedule 3s 273ms

And Fill advice form 18s 711ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 463ms

After Hooks.deleteTransportAfterTest() 713ms

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

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

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

And Show all transport types 1s 167ms

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

And Go to "TRANSPORT_TABLE" 425ms

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

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

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

And Fill transport form 5s 213ms

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

And Expand advice panel 265ms

And Edit advice in transport details 17s 584ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 406ms

After Hooks.deleteTransportAfterTest() 735ms

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

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

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

And Show all transport types 1s 147ms

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

And Go to "TRANSPORT_TABLE" 487ms

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

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

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

And Fill transport form 1m 8s 880ms

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

And Expand advice panel 243ms

And Edit advice in transport details 8s 087ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 108ms

After Hooks.deleteTransportAfterTest() 986ms

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

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

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

And Show all transport types 1s 166ms

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

And Go to "TRANSPORT_TABLE" 457ms

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

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

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

And Fill transport form 28s 723ms

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

And Expand advice panel 283ms

And Edit advice in transport details 23s 761ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 563ms

After Hooks.deleteTransportAfterTest() 771ms

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

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

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

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

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

Then Check if user got a mail 000ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 986ms

After Hooks.deleteTransportAfterTest() 834ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 684ms

After Hooks.deleteTransportAfterTest() 722ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 414ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 021ms

After Hooks.deleteTransportAfterTest() 756ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 057ms

After Hooks.deleteTransportAfterTest() 607ms

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

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

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

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

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

And Wait till auction end 1m 57s 015ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 496ms

After Hooks.deleteTransportAfterTest() 645ms

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

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

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

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

And Wait till auction end 1m 57s 015ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 387ms

After Hooks.deleteTransportAfterTest() 615ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 074ms

After Hooks.deleteTransportAfterTest() 588ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 324ms

After Hooks.deleteTransportAfterTest() 561ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 070ms

After Hooks.deleteTransportAfterTest() 609ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 123ms

After Hooks.deleteTransportAfterTest() 666ms

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

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

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

And Go to "TRANSPORT_TABLE" 404ms

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

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

And Fill transport form 43s 164ms

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

And Fill discrepancy report section 52s 401ms

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

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

And Generate discrepancy report 21s 605ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 502ms

After Hooks.deleteTransportAfterTest() 882ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 511ms

After Hooks.deleteModeOfTransportationAfterTest() 314ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 611ms

After Hooks.deleteModeOfTransportationAfterTest() 323ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 422ms

And Select warehouse "Serownia" 1s 551ms

And Set week view 1s 223ms

And Show yesterday 1s 149ms

And Move window into the past 447ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 700ms

After Hooks.deleteTransportAfterTest() 784ms

After Hooks.rollbackAddedAuthorities() 211ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 103ms

After Hooks.deleteTransportAfterTest() 583ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 120ms

After Hooks.deleteTransportAfterTest() 578ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @FLAKY-A-7913

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

Error message

java.lang.AssertionError: Formularz nie zniknął! Pojawił się błędy walidacji:
[Podana data nie może być w przeszłości]
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:288)
	at CucumberTests.Transport.TransferTransportTest.transferTransportToCarrier(TransferTransportTest.java:37)
	at ✽.Transfer transport to carrier "Przewoźnik Adama Automat 1" with "true"(file:Features/Atom/Mail/TransportTransferMail.feature:8)

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 088ms

After Hooks.deleteTransportAfterTest() 585ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @FLAKY-A-7913

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

Error message

java.lang.AssertionError: Formularz nie zniknął! Pojawił się błędy walidacji:
[Podana data nie może być w przeszłości]
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at Pages.Transport.TransportsPage.transferTransportToCarrier(TransportsPage.java:288)
	at CucumberTests.Transport.TransferTransportTest.transferTransportToCarrier(TransferTransportTest.java:37)
	at ✽.Transfer transport to carrier "Przewoźnik Adama Automat 1" with "false"(file:Features/Atom/Mail/TransportTransferMail.feature:20)

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 229ms

After Hooks.deleteTransportAfterTest() 533ms

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

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

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

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

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

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

Then If user is login then logout 275ms

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

And Go to auction details 1s 940ms

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

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nie otrzymano zlecenia" 2m 46s 091ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 159ms

After Hooks.deleteTransportAfterTest() 681ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 722ms

After Hooks.deleteTransportAfterTest() 666ms

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 279ms

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

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

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

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

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

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

And Set advice window in schedule 3s 422ms

And Fill advice form 20s 673ms

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

And Go to "TRANSPORT_TABLE" 426ms

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

Then Check are advice values equals 5s 010ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 366ms

After Hooks.deleteTransportAfterTest() 812ms

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

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

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

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

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

And Check is transport "OWN_COLLECTION" created in transport table and set transport id 4s 174ms

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

And Set advice window in schedule 3s 386ms

And Fill advice form 20s 679ms

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

And Go to "TRANSPORT_TABLE" 444ms

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

Then Check are advice values equals 4s 995ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 132ms

After Hooks.deleteTransportAfterTest() 797ms

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

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

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

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

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

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

And Set advice window in schedule 3s 399ms

And Fill advice form 20s 501ms

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

And Go to "TRANSPORT_TABLE" 475ms

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

Then Check are advice values equals 4s 980ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 283ms

After Hooks.deleteTransportAfterTest() 792ms

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

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

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

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 "TRANSPORT_ORDER" created in transport table and set transport id 3s 892ms

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

And Set advice window in schedule 3s 393ms

And Fill advice form 20s 389ms

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

And Go to "TRANSPORT_TABLE" 497ms

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

Then Check are advice values equals 5s 013ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 711ms

After Hooks.deleteTransportAfterTest() 794ms

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

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

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

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

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

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

And Set advice window in schedule 30s 154ms

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.Uctaot}, 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: 59b464e42b904934710a44439613d6ac
*** 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:323)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:91)
	at ✽.Set advice window in schedule(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:13)

And Fill advice form 000ms

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

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "TRANSPORT_ORDER" 000ms

Then Check are advice values equals 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 775ms

After Hooks.deleteTransportAfterTest() 531ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 365ms

And Fill advice form 20s 569ms

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

And Go to "TRANSPORT_TABLE" 462ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 139ms

After Hooks.deleteTransportAfterTest() 822ms

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

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

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

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 3s 971ms

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

And Set advice window in schedule 3s 449ms

And Fill advice form 20s 480ms

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

And Go to "TRANSPORT_TABLE" 471ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 316ms

After Hooks.deleteTransportAfterTest() 837ms

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

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

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

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

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

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

And Set advice window in schedule 3s 381ms

And Fill advice form 20s 476ms

And Click advice save button and wait for advice form to disappear 18s 421ms

And Go to "TRANSPORT_TABLE" 493ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 121ms

After Hooks.deleteTransportAfterTest() 805ms

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

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

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

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

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

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

And Set advice window in schedule 3s 334ms

And Fill advice form 20s 471ms

And Click advice save button and wait for advice form to disappear 18s 388ms

And Go to "TRANSPORT_TABLE" 492ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 941ms

After Hooks.deleteTransportAfterTest() 869ms

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

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

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

And Add transport by SKApi in "MGW" assigned to "automaty@test.pl" 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 7s 560ms

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

And Set advice window in schedule 3s 383ms

And Fill advice form 20s 390ms

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

And Go to "TRANSPORT_TABLE" 460ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 751ms

After Hooks.deleteTransportAfterTest() 788ms

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

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

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

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

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

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

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

When Reject status: Book of disinfection 225ms

And Check if reject date is visible 981ms

Then If user is login then logout 270ms

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

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

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

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

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 250ms

After Hooks.deleteTransportAfterTest() 765ms

After Hooks.rollbackWarehousesAccess() 715ms

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

And Prepare login page 385ms

And Click remind password button 251ms

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

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

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

And Extract password from mailgun mail 3s 947ms

And Reset password from link 1s 556ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 946ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7965

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

Hooks

Before Hooks.showScenarioName(Scenario) 011ms

Steps

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

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

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

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

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

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

Then Save user details 1s 035ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 646ms

After Hooks.rollbackAddedAuthorities() 243ms

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

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

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

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

And Expand "other" notification section 2s 450ms

And Select all notifications in "other" section 259ms

Then Save user details 1s 466ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 919ms

After Hooks.rollbackAddedAuthorities() 154ms

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

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

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

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

And Go to "USERS_TAB" 2s 916ms

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

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

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

Then Save user details 1s 041ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 665ms

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

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

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

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

And Go to "USERS_TAB" 1s 498ms

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

And Expand "GLUE_FACTORY" notification section 552ms

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

Then Save user details 1s 802ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 067ms

After Hooks.rollbackAddedAuthorities() 252ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@cleanUserDetailsAfterTest	426	3	9	0	0	438	42	3	45	55m 46s 899ms	Failed

Tag Report