Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.159	16 wrz 2021, 07:01

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	445	8	19	0	0	472	40	8	48	1h 3m 2s 404ms	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" 282ms

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

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

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

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

Then Go to "INVITATIONS_TAB" 649ms

And Go to invitation details 134ms

Then Reject invitation by button as user 287ms

When If user is login then logout 319ms

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

And Go to "INVITATIONS_TAB" 464ms

And Go to "REJECTED_TAB" invitation status tab 257ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 143ms

After Hooks.cleanUserDetailsAfterTest() 1s 260ms

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

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

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

And Go to "INVITATIONS_TAB" 478ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 118ms

Hooks

After Hooks.deleteInvitationAfterTest() 192ms

After Hooks.cleanUserDetailsAfterTest() 1s 265ms

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

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

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

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

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

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

Given Click remind password button 265ms

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

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

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

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

And Reset password from link 1s 343ms

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

And User is successfully logged 029ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 946ms

After Hooks.clearUserPasswordDataAfterTest() 477ms

After Hooks.rollbackParameters() 092ms

After Hooks.unlockUsers() 143ms

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

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

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

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

And Show all transport types 1s 209ms

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

And Set advice window in schedule 3s 279ms

And Fill advice form 17s 218ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 298ms

After Hooks.deleteTransportAfterTest() 883ms

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

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

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

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

And Show all transport types 1s 157ms

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

And Set advice window in schedule 3s 369ms

And Fill advice form 12s 974ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 020ms

After Hooks.deleteTransportAfterTest() 812ms

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

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

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

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

And Show all transport types 1s 143ms

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

And Set advice window in schedule 3s 289ms

And Fill advice form 18s 705ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 499ms

After Hooks.deleteTransportAfterTest() 726ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

And Show all transport types 1s 159ms

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

And Go to "TRANSPORT_TABLE" 416ms

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

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

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

And Fill transport form 5s 201ms

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

And Expand advice panel 230ms

And Edit advice in transport details 17s 598ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 272ms

After Hooks.deleteTransportAfterTest() 765ms

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

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

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

And Show all transport types 1s 135ms

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

And Go to "TRANSPORT_TABLE" 338ms

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

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

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

And Fill transport form 1m 8s 449ms

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

And Expand advice panel 255ms

And Edit advice in transport details 8s 118ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 063ms

After Hooks.deleteTransportAfterTest() 948ms

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

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

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

And Show all transport types 1s 164ms

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

And Go to "TRANSPORT_TABLE" 373ms

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

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

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

And Fill transport form 28s 608ms

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

And Expand advice panel 281ms

And Edit advice in transport details 23s 505ms

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

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

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

After Hooks.deleteTransportAfterTest() 954ms

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

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

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

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

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

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

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

After Hooks.deleteTransportAfterTest() 861ms

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

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

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

And Login as "dha1-supplier-2" and set token of apiUsername "dha1-supplier-2" 8s 880ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 755ms

After Hooks.deleteTransportAfterTest() 773ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 468ms

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

Steps

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

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

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

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

And Go to "TRANSPORT_TABLE" 533ms

And Show all transport types 15s 071ms

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

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

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

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

Then Check if user did not get an mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 900ms

After Hooks.deleteTransportAfterTest() 899ms

After Hooks.enableDisabledUserAfterTest() 877ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 123ms

After Hooks.deleteTransportAfterTest() 731ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 017ms

After Hooks.deleteTransportAfterTest() 631ms

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" 11s 435ms

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

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

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

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

And Wait till auction end 1m 56s 018ms

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

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

After Hooks.deleteTransportAfterTest() 657ms

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

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

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

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

And Wait till auction end 1m 57s 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 344ms

After Hooks.deleteTransportAfterTest() 655ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 071ms

After Hooks.deleteTransportAfterTest() 600ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 259ms

After Hooks.deleteTransportAfterTest() 598ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after accepting minimal price

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

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

After Hooks.deleteTransportAfterTest() 622ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 071ms

After Hooks.deleteTransportAfterTest() 687ms

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

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

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

And Go to "TRANSPORT_TABLE" 382ms

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

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

And Fill transport form 1s 342ms

Error message

org.openqa.selenium.StaleElementReferenceException: stale element reference: element is not attached to the page document
  (Session info: headless chrome=93.0.4577.63)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/stale_element_reference.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/temp/buildTmp/.com.google.Chrome.iZv8El}, 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: 2f6929344068bebcb852b82e76cd0251
	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.RemoteWebElement.execute(RemoteWebElement.java:279)
	at org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:83)
	at CucumberTests.Transport.Transport.selectValue(Transport.java:227)
	at CucumberTests.Transport.Transport.fillSelectInput(Transport.java:216)
	at CucumberTests.Transport.Transport.fillFields(Transport.java:172)
	at CucumberTests.Transport.Transport.fillForm(Transport.java:150)
	at CucumberTests.Transport.CreateTransport.fillTransportForm(CreateTransport.java:184)
	at ✽.Fill transport form(file:Features/Atom/Mail/DiscrepancyReportMail.feature:11)

And Open section: "discrepancy-report-panel" 000ms

And Fill discrepancy report section 000ms

And Go to transport details "DELIVERY" 000ms

And Change filled value in details "rodo-acceptance" "checkbox" "true" "0" 000ms

And Generate discrepancy report 000ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 071ms

After Hooks.deleteTransportAfterTest() 773ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 556ms

After Hooks.deleteModeOfTransportationAfterTest() 368ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 553ms

After Hooks.deleteModeOfTransportationAfterTest() 308ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 179ms

And Select warehouse "Serownia" 1s 633ms

And Set week view 1s 214ms

And Show yesterday 1s 143ms

And Move window into the past 452ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 659ms

After Hooks.deleteTransportAfterTest() 827ms

After Hooks.rollbackAddedAuthorities() 167ms

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

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

And Wait "60" seconds 1m

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

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

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

After Hooks.deleteTransportAfterTest() 551ms

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

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

And Wait "60" seconds 1m

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

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

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

After Hooks.deleteTransportAfterTest() 581ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 048ms

After Hooks.deleteTransportAfterTest() 762ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 070ms

After Hooks.deleteTransportAfterTest() 556ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 966ms

After Hooks.deleteTransportAfterTest() 886ms

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

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

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" 3s 488ms

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

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

Then If user is login then logout 609ms

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

And Go to auction details 1s 841ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 708ms

After Hooks.deleteTransportAfterTest() 840ms

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" 3s 025ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 907ms

After Hooks.deleteTransportAfterTest() 687ms

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 286ms

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

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

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

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

And Check is transport "CONTAINER" created in transport table and set transport id 6s 961ms

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

And Set advice window in schedule 3s 304ms

And Fill advice form 20s 447ms

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

And Go to "TRANSPORT_TABLE" 376ms

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

Then Check are advice values equals 4s 891ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 310ms

After Hooks.deleteTransportAfterTest() 830ms

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

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

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

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

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

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

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

And Set advice window in schedule 3s 331ms

And Fill advice form 20s 531ms

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

And Go to "TRANSPORT_TABLE" 463ms

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

Then Check are advice values equals 4s 963ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 131ms

After Hooks.deleteTransportAfterTest() 805ms

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

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

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

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

And Set advice window in schedule 3s 384ms

And Fill advice form 20s 503ms

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

And Go to "TRANSPORT_TABLE" 448ms

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

Then Check are advice values equals 4s 976ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 415ms

After Hooks.deleteTransportAfterTest() 832ms

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

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

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

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

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

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

And Set advice window in schedule 3s 357ms

And Fill advice form 20s 383ms

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

And Go to "TRANSPORT_TABLE" 459ms

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

Then Check are advice values equals 4s 972ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 740ms

After Hooks.deleteTransportAfterTest() 832ms

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

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

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

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

And Set advice window in schedule 30s 156ms

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/temp/buildTmp/.com.google.Chrome.iZv8El}, 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: 2f6929344068bebcb852b82e76cd0251
*** 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 805ms

After Hooks.deleteTransportAfterTest() 541ms

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

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

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

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

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

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

And Set advice window in schedule 3s 401ms

And Fill advice form 20s 416ms

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

And Go to "TRANSPORT_TABLE" 483ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 235ms

After Hooks.deleteTransportAfterTest() 899ms

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

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

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

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

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

And Check is transport "CONTAINER" created in transport table and set transport id 6s 974ms

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

And Set advice window in schedule 3s 324ms

And Fill advice form 20s 508ms

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

And Go to "TRANSPORT_TABLE" 417ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 321ms

After Hooks.deleteTransportAfterTest() 805ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Set advice window in schedule 3s 407ms

And Fill advice form 20s 467ms

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

And Go to "TRANSPORT_TABLE" 467ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 232ms

After Hooks.deleteTransportAfterTest() 927ms

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

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

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

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

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

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

And Set advice window in schedule 3s 365ms

And Fill advice form 20s 309ms

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

And Go to "TRANSPORT_TABLE" 559ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 129ms

After Hooks.deleteTransportAfterTest() 895ms

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

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

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

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

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

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

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

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

And Go to "TRANSPORT_TABLE" 427ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 690ms

After Hooks.deleteTransportAfterTest() 825ms

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

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

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

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

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

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

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

When Reject status: Book of disinfection 194ms

And Check if reject date is visible 996ms

Then If user is login then logout 251ms

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

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

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

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/temp/buildTmp/.com.google.Chrome.iZv8El}, 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: 2f6929344068bebcb852b82e76cd0251
*** 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 112ms

After Hooks.deleteTransportAfterTest() 734ms

After Hooks.rollbackWarehousesAccess() 739ms

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

And Prepare login page 449ms

And Click remind password button 265ms

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

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

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

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 938ms

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

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

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

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

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

Then Save user details 1s 030ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 673ms

After Hooks.rollbackAddedAuthorities() 266ms

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

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

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

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

And Expand "other" notification section 2s 442ms

And Select all notifications in "other" section 284ms

Then Save user details 1s 507ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 957ms

After Hooks.rollbackAddedAuthorities() 171ms

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

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

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

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

And Go to "USERS_TAB" 1s 504ms

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

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

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

Then Save user details 1s 074ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 651ms

After Hooks.rollbackAddedAuthorities() 252ms

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

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

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

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

And Go to "USERS_TAB" 1s 559ms

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

And Expand "GLUE_FACTORY" notification section 509ms

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

Then Save user details 1s 752ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 071ms

After Hooks.rollbackAddedAuthorities() 250ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@cleanUserDetailsAfterTest	445	8	19	0	0	472	40	8	48	1h 3m 2s 404ms	Failed

Tag Report