Cucumber-JVM Reports - Tag: @cleanUserDetailsAfterTest

Project	Number	Date
ApolloFullRunnerReport	apollo-test-2.146	05 wrz 2021, 06:14

	Steps	Scenarios	Features
@cleanUserDetailsAfterTest	427	2	12	0	0	441	43	2	45	52m 6s 645ms	Failed

View Feature Invitation

@deleteInvitationAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if rejected invitation is visible in rejected tab

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

Given Set token of apiUsername "super-admin-piast" 220ms

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

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

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

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

Then Go to "INVITATIONS_TAB" 737ms

And Go to invitation details 146ms

Then Reject invitation by button as user 305ms

When If user is login then logout 609ms

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

And Go to "INVITATIONS_TAB" 485ms

And Go to "REJECTED_TAB" invitation status tab 299ms

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

Hooks

After Hooks.deleteInvitationAfterTest() 156ms

After Hooks.cleanUserDetailsAfterTest() 1s 373ms

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

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

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

And Go to "INVITATIONS_TAB" 444ms

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

And Wait "3" seconds 3s

Then Create invitation success alert is displayed 126ms

Hooks

After Hooks.deleteInvitationAfterTest() 197ms

After Hooks.cleanUserDetailsAfterTest() 1s 280ms

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

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

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

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

And Show all transport types 1s 145ms

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

And Set advice window in schedule 3s 355ms

And Fill advice form 17s 245ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 141ms

After Hooks.deleteTransportAfterTest() 787ms

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

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

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

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

And Show all transport types 1s 145ms

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

And Set advice window in schedule 3s 375ms

And Fill advice form 12s 959ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 014ms

After Hooks.deleteTransportAfterTest() 743ms

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

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

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

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

And Show all transport types 1s 138ms

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

And Set advice window in schedule 3s 185ms

And Fill advice form 18s 832ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 498ms

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

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

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

And Show all transport types 1s 166ms

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

And Go to "TRANSPORT_TABLE" 377ms

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

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

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

And Fill transport form 5s 181ms

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

And Expand advice panel 259ms

And Edit advice in transport details 17s 560ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 294ms

After Hooks.deleteTransportAfterTest() 715ms

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

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

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

And Show all transport types 1s 145ms

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

And Go to "TRANSPORT_TABLE" 416ms

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

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

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

And Fill transport form 1m 8s 694ms

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

And Expand advice panel 236ms

And Edit advice in transport details 8s 171ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 104ms

After Hooks.deleteTransportAfterTest() 972ms

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

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

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

And Show all transport types 1s 146ms

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

And Go to "TRANSPORT_TABLE" 365ms

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

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

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

And Expand advice panel 275ms

And Edit advice in transport details 23s 110ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 709ms

After Hooks.deleteTransportAfterTest() 926ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 923ms

After Hooks.deleteTransportAfterTest() 826ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 669ms

After Hooks.deleteTransportAfterTest() 743ms

After Hooks.rollbackVerificationEmailSettingAfterTest() 422ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 090ms

After Hooks.deleteTransportAfterTest() 719ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing auction

Hooks

Before Hooks.showScenarioName(Scenario) 002ms

Steps

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 030ms

After Hooks.deleteTransportAfterTest() 610ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after bid has been added to auction

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-producer" and set token of apiUsername "super-admin-skz" 12s 206ms

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

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

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

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

And Wait till auction end 1m 56s 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 480ms

After Hooks.deleteTransportAfterTest() 650ms

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

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

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

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

And Wait till auction end 1m 57s 016ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 387ms

After Hooks.deleteTransportAfterTest() 673ms

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

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 060ms

After Hooks.deleteTransportAfterTest() 588ms

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

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 261ms

After Hooks.deleteTransportAfterTest() 667ms

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

And Prepare user "paa1-carrier@qa.qa-test" 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 091ms

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@qa.qa-test" for "super-admin-adama" 1s 860ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 055ms

After Hooks.deleteTransportAfterTest() 591ms

View Feature Auctions Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail two hours before auction ends

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 189ms

After Hooks.deleteTransportAfterTest() 689ms

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

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

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

And Go to "TRANSPORT_TABLE" 379ms

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

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

And Fill transport form 1s 300ms

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.15 (660fc11082ba57405eca2e8c49c3e1af756fbfae-refs/branch-heads/4577@{#203}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.JodGHj}, 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: 5b4be4f0d4e5e9c51e0c52affa36e4e5
	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 105ms

After Hooks.deleteTransportAfterTest() 880ms

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

Steps

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 531ms

After Hooks.deleteModeOfTransportationAfterTest() 365ms

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 524ms

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

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

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

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

And Go to "WAREHOUSE_TAB" 1s 424ms

And Select warehouse "Serownia" 1s 651ms

And Set week view 1s 258ms

And Show yesterday 1s 148ms

And Move window into the past 413ms

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 386ms

After Hooks.deleteTransportAfterTest() 768ms

After Hooks.rollbackAddedAuthorities() 216ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 172ms

After Hooks.deleteTransportAfterTest() 613ms

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

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

And Wait "60" seconds 1m

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 314ms

After Hooks.deleteTransportAfterTest() 566ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 023ms

After Hooks.deleteTransportAfterTest() 814ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 123ms

After Hooks.deleteTransportAfterTest() 574ms

View Feature Transport Transfer Mail

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check mail after loosing inquiry

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

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

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

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

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

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

And Add a bid "500" to an auction by JSON file as "pskza2-carrier-2@qa.qa-test" for "pskza2-carrier-2@qa.qa-test" 1s 178ms

Then If user is login then logout 267ms

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

And Go to auction details 2s 208ms

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 775ms

After Hooks.deleteTransportAfterTest() 1s 031ms

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

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

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

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

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

Then Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 762ms

After Hooks.deleteTransportAfterTest() 671ms

View Feature Remind password

@cleanUserDetailsAfterTest

Scenario Outline Check if remind password http status is ok

Hooks

Before Hooks.showScenarioName(Scenario) 003ms

Steps

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

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

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 500ms

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

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

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

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

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

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

And Set advice window in schedule 3s 503ms

And Fill advice form 20s 343ms

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

And Go to "TRANSPORT_TABLE" 465ms

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

Then Check are advice values equals 4s 989ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 374ms

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

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

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

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

And Set advice window in schedule 3s 333ms

And Fill advice form 20s 465ms

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

And Go to "TRANSPORT_TABLE" 448ms

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

Then Check are advice values equals 4s 908ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 098ms

After Hooks.deleteTransportAfterTest() 857ms

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

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

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

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

And Set advice window in schedule 3s 277ms

And Fill advice form 20s 294ms

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

And Go to "TRANSPORT_TABLE" 488ms

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

Then Check are advice values equals 4s 949ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 275ms

After Hooks.deleteTransportAfterTest() 787ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it possible to advice transport when transport is created by sk API

The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 8s 482ms

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

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

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

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

And Set advice window in schedule 3s 477ms

And Fill advice form 20s 461ms

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

And Go to "TRANSPORT_TABLE" 454ms

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

Then Check are advice values equals 4s 945ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 673ms

After Hooks.deleteTransportAfterTest() 779ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Check if it possible to advice transport when transport is created by sk API

The scenario checks if you can correctly add an advice to the order. After correct creation of the advice, the validity of the advice data on the platform is checked.

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 7s 386ms

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

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

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

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

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

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

And Set advice window in schedule 30s 126ms

Error message

org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//button[@data-button-name='SHIFT_RIGHT_DAY']"}
  (Session info: headless chrome=93.0.4577.63)
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'apollo-test-2', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '5.8.0-50-generic', java.version: '1.8.0_292'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{networkConnectionEnabled=false, chrome={chromedriverVersion=93.0.4577.15 (660fc11082ba57405eca2e8c49c3e1af756fbfae-refs/branch-heads/4577@{#203}), userDataDir=/home/teamcity/build-agent-2/temp/buildTmp/.com.google.Chrome.JodGHj}, 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: 5b4be4f0d4e5e9c51e0c52affa36e4e5
*** Element info: {Using=xpath, value=//button[@data-button-name='SHIFT_RIGHT_DAY']}
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:185)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:120)
	at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)
	at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
	at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
	at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:356)
	at org.openqa.selenium.remote.RemoteWebDriver.findElementByXPath(RemoteWebDriver.java:458)
	at org.openqa.selenium.By$ByXPath.findElement(By.java:361)
	at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:348)
	at Pages.BasePage.getWebElementByXpath(BasePage.java:325)
	at CucumberTests.Transport.AdviceTransport.setAdviceWindowInSchedule(AdviceTransport.java:82)
	at ✽.Set advice window in schedule(file:Features/Atom/SK_API/SkApiTransportAdvice.feature:13)

And Fill advice form 000ms

And Click advice save button and wait for advice form to disappear 000ms

And Go to "TRANSPORT_TABLE" 000ms

And Go to transport details "TRANSPORT_ORDER" 000ms

Then Check are advice values equals 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 757ms

After Hooks.deleteTransportAfterTest() 554ms

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

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

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

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

And Set advice window in schedule 3s 427ms

And Fill advice form 20s 510ms

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

And Go to "TRANSPORT_TABLE" 454ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 150ms

After Hooks.deleteTransportAfterTest() 881ms

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

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

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

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

And Set advice window in schedule 3s 338ms

And Fill advice form 20s 355ms

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

And Go to "TRANSPORT_TABLE" 448ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 290ms

After Hooks.deleteTransportAfterTest() 830ms

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

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

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

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

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

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

And Set advice window in schedule 3s 500ms

And Fill advice form 19s 935ms

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

And Go to "TRANSPORT_TABLE" 538ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 181ms

After Hooks.deleteTransportAfterTest() 810ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "pskza1-carrier@qa.qa-test" and set token of apiUsername "super-admin-skz" 6s 511ms

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

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

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

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

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

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

And Set advice window in schedule 3s 377ms

And Fill advice form 20s 447ms

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

And Go to "TRANSPORT_TABLE" 534ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 2s 962ms

After Hooks.deleteTransportAfterTest() 905ms

View Feature SK Api - Advice transport

@deleteTransportAfterTest @cleanUserDetailsAfterTest

Scenario Outline Verify that advice data are saved properly

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

Hooks

Before Hooks.showScenarioName(Scenario) 001ms

Steps

Given Login as "swisskrono-tradesman@qa.qa-test" and set token of apiUsername "super-admin-skz" 8s 666ms

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

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

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

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

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

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

And Set advice window in schedule 3s 391ms

And Fill advice form 20s 594ms

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

And Go to "TRANSPORT_TABLE" 500ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 686ms

After Hooks.deleteTransportAfterTest() 789ms

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

Steps

Given Login as "lantmannen-admin" and set token of apiUsername "super-admin-lantmannen" 4s 462ms

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

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

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

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

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

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

When Reject status: Book of disinfection 203ms

And Check if reject date is visible 853ms

Then If user is login then logout 318ms

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

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

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

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

And Check if user got a mail 000ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 239ms

After Hooks.deleteTransportAfterTest() 709ms

After Hooks.rollbackWarehousesAccess() 795ms

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

And Prepare login page 437ms

And Click remind password button 277ms

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

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

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

And Extract password from mailgun mail 3s 925ms

And Reset password from link 1s 565ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 962ms

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

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

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

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

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

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

Then Save user details 1s 083ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 657ms

After Hooks.rollbackAddedAuthorities() 233ms

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

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

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

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

And Expand "other" notification section 2s 392ms

And Select all notifications in "other" section 290ms

Then Save user details 1s 447ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 887ms

After Hooks.rollbackAddedAuthorities() 156ms

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

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

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

When Login as "adama-buyer@qa.qa-test" 4s 883ms

And Go to "USERS_TAB" 1s 476ms

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

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

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

Then Save user details 1s 008ms

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

Hooks

After Hooks.cleanUserDetailsAfterTest() 650ms

After Hooks.rollbackAddedAuthorities() 255ms

View Feature UserAuthority

@rollbackAddedAuthorities @cleanUserDetailsAfterTest @TmsLink=A-7887

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

Hooks

Before Hooks.showScenarioName(Scenario) 000ms

Steps

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

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

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

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

And Go to "USERS_TAB" 1s 588ms

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

And Expand "GLUE_FACTORY" notification section 521ms

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

Then Save user details 1s 839ms

Hooks

After Hooks.cleanUserDetailsAfterTest() 1s 081ms

After Hooks.rollbackAddedAuthorities() 231ms

	Steps						Scenarios			Features
Tag	Passed	Failed	Skipped	Pending	Undefined	Total	Passed	Failed	Total	Duration	Status
@cleanUserDetailsAfterTest	427	2	12	0	0	441	43	2	45	52m 6s 645ms	Failed

Tag Report