Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.140	01 wrz 2021, 05:52

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

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

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

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

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

Then Go to "INVITATIONS_TAB" 730ms

And Go to invitation details 148ms

Then Reject invitation by button as user 303ms

When If user is login then logout 315ms

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

And Go to "INVITATIONS_TAB" 461ms

And Go to "REJECTED_TAB" invitation status tab 305ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 151ms

After Hooks.cleanUserDetailsAfterTest() 1s 337ms

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

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

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

And Go to "INVITATIONS_TAB" 472ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 117ms

Hooks

After Hooks.deleteInvitationAfterTest() 202ms

After Hooks.cleanUserDetailsAfterTest() 1s 274ms

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

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

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

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

And Show all transport types 1s 142ms

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

And Set advice window in schedule 3s 308ms

And Fill advice form 17s 053ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 288ms

After Hooks.deleteTransportAfterTest() 801ms

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

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

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

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

And Show all transport types 1s 167ms

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

And Set advice window in schedule 3s 465ms

And Fill advice form 12s 961ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 066ms

After Hooks.deleteTransportAfterTest() 766ms

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

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

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

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

And Show all transport types 1s 152ms

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

And Set advice window in schedule 3s 259ms

And Fill advice form 18s 818ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 561ms

After Hooks.deleteTransportAfterTest() 746ms

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

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

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

And Show all transport types 1s 175ms

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

And Go to "TRANSPORT_TABLE" 429ms

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

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

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

And Fill transport form 5s 197ms

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

And Expand advice panel 230ms

And Edit advice in transport details 17s 682ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 340ms

After Hooks.deleteTransportAfterTest() 722ms

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

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

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

And Show all transport types 1s 143ms

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

And Go to "TRANSPORT_TABLE" 385ms

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

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

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

And Fill transport form 1m 8s 679ms

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

And Expand advice panel 244ms

And Edit advice in transport details 8s 159ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 126ms

After Hooks.deleteTransportAfterTest() 999ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after editing advice

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "keeeper-admin" and set token of apiUsername "super-admin-keeeper" 6s 293ms

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

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

And Show all transport types 1s 167ms

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

And Go to "TRANSPORT_TABLE" 416ms

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

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

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

And Fill transport form 28s 734ms

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

And Expand advice panel 283ms

And Edit advice in transport details 23s 462ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 637ms

After Hooks.deleteTransportAfterTest() 789ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 934ms

After Hooks.deleteTransportAfterTest() 832ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 633ms

After Hooks.deleteTransportAfterTest() 789ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 462ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 043ms

After Hooks.deleteTransportAfterTest() 703ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 064ms

After Hooks.deleteTransportAfterTest() 603ms

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

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

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

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

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

And Wait till auction end 1m 57s 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 562ms

After Hooks.deleteTransportAfterTest() 611ms

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

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

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

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

And Wait till auction end 1m 57s 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 441ms

After Hooks.deleteTransportAfterTest() 663ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 193ms

After Hooks.deleteTransportAfterTest() 570ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 240ms

After Hooks.deleteTransportAfterTest() 569ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 258ms

After Hooks.deleteTransportAfterTest() 571ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail two hours before auction ends

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 152ms

After Hooks.deleteTransportAfterTest() 673ms

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

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

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

And Go to "TRANSPORT_TABLE" 423ms

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

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

And Fill transport form 43s 108ms

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

And Fill discrepancy report section 52s 559ms

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

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

And Generate discrepancy report 21s 106ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 503ms

After Hooks.deleteTransportAfterTest() 935ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 498ms

After Hooks.deleteModeOfTransportationAfterTest() 363ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 494ms

After Hooks.deleteModeOfTransportationAfterTest() 327ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackAddedAuthorities

Scenario Outline Check if mail was sent to after transport delay

Hooks

Before Hooks.showScenarioName(Scenario) 011ms

Steps

Given Login as "hochland-admin" and set token of apiUsername "super-admin-hochland" 9s 485ms

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

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

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

And Go to "WAREHOUSE_TAB" 1s 308ms

And Select warehouse "Serownia" 1s 581ms

And Set week view 1s 214ms

And Show yesterday 1s 148ms

And Move window into the past 424ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 351ms

After Hooks.deleteTransportAfterTest() 822ms

After Hooks.rollbackAddedAuthorities() 180ms

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

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

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" 38s 148ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 145ms

After Hooks.deleteTransportAfterTest() 575ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 200ms

After Hooks.deleteTransportAfterTest() 557ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 068ms

After Hooks.deleteTransportAfterTest() 773ms

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

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 043ms

After Hooks.deleteTransportAfterTest() 588ms

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

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

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

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

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

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

Then If user is login then logout 277ms

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

And Go to auction details 2s 279ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 791ms

After Hooks.deleteTransportAfterTest() 842ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 753ms

After Hooks.deleteTransportAfterTest() 677ms

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 378ms

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

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

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

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 6s 999ms

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

And Set advice window in schedule 3s 309ms

And Fill advice form 20s 419ms

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

And Go to "TRANSPORT_TABLE" 457ms

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

Then Check are advice values equals 4s 983ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 304ms

After Hooks.deleteTransportAfterTest() 814ms

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

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

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

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

And Set advice window in schedule 3s 390ms

And Fill advice form 20s 431ms

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

And Go to "TRANSPORT_TABLE" 509ms

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

Then Check are advice values equals 4s 961ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 096ms

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-admin" and set token of apiUsername "super-admin-skz" 7s 541ms

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

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 7s 410ms

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

And Set advice window in schedule 3s 417ms

And Fill advice form 20s 518ms

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

And Go to "TRANSPORT_TABLE" 448ms

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

Then Check are advice values equals 5s 008ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 117ms

After Hooks.deleteTransportAfterTest() 778ms

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

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

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

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

And Set advice window in schedule 3s 412ms

And Fill advice form 20s 494ms

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

And Go to "TRANSPORT_TABLE" 481ms

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

Then Check are advice values equals 4s 988ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 965ms

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 "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 7s 634ms

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

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

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

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

And Set advice window in schedule 30s 152ms

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.pewAwv}, 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: 1dd3b576686a35e527449e67c4ca3cdc
*** 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 783ms

After Hooks.deleteTransportAfterTest() 571ms

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

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

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

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

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

And Set advice window in schedule 3s 340ms

And Fill advice form 20s 407ms

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

And Go to "TRANSPORT_TABLE" 461ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 128ms

After Hooks.deleteTransportAfterTest() 805ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

The scenario checks if you can correctly add an advice to the order. After the correct addition of the advice on the platform, the correctness of the data that has been sent to the SK API microservice database is also verified.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Set advice window in schedule 3s 335ms

And Fill advice form 20s 458ms

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

And Go to "TRANSPORT_TABLE" 468ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 365ms

After Hooks.deleteTransportAfterTest() 790ms

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

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

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

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

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

And Set advice window in schedule 3s 414ms

And Fill advice form 20s 325ms

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

And Go to "TRANSPORT_TABLE" 477ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 113ms

After Hooks.deleteTransportAfterTest() 810ms

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

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

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

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

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

And Set advice window in schedule 3s 357ms

And Fill advice form 20s 341ms

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

And Go to "TRANSPORT_TABLE" 503ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 981ms

After Hooks.deleteTransportAfterTest() 923ms

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

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

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

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

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

And Set advice window in schedule 3s 619ms

And Fill advice form 20s 453ms

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

And Go to "TRANSPORT_TABLE" 515ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 665ms

After Hooks.deleteTransportAfterTest() 811ms

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

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

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

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

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

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

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

When Reject status: Book of disinfection 225ms

And Check if reject date is visible 909ms

Then If user is login then logout 259ms

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

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

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

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

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 257ms

After Hooks.deleteTransportAfterTest() 710ms

After Hooks.rollbackWarehousesAccess() 724ms

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

And Prepare login page 463ms

And Click remind password button 274ms

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

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

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

And Extract password from mailgun mail 4s 068ms

And Reset password from link 1s 620ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 937ms

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

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

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

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

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

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

Then Save user details 1s 011ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 674ms

After Hooks.rollbackAddedAuthorities() 299ms

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

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

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

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

And Expand "other" notification section 2s 565ms

And Select all notifications in "other" section 291ms

Then Save user details 1s 515ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 921ms

After Hooks.rollbackAddedAuthorities() 139ms

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

Steps

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

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

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

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

And Go to "USERS_TAB" 1s 555ms

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

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

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

Then Save user details 1s 058ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 620ms

After Hooks.rollbackAddedAuthorities() 243ms

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

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

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

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

And Go to "USERS_TAB" 1s 592ms

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

And Expand "GLUE_FACTORY" notification section 561ms

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

Then Save user details 1s 880ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 083ms

After Hooks.rollbackAddedAuthorities() 243ms

	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 10s 950ms	Failed

Tag Report