Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.149	08 wrz 2021, 06:16

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	448	2	5	0	0	455	44	2	46	55m 13s 034ms	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" 233ms

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

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

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

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

Then Go to "INVITATIONS_TAB" 687ms

And Go to invitation details 145ms

Then Reject invitation by button as user 301ms

When If user is login then logout 309ms

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

And Go to "INVITATIONS_TAB" 463ms

And Go to "REJECTED_TAB" invitation status tab 241ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 167ms

After Hooks.cleanUserDetailsAfterTest() 1s 246ms

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

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

And Go to "INVITATIONS_TAB" 483ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 120ms

Hooks

After Hooks.deleteInvitationAfterTest() 191ms

After Hooks.cleanUserDetailsAfterTest() 1s 301ms

View Feature Login feature

@rollbackParameters @unlockUsers @cleanUserDetailsAfterTest @clearUserPasswordDataAfterTest

Scenario Outline Verify that password reset cancel login blockade [A-7286]

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skd" 241ms

And Prepare parameter "NUMBER_OF_FAILED_LOGIN_ATTEMPTS" with value: "1" 105ms

Given Failed login as "swiss-krono-delivery-admin-2" 1s 519ms

Then Verify that login error reason is "auth.invalidLoginOrPassword" 634ms

Given Try login as "swiss-krono-delivery-admin-2" 1s 527ms

Then Verify that login error reason is "auth.accountLocked" 295ms

Given Click remind password button 225ms

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

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

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

And Extract password reset link from mailgun mail 4s 397ms

And Reset password from link 1s 478ms

Then Login as "swiss-krono-delivery-admin-2" with new password 5s 040ms

And User is successfully logged 029ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 077ms

After Hooks.clearUserPasswordDataAfterTest() 711ms

After Hooks.rollbackParameters() 097ms

After Hooks.unlockUsers() 138ms

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

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

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

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

And Show all transport types 1s 172ms

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

And Set advice window in schedule 3s 498ms

And Fill advice form 17s 214ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 290ms

After Hooks.deleteTransportAfterTest() 759ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "piast-admin" and set token of apiUsername "super-admin-piast" 2s 573ms

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

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

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

And Show all transport types 1s 147ms

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

And Set advice window in schedule 3s 440ms

And Fill advice form 12s 971ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 061ms

After Hooks.deleteTransportAfterTest() 784ms

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

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

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

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

And Show all transport types 1s 150ms

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

And Set advice window in schedule 3s 276ms

And Fill advice form 18s 959ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 482ms

After Hooks.deleteTransportAfterTest() 827ms

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

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

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

And Show all transport types 1s 159ms

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

And Go to "TRANSPORT_TABLE" 415ms

And Go to transport details "CONTAINER" 3s 015ms

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

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

And Fill transport form 5s 231ms

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

And Expand advice panel 247ms

And Edit advice in transport details 17s 618ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 297ms

After Hooks.deleteTransportAfterTest() 790ms

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

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

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

And Show all transport types 1s 140ms

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

And Go to "TRANSPORT_TABLE" 407ms

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

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

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

And Fill transport form 1m 8s 690ms

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

And Expand advice panel 268ms

And Edit advice in transport details 8s 116ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 096ms

After Hooks.deleteTransportAfterTest() 901ms

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

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

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

And Show all transport types 1s 145ms

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

And Go to "TRANSPORT_TABLE" 375ms

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

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

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

And Fill transport form 28s 664ms

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

And Expand advice panel 247ms

And Edit advice in transport details 23s 344ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 615ms

After Hooks.deleteTransportAfterTest() 817ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to creator after status confirmation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-skd" 253ms

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

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

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

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

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

Then Check if user got a mail 000ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 956ms

After Hooks.deleteTransportAfterTest() 867ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 728ms

After Hooks.deleteTransportAfterTest() 764ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 438ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after creating a new auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 086ms

After Hooks.deleteTransportAfterTest() 705ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 087ms

After Hooks.deleteTransportAfterTest() 586ms

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

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

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

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

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

And Wait till auction end 1m 56s 015ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 493ms

After Hooks.deleteTransportAfterTest() 702ms

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

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

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

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

And Wait till auction end 1m 57s 015ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 441ms

After Hooks.deleteTransportAfterTest() 602ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 053ms

After Hooks.deleteTransportAfterTest() 611ms

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

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

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

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

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" 1m 37s 748ms

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 234ms

After Hooks.deleteTransportAfterTest() 565ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 127ms

After Hooks.deleteTransportAfterTest() 620ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 252ms

After Hooks.deleteTransportAfterTest() 758ms

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

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

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

And Go to "TRANSPORT_TABLE" 394ms

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

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

And Fill transport form 43s 154ms

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

And Fill discrepancy report section 52s 427ms

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

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

And Generate discrepancy report 21s 648ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 355ms

After Hooks.deleteTransportAfterTest() 979ms

View Feature Mode of transportation mail

@deleteModeOfTransportationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent after updating mode of transportation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Set token of apiUsername "super-admin-bausch" 252ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 519ms

After Hooks.deleteModeOfTransportationAfterTest() 343ms

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 464ms

After Hooks.deleteModeOfTransportationAfterTest() 294ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 413ms

And Select warehouse "Serownia" 1s 646ms

And Set week view 1s 262ms

And Show yesterday 1s 175ms

And Move window into the past 436ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 433ms

After Hooks.deleteTransportAfterTest() 773ms

After Hooks.rollbackAddedAuthorities() 189ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 053ms

After Hooks.deleteTransportAfterTest() 597ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 258ms

After Hooks.deleteTransportAfterTest() 634ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 007ms

After Hooks.deleteTransportAfterTest() 756ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 042ms

After Hooks.deleteTransportAfterTest() 520ms

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

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

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

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

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

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

Then If user is login then logout 258ms

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

And Go to auction details 1s 856ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 721ms

After Hooks.deleteTransportAfterTest() 830ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 687ms

After Hooks.deleteTransportAfterTest() 654ms

View Feature Remind password

@cleanUserDetailsAfterTest

Scenario Outline Check if remind password http status is ok

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 263ms

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

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

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

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

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

And Set advice window in schedule 3s 361ms

And Fill advice form 20s 486ms

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

And Go to "TRANSPORT_TABLE" 402ms

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

Then Check are advice values equals 4s 979ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 278ms

After Hooks.deleteTransportAfterTest() 807ms

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

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

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

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

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

And Set advice window in schedule 3s 379ms

And Fill advice form 20s 523ms

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

And Go to "TRANSPORT_TABLE" 409ms

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

Then Check are advice values equals 4s 955ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 196ms

After Hooks.deleteTransportAfterTest() 843ms

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

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

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

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

And Set advice window in schedule 3s 385ms

And Fill advice form 20s 497ms

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

And Go to "TRANSPORT_TABLE" 476ms

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

Then Check are advice values equals 4s 991ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 300ms

After Hooks.deleteTransportAfterTest() 796ms

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

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

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

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

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

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

And Set advice window in schedule 3s 379ms

And Fill advice form 20s 400ms

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

And Go to "TRANSPORT_TABLE" 475ms

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

Then Check are advice values equals 4s 942ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 708ms

After Hooks.deleteTransportAfterTest() 782ms

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

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

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

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

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

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

And Set advice window in schedule 30s 094ms

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=93.0.4577.63)
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=93.0.4577.15 (660fc11082ba57405eca2e8c49c3e1af756fbfae-refs/branch-heads/4577@{#203}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.YcHu2J}, 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=93.0.4577.63, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 13fedc522d7dee1a732dea1116ebf13a
*** 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 815ms

After Hooks.deleteTransportAfterTest() 573ms

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

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

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

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

And Set advice window in schedule 3s 287ms

And Fill advice form 20s 470ms

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

And Go to "TRANSPORT_TABLE" 460ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 221ms

After Hooks.deleteTransportAfterTest() 835ms

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

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

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

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

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

And Set advice window in schedule 3s 328ms

And Fill advice form 20s 419ms

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

And Go to "TRANSPORT_TABLE" 448ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 272ms

After Hooks.deleteTransportAfterTest() 832ms

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

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

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

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

And Set advice window in schedule 3s 385ms

And Fill advice form 20s 507ms

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

And Go to "TRANSPORT_TABLE" 466ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 139ms

After Hooks.deleteTransportAfterTest() 864ms

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

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

And Add transport by SKApi in "MGW" assigned to "" 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 3s 800ms

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

And Set advice window in schedule 3s 386ms

And Fill advice form 20s 388ms

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

And Go to "TRANSPORT_TABLE" 468ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 910ms

After Hooks.deleteTransportAfterTest() 839ms

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

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

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

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

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

And Set advice window in schedule 3s 382ms

And Fill advice form 20s 466ms

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

And Go to "TRANSPORT_TABLE" 437ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 736ms

After Hooks.deleteTransportAfterTest() 851ms

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

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

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

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

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

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

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

When Reject status: Book of disinfection 206ms

And Check if reject date is visible 952ms

Then If user is login then logout 291ms

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

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

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

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

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 249ms

After Hooks.deleteTransportAfterTest() 777ms

After Hooks.rollbackWarehousesAccess() 772ms

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

And Prepare login page 456ms

And Click remind password button 262ms

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

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

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

And Extract password reset link from mailgun mail 4s 101ms

And Reset password from link 1s 568ms

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

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div[contains(@class, 'alert-danger')]"}
  (Session info: headless chrome=93.0.4577.63)
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=93.0.4577.15 (660fc11082ba57405eca2e8c49c3e1af756fbfae-refs/branch-heads/4577@{#203}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.YcHu2J}, 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=93.0.4577.63, browserName=chrome, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, webauthn:extension:largeBlob=true, webauthn:virtualAuthenticators=true}]
Session ID: 13fedc522d7dee1a732dea1116ebf13a
*** Element info: {Using=xpath, value=//div[contains(@class, 'alert-danger')]}
	at sun.reflect.GeneratedConstructorAccessor213.newInstance(Unknown Source)
	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.LoginTest.isAlertDisplayedInRemindPasswordPage(LoginTest.java:132)
	at ✽.Check if alert is displayed "Hasło nie może być takie samo jak aktualne hasło użytkownika." in remind password page(file:Features/Atom/Users/User.feature:139)

Hooks

After Hooks.cleanUserDetailsAfterTest() 935ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7965

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

Then Save user details 981ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 658ms

After Hooks.rollbackAddedAuthorities() 279ms

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

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

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

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

And Expand "other" notification section 2s 435ms

And Select all notifications in "other" section 283ms

Then Save user details 1s 498ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 876ms

After Hooks.rollbackAddedAuthorities() 147ms

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

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

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

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

And Go to "USERS_TAB" 1s 452ms

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

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

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

Then Save user details 986ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 765ms

After Hooks.rollbackAddedAuthorities() 286ms

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

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

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

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

And Go to "USERS_TAB" 1s 606ms

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

And Expand "GLUE_FACTORY" notification section 595ms

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

Then Save user details 1s 907ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 005ms

After Hooks.rollbackAddedAuthorities() 231ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@cleanUserDetailsAfterTest	448	2	5	0	0	455	44	2	46	55m 13s 034ms	Failed

Tag Report