Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.154	11 wrz 2021, 06:36

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	450	2	9	0	0	461	45	2	47	52m 7s 338ms	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" 235ms

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

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

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

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

Then Go to "INVITATIONS_TAB" 662ms

And Go to invitation details 133ms

Then Reject invitation by button as user 321ms

When If user is login then logout 602ms

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

And Go to "INVITATIONS_TAB" 464ms

And Go to "REJECTED_TAB" invitation status tab 280ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 154ms

After Hooks.cleanUserDetailsAfterTest() 1s 235ms

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

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

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

And Go to "INVITATIONS_TAB" 552ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 109ms

Hooks

After Hooks.deleteInvitationAfterTest() 198ms

After Hooks.cleanUserDetailsAfterTest() 1s 348ms

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

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

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

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

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

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

Given Click remind password button 260ms

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

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

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

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

And Reset password from link 1s 408ms

Then Login as "swiss-krono-delivery-admin-2" with new password 4s 835ms

And User is successfully logged 030ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 002ms

After Hooks.clearUserPasswordDataAfterTest() 473ms

After Hooks.rollbackParameters() 110ms

After Hooks.unlockUsers() 145ms

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

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

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

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

And Show all transport types 1s 153ms

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

And Set advice window in schedule 3s 340ms

And Fill advice form 17s 131ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 297ms

After Hooks.deleteTransportAfterTest() 869ms

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

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

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

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

And Show all transport types 1s 197ms

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

And Set advice window in schedule 3s 748ms

And Fill advice form 12s 955ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 062ms

After Hooks.deleteTransportAfterTest() 789ms

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

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

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

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

And Show all transport types 1s 162ms

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

And Set advice window in schedule 3s 293ms

And Fill advice form 18s 987ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 481ms

After Hooks.deleteTransportAfterTest() 745ms

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

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

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

And Show all transport types 1s 124ms

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

And Go to "TRANSPORT_TABLE" 407ms

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

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

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

And Fill transport form 5s 224ms

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

And Expand advice panel 271ms

And Edit advice in transport details 17s 668ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 393ms

After Hooks.deleteTransportAfterTest() 736ms

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

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

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

And Show all transport types 1s 132ms

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

And Go to "TRANSPORT_TABLE" 332ms

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

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

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

And Fill transport form 1m 8s 546ms

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

And Expand advice panel 257ms

And Edit advice in transport details 8s 147ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 114ms

After Hooks.deleteTransportAfterTest() 909ms

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

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

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

And Show all transport types 1s 173ms

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

And Go to "TRANSPORT_TABLE" 417ms

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

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

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

And Fill transport form 28s 661ms

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

And Expand advice panel 276ms

And Edit advice in transport details 23s 353ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 773ms

After Hooks.deleteTransportAfterTest() 866ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 948ms

After Hooks.deleteTransportAfterTest() 822ms

View Feature Advice Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest @rollbackVerificationEmailSettingAfterTest

Scenario Outline Check if verification mail was sent to transport creator

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 689ms

After Hooks.deleteTransportAfterTest() 722ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 435ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 070ms

After Hooks.deleteTransportAfterTest() 740ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 134ms

After Hooks.deleteTransportAfterTest() 597ms

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

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

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

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

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

And Wait till auction end 1m 57s 015ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 397ms

After Hooks.deleteTransportAfterTest() 582ms

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

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

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

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

And Wait till auction end 1m 57s 018ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 389ms

After Hooks.deleteTransportAfterTest() 650ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 061ms

After Hooks.deleteTransportAfterTest() 576ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 263ms

After Hooks.deleteTransportAfterTest() 564ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 966ms

After Hooks.deleteTransportAfterTest() 630ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 079ms

After Hooks.deleteTransportAfterTest() 699ms

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

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

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

And Go to "TRANSPORT_TABLE" 416ms

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

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

And Fill transport form 1s 276ms

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-2/temp/buildTmp/.com.google.Chrome.jmHEYW}, 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: 71dd6aa921b779f6ffe9792924bce038
	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 067ms

After Hooks.deleteTransportAfterTest() 941ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 526ms

After Hooks.deleteModeOfTransportationAfterTest() 361ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 499ms

After Hooks.deleteModeOfTransportationAfterTest() 313ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 274ms

And Select warehouse "Serownia" 1s 589ms

And Set week view 1s 234ms

And Show yesterday 1s 130ms

And Move window into the past 451ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 373ms

After Hooks.deleteTransportAfterTest() 773ms

After Hooks.rollbackAddedAuthorities() 179ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 112ms

After Hooks.deleteTransportAfterTest() 559ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 340ms

After Hooks.deleteTransportAfterTest() 551ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 065ms

After Hooks.deleteTransportAfterTest() 734ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 014ms

After Hooks.deleteTransportAfterTest() 566ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 921ms

After Hooks.deleteTransportAfterTest() 795ms

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

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

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

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

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

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

Then If user is login then logout 244ms

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

And Go to auction details 1s 845ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 885ms

After Hooks.deleteTransportAfterTest() 859ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 722ms

After Hooks.deleteTransportAfterTest() 671ms

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 222ms

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

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

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

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

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

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

And Set advice window in schedule 3s 397ms

And Fill advice form 20s 198ms

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

And Go to "TRANSPORT_TABLE" 465ms

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

Then Check are advice values equals 4s 981ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 304ms

After Hooks.deleteTransportAfterTest() 770ms

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_OWN_COLLECTION" "super-admin-skz" 001ms

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

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

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

And Set advice window in schedule 3s 403ms

And Fill advice form 20s 435ms

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

And Go to "TRANSPORT_TABLE" 461ms

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

Then Check are advice values equals 4s 982ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 095ms

After Hooks.deleteTransportAfterTest() 785ms

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

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

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

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

And Set advice window in schedule 3s 375ms

And Fill advice form 20s 403ms

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

And Go to "TRANSPORT_TABLE" 469ms

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

Then Check are advice values equals 5s 003ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 274ms

After Hooks.deleteTransportAfterTest() 799ms

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

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

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

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

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

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

And Set advice window in schedule 3s 374ms

And Fill advice form 20s 393ms

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

And Go to "TRANSPORT_TABLE" 524ms

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

Then Check are advice values equals 4s 961ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 829ms

After Hooks.deleteTransportAfterTest() 826ms

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" 8s 713ms

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

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

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

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

And Set advice window in schedule 3s 410ms

And Fill advice form 20s 512ms

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

And Go to "TRANSPORT_TABLE" 446ms

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

Then Check are advice values equals 4s 973ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 777ms

After Hooks.deleteTransportAfterTest() 832ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

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

And Set advice window in schedule 3s 369ms

And Fill advice form 20s 398ms

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

And Go to "TRANSPORT_TABLE" 410ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 063ms

After Hooks.deleteTransportAfterTest() 779ms

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

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

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

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

And Set advice window in schedule 3s 404ms

And Fill advice form 20s 375ms

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

And Go to "TRANSPORT_TABLE" 506ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 305ms

After Hooks.deleteTransportAfterTest() 813ms

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

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

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

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

And Set advice window in schedule 3s 346ms

And Fill advice form 20s 679ms

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

And Go to "TRANSPORT_TABLE" 512ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 254ms

After Hooks.deleteTransportAfterTest() 804ms

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

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

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

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

And Set advice window in schedule 3s 437ms

And Fill advice form 20s 388ms

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

And Go to "TRANSPORT_TABLE" 478ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 3s 060ms

After Hooks.deleteTransportAfterTest() 946ms

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

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

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

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

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

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

And Set advice window in schedule 3s 341ms

And Fill advice form 20s 459ms

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

And Go to "TRANSPORT_TABLE" 446ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 672ms

After Hooks.deleteTransportAfterTest() 807ms

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

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

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

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

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

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

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

When Reject status: Book of disinfection 217ms

And Check if reject date is visible 875ms

Then If user is login then logout 659ms

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

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

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

Error message

java.lang.AssertionError: Nie znaleziono wpisu w historii zlecenia o odrzuceniu statusu!
	at org.junit.Assert.fail(Assert.java:88)
	at org.junit.Assert.assertTrue(Assert.java:41)
	at Pages.Transport.TransportFormPage.checkIfHistoryNoteWasAddedToTransport(TransportFormPage.java:243)
	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 101ms

After Hooks.deleteTransportAfterTest() 725ms

After Hooks.rollbackWarehousesAccess() 736ms

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

And Prepare login page 476ms

And Click remind password button 246ms

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

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

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

And Extract password reset link from mailgun mail 3s 975ms

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

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() 934ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7965

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

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

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

Then Save user details 1s 047ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 691ms

After Hooks.rollbackAddedAuthorities() 264ms

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

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

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

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

And Expand "other" notification section 2s 528ms

And Select all notifications in "other" section 313ms

Then Save user details 1s 519ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 115ms

After Hooks.rollbackAddedAuthorities() 159ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

And Go to "USERS_TAB" 1s 478ms

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

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

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

Then Save user details 1s 024ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 693ms

After Hooks.rollbackAddedAuthorities() 240ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

And Go to "USERS_TAB" 1s 557ms

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

And Expand "GLUE_FACTORY" notification section 529ms

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

Then Save user details 1s 809ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 056ms

After Hooks.rollbackAddedAuthorities() 238ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@cleanUserDetailsAfterTest	450	2	9	0	0	461	45	2	47	52m 7s 338ms	Failed

Tag Report