Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.158	15 wrz 2021, 06:58

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	453	7	12	0	0	472	41	7	48	1h 4m 51s 380ms	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" 287ms

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

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

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

When Login as "piast-admin" 4s 881ms

Then Go to "INVITATIONS_TAB" 651ms

And Go to invitation details 140ms

Then Reject invitation by button as user 451ms

When If user is login then logout 895ms

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

And Go to "INVITATIONS_TAB" 480ms

And Go to "REJECTED_TAB" invitation status tab 306ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 159ms

After Hooks.cleanUserDetailsAfterTest() 1s 346ms

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

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

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

And Go to "INVITATIONS_TAB" 428ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 118ms

Hooks

After Hooks.deleteInvitationAfterTest() 180ms

After Hooks.cleanUserDetailsAfterTest() 1s 303ms

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

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

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

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

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

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

Given Click remind password button 217ms

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

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

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

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

And Reset password from link 1s 343ms

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

And User is successfully logged 030ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 965ms

After Hooks.clearUserPasswordDataAfterTest() 470ms

After Hooks.rollbackParameters() 091ms

After Hooks.unlockUsers() 142ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

And Show all transport types 1s 158ms

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

And Set advice window in schedule 3s 310ms

And Fill advice form 17s 158ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 272ms

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

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

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

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

And Show all transport types 1s 141ms

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

And Set advice window in schedule 3s 365ms

And Fill advice form 12s 900ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 078ms

After Hooks.deleteTransportAfterTest() 878ms

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

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

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

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

And Show all transport types 1s 153ms

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

And Set advice window in schedule 3s 239ms

And Fill advice form 19s 199ms

And Click advice save button and wait for advice form to disappear 17s 816ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 452ms

After Hooks.deleteTransportAfterTest() 755ms

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

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

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

And Show all transport types 1s 157ms

And Create advice by JSON file "CREATE_ADVICE_FOR_CONTAINER" as "super-admin-adama" 2s 996ms

And Go to "TRANSPORT_TABLE" 412ms

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

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

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

And Fill transport form 5s 208ms

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

And Expand advice panel 251ms

And Edit advice in transport details 17s 725ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 275ms

After Hooks.deleteTransportAfterTest() 700ms

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

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

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

And Show all transport types 1s 140ms

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

And Go to "TRANSPORT_TABLE" 390ms

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

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

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

And Fill transport form 1m 8s 640ms

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

And Expand advice panel 229ms

And Edit advice in transport details 8s 127ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 111ms

After Hooks.deleteTransportAfterTest() 860ms

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

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

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

And Show all transport types 1s 152ms

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

And Go to "TRANSPORT_TABLE" 360ms

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

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

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

And Fill transport form 28s 684ms

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

And Expand advice panel 230ms

And Edit advice in transport details 23s 361ms

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

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

Then Check if user got a mail 000ms

Error message

java.lang.AssertionError: Użytkownik nie otrzymał maila. Actual: []
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failEquals(Assert.java:185)
	at org.junit.Assert.assertNotEquals(Assert.java:161)
	at CucumberTests.Mail.MailTest.checkIfUseGotMail(MailTest.java:49)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/AdviceMail.feature:39)

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 716ms

After Hooks.deleteTransportAfterTest() 785ms

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

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

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

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

And Confirm status "ARRIVAL" by Public API "v1" 808ms

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu" 3m 1s 065ms

Then Check if user got a mail 000ms

Error message

java.lang.AssertionError: Użytkownik nie otrzymał maila. Actual: []
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failEquals(Assert.java:185)
	at org.junit.Assert.assertNotEquals(Assert.java:161)
	at CucumberTests.Mail.MailTest.checkIfUseGotMail(MailTest.java:49)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/AdviceMail.feature:54)

And Assign Queue to classification resource: "super-admin-skd" "trociny" "CLASSIFICATION" 000ms

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

And Confirm status "DEPARTURE" by Public API "v1" 000ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 051ms

After Hooks.deleteTransportAfterTest() 735ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackVerificationEmailSettingAfterTest

Scenario Outline Check if verification mail was sent to transport creator

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Login as "dha1-supplier-2" and set token of apiUsername "dha1-supplier-2" 9s 094ms

And Create transport "CREATE_DELIVERY" by JSON file as "dha1-supplier-2" 17s 156ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 715ms

After Hooks.deleteTransportAfterTest() 730ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 450ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @enableDisabledUserAfterTest

Scenario Outline Check if mail was not sent to creator if user is not enabled

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

And Create transport "CREATE_DELIVERY" by JSON file as "swiss-krono-delivery-producer" 16s 614ms

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

When Login as "swiss-krono-delivery-producer" 5s 224ms

And Go to "TRANSPORT_TABLE" 427ms

And Show all transport types 15s 066ms

And Check if transport is "visible" in table of transports 073ms

And Disable user "swiss-krono-delivery-producer" 877ms

And Confirm status "ARRIVAL" by Public API "v1" 832ms

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Potwierdzono status Wjazd na teren zakładu" 2m 43s 390ms

Then Check if user did not get an mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 861ms

After Hooks.deleteTransportAfterTest() 771ms

After Hooks.enableDisabledUserAfterTest() 821ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 043ms

After Hooks.deleteTransportAfterTest() 685ms

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

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

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

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

And Add a bid "1500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama" 1s 281ms

And Add a bid "500" to an auction by JSON file as "paa2-carrier" for "super-admin-adama" 1s 755ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 049ms

After Hooks.deleteTransportAfterTest() 516ms

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" 10s 761ms

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

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

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

And Add a bid "1500" to an auction by JSON file as "pskza1-carrier" for "pskza1-carrier" 882ms

And Wait till auction end 1m 57s 018ms

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

Then Check if user got a mail 000ms

Error message

java.lang.AssertionError: Użytkownik nie otrzymał maila. Actual: []
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failEquals(Assert.java:185)
	at org.junit.Assert.assertNotEquals(Assert.java:161)
	at CucumberTests.Mail.MailTest.checkIfUseGotMail(MailTest.java:49)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/AuctionMail.feature:39)

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 492ms

After Hooks.deleteTransportAfterTest() 586ms

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

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

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

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

And Wait till auction end 1m 58s 015ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 427ms

After Hooks.deleteTransportAfterTest() 564ms

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

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

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

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

And Add a bid "1500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama" 889ms

And Add a bid "500" to an auction by JSON file as "paa2-carrier" for "super-admin-adama" 1s 465ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 050ms

After Hooks.deleteTransportAfterTest() 551ms

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

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

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

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

And Add a bid "1500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama" 900ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 282ms

After Hooks.deleteTransportAfterTest() 567ms

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

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

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

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

And Add a bid "500" to an auction by JSON file as "paa1-carrier" for "super-admin-adama" 1s 394ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 027ms

After Hooks.deleteTransportAfterTest() 589ms

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" and set token of apiUsername "super-admin-adama" 5s 044ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 232ms

After Hooks.deleteTransportAfterTest() 633ms

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

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

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

And Go to "TRANSPORT_TABLE" 408ms

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

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

And Fill transport form 42s 972ms

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

And Fill discrepancy report section 52s 442ms

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

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

And Generate discrepancy report 21s 640ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 390ms

After Hooks.deleteTransportAfterTest() 869ms

View Feature Mode of transportation mail

@deleteModeOfTransportationAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 507ms

After Hooks.deleteModeOfTransportationAfterTest() 372ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 571ms

After Hooks.deleteModeOfTransportationAfterTest() 323ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackAddedAuthorities

Scenario Outline Check if mail was sent to after transport delay

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 202ms

And Select warehouse "Serownia" 1s 537ms

And Set week view 1s 255ms

And Show yesterday 1s 168ms

And Move window into the past 437ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 354ms

After Hooks.deleteTransportAfterTest() 772ms

After Hooks.rollbackAddedAuthorities() 218ms

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

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

And Wait "60" seconds 1m

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

When Get mail "apolloautomattest@gmail.com" message from mailgun with "Drobnica import" 2m 41s 694ms

Then Check if user got a mail 000ms

Error message

java.lang.AssertionError: Użytkownik nie otrzymał maila. Actual: []
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failEquals(Assert.java:185)
	at org.junit.Assert.assertNotEquals(Assert.java:161)
	at CucumberTests.Mail.MailTest.checkIfUseGotMail(MailTest.java:49)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/TransportMail.feature:27)

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 369ms

After Hooks.deleteTransportAfterTest() 561ms

View Feature Transport Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if mail was sent to after transport creation

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Error message

java.lang.AssertionError: Użytkownik nie otrzymał maila. Actual: []
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.failEquals(Assert.java:185)
	at org.junit.Assert.assertNotEquals(Assert.java:161)
	at CucumberTests.Mail.MailTest.checkIfUseGotMail(MailTest.java:49)
	at ✽.Check if user got a mail(file:Features/Atom/Mail/TransportMail.feature:27)

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 467ms

After Hooks.deleteTransportAfterTest() 531ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 232ms

After Hooks.deleteTransportAfterTest() 585ms

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" 18s 195ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 046ms

After Hooks.deleteTransportAfterTest() 516ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Transfer transport to carrier "Przewoźnik SKZ Automat 1" 34s 738ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 736ms

After Hooks.deleteTransportAfterTest() 577ms

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" 2s 927ms

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

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

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

And Add a bid "1500" to an auction by JSON file as "pskza1-carrier" for "pskza1-carrier" 980ms

And Add a bid "500" to an auction by JSON file as "pskza2-carrier-2" for "pskza2-carrier-2" 1s 039ms

Then If user is login then logout 262ms

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

And Go to auction details 2s 225ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 781ms

After Hooks.deleteTransportAfterTest() 691ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 709ms

After Hooks.deleteTransportAfterTest() 643ms

View Feature Remind password

@cleanUserDetailsAfterTest

Scenario Outline Check if remind password http status is ok

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 296ms

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

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

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 9s 948ms

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

And Set advice window in schedule 3s 364ms

And Fill advice form 20s 246ms

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

And Go to "TRANSPORT_TABLE" 465ms

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

Then Check are advice values equals 4s 948ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 427ms

After Hooks.deleteTransportAfterTest() 750ms

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

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

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

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

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

And Set advice window in schedule 3s 335ms

And Fill advice form 20s 764ms

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

And Go to "TRANSPORT_TABLE" 451ms

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

Then Check are advice values equals 4s 959ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 121ms

After Hooks.deleteTransportAfterTest() 720ms

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

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

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

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

And Set advice window in schedule 3s 382ms

And Fill advice form 20s 390ms

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

And Go to "TRANSPORT_TABLE" 489ms

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

Then Check are advice values equals 4s 991ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 313ms

After Hooks.deleteTransportAfterTest() 833ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 389ms

And Fill advice form 20s 415ms

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

And Go to "TRANSPORT_TABLE" 517ms

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

Then Check are advice values equals 4s 973ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 694ms

After Hooks.deleteTransportAfterTest() 764ms

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

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

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

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

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

And Set advice window in schedule 30s 123ms

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.63 (ff5c0da2ec0adeaed5550e6c7e98417dac77d98a-refs/branch-heads/4577@{#1135}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.FGRir8}, 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: 1200fca61a4ea8963b6e3429618a28eb
*** 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:83)
	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 778ms

After Hooks.deleteTransportAfterTest() 498ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 332ms

And Fill advice form 20s 467ms

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

And Go to "TRANSPORT_TABLE" 464ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 270ms

After Hooks.deleteTransportAfterTest() 745ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

And Set advice window in schedule 3s 323ms

And Fill advice form 20s 570ms

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

And Go to "TRANSPORT_TABLE" 447ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 340ms

After Hooks.deleteTransportAfterTest() 855ms

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

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

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

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

And Set advice window in schedule 3s 413ms

And Fill advice form 20s 393ms

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

And Go to "TRANSPORT_TABLE" 492ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 145ms

After Hooks.deleteTransportAfterTest() 771ms

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

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

And Prepare user "pskza1-carrier" details with all notifications and "" by JSON file 3s 407ms

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

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

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

And Set advice window in schedule 3s 421ms

And Fill advice form 20s 449ms

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

And Go to "TRANSPORT_TABLE" 473ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 039ms

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

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

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

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

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

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

And Set advice window in schedule 3s 469ms

And Fill advice form 20s 462ms

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

And Go to "TRANSPORT_TABLE" 426ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 674ms

After Hooks.deleteTransportAfterTest() 733ms

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

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

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

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

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

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

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

When Reject status: Book of disinfection 184ms

And Check if reject date is visible 1s 021ms

Then If user is login then logout 330ms

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

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

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

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//div//h5[@data-field-name='transport-logs-section']"}
  (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.63 (ff5c0da2ec0adeaed5550e6c7e98417dac77d98a-refs/branch-heads/4577@{#1135}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.FGRir8}, 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: 1200fca61a4ea8963b6e3429618a28eb
*** Element info: {Using=xpath, value=//div//h5[@data-field-name='transport-logs-section']}
	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.Transport.TransportFormPage.checkIfHistoryNoteWasAddedToTransport(TransportFormPage.java:227)
	at CucumberTests.StatusTests.RejectStatuses.checkIfHistoryNoteWasAddedToTransportAfterStatusRejection(RejectStatuses.java:67)
	at ✽.Check if history note was added to transport after status rejection - "LOAD"(file:Features/Atom/Statuses/RejectStatuses.feature:17)

And Get mail "apolloautomattest@gmail.com" message from mailgun with "Nieaktualna księga mycia i dezynfekcji" 000ms

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 124ms

After Hooks.deleteTransportAfterTest() 680ms

After Hooks.rollbackWarehousesAccess() 705ms

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

And Prepare login page 385ms

And Click remind password button 262ms

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

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

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

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

And Reset password from link with the same password 1s 416ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 993ms

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

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_USERS_MAIN_DATA" to user "oaa1-receiver-2" 443ms

When Login as "oaa1-receiver-2" 4s 312ms

And Go to user "oaa1-receiver" details edition by prepared link 143ms

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

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

Then Save user details 992ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 679ms

After Hooks.rollbackAddedAuthorities() 306ms

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

And Set basic authorities "ROLE_USERS_TAB;EDIT_USERS_NOTIFICATION" to user "pskza1-carrier-2" 247ms

When Login as "pskza1-carrier-2" 7s 211ms

And Go to user "pskza1-carrier" details edition by prepared link 097ms

And Expand "other" notification section 2s 486ms

And Select all notifications in "other" section 317ms

Then Save user details 1s 502ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 924ms

After Hooks.rollbackAddedAuthorities() 176ms

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

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;ROLE_EDIT_USERS_MAIN_DATA" to user "adama-buyer" 497ms

And Set user details json of user "oaa1-receiver" 012ms

When Login as "adama-buyer" 4s 994ms

And Go to "USERS_TAB" 1s 499ms

And Find user "oaa1-receiver" 3s 561ms

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

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

Then Save user details 1s 134ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 658ms

After Hooks.rollbackAddedAuthorities() 255ms

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

And Set basic authorities "ROLE_USERS_TAB;ROLE_EDIT_ALL_USERS;EDIT_USERS_NOTIFICATION" to user "swisskrono-tradesman" 401ms

And Set user details json of user "pskza1-carrier" 010ms

When Login as "swisskrono-tradesman" 9s 031ms

And Go to "USERS_TAB" 1s 584ms

And Find user "pskza1-carrier" 3s 572ms

And Expand "GLUE_FACTORY" notification section 518ms

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

Then Save user details 1s 763ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 064ms

After Hooks.rollbackAddedAuthorities() 244ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@cleanUserDetailsAfterTest	453	7	12	0	0	472	41	7	48	1h 4m 51s 380ms	Failed

Tag Report