Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.138	30 sie 2021, 06:02

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	435	1	5	0	0	441	44	1	45	54m 15s 112ms	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" 229ms

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

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

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

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

Then Go to "INVITATIONS_TAB" 706ms

And Go to invitation details 143ms

Then Reject invitation by button as user 279ms

When If user is login then logout 257ms

Then Login as "super-admin-alrec" and set token of apiUsername "super-admin-alrec" 5s 048ms

And Go to "INVITATIONS_TAB" 564ms

And Go to "REJECTED_TAB" invitation status tab 314ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 166ms

After Hooks.cleanUserDetailsAfterTest() 1s 353ms

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

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

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

And Go to "INVITATIONS_TAB" 471ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 114ms

Hooks

After Hooks.deleteInvitationAfterTest() 182ms

After Hooks.cleanUserDetailsAfterTest() 1s 298ms

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

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

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

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

And Show all transport types 1s 160ms

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

And Set advice window in schedule 3s 295ms

And Fill advice form 17s 238ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 279ms

After Hooks.deleteTransportAfterTest() 771ms

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

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

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

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

And Show all transport types 1s 160ms

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

And Set advice window in schedule 3s 422ms

And Fill advice form 12s 953ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 097ms

After Hooks.deleteTransportAfterTest() 776ms

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

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

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

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

And Show all transport types 1s 155ms

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

And Set advice window in schedule 3s 219ms

And Fill advice form 18s 756ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 481ms

After Hooks.deleteTransportAfterTest() 737ms

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

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

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

And Show all transport types 1s 156ms

And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama" 3s 321ms

And Go to "TRANSPORT_TABLE" 428ms

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

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

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

And Fill transport form 5s 255ms

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

And Expand advice panel 268ms

And Edit advice in transport details 17s 641ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 290ms

After Hooks.deleteTransportAfterTest() 768ms

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

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

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

And Show all transport types 1s 147ms

And Create advice by JSON file "CREATE_ADVICE_FOR_DELIVERY" as "super-admin-piast" 3s 485ms

And Go to "TRANSPORT_TABLE" 410ms

And Go to transport details "DELIVERY" 3s 071ms

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

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

And Fill transport form 1m 8s 853ms

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

And Expand advice panel 262ms

And Edit advice in transport details 8s 091ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 154ms

After Hooks.deleteTransportAfterTest() 931ms

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

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

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

And Show all transport types 1s 166ms

And Create advice by JSON file "CREATE_ADVICE_FOR_LOAD" as "super-admin-keeeper" 3s 433ms

And Go to "TRANSPORT_TABLE" 400ms

And Go to transport details "LOAD" 3s 052ms

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

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

And Fill transport form 28s 584ms

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

And Expand advice panel 280ms

And Edit advice in transport details 23s 506ms

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Zmiana w awizacji numer" 2m 41s 633ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 685ms

After Hooks.deleteTransportAfterTest() 794ms

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

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

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

And Confirm status "REPORTING" by Public API "v1" 580ms

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

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

Then Check if user got a mail 000ms

And Assign Queue to classification resource: "super-admin-skd" "trociny" "CLASSIFICATION" 1s 090ms

And Assign Place to classification resource: "super-admin-skd" "trociny" "Rozładunek" "UNLOAD" 1s 078ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 957ms

After Hooks.deleteTransportAfterTest() 803ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackVerificationEmailSettingAfterTest

Scenario Outline Check if verification mail was sent to transport creator

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 702ms

After Hooks.deleteTransportAfterTest() 758ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 420ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 104ms

After Hooks.deleteTransportAfterTest() 717ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 043ms

After Hooks.deleteTransportAfterTest() 598ms

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

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

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

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

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

And Wait till auction end 1m 57s 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 356ms

After Hooks.deleteTransportAfterTest() 654ms

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

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

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

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

And Wait till auction end 1m 57s 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 447ms

After Hooks.deleteTransportAfterTest() 605ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 040ms

After Hooks.deleteTransportAfterTest() 593ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 311ms

After Hooks.deleteTransportAfterTest() 559ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 150ms

After Hooks.deleteTransportAfterTest() 578ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 179ms

After Hooks.deleteTransportAfterTest() 704ms

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

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

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

And Go to "TRANSPORT_TABLE" 410ms

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

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

And Fill transport form 43s 003ms

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

And Fill discrepancy report section 52s 474ms

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

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

And Generate discrepancy report 6s 663ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 432ms

After Hooks.deleteTransportAfterTest() 910ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 502ms

After Hooks.deleteModeOfTransportationAfterTest() 381ms

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 443ms

After Hooks.deleteModeOfTransportationAfterTest() 318ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 307ms

And Select warehouse "Serownia" 1s 686ms

And Set week view 1s 255ms

And Show yesterday 1s 156ms

And Move window into the past 403ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 369ms

After Hooks.deleteTransportAfterTest() 782ms

After Hooks.rollbackAddedAuthorities() 200ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 160ms

After Hooks.deleteTransportAfterTest() 585ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 422ms

After Hooks.deleteTransportAfterTest() 598ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 094ms

After Hooks.deleteTransportAfterTest() 770ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 062ms

After Hooks.deleteTransportAfterTest() 591ms

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

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

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

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

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

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

Then If user is login then logout 284ms

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

And Go to auction details 1s 854ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 729ms

After Hooks.deleteTransportAfterTest() 856ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 724ms

After Hooks.deleteTransportAfterTest() 652ms

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 333ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 344ms

And Fill advice form 20s 299ms

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

And Go to "TRANSPORT_TABLE" 464ms

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

Then Check are advice values equals 4s 986ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 253ms

After Hooks.deleteTransportAfterTest() 793ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 399ms

And Fill advice form 20s 507ms

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

And Go to "TRANSPORT_TABLE" 468ms

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

Then Check are advice values equals 4s 995ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 127ms

After Hooks.deleteTransportAfterTest() 793ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 290ms

And Fill advice form 20s 480ms

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

And Go to "TRANSPORT_TABLE" 492ms

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

Then Check are advice values equals 4s 910ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 336ms

After Hooks.deleteTransportAfterTest() 784ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 350ms

And Fill advice form 20s 513ms

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

And Go to "TRANSPORT_TABLE" 498ms

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

Then Check are advice values equals 4s 959ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 715ms

After Hooks.deleteTransportAfterTest() 803ms

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

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

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

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

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

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

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

And Set advice window in schedule 30s 107ms

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.djoqZ2}, 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: 4da38e90089a7465037b99e615219878
*** 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:82)
	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 802ms

After Hooks.deleteTransportAfterTest() 552ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 435ms

And Fill advice form 20s 482ms

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

And Go to "TRANSPORT_TABLE" 486ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 109ms

After Hooks.deleteTransportAfterTest() 806ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 351ms

And Fill advice form 20s 347ms

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

And Go to "TRANSPORT_TABLE" 468ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 349ms

After Hooks.deleteTransportAfterTest() 797ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 379ms

And Fill advice form 20s 338ms

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

And Go to "TRANSPORT_TABLE" 530ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 099ms

After Hooks.deleteTransportAfterTest() 811ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 327ms

And Fill advice form 20s 479ms

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

And Go to "TRANSPORT_TABLE" 461ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 963ms

After Hooks.deleteTransportAfterTest() 804ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 449ms

And Fill advice form 20s 367ms

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

And Go to "TRANSPORT_TABLE" 455ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 735ms

After Hooks.deleteTransportAfterTest() 776ms

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

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

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

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

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

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

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

When Reject status: Book of disinfection 233ms

And Check if reject date is visible 902ms

Then If user is login then logout 273ms

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

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

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

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

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 289ms

After Hooks.deleteTransportAfterTest() 723ms

After Hooks.rollbackWarehousesAccess() 719ms

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

And Prepare login page 444ms

And Click remind password button 265ms

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

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

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

And Extract password from mailgun mail 4s 643ms

And Reset password from link 1s 437ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 977ms

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

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

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

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

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

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

Then Save user details 1s 021ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 631ms

After Hooks.rollbackAddedAuthorities() 242ms

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

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

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

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

And Expand "other" notification section 2s 563ms

And Select all notifications in "other" section 285ms

Then Save user details 1s 473ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 870ms

After Hooks.rollbackAddedAuthorities() 142ms

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

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

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

And Go to "USERS_TAB" 1s 514ms

And Find user "oaa1-receiver@qa.qa-test" 3s 647ms

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

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

Then Save user details 1s 041ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 661ms

After Hooks.rollbackAddedAuthorities() 232ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

And Go to "USERS_TAB" 1s 581ms

And Find user "pskza1-carrier@qa.qa-test" 3s 694ms

And Expand "GLUE_FACTORY" notification section 525ms

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

Then Save user details 1s 770ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 116ms

After Hooks.rollbackAddedAuthorities() 235ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@cleanUserDetailsAfterTest	435	1	5	0	0	441	44	1	45	54m 15s 112ms	Failed

Tag Report