Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.137	29 sie 2021, 05:53

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 715ms

And Go to invitation details 148ms

Then Reject invitation by button as user 288ms

When If user is login then logout 293ms

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

And Go to "INVITATIONS_TAB" 447ms

And Go to "REJECTED_TAB" invitation status tab 221ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 168ms

After Hooks.cleanUserDetailsAfterTest() 1s 287ms

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

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

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

And Go to "INVITATIONS_TAB" 465ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 120ms

Hooks

After Hooks.deleteInvitationAfterTest() 165ms

After Hooks.cleanUserDetailsAfterTest() 1s 287ms

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

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

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

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

And Show all transport types 1s 153ms

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

And Set advice window in schedule 3s 271ms

And Fill advice form 17s 330ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 290ms

After Hooks.deleteTransportAfterTest() 733ms

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

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

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

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

And Show all transport types 1s 212ms

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

And Set advice window in schedule 3s 459ms

And Fill advice form 13s 029ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 046ms

After Hooks.deleteTransportAfterTest() 760ms

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

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

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

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

And Show all transport types 1s 146ms

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

And Set advice window in schedule 3s 280ms

And Fill advice form 18s 912ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 529ms

After Hooks.deleteTransportAfterTest() 726ms

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

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

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

And Show all transport types 1s 187ms

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

And Go to "TRANSPORT_TABLE" 411ms

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

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

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

And Fill transport form 5s 177ms

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

And Expand advice panel 246ms

And Edit advice in transport details 17s 610ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 311ms

After Hooks.deleteTransportAfterTest() 766ms

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

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

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

And Show all transport types 1s 156ms

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

And Go to "TRANSPORT_TABLE" 397ms

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

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

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

And Fill transport form 1m 8s 771ms

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

And Expand advice panel 263ms

And Edit advice in transport details 7s 971ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 203ms

After Hooks.deleteTransportAfterTest() 937ms

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

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

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

And Show all transport types 1s 166ms

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

And Go to "TRANSPORT_TABLE" 387ms

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

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

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

And Fill transport form 28s 767ms

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

And Expand advice panel 253ms

And Edit advice in transport details 23s 638ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 810ms

After Hooks.deleteTransportAfterTest() 813ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 954ms

After Hooks.deleteTransportAfterTest() 785ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 723ms

After Hooks.deleteTransportAfterTest() 731ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 417ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating a new auction

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 351ms

After Hooks.deleteTransportAfterTest() 762ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 005ms

After Hooks.deleteTransportAfterTest() 614ms

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

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

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

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

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

And Wait till auction end 1m 56s 015ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 419ms

After Hooks.deleteTransportAfterTest() 675ms

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

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

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

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

And Wait till auction end 1m 57s 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 397ms

After Hooks.deleteTransportAfterTest() 624ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing first place in auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 059ms

After Hooks.deleteTransportAfterTest() 653ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 274ms

After Hooks.deleteTransportAfterTest() 604ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 070ms

After Hooks.deleteTransportAfterTest() 569ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 024ms

After Hooks.deleteTransportAfterTest() 726ms

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

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

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

And Go to "TRANSPORT_TABLE" 372ms

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

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

And Fill transport form 43s 197ms

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

And Fill discrepancy report section 52s 365ms

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

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

And Generate discrepancy report 21s 621ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 339ms

After Hooks.deleteTransportAfterTest() 869ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 561ms

After Hooks.deleteModeOfTransportationAfterTest() 376ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 396ms

After Hooks.deleteModeOfTransportationAfterTest() 269ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 620ms

And Select warehouse "Serownia" 1s 604ms

And Set week view 1s 233ms

And Show yesterday 1s 176ms

And Move window into the past 408ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 519ms

After Hooks.deleteTransportAfterTest() 833ms

After Hooks.rollbackAddedAuthorities() 197ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 345ms

After Hooks.deleteTransportAfterTest() 558ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 454ms

After Hooks.deleteTransportAfterTest() 586ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 035ms

After Hooks.deleteTransportAfterTest() 840ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 065ms

After Hooks.deleteTransportAfterTest() 647ms

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

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

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

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

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

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

Then If user is login then logout 263ms

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

And Go to auction details 1s 897ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 821ms

After Hooks.deleteTransportAfterTest() 915ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 785ms

After Hooks.deleteTransportAfterTest() 655ms

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 331ms

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

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

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

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

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

And Check is transport "CONTAINER" created in transport table and set transport id 7s 003ms

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

And Set advice window in schedule 3s 433ms

And Fill advice form 20s 372ms

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

And Go to "TRANSPORT_TABLE" 503ms

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

Then Check are advice values equals 4s 991ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 310ms

After Hooks.deleteTransportAfterTest() 858ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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 4s 117ms

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

And Set advice window in schedule 3s 381ms

And Fill advice form 20s 576ms

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

And Go to "TRANSPORT_TABLE" 458ms

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

Then Check are advice values equals 4s 980ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 108ms

After Hooks.deleteTransportAfterTest() 771ms

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

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

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

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

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

And Set advice window in schedule 3s 372ms

And Fill advice form 20s 452ms

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

And Go to "TRANSPORT_TABLE" 458ms

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

Then Check are advice values equals 5s 004ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 396ms

After Hooks.deleteTransportAfterTest() 821ms

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

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

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

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

And Set advice window in schedule 3s 483ms

And Fill advice form 20s 440ms

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

And Go to "TRANSPORT_TABLE" 461ms

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

Then Check are advice values equals 4s 956ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 685ms

After Hooks.deleteTransportAfterTest() 783ms

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

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

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

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

And Set advice window in schedule 30s 144ms

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-2/temp/buildTmp/.com.google.Chrome.8gEB6u}, 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: 0a82d96292792fa55343cd66dd45d00b
*** 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 869ms

After Hooks.deleteTransportAfterTest() 543ms

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

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

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

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 "OWN_COLLECTION" created in transport table and set transport id 7s 174ms

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

And Set advice window in schedule 3s 346ms

And Fill advice form 20s 284ms

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

And Go to "TRANSPORT_TABLE" 467ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 105ms

After Hooks.deleteTransportAfterTest() 796ms

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

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

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

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

And Set advice window in schedule 3s 339ms

And Fill advice form 20s 618ms

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

And Go to "TRANSPORT_TABLE" 444ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 261ms

After Hooks.deleteTransportAfterTest() 796ms

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

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

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

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

And Set advice window in schedule 3s 424ms

And Fill advice form 20s 429ms

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

And Go to "TRANSPORT_TABLE" 493ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 135ms

After Hooks.deleteTransportAfterTest() 794ms

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

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

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

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

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

And Set advice window in schedule 3s 448ms

And Fill advice form 20s 522ms

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

And Go to "TRANSPORT_TABLE" 402ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 981ms

After Hooks.deleteTransportAfterTest() 845ms

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

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

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

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

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

And Set advice window in schedule 3s 391ms

And Fill advice form 20s 335ms

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

And Go to "TRANSPORT_TABLE" 436ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 667ms

After Hooks.deleteTransportAfterTest() 789ms

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

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

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

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

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

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

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

When Reject status: Book of disinfection 243ms

And Check if reject date is visible 867ms

Then If user is login then logout 274ms

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

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

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

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

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 268ms

After Hooks.deleteTransportAfterTest() 748ms

After Hooks.rollbackWarehousesAccess() 749ms

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

And Click remind password button 282ms

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

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

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

And Extract password from mailgun mail 4s 348ms

And Reset password from link 1s 395ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 966ms

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

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

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

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

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

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

Then Save user details 1s 064ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 644ms

After Hooks.rollbackAddedAuthorities() 290ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

And Expand "other" notification section 2s 427ms

And Select all notifications in "other" section 295ms

Then Save user details 1s 420ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 887ms

After Hooks.rollbackAddedAuthorities() 150ms

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

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

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

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

And Go to "USERS_TAB" 1s 563ms

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

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

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

Then Save user details 1s 005ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 646ms

After Hooks.rollbackAddedAuthorities() 230ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Go to "USERS_TAB" 1s 542ms

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

And Expand "GLUE_FACTORY" notification section 628ms

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

Then Save user details 1s 824ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 040ms

After Hooks.rollbackAddedAuthorities() 245ms

	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 45s 817ms	Failed

Tag Report